AJIO seller operations: the daily workflow, end to end.
From the moment an order drops to the manifest closing at 17:30 — eleven stages, a document pipeline, and an SLA window that doesn't negotiate. This guide walks you through the full daily AJIO ops flow, where it breaks manually, and how to run it on autopilot.
- AJIO daily ops is an 11-stage flow: from open order to closed manifest. Every stage has a document requirement and a sequence — doing stage 4 before stage 3 fails the batch.
- The 17:30 manifest cut-off is binary. Manifests submitted after it are treated as next-day dispatch and trigger SLA penalties, even if the courier picks up the same evening.
- Robnu connects via the Chrome extension — your AJIO password never leaves your computer — and runs the full pipeline autonomously, from batch acceptance to manifest closure.
What 'AJIO operations' actually covers
AJIO seller operations is the daily work between order placement and courier pickup. It is not just packing — it is a sequenced process with specific document requirements at each stage that AJIO enforces strictly.
The sequence matters because AJIO's portal gates each stage behind the previous one. You cannot generate a manifest without confirmed pickings. You cannot print a label without a confirmed order. Skipping or reordering stages fails the batch.
Downstream of daily ops — returns processing, deduction claims, and payment reconciliation — are separate workflows that Robnu also handles, but this guide focuses on the core daily dispatch flow.
Open order to closed manifest — the full pipeline
This is the sequence Robnu runs autonomously. When you do it manually, this is what your morning looks like — multiplied by however many orders are in the batch.
- 1Connect onceGuided wizard links AJIO or Meesho. Session self-heals — no daily re-login.
- 2Sync open ordersRobnu pulls every open order on schedule — no portal-tab juggling.
- 3Accept automaticallyQuantities confirmed against stock rules. All-or-nothing constraints handled for you.
- 4Generate labelsEvery label persisted and retried until safely stored — never lost.
- 5Packing slipsSlips rendered, batched, and indexed by SKU — printer-ready.
- 6InvoicesCustomer and vendor invoices generated into the document pipeline.
- 7Document pipelineSlip + invoices + manifest tied to each shipment. Audit-ready forever.
- 8Build the manifestManifest assembled from confirmed shipments and submitted on your closure policy.
- 9SLA watchdogHeadroom tracked per batch. Warned before the deadline, not fined after it.
- 10One email to youA single download link with every document for the run. Print and hand over.
- 11Reconcile the moneySettlement matched to the rupee against the closed manifest. Divergence flagged.
- Connect
- Sync
- Batch
- Confirm
- Upload
- List
- Slips
- Invoices
- Docs
- Manifest
- Closed
The three ways manual AJIO ops go wrong
Wrong document attached
Vendor invoice attached where customer invoice is required — or vice versa. AJIO rejects the order at the next stage. You discover this at 16:45, with 45 minutes to fix it and still close the manifest.
Missed manifest window
You finished packing at 17:25, started the manifest at 17:28, lost mobile signal or had a portal timeout. The cut-off passed. The whole batch is now next-day dispatch for SLA purposes.
Weight discrepancy at courier scan
Your label says 400g, the courier scan says 550g. The difference is deducted from your settlement as a weight charge. Multiplied across 20 orders a day, this is a significant invisible leak.
Running AJIO ops on autopilot with Robnu
Robnu connects to your AJIO account via the Chrome extension — your password stays in your browser. Once connected, the agentic pipeline reads your open order queue, processes every order through all 11 stages in the correct sequence, generates and attaches the right documents at each stage, and closes the manifest before 17:30.
The SLA-Watchdog runs alongside, monitoring headroom percentage per batch. If a batch is approaching the cut-off, the pipeline prioritises it above everything else.
Most sellers connect and run their first batch in under 30 minutes. No integration project, no API credentials, no data mapping. The extension reads your AJIO seller portal the same way you do — it just does it faster and without errors.
Catches a missed manifest before AJIO does
AJIO's deductions for missed manifests are immediate and silent — they appear in the next settlement without any notification. By then it's too late to do anything about it.
The SLA-Watchdog surfaces headroom percentage per batch in real time — so you can close the day's batches cleanly at 17:00 instead of discovering a breach at 18:00 when the settlement email lands.
When you run Robnu's autonomous pipeline, the watchdog feeds directly into batch prioritisation — the pipeline never lets a batch sit below a safe headroom threshold.
AJIO operations, answered
AJIO seller operations covers everything from the moment an order is placed to the point the manifest is closed and handed to the courier: accepting the order, generating the picking slip, printing labels, attaching customer and vendor invoices, packing, scheduling pickup, and closing the daily manifest by 17:30. Returns, claims, and payment reconciliation are downstream operations that start after dispatch.
The AJIO manifest is the daily shipment record that groups all orders dispatched in a given batch. It must be 'closed' — finalised and submitted — by 17:30 each day. A late or missing manifest triggers SLA penalties because AJIO uses the manifest to confirm pickup with the courier. Unclosed manifests are one of the most common and most avoidable sources of deductions.
Per order you need: a picking slip (printed from the AJIO portal), a customer invoice (with GST if applicable), a vendor invoice, and a shipping label. The document pipeline is strict about which document attaches at which stage — attaching the wrong invoice to the wrong order is a rejection reason.
17:30 is the daily manifest closure deadline. All orders in a batch must be confirmed, packed, and the manifest submitted before this time. A manifest submitted at 17:31 is treated as next-day dispatch for SLA purposes, even if the courier picks up the same evening. The cut-off is enforced at the portal level — the submit button closes.
The Robnu Chrome extension connects to your AJIO seller account via the browser session — your AJIO password never leaves your computer. Once connected, Robnu reads your order queue, runs the 11-stage pipeline on each batch, generates documents, and closes manifests autonomously within the Chrome extension's session.
Yes. Robnu handles the downstream operations after dispatch — return detection, deduction identification, and claims filing — as part of the same agentic pipeline. When a shipment returns, Robnu catches it, checks the reverse-freight charge against the correct weight and lane, and files the claim if the charge is wrong.
Most sellers run their first AJIO batch with Robnu in under 30 minutes after connecting the Chrome extension. The setup is connect → confirm access → run batch. There is no integration project, no API key, no data mapping.