Product Profiles

Stake Holders

• Derek Neumann
• Janet Carter <[email protected]>

Purpose

We're automating a painful, manual process.

Reaction Retails clients (Macys, Boomingdales, etc) will request a sampler kit, like 'Summer Sample 2022' or such. This request will come along with a list of items the want to look at including.

The Reaction Retail project manager will then send the manufacturers of those items (L'oreal, etc.) an email with a 'profile sheet'. These profile sheets are excel spreadsheets that the rep at the manufacturer is expected to fill out and return.

When the profile sheets are returned, the clinet reviews and selects the items to include.

Selected items can not be sold to other clients during a set amount of time.

The profile sheets are repeatedly sent for the same item, often annoying vendors who have just recently filled out the sheet for the exact item.

Solution

New module will be created.

Profile Projects (final name TBD) will be a top level menu item.

Profile Projects will have line items, called Profile Sheets, representing the items chosen by the client.

During the normal flow of production, the actual item can be associated with the Profile Sheet.

Vendor and their Contacts will need to be created.

We'll be creating a stand alone web app for vendors to fill out profile sheets

Workflow of using the module

PM checks for Vendor and Vendor contacts in slate. Creating them if they don't exist yet.

PM creates Profile Project

PM adds or imports Profile Sheets

Once Profile Project is confirmed correct, PM triggers email to vendor contacts for each Profile Sheet

Email contains a link to no-login form to the profile sheet on a seperate site

Vendor contact fills in the form for new items, or confirms details for existing items

Project manager for Profile Project is notified when Profile Sheets are completed

Project Managers are responsible for linking Profile sheets to item as they are created

Problems, Cencerns, and 'Gotchas'

When an item is selected by one client, it can't be sold to another client for that season, and must be marked as such.

If PMs don't link the items, or don't use consistent names, they might duplicate an item and violate the no double sale rule.

Timeline

Slate Internal

• [X] Backend Models / DB setup
• [X] Backend Views / API setup
• [X] Frontend Profile List View
• [X] Frontend Profile Detail view
• [X] Frontend Product SubList
• [X] Frontend Product Detail View
• [X] Backend Link Products to Variations
• [X] Frontend Link Products to Variations
• [ ] Backend Import Products to Profile from Variation
• [ ] Frontend Import Products to Profile from Variation
• [ ] Frontend Profile tab for Variations

Vendor Site

• [X] Basic site setup
• [X] Api Access
• [X] Styling / Appearence
• [X] Forms
• [X] Validation / Demo /Testing
• [ ] File Uploads
• [ ] Styling / Visual improvements