What this article covers
- what happens after stock arrives at a prep centre
- prep centre receiving process
- amazon prep centre workflow
- stock arrives prep centre
What Happens After Stock Arrives at a Prep Centre?
A delivery scan is not the end of the job. Once stock reaches a prep centre, the warehouse still has to confirm what landed, separate clean stock from problem stock, move the right units into prep and keep the seller clear on what is ready, what is on hold and what still needs a decision. That is where good operations feel calm and weak ones start turning delivered stock into a black box.
Delivered is only the handover. Good prep starts with clean receiving, clear hold logic and a visible route from check-in to dispatch.
Why it matters
A practical walkthrough of what should happen after stock arrives at a prep centre, from receiving and check-in through prep, short-term holding and dispatch into Amazon.
Next step
ATP supports supplier receiving, short-term holding, prep and dispatch so wholesale stock and staged shipments can keep moving without disappearing into a vague queue.
Delivery is only the handover
When stock shows delivered, the warehouse has only taken custody. It still needs to confirm references, check what physically landed and decide whether the stock can move straight into prep or needs holding first.
That distinction matters because delivered stock is not yet usable stock. Until receipt is clear, prep instructions are matched and exceptions are isolated, the seller is still operating against uncertainty.
The workflow should move through clear states
A solid prep operation does not hide everything inside one vague status. It moves stock through a few named stages so the seller can tell the difference between landed, checked-in, held, prepped and ready-to-dispatch inventory.
That matters most when inbound lands in pieces. Wholesale cartons, staged send-ins and short-term holding only stay manageable when each state is explicit.
| Stage | What should happen | Why sellers care |
|---|---|---|
| Delivered to warehouse | Carrier handover is confirmed and the stock enters receiving | Stops a delivery scan being mistaken for completed check-in |
| Checked in | Parcels or cartons are matched to the right sender, batch or supplier reference | Shows what has physically landed and what has not |
| In prep | Clean stock moves into labelling, packaging or shipment work | Tells the seller the stock is moving rather than waiting |
| On hold | Problem stock or incomplete inbound is separated with a named reason | Prevents one issue from contaminating the whole batch |
| Ready to dispatch | Prep is complete and the next outbound move is clear | Lets the seller act instead of chase updates |
Receiving should separate what has landed from what still needs chasing
For wholesale inbound, receiving is where supplier cartons are matched to the right purchase order or batch reference. For staged shipments, it is where early stock is logged without pretending the whole batch has already arrived.
A useful prep centre makes it obvious what is physically in the building, what is expected later and what is still unresolved. That is what allows short-term holding to support the workflow instead of obscuring it.
- Confirm the sender or supplier reference before anything is merged into stock already on site
- Separate fully received stock from part-received or still-outstanding inbound
- Keep held stock visible when the rest of a batch is still landing
- Flag anything that needs seller instruction before prep starts
Check-in is where shortage and condition issues should surface
Check-in should catch the awkward stuff early: short cartons, damaged outer boxes, wrong SKUs or stock that arrived in stages and needs holding. If those issues are found late, they slow the whole shipment and make supplier follow-up worse.
This matters especially for wholesale stock. If a case-pack arrives short and nobody notices until dispatch is being built, replenishment planning gets distorted for no good reason.
Prep should only start once the stock is identified cleanly
Prep is the execution stage, not the detective stage. By the time stock reaches the bench, the warehouse should already know what it is handling, what instructions apply and whether any units are blocked.
That keeps clean stock moving while any problem units stay on hold. When prep and investigation are blurred together, sellers lose both speed and visibility.
- Match prep instructions before labels, bagging or bundling start
- Keep clean stock moving instead of pausing an entire batch for one exception
- Use separate hold logic for damaged, short or still-incomplete inbound
- Make it obvious when stock is ready versus merely touched
Short-term holding only makes sense when the next move is already known
Short-term storage is useful when stock is waiting on a defined next step. Maybe the second half of a wholesale order has not landed yet. Maybe a staged Amazon shipment needs a brief pause before dispatch. In both cases, the hold supports movement rather than delaying it.
What does not work is passive storage with no clear trigger to move. If inventory is being held, the seller should know why, what it is waiting on and what will release it.
Exception handling is where trust is won or lost
Most prep centres sound organised when everything arrives exactly as expected. The real test is what happens when one parcel is missing, a supplier carton is short or half a staged batch lands without the rest.
A controlled workflow isolates the problem, keeps the clean stock visible and tells the seller what decision is needed next. A weak workflow lets the whole batch disappear into a vague queue.
| Issue | What a controlled workflow looks like | What a weak workflow looks like |
|---|---|---|
| Delivered but not checked in | Receiving search, reference check and a named status update | The seller is told to wait without knowing whether stock is missing or simply unprocessed |
| Short or damaged supplier stock | Problem units are separated and evidenced before the next action | The issue is found late after the batch has already moved forward |
| Split inbound for one shipment | Early units are held visibly until the batch can move cleanly | Partial deliveries disappear into generic storage with no clear release point |
Dispatch should feel like a controlled release, not a vanishing act
Once prep is complete, dispatch should be the cleanest part of the chain. The seller should know what is ready, what is still on hold and whether the stock is moving as one shipment or in stages.
That matters for both replenishment and cash flow. The cleaner the handoff from ready to dispatched, the easier it is to plan the next buy without second-guessing the warehouse.
What sellers should ask about post-delivery workflow
If the answers are specific, the workflow usually is too. If everything collapses into 'delivered' and 'done', that is usually where sellers start losing visibility.
- What status labels do you use between delivery and dispatch?
- How do you handle split supplier deliveries or staged inbound that cannot move immediately?
- What happens when part of a batch is clean and part needs to be held?
- How are shortages, damage or wrong stock surfaced before prep continues?
- When stock is held, how do you show what it is waiting for?
Need a prep workflow that stays clear after delivery?
ATP supports supplier receiving, short-term holding, prep and dispatch so wholesale stock and staged shipments can keep moving without disappearing into a vague queue.