Overview
If you supply Blinkit, Swiggy Instamart, Zepto, BigBasket Now, PharmEasy or Tata 1mg, orders don't come as a WhatsApp message — they land as a purchase order in the platform's vendor portal, against a clock, split across several distribution centres. Miss the acknowledge or dispatch deadline and the platform docks money off your next payout. The Quick Commerce Pack pulls those POs into Neev and runs the full flow: acknowledge the PO, allocate stock per DC, send the ASN, match the GRN, then reconcile the monthly settlement and dispute any deduction you don't agree with. One ledger of what was ordered, what shipped, what arrived, and what you actually got paid.
Paid Pack · locked
This article is part of the Quick-Commerce PackQuick-Commerce Pack
You can read the guide. The actions it describes unlock when an owner adds this Pack in Billing & entitlements.
This is a paid Pack and it is off by default. The Owner installs it from Settings; only after install do the Quick Commerce screens and actions become available. It is an operational Pack, so it sits on top of whatever vertical Pack you already run — Dairy Pack + Quick Commerce for a dairy supplying Blinkit, Pharma Pack + Quick Commerce for a distributor supplying PharmEasy.
Where to find it
After the Pack is installed, you get four screens under Quick Commerce in the sidebar, all on web (there is no mobile surface for this Pack):
- Purchase orders —
/quick-commerce/purchase-orders - ASN / GRN —
/quick-commerce/asn-grn - Settlements —
/quick-commerce/settlements - Deductions —
/quick-commerce/deductions
All four screens are owner-only. They live in a dedicated Quick Commerce shell — while you're inside Quick Commerce the sidebar shows only these four items.
Key concepts
Purchase order — the order from the platform. It moves through nine states: pending acknowledge → acknowledged → allocating → dispatching → GRN pending → GRN received → invoiced → closed, plus a cancelled exit. A PO can fan out across several DCs, each with its own ship-to address and expected delivery.
— what you send the platform before the truck arrives: how many units, on which vehicle, to which DC. One ASN per PO, with a per-DC breakdown.
— what the platform's DC actually booked in. Neev matches the GRN against your ASN; if the short-shipped and damaged units are within 2%, it auto-reconciles. Beyond that it lands as disputed for you to review.
Settlement — the periodic statement the platform pays against, typically net 30 or net 45. Gross, total deductions, and net amount, all settled monthly.
Deduction — money the platform takes off a settlement: short supply, expiry proximity, damaged, quality reject, SLA miss, platform fee, tax correction. Each one you can accept or dispute.
SKU mapping — the link between the platform's SKU code and your own product. Mapping is mandatory: until a PO line is mapped to a product, you can't allocate stock against it.
Common workflows
Role notes
This Pack is owner-only. Every one of the four screens is gated to the Owner role, and every action behind them — acknowledging POs, allocating stock, sending ASNs, reconciling GRNs and settlements, accepting or disputing deductions — runs only for the OWNER.
Pack powers are not handed out automatically. Even the OWNER does not hold Quick Commerce permissions until the Pack is installed; installing it is what binds them. No other role (Manager, Operator, Accountant, Warehouse, Delivery, Sales) sees these screens or can run any Quick Commerce action.
Tips & time-savers
The reconcile step auto-clears any GRN whose short and damaged units stay within 2% of the ASN, so you only have to look at the ones that fall outside tolerance.
Gotchas
A live note on scope: this Pack ships the PO → ASN → GRN → settlement → deduction flow across four screens. A fill-rate dashboard and contract-price tracking were planned but are roadmap, not in the product yet.