The Amazon order processing steps, in order
An Amazon order passes through the same sequence every time. Knowing which state a stuck order is in tells you both the cause and which account-health metric is about to move.
An Amazon order runs: payment confirmed, order visible to you, stock allocated, handling time counting down, label generated, dispatch confirmed, handover scanned. Most problems are a stall between label generated and handover scanned, and that gap is what the late dispatch rate measures. Knowing the state names the cause faster than any report does.
- Seven states, always the same order, from payment to courier scan.
- The clock starts when the order is visible to you, not when you notice it.
- Confirming dispatch is a claim about reality, not a step that moves a parcel.
- Most stalls sit between label generated and handover scanned.
- Each stall feeds a specific metric, so the state tells you what is at risk.
Order processing sounds like one activity and is actually a chain of seven, each of which can fail differently. Sellers who can name the state an order is stuck in diagnose in seconds what otherwise takes an afternoon of clicking.
State one and two: payment confirmed, then visible to you
An order exists for the buyer before it exists for you. Amazon confirms payment, runs its own fraud and verification checks, and only then surfaces the order in your queue. That gap is usually minutes and can be longer, and it is why an order a buyer insists they placed is sometimes genuinely not in your view yet.
The important consequence is that your handling clock starts when the order becomes available to you, not when you happen to look. A seller who checks the queue twice a day has already spent part of the window before seeing the order, which is the single most common reason a comfortable-looking handling time is not comfortable in practice.
State three: stock allocated
You accept the order against stock you believe you hold. If the published quantity was wrong, this is where it surfaces, and the only honest options are to source the unit or to cancel. A cancellation here is what the cancellation rate counts, which makes this state an inventory accuracy checkpoint wearing a fulfilment name.
Sellers running the same stock across Amazon, Meesho and AJIO hit this state hardest, because three independently maintained quantities will oversell. A shared figure or a deliberate buffer is the structural answer, and both are cheaper than the metric damage.
State four: handling time counting down
Handling time is the promise you made on the listing, and it is now running. Weekends, holidays and your own daily cut-off all consume it invisibly: an order arriving at eight in the evening against a one-day promise may leave you a few working hours rather than a day.
This is the state where a problem is still cheap to fix. Once the window closes the damage is recorded; before it closes you can still prioritise, split a shipment or escalate a stock problem.
State five: label generated
The label is the shipping document and the barcode the courier scans. A label that will not generate usually means the shipment has not reached a state where Amazon will issue one, or a courier allocation is pending, and that is different from a label that generates and will not print.
Print at actual size. A scaled label still looks right to a human and fails a scanner, because scaling changes the bar widths, and the failure then arrives at handover rather than at the printer.
State six: dispatch confirmed
This is a claim, not an action. Confirming dispatch tells Amazon and the buyer that the parcel has left, and it stops the late dispatch clock. Nothing about it moves a box.
That gap between claim and reality is where the most damaging habit in Indian marketplace operations lives. Confirming early to protect the late dispatch rate produces tracking that shows movement which has not happened, buyers who see a stalled shipment, and complaints and A to Z claims that feed the order defect rate instead. You have traded a metric with a settings fix for one without.
State seven: handover scanned
The courier scans the parcel into their network and the order becomes genuinely in transit. Until this scan, the parcel exists only in your warehouse regardless of what the system says.
A gap between confirmed dispatch and first scan is the single most diagnostic number in your operation. If it is consistently hours, your flow is healthy. If it is consistently a day or more, you are confirming early, and the complaints that follow will not look like a dispatch problem when they arrive.
Where each stall shows up
A stall at stock allocation becomes a cancellation and feeds the cancellation rate. A stall during handling time becomes a late dispatch and feeds the late dispatch rate. A stall between confirmed dispatch and handover becomes a buyer complaint or an A to Z claim and feeds the order defect rate, which is the metric with the shortest path to deactivation.
That mapping is the practical value of knowing the states. A rising metric tells you something is wrong; the state tells you where, and the three remedies have nothing in common.
Where this sits in the rest of your Amazon operation
Robnu is read-only on Amazon today: orders, returns, payouts and inventory sync so you can see and reconcile them, and it cannot accept Amazon orders or make their labels. Order processing is live for AJIO and Meesho. Related reading:
Sources & further reading
- Amazon India, how to list your products the one publicly readable Amazon.in page that states listing figures: title 200 characters, images 500x500 or 1,000x1,000. Read 23 October 2026.
- Amazon India Seller University the public training hub. It serves, and it does not publish the account-health thresholds. Read 23 October 2026.
- Amazon listing and image style guides login-gated. It redirects to Amazon sign-in, so the detailed rules it holds are not quoted here and are described as market convention instead. Read 23 October 2026.
Not legal or tax advice. Amazon changes fees, windows and policies without notice, and the detailed style guides and account-health thresholds sit behind a Seller Central login, so any figure quoted here as convention is not Amazon-published. Check anything you plan to act on against your own Seller Central account first.
Questions sellers ask
Payment confirmed, order visible to you, stock allocated, handling time counting down, label generated, dispatch confirmed, handover scanned. The sequence is the same every time, which is what makes it useful: naming the state an order is stuck in identifies both the cause and the metric at risk.
Because Amazon confirms payment and runs its own verification checks before surfacing the order in your queue. The gap is usually minutes and can be longer. It also means your handling clock starts when the order becomes available to you, not when you next check the queue.
No. It is a claim that the parcel has left, and it stops the late dispatch clock without moving anything. Confirming before the parcel genuinely goes produces tracking showing movement that has not happened, which turns into buyer complaints and A to Z claims that feed the order defect rate.
The gap between confirmed dispatch and the courier's first scan. Consistently hours means a healthy flow. Consistently a day or more means you are confirming early, and the complaints that follow will not look like a dispatch problem by the time they arrive.
A stall at stock allocation becomes a cancellation and feeds the cancellation rate. A stall in handling time feeds the late dispatch rate. A stall between confirmed dispatch and handover feeds the order defect rate, which has the shortest path to deactivation. The three remedies share nothing.
Because weekends, holidays and your daily cut-off consume it invisibly. An order arriving in the evening against a one-day promise can leave a few working hours rather than a day, and orders keep arriving when the warehouse is shut.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Meesho Order Processing: From Order to Handover (2026)
Meesho order processing explained end to end: new order, accept, label and invoice, pack, ready to ship, manifest, courier pickup, delivery or RTO, and settlement. Learn each SLA stage and where sellers lose time and money.
Bulk order processing on Amazon without the mistakes
Processing Amazon orders in batches is where throughput comes from and where the expensive mistakes happen. What batches safely, what never should, and the checks that catch a bad batch early.
What goes in an Amazon description when you have A plus content
The description and A plus content overlap, and which one a buyer sees is not always your choice. What to put where, and what Amazon publishes about limits, which is nothing.
Amazon Section 3 deactivation and what the notice means
A Section 3 notice cites the Business Solutions Agreement rather than a specific policy, which is why it feels unanswerable. What it actually covers and how appeals are structured.
Amazon listing uploaded with no error and showing nowhere
A clean processing report does not mean a live listing. The six states an uploaded listing sits in while buyers cannot see it, and how to tell them apart.
Amazon flat file error codes and what each one means
The processing report is the only place Amazon explains a failed upload. How to read it, and why the warnings matter as much as the errors.
Meesho Order On Hold Meaning: Why an Order Is Held and What to Do
Meesho order on hold means Meesho paused the order before ready to ship, usually for a payment, address or risk check. Why, how long it lasts, and what to do.
Meesho Ready to Ship: What It Means and the Steps (2026)
Meesho Ready to Ship (RTS) explained: what the status means, how to move an order to RTS step by step, the dispatch SLA clock, penalties for missing it, and how accepted, RTS and handed over differ.