How do consumer brands manage inventory and POs for Blinkit, Zepto and Instamart dark stores?

Updated:

Consumer brands keep Blinkit, Zepto and Swiggy Instamart dark stores stocked mainly by filling the platforms' purchase orders (POs). The platform usually raises POs per city from its own demand data, then moves stock to its dark stores. The brand checks each PO, ships the right SKUs, MRP and shelf life on time, and reconciles the goods receipt (GRN).

How stock reaches a dark store

  • Many brands supply quick-commerce platforms as vendors. The platform's buying team raises a purchase order (PO), usually for one of its city warehouses or hubs, and the platform then moves the stock to dark stores near shoppers.
  • Some platforms also run a seller (marketplace) model alongside the vendor model. Check your platform's current vendor terms before you plan.
  • So a brand rarely ships a single shopper's order to a quick-commerce platform. It ships cases against POs, and POs can arrive often, per city and per platform.
Marketplace order (seller ships)Quick-commerce vendor PO
What you ship againstOne shopper's orderA platform purchase order
Where it goesThe shopper's addressA platform warehouse or hub named on the PO
What you shipUsually one parcel per orderCases per SKU, in the pack size on the PO
What decides successOn-time dispatch and few returnsPO fill rate, on-time delivery and few rejections at inward

Glossary: dark store, quick commerce.

The PO cycle, step by step

  1. Check the PO. Read the SKU codes, quantities, MRP, EAN barcode, case pack, delivery location and PO expiry date. Match them against your item master before you accept the PO.
  2. Decide what you can fill. Compare each PO line with stock that is free to ship, after what other channels already need. Decide line by line: fill in full, fill partly, or decline, as the platform's terms allow.
  3. Allocate by shelf life. Platforms usually set a minimum remaining shelf life for stock arriving at their warehouses. Allocate the earliest-expiring stock that still meets that minimum (first-expiry-first-out, FEFO), and keep shorter-dated stock for channels that accept it.
  4. Pick and pack per PO. Pick against the PO, pack in the case pack it asks for, and label cases and documents the way the platform's vendor guidelines say.
  5. Book delivery and send documents. Many platform warehouses take deliveries by appointment. Send the invoice, and an advance shipping notice (ASN) where the platform asks for one, before the truck arrives.
  6. Reconcile the GRN. The platform's goods receipt note (GRN) records what it accepted. Match it against your invoice, and raise short, excess or rejected quantities while the evidence is fresh.
  7. Plan the next round. Use the sales and stock data the platform shares with vendors, where it does, to plan production and stock at your own warehouse before the next POs arrive.

Glossary: FIFO and FEFO, ASN, GRN.

Why stock gets rejected at inward

These are common reasons. Rules vary by platform.

  • Remaining shelf life is below the platform's minimum.
  • MRP, EAN or pack size doesn't match the PO.
  • More units arrive than the PO ordered.
  • Cases are damaged or wrongly labelled.
  • The truck misses its delivery appointment, or the PO expires before delivery.
  • The invoice or ASN is missing or doesn't match the shipment.

What to measure, per platform and city

  • PO fill rate: units accepted at the platform's GRN as a share of units ordered on the PO.
  • On-time delivery: deliveries made inside the agreed slot or before the PO expiry date.
  • Rejection rate at inward, with the reason for each rejection.
  • Lapsed POs: POs that expired before you delivered.
  • Days of cover at your own warehouse for your quick-commerce SKUs.

Checklist before the next PO cycle

  • An item master with each platform's SKU code, EAN, MRP and case pack.
  • Each platform's minimum shelf life, by category.
  • One owner who accepts or declines POs, and a cut-off time for doing it.
  • Invoice and ASN formats that each platform accepts.
  • One owner who reconciles GRNs and raises disputes.
  • A plan for stock the platform rejects or sends back.

How Fretron CommerceOS handles quick-commerce POs

Fretron CommerceOS is order, warehouse and shipping software for Indian consumer brands, running orders, warehouse and delivery on one live record beside your ERP. There is no prebuilt ERP connector. ERP data moves through Fretron's REST API, webhooks or CSV, with the mapping set up per customer.

  • Quick-commerce vendor POs from Blinkit and Zepto land as orders you can acknowledge and ship against. In Fretron CommerceOS, a brand accepts or rejects Blinkit, Zepto and Swiggy Instamart POs from its own panel, allocates partially against a bulk PO, and books the delivery slot.
  • Stock is tracked by batch and expiry date, and orders can be reserved first-expiry-first-out (FEFO) when they are allocated. Batch and expiry dates have to be recorded at receipt for FEFO to apply, expiry notices are shown in the app only, and short-dated stock can still be shipped.

More on quick-commerce fulfilment in Fretron CommerceOS →

Frequently asked questions

Do Blinkit, Zepto and Swiggy Instamart buy stock from brands?
Quick-commerce platforms usually buy stock from brands through vendor purchase orders (POs), so they need a PO flow rather than a shopping-cart connector. Some also run a seller model, so check your platform's current vendor terms.
Who decides how much stock goes to each dark store?
Usually the platform. It raises POs from its own demand data and moves stock from its warehouses to its dark stores. The brand's job is to fill those POs in full and on time, so the right SKUs stay in stock at the dark stores, and to plan from the sales data the platform shares.
What should we do when we can't fill a PO in full?
Decide line by line before the PO expires. Fill partly if the platform accepts partial supply, tell the platform's buyer what is short, and record the shortfall so your PO fill rate matches the platform's GRN.
Why does a platform warehouse reject stock at inward?
Common reasons are remaining shelf life below the platform's minimum, an MRP, EAN or pack size that doesn't match the PO, more units than ordered, damaged cases, and late or missing delivery documents. Rules vary by platform, so keep each one's current vendor guidelines to hand.
How do Blinkit and Zepto purchase orders work in Fretron CommerceOS?
Quick-commerce vendor POs from Blinkit and Zepto land as orders you can acknowledge and ship against. In Fretron CommerceOS, a brand accepts or rejects Blinkit, Zepto and Swiggy Instamart POs from its own panel, allocates partially against a bulk PO, and books the delivery slot.