Ajio's seller flow is mature, opinionated, and full of small rules that aren't obvious from the documentation. After running this end-to-end every day for the last several months, here's what an early-stage seller should actually expect.
The 11 stages, decoded
The shape of the flow:
- Connect. You sign in to Ajio Seller Hub once. The Chrome extension does a token handshake — Robnu never sees your password.
- Sync open orders. The orders endpoint pulls confirmed orders into Robnu's queue. Latency is usually 30–90 seconds.
- Batch download. Item-level Excel. Ajio is strict about format here.
- Review and confirm quantity. You can confirm less than ordered if stock is short, but the upload is all-or-nothing — every line in the batch goes in, or none does.
- Upload confirmed Excel. One transaction. Failures are detailed in the response.
- List shipments. Ajio assigns the courier and the AWB.
- Generate packing slips. Strict format — barcode placement matters, font size matters.
- Accept invoices. Vendor and customer invoices flow into the document pipeline.
- Document pipeline. Slip + customer invoice + vendor invoice tied to one shipment record.
- Generate manifests. Built from confirmed shipments.
- Closure policy + SLA watchdog. Pick your closure mode; the watchdog watches the clock.
The unwritten rules
A few things the docs don't make obvious:
The all-or-nothing rule is real. If your confirmed-quantity batch has 47 lines and 1 fails validation, all 47 are rejected. This is by design — it prevents partial uploads. The implication: validate locally before upload. Robnu does this; if you're not on Robnu, you should still validate the Excel against your inventory before submitting.
Vendor invoice quantities drive the settlement. If your vendor invoice undercounts a SKU, the settlement matches the vendor invoice, not the actual shipment. The customer invoice can be correct and the slip can be correct — if the vendor invoice is short, the marketplace pays you short. This is the silent-loss vector #2 and it's painful.
Manifest closure is per-batch, not per-day. You can run two batches a day with two closures. Many sellers use this — morning batch closes at 13:00, evening batch closes at 17:30. The SLA window resets per batch.
Slip barcode placement is enforced by the courier scanner, not the marketplace. A slip that the marketplace accepts can still get bounced at the courier hub if the barcode is in the wrong corner. Use Robnu's slip template or a known-good template.
Where Ajio changed in 2025–2026
Two notable shifts since the seller hub redesigned:
- Tighter SLA accounting. What was a 24-hour window for some categories is now a same-day window for many. Check your specific category — the SLA dashboard in Seller Hub has the current values.
- Stricter return-evidence requirements. Quality disputes now require photo evidence from the buyer in some cases. This actually helps you — the dispute is more disprovable on your side, not less.
What to do this week
If you're new to Ajio:
- Get the Chrome extension installed.
- Connect your account via the token handshake.
- Run your first batch end-to-end — even a small one (3–5 orders) — to see all 11 stages.
- Turn the SLA watchdog defaults on. They're conservative; you can loosen them later.
If you've been on Ajio for a while:
- Audit your last 30 settlements for deductions you didn't dispute.
- Cross-reference deduction reasons with the four silent-loss vectors.
- Estimate how much was recoverable. That's roughly what the Protect pillar recovers.
Start free. The Process pillar is live for Ajio; the same operating model adapts to other marketplaces as they light up — Meesho and Amazon are live today, Flipkart and Myntra are coming.