Skip to content
Keyword Regex checks on catalog upload for both single and bulk upload(Keyword Variation Table) - A master list of Keywords, their variation and relevant tags saved and updated in mercury table by QC ops. This will act as a source for keyword based regex. 
(Supplier Authorisation Map) - A master list of all Brand_Name and sellers who are authorized to sell that brand will be saved in another mercury table - Common key between the Keyword variation Table will be the brand_name tableA mapping of sellers P0,P1, P2 & P3 will be stored in model table which will give flag at seller level (P0,P1)Model table name - gold.repeated_offenders_weekly. This table will be updated daily to flag all (P0 &P1) sellersDifferential Handling of keyword & supplier group Regex checks (nature)For any free text field or Brand related field (fields which have Brand in their name) in taxonomy or psm level apply keyword based regex based on keyword variation present in Keyword Variation Table. Regex should be the exact matches of the keyword present in the variation map (including lowercase & uppercase variation). This should not be a partial match since we have some very small brand keywords like “Mi” as brand name which can get flagged at later stages where it was only used inside of some broader word/sentences (for example - “Good looking mittal saree” keyword “mi” should not be partially matched with the sentence here. Regex check should happen for the key - i.e. Brand_Name and as well as they variation of it stored in the variation column of Keyword Variation Table.Validation Failure Cases: Keyword tags flagged for validation failure by regex checks during submission (for bulk upload - Template upload) then for that keyword variation, check its corresponding brand_name in Keyword Variation Table. (For example if l-a-k-m-e has a regex check with supplier provided input, look for its proper brand name in brand_name column - i.e. Lakme). Then check for supplier entry in Supplier Authorisation Map. If a particular supplier has an entry with brand_name (common key between Keyword Variation Table & Supplier Authorisation Map) then allow normal catalog submission - No change in submission flowIf for any keyword regex match the supplier entry is not present in Supplier Authorisation Map against the corresponding brand_name for the keyword variation, do a validation failure of the file. Single Upload - Throw error highlighting problematic fields with mention of problematic keywords used in that field. (Async on Submission)Bulk Upload - throw row level error writing error with problematic keywords in the error and attribute names with which error was associated with. (Async on Submission)Details on Single and Bulk flow here - Warning Nudge Cases: If any keyword is for warning flagged by regex checks during submission (for bulk upload - Template upload) then for that keyword variation, check its corresponding brand_name in Keyword Variation Table. (For example if l-a-k-m-e has a regex check with supplier provided input, look for its proper brand name in brand_name column - i.e. Lakme). Then check for supplier entry in Supplier Authorisation Map. If a particular supplier has an entry with brand_name (common key between Keyword Variation Table & Supplier Authorisation Map) then allow normal catalog submission - No change in submission flowIf for any keyword regex match the supplier entry is not present in Supplier Authorisation Map against the corresponding brand_name for the keyword variation, throw a warning nudge at upload/submission time. Details on flow here - On all cases where submission is happening fail hygiene check (make product value=0 by default, reactivation or flag change will be done by QC team on uploading eligible catalogs, Go live will pick these catalogs for activation once their hygiene checks are changed)
Validation Failed CasesPrompt with summary of errors highlightedRedirectionTo go back to upload form correct errors (error should be at field level) - Not NeededOption to report a error (if its not relevant) - TBDKeep catalog in draft and proceed to support section for Brand Auth request Warning CasesTrigger warning prompt screen on submission with summary of errors highlightedRedirectionsTo go back to upload form correct errors (error should be at field level) - Not NeededOption to report a error (if its not relevant) - TBDSubmit catalog and proceed to support section for Brand Auth requestSubmit Catalog AnywaysIf file has both warning & validation fail case - show warning state with an option to download or upload file or move ahead for submitting it anywaysOn downloading warning file both warning error and validation error should get clubbed at row level.On submission/re-submissionIf File has no Validation or Warning error -it becomes QC pass. If File has only validation error - change state to QC error If File only has warning error - Take final submissionIf File only has both again - Follow normal QC error route (existing Behaviour)If file only has warning cases then- change state to warning state and option to download file or move ahead for submitting it anyways (final submission)On downloading warning file both warning error are clubbed at row level.On correction If there is warning & validation error - Change to QC errorif there is only warning case - Take final submissionif there is only QC error - change state to QC error
Design brief
Flow Debrief
V1 Proposed Upload Flow Compliance Gating
Cases where we want to throw warning v/s do validation failure
Catalog Upload - Backend Flow detailing
Broken link
Broken link
Alternate Simplified (Preferred Approach) - To be Executed via “Supplier Attribute”
Priority order of Warning Nudge, Validation Failure & Submission behaviour - FE/Design
Approach 2 (Preferred) - Validate Warning cases (Happens in Sync for Single & Mweb) and Validation fail cases (Async)
Single
Bulk
(In both cases non problematic products are submitted automatically on 1st submission)
Design Brief
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.