Explore

Brand registrations

Objective -

Instrumenting seller to brand mapping in internal DB with authorization doc mapping as well as details on expiry date

Use this instrumentation across processes -

Restricting brand dropdown at seller cross category level

Using this mapping for a reactivation CRON as and when seller gets authorised - Not part of current scope

Make brands a mandatory attribute across categories for Malls sellers (Attribute ID - 93, TRUE)

Current process walkthrough -

Sellers reach out for brand registration by filling the form in support section here -

https://supplier.meesho.com/panel/v3/new/payouts/j2dlq/support/2/67/create⁠

⁠

Cataloging ops team vets the certificate and adds the mapping to -

⁠

https://docs.google.com/spreadsheets/d/1fAAoFuz6zRkAE1e9FItdcKVyf4-csuU86U9YNrY-4pI/edit?pli=1#gid=519066210⁠

⁠

Documents at seller cross brand level maintained in a different sheet -

https://docs.google.com/spreadsheets/d/1iPZjBY7sP6ykTFDhnc5BSg3-2JO6A1G4m_3qO0oFmOo/edit#gid=0⁠

⁠

The updated sellers are manually fed into sheet based Suraksha list and is then used across processes

Instrumentation change details -

Create an admin uploader to upload new brand authorisation or TMC from seller

The uploader would have the following details -

Brand name - Drop-down selected from existing Suraksha + All taxonomy brand list

TMC / Brand VAL authorisation attachment

Type of document, Allowed values -

Authorisation letter

Trademark certificate

Invoice

Status - Approved / Rejected

Done when entry is created

Rejection reason - Dropdown

Document expiry date - 2034-Jan-1 by default

QC team should be able to navigate this config, search for a seller and edit above data at a brand level for any changes post first time ingestion - Support for seller / brand name master filters

The data from this uploader would flow into a prism presto table which records -

Supplier ID

Brand name

Document type

Image link for attached document

Verification status - Verified / in QC / Rejected

Rejection reason

Expiry date

5 to check if comma separated seller IDs can be mapped against the brand in existing Suraksha list

Sellers will still raise tickets through the same route of support

New brand addition would use the same existing flow

We would also want to backfill existing data stored in google sheets attached in current process walkthrough while setting up the new repo

Restricting brand as an attribute -

The change will be rolled for the following taxonomy fields -

Brand

Brands

Trends

Originals

For these cases, we have to make an update such that dropdown values have -

Only brands having authorisation which are present in Suraksha list

All brands not part of Suraksha

This change will make brand dropdown a seller cross category property

Ensuring brand attribute mandatory for malls sellers -

This update will ensure we ask for the following taxonomy fields mandatorily from Malls sellers -

Brand

Brands

Trends

Originals

We’d make these fields mandatory across upload flow (Single / Bulk / Mweb for malls sellers)

Malls seller - Attribute ID 93 - TRUE

Design high level mock -

⁠

IMG_6753.jpg

⁠

Filters -

Search by supplier ID - Ability to check for seller’s mapped brands by filtering on seller ID

Filter brand - Dropdown of all Suraksha, possible to do a string match search

Adding a new seller-brand mapping -

Option 1 - Open a modal which records all elements in below paginated list like -

Supplier ID → Brand name (Dropdown) → Document link (Opens on click) → Document type (Dropdown) → Status (Dropdown) → Rejection reason (Dropdown) → Expiry date

For every submission, all these fields would be mandatory, except

Rejection reason - Only needed if status - Rejected

Expiry date would also be non mandatory and would assume the default value in case of no input

Option 2 - Have an add entry button inside the common navigation table, opens a row on new authorisation entry

Navigating / Editing existing mappings -

All existing mappings would be visible in a table format with an save button at the end

Users will be able to click on any column of a row entry and make changes to it, post changes they’ll be required to click on save

For deleting a seller - brand mapping, status can be changed to rejected and then entry saved

Net Seller - Authorisation mappings in system - 1503

Unique seller count - 900 (Max 1 seller could have up to 600 brands tagged as per current data, we can make it scalable upto 1000 brands)

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.