Overview
When Blinkit, Zepto, Swiggy Instamart or any quick-commerce platform pays you, they almost never pay the full PO. They chop off money for short supply, damages, expiry, SLA misses, platform fees and more — line by line, on every settlement. The Deductions page is where you fight back: each debit note lands here, and you decide whether to take the hit or push back with proof.
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 page is part of the Quick Commerce Pack. The Owner installs the Pack from billing; until then the screen does not show.
Where to find it
Web only. Go to Quick Commerce → Deductions — canonical route /quick-commerce/deductions. The Quick Commerce sidebar group shows for the Owner only, so this is an owner's screen.
A deduction row links straight to the settlement it came from. From the Settlements page you can deep-link into Deductions already filtered to one settlement — the filter rides in the page URL, so the link always opens the right slice.
Key concepts
- Deduction — one line of money the platform held back inside a settlement. It carries an amount, a reason, and a dispute state. A deduction is usually tied to one PO, but scheme-adjustment deductions sit on the settlement with no PO link.
- Canonical reason code — Neev's own clean reason for the cut. Every platform names its reasons differently; the Blinkit adapter maps that raw platform reason onto one of eight canonical codes: short supply, expiry proximity, damaged, quality reject, SLA miss, platform fee, tax correction, other. Both the raw code and the canonical code are kept.
- Dispute state — where the deduction sits in its lifecycle: Pending review (just landed, nothing done), Disputed (you pushed back), Resolved (settled in your favour, full or partial), Rejected (dispute lost, deduction stands), Closed (you accepted it without disputing). Resolved, Rejected and Closed are final — you can't reopen them.
Reason codes show as colour-coded tags: pink for money-loss reasons (short supply, damaged, quality reject, expiry proximity), black for finance fees (platform fee, tax correction), and a plain tag for ops reasons (SLA miss, other).
Common workflows
A Partial resolution returns part of the deduction — you enter the resolved amount and it must land between zero and the original deduction amount. Platform reversed returns the full amount. Tenant accepted returns nothing and marks the dispute Rejected.
Role notes
Deductions is an Owner-only screen. The Owner holds every non-Pack permission in Neev, but Quick Commerce powers are different — they bind to the Owner only once the Quick Commerce Pack is installed. No Pack, no Deductions page.
There is no separate accountant, manager or operator access here in this release: working deductions — accept, dispute, resolve — sits entirely with the Owner. Because the whole screen is Owner-gated, a who-can-do-what grid would have a single row, so it is left out.
The last-Owner guard stops you removing the final Owner from the business. Since Deductions is Owner-only, keep at least one active Owner who can install the Pack and work the debit notes, or the screen has nobody to drive it.
Tips & time-savers
On the Settlements page, open a settlement and follow its deductions link — Deductions opens already filtered to that settlement ID. The filter is carried in the page URL, so you can bookmark or WhatsApp the link to yourself and reopen the exact same slice later. No re-filtering by hand.
Use the reason filter to triage fast: filter to short supply or damaged (the pink money-loss tags) first — those are the cuts most worth disputing. Leave platform fee and tax correction (the black finance tags) for last; they rarely move.
When you dispute, write the numbers in the reason box — dispatched units, received units, GRN reference. The platform reads that text, so concrete counts win disputes faster than "this is wrong".
Gotchas
Once a deduction is Closed (you accepted it), Resolved or Rejected, it can't be reopened — those states are terminal. Don't hit Accept to "clear" a row you actually want to fight; that closes it for good. Dispute first if there's any chance you're right.
The Dispute box captures your written reason only — there is no file attachment in this release. Don't wait around for an upload button; put your dispatch photo references and GRN numbers into the reason text instead. File upload comes in a later release.
One more: you can only Dispute or Accept a deduction that's still in Pending review, and you can only Resolve one that's in Disputed. A deduction that's already terminal shows no actions — that's expected, not a bug.