Mocking downstream responses (e.g., order platform, manifest) to avoid serviceability failures while testing
Processing Queue Segregation for OMS Clients -
Resolved P99 latency spikes for Unicommerce (caused by inactive seller requests) during MBS sale. Fix deployed before the Diwali sale to isolate queue processing per client
Team was able to pitch in and help multiple brands facing order processing failures during MBS due to RTS breach by enabling panel processing (e.g. Mamaearth)
Team was able to close deployment for persisting brand logos in taxonomy, task transitioned to F&E logistics
Decent collaboration with discovery to close solutioning for A2C / BN block on PDP for CF catalogs
What did not go well -
Limited Cross-Pod Bandwidth from F&E causing delays. Key impact areas -
Incorporating brand authenticity checks in claims approval
SG Bandwidth - Additional support for recurring hygiene issues -
Improving seller address update mechanisms
Preventing premature catalog activation by avoiding inventory carryover during PSM replication
Business/Category Support -
Sourcing brand authenticity images for reverse QC and claims approval
Prioritising OMS client onboarding based on the presence of focus/anchor brands
Analytics: Assistance in setting up metric dashboards.
Deprioritisation alignment -
Onboarding omni channels - In-house development for omni-channel onboarding requires ~8-10 sprints. To expedite, Browntape’s OMS was evaluated as a 3P solution
Context -
Vmart fulfills online orders via franchisee outlets with lean inventory, requiring order hopping if SKUs go out of stock due to offline sales. Browntape can handle order-hopping logic with updates on Meesho's end
Suggested flow changes -
Vmart operates under a single seller account consolidating all store listings.
Orders placed on this account are split into sub-shipments by vSKU and quantity (~60% of orders need multi-outlet fulfillment).
Browntape maps APOBs, allocates sub-shipments to outlets, and provides dispatch, return, and GSTIN details.
Meesho manifests orders with Browntape-provided data. Returns go to designated addresses; RTOs return to dispatching stores.
For out-of-stock scenarios, Browntape reallocates to another store until SLA is breached.
Effort view -
The changes requires changes across multiple pods -
Sub-shipment breakout - Changes in Transact pod (effort TBD)
Manifestation & order hopping - ~6 sprints across order platforms, logistics pods
Invoicing flow changes - Effort TBD
Build scalability - Browntap based solution works for specific brands (e.g - Vmart, Manyavar, Fossil) but isn’t compatible with brands using their own OMS (e.g., Pantaloons).
Defining metrics for Brand experience
Focus brands onboarded
OMS clients onboarded
Order fulfilment rate
Order acceptance rate w.r.t marketplace
Order manifestation rate w.r.t. marketplace
Net order fulfilment w.r.t. marketplace
Brand N/G
N/G as compared to marketplace
Brand claim %
Brand claim approval rate
Want to print your doc? This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (