07 · Packs
Paid Pack

ASN dispatch & GRN reconciliation

Send the platform an Advance Shipment Notice, then reconcile their Goods Receipt Note against it — auto-reconcile within tolerance, auto-dispute beyond it, with state machines driving the parent PO forward.

5 min read · updated 28/05/2026

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.

Overview

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.

When you ship to Blinkit, Zepto, Swiggy Instamart or PharmEasy, two documents settle the money: the you send before the truck rolls, and the the platform's dark store cuts when it counts what arrived. If those two numbers don't match, you get short-paid. This screen sends the ASN, pulls back the GRN, and tells you in one glance whether the counts line up or whether you need to fight a deduction.

To turn it on, the Owner installs the Quick Commerce Pack. Until it's installed nobody on the tenant — even the Owner — holds the Pack permissions, so the screen stays locked.

Where to find it

Web only. Open Quick Commerce → ASN & GRN at /quick-commerce/asn-grn. It's a single page with three tabs:

  • ASNs — every shipment notice, with dispatch / submit / reject actions.
  • GRNs — every receipt note from the platform, with reconcile / mark-disputed actions.
  • Create — pick a purchase order and assemble a new ASN.

The whole Quick Commerce section sits in the Owner sidebar only.

Key concepts

  • — Advance Shipment Notice. One ASN per PO. A multi-DC PO ships one consolidated ASN carrying a per-DC breakdown — how many units go to each distribution centre.
  • — Goods Receipt Note. The platform's count of what actually landed, split into units received, short-shipped, damaged and expiry-rejected.
  • Per-DC breakdown — the line that says DC BLR-WH1 gets 240 units, DC DEL-WH3 gets 160. Your ASN breakdown must equal the PO line totals for each DC, or it won't save.
  • Reconciliation tolerance — Neev compares ASN units against GRN units. Variance is (ASN − GRN) ÷ ASN × 100. Inside ±2% it auto-reconciles. Beyond ±2% it auto-disputes.

Common workflows

1
Create the ASN

Open the Create tab, pick a PO (only POs in allocating or dispatching show up), give it an ASN number, optionally add vehicle no, driver name and phone. Each DC row pre-fills with its PO line total — leave it as is. The breakdown must equal the PO line total for every DC, so the pre-filled value is the only one that saves; anything else is rejected with a mismatch error. Hit Create. The ASN lands in draft.

2
Mark it dispatched

On the ASNs tab, hit Dispatch on the draft. Enter total units dispatched — it must equal the per-DC breakdown sum or you'll get a mismatch error. This stamps the dispatch time and moves the parent PO from allocating to dispatching.

3
Submit to the platform

Hit Submit. Neev pushes the ASN to the platform over the channel on the account. Submit is safe to retry — if a submitted ASN already went out, hitting it again returns the same record instead of double-sending.

4
Reconcile the GRN

Once the GRN arrives, open the GRNs tab and hit Reconcile. Within ±2% variance it flips to reconciled on its own. Beyond ±2% it flips to disputed and stamps the variance percent as the reason.

5
Push back on a bad count

If a count is wrong even though it's inside tolerance, hit Mark disputed, write the reason (e.g. "vehicle showed 240 units, GRN shows 200 — short by 40, no damage at gate"), and it moves to disputed regardless of the tolerance maths.

Role notes

Only Owner reaches this screen — Quick Commerce is an Owner-only Pack section. The Owner can create, dispatch, submit and reject ASNs, and reconcile or dispute GRNs. No other role has the Quick Commerce permissions, so there's no who-can-do-what grid here: it's the Owner or no one.

One real limit even on the Owner: Pack permissions don't exist until the Pack is installed. The Owner's all-powers binding deliberately skips Pack keys, so an Owner on a tenant without the Quick Commerce Pack cannot open this screen at all.

Tips & time-savers

Tip
Each DC row on the Create tab pre-fills with that DC's PO line total — that pre-filled number is exactly what the ASN needs, so leave every box untouched and just hit Create. The breakdown has to equal the PO total for each DC; typing a different number only earns a mismatch error.

Submit is idempotent. If the network drops mid-submit, hit Submit again — an already-sent ASN comes straight back instead of going out twice.

Gotchas

Warning
Reconcile is not "approve" — it's a check. If the GRN count is more than 2% under your ASN, hitting Reconcile flips the GRN straight to disputed, not reconciled, and disputed is the end of the line. Once a GRN is disputed you can't pull it back to reconciled; it's a one-way door.

Two more dead-ends to know:

  • A GRN can never report more units than the ASN sent. If the platform's count overshoots, Neev rejects it outright as an overstated receipt — fix the ASN side, don't force the GRN.
  • Acknowledged and rejected ASNs are terminal. A rejected ASN can't be revived; re-draft a fresh one against the PO (which is why a dispatching PO can still take a new ASN).

Related

Related
Purchase orders & webhook intakeQuick Commerce Pack overview