07 · Packs
Paid Pack

Purchase orders & webhook intake

How a platform PO lands — Blinkit webhook → HMAC verify → adapter Zod-parse → cross-tenant vendor resolve → canonical multi-DC PO with SKU resolution and SLA deadlines, then the OWNER's acknowledge/allocate/cancel flow.

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

When you supply Blinkit, the order does not arrive as a WhatsApp message — it arrives as a webhook from their system, often split across many dark stores, on a clock. Neev catches that webhook, checks it is genuinely from the platform, and turns it into a clean purchase order you can act on: one PO header, the distribution centres it ships to, and every line with your own product matched in. No retyping, no missed acknowledgement deadline.

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 part of the Quick Commerce Pack. Your Owner installs the Pack to switch it on — until then these screens and powers are not available to anyone, including the Owner.

Where to find it

Web only. Quick Commerce → Purchase Orders at /quick-commerce/purchase-orders. The Quick Commerce section sits in the sidebar for the Owner only.

The PO inbox opens with four number tiles — Pending Ack, Allocating, Dispatching, and Open Value (the rupee total of every PO still in play, e.g.

Open value
₹25,00,000
). Below that is the PO table with platform and state filters. Click any row to open the detail drawer (Overview / DCs / Lines / Allocations / ASNs / GRNs).

Key concepts

  • A webhook is the platform pushing the order to Neev automatically. Neev verifies the message is really from Blinkit and matches it to your vendor account before it creates anything.
  • Multi-DC PO — one PO can ship to many dark stores. Each distribution centre carries its own address and expected-delivery time; lines are scoped to the DC they belong to. One Blinkit PO for 500L of milk can fan out across 30 dark stores.
  • SKU resolution — each platform SKU code on the PO is matched to your product. A code Neev has never seen lands the line unmapped (tinted pink in the Lines tab) but the PO is still accepted — you map it later from the owner tray.
  • SLA deadlines — every PO gets an acknowledge deadline and an ASN deadline, computed when it lands. Admin-entered POs without webhook context fall back to 30-min ack / 24-hr ASN. The inbox shows a live countdown chip per PO that changes colour as the deadline nears.
  • PO states — pending_ack → acknowledged → allocating → dispatching → grn_pending → grn_received → invoiced → closed. A PO can also be cancelled.

Common workflows

1
Acknowledge a new PO
A fresh webhook PO sits in pending_ack. Open Purchase Orders, hit Ack on the row. It moves to acknowledged — this is what stops the SLA clock.
2
Fix the line quantity or price (before allocating)
In pending_ack or acknowledged, you can still correct a line's quantity or unit price. Once you start allocating, lines lock.
3
Start allocating stock
Hit Allocate on an acknowledged PO to move it to allocating. Stock is then committed against each line from your inventory batches, and Neev blocks any commitment beyond the quantity ordered.
4
Cancel a PO
If a PO cannot be fulfilled, hit Cancel, type a clear reason, and confirm. Cancellation is only available before dispatch.
5
Check an unmapped line
Open the row, go to the Lines tab. Pink-tinted lines read "Unmapped — needs owner-tray confirmation." Map the SKU and the line resolves to your product.

Role notes

These screens are Owner-only. The Owner holds every Pack permission once the Quick Commerce Pack is installed — acknowledge, allocate, cancel, edit lines, and view the full PO drawer. No other role (Manager, Operator, Sales, Warehouse, Delivery, Accountant) sees the Quick Commerce section at all, and Pack permissions are never auto-granted before the Pack is installed.

Tips & time-savers

Tip
Work the Pending Ack tile first, sorted by the SLA countdown chip. The PO closest to its acknowledge deadline is the one that costs you a fill-rate penalty if you miss it — clear those before the comfortable ones.

A brand-new platform SKU never blocks you. The line lands unmapped, the PO is still accepted, and you acknowledge on time — then map the SKU from the owner tray when you have a minute. You never have to make the platform re-send an order over one new code.

Gotchas

Warning
Cancelling a PO is permanent and you must type a reason. It is only allowed before dispatch — once a PO reaches dispatching or later, the Cancel button is gone, because the shipment is already in motion on the platform side.

Line edits also have a cutoff: you can change a line's quantity or price only while the PO is in pending_ack or acknowledged. The moment you move it to allocating, lines lock — fix the numbers before you start committing stock.

Related

Related
Quick Commerce Pack overviewASN dispatch & GRN reconciliation