Inbound Pipeline

Open it from /inventory → Inbound Pipeline. The Inbound Pipeline is the finished-goods view of stock between your manufacturer and an Amazon warehouse, with one column for each lot. For the full shipment register — including AWD transfers and AWD → external (MCD) orders — use Shipments.

What a lot is

The first columns are not lots: they are the channel’s current Sellable stock and, on Amazon, the shared AWD (pool). Every column after those is an individual lot — a purchase order, a shipment, or an AWD lot — carrying:

• a pickup date (ETD), and
• an estimated arrival (ETA).

One column per lot, not one column for “inbound”. The Counted badge identifies shipments included in planning.

The lot columns are grouped by stage:

Stage	What it holds
AWD (pool)	Stock already in the shared AWD pool.
Recently Arrived	Shipments that have arrived. History only: they are already in the destination’s stock and are not added again.
In Transit	App shipments that are approved, dispatched or in transit, and marketplace shipments that are not matched yet.
Processed Stock	Goods the factory has produced that are not on a shipment yet.
In Production	Purchase orders that are still being produced.
Cancelled	Cancelled shipments, kept visible so you can review them.

Reading a lot column

The header carries the identifier, the dates, and the shipment’s status — for example Approved (awaiting dispatch), Dispatched or In transit. A separate badge answers one question: does the projection count this lot?

Badge	What it means
Counted	Already added to the projection grid in its arrival week.
Not counted	A marketplace shipment that is not matched to a lot in the App. Its quantities are shown for review but the column is not added to the projection until you match it.
Receiving	At the warehouse and being received. The cells show only the units not received yet; the rest is already in stock.
Already in stock	Arrived and already part of on-hand inventory, so it is not added a second time.
Received short	The warehouse finished receiving with fewer units than were shipped. The received units are in stock; on Amazon the shortfall is listed under Inventory issues on Order Planning.
Closed, not received	The marketplace closed the shipment before receiving anything. It still counts as inbound — check with the marketplace.
Cancelled	Cancelled, so it is left out of the projection.

Open a lot to verify the dates and match that make it count in the projection.

The badge is about whether the projection counts the lot, not where the goods are. An Amazon shipment sent directly to FBA and not matched yet still counts: the units it still expects to receive are already in FBA stock. An Amazon shipment to AWD does not. Until it is matched, the projection leaves it out, so the grid shows a shortage you may have already solved. The page tells you how many Amazon shipments, AWD or direct to FBA, are waiting with “Amazon inbound shipments (AWD or direct to FBA) are not being tracked.”

On the Walmart and TikTok tabs the marketplace’s own inbound shipments appear the same way, and Match lot pairs them with a plan.

Match a shipment

Choose Match lot on a Not counted column. The App shows what is on the shipment and asks what it corresponds to:

• Pair with a shipment plan — pick the plan that ordered these goods; the App marks a plan that matches every SKU. Pair uses the plan quantities, never more than the shipment holds, and only shows a difference rather than changing anything. Only plan lines that already have a PO can be paired.
• A lot already in the App — under Other ways to link this shipment, select that lot and choose Link.
• Nothing yet — it predates the App — Add to inventory plan creates a standalone lot from the Amazon manifest so the quantity counts, without creating a PO or new demand. When no plan matches the shipment, this is the first option the App offers, as Add to inventory.

A paired shipment reads Paired with a plan; Undo pairing returns the goods to the plan until the shipment leaves. A lot created from the manifest reads Included in inventory plan, and Manage tracking reviews or unlinks it. A shipment linked to an existing lot reads Linked.

The cells beneath are the boxes of each Sales SKU in that lot, so you can see which pack sizes it is carrying — which is what decides whether it relieves the row that is short.

Under the grid, Total units and CBM give each column’s total for the whole shipment, including SKUs hidden by search or filters. How to read in the toolbar explains the columns, the date symbols and the badges.

A healthy AWD figure against a thin FBA one is a replenishment problem, not a supply one. The pipeline does not list MCD orders; those are maintained on the Shipments page.

How it connects to the projection

The estimated arrival is what puts the marked week in the stock projection. Open a projection cell that shows units arriving and you can follow it to the lot they came from.

That link is the point of holding the chain in one place. A number in the grid is always traceable to a shipment that exists, with a date somebody committed to.

Keeping it accurate

A lot that slips and is not updated makes every downstream week optimistic — the projection will show cover you do not have, and Order Planning will not raise a proposal you need.

When a date moves, move it here: select the ETD or ETA in a lot’s header to change it, or Use estimate to go back to the calculated date. A plan still in production can change both; a shipment on its way changes only its ETA. Everything downstream re-reads from it. Use the Shipments register to update or inspect marketplace tracking details such as AGL IDs and received-unit status.

Considerations

• Estimated arrival is an estimate. Treat the week it lands as approximate and keep the buffer doing the work it exists to do.
• A lot matched to the wrong shipment is worse than an unmatched one, because it looks correct.