Amazon AWD Inventory and Accounting: Batch Cost from PO to Sale

This is an Amazon seller that buys wholesale from an overseas supplier. Most of that stock goes first into Amazon Warehousing and Distribution, AWD. AWD then feeds FBA in small replenishment shipments, week after week. Spreadsheets lose the thread somewhere between the deposit and the last sale. So we will follow one purchase order all the way through.

It is 2,500 units of the Brightwater insulated water bottle, 32-ounce, in slate. Here is the story in five parts. First, one unit’s cost at every step, from supplier to customer. Second, the 100 shipments from AWD to FBA. Third, Amazon fees and an invoice that shows up late. Fourth, how many times the cash came back, and how fast.

And fifth, letting an AI assistant take on some of this work.

This is the purchase order. The line reads 500 boxes of five, which is 2,500 units. Quantity is always units; boxes are simply how the supplier and Amazon count stock. The supplier price is $7.20 a unit. Open the unit cost, and you see what each unit really cost on arrival. The supplier price comes first, $7.20.

Then each landed cost bill has its own line. Freight, prep, duty and Amazon’s AWD fee. Together they add $1.66, which brings the unit to $8.86. The bills themselves sit on the order. Freight from the forwarder, prep from the prep center, and duty from the customs broker. Amazon’s AWD processing fee arrived through the settlement and landed here by itself.

You can split a bill by cost, volume, weight, quantity or estimated duty. The cash went out in two steps. A 40% deposit on the day the order was placed. Then the balance, just before the goods shipped. Both payments carry their real dates, and that matters for cash return later. The whole order went to AWD as one inbound shipment of 500 boxes.

Amazon reported it received, matched to this purchase order. From here on, every unit carries the cost of this one order. When stock arrives, SKU.io records it as a cost layer. This layer is the stock that arrived at AWD. Its cost breakdown splits that into product, freight, customs duty and handling for the prep. Other is Amazon’s AWD processing fee, matched from the settlement.

Every unit in the layer carries exactly this cost: $8.86. As AWD ships units to FBA, each replenishment shipment draws its units from this layer. The usages list every one of those departures, all at the same unit cost. The layer empties out, shipment by shipment, until it is gone. Here is one of those FBA layers. It starts from the AWD cost, then adds the fees billed to that shipment.

Those fees come from Amazon’s settlement, matched to the shipment they were billed to. So the FBA cost is the AWD cost plus the transfer fees. Here that comes to $9.24 a unit. On auto-replenishment, Amazon says AWD pricing covers inbound placement, so you may see no fee at all, and the two costs match. Then a customer buys one on Amazon. The order’s profit tab shows the unit’s revenue, Amazon fees and cost, side by side. Expand the line, and it names the exact cost layer behind that unit.

That is one unit, traced from the supplier’s invoice to a customer’s doorstep.

Now the middle of the story, where most of the work hides. AWD replenished FBA in about 100 small shipments over four months. Each one shows what was expected and what Amazon received. SKU.io checks Amazon for new AWD and FBA shipments every 15 minutes. Settlements come in hourly, and AWD departures are matched once a day. If you want it now, refresh from Amazon yourself.

On the inbound shipment itself, Amazon counts in boxes as well as units. 500 boxes expected, 500 received, nothing pending. The last sync time shows exactly how fresh the numbers are. Across all 100 replenishment shipments, this one view lines up shipped, received and short. Most arrived complete. Three arrived short, and four are still in transit.

Short units stay on the books until Amazon finds the stock or pays for it. Here Amazon reimbursed one short shipment, $64.25. That payment counts as cash back on the original purchase order. Sometimes Amazon moves stock out of AWD without saying where it went. Those departures land here, unattributed. Here two shipments match exactly, so SKU.io asks instead of guessing.

Pick the FBA shipment each one fed, and its cost follows the units exactly. One click, and the departure drops off this list with its cost attached.

Amazon charges to move stock: freight and duty, AWD processing, placement and carrier fees. SKU.io reads those fees from the settlement report. When a fee names its shipment, SKU.io adds it to that batch’s cost by itself. The status tells you what happened. Created new bill means SKU.io found the shipment and booked the fee by itself. The link beside it opens that exact FBA shipment.

If it cannot match one, the fee waits in this column as awaiting a manual bill. Fees that name no shipment never get a link here. They are booked as Amazon fees, not batch cost, so nothing is counted twice. Now the hard case: the freight invoice that arrives after most units have sold. Enter it like any landed cost bill, straight from this purchase order. Before anything is applied, SKU.io shows you exactly where the money goes.

Pick the carrier, and add its invoice number. Describe the charge, and enter $1,000. File it under the freight category, so it lands in the batch as freight. The preview shows how the bill will be split across the order. Save it, and SKU.io checks your rule before it touches any cost. Your rule says landed cost bills wait for review, so SKU.io holds this one.

Open it, and the split is right there. The review shows the total, and where every dollar lands. $821.20 belongs to units that already sold. $178.80 belongs to stock still on hand. Every unit gets its true share: 40 cents each, across all 104 layers. Then you choose how to book it.

Restate puts each sold unit’s share back in the month it shipped. Prior periods are corrected, and every change is recorded. The impact tree shows the same bill, one cost layer at a time. Pick a layer, and you see its old and new unit cost. Every Amazon order that drew from it is listed, with its share of the bill. Under restate, each share lands in the month those units shipped.

Going forward still gives every single unit its true share of the bill. But the sold units’ share posts as one catch-up line this month. Closed months stay exactly as they were. It is what people usually mean by putting the bill on remaining stock. Loading it all onto stock on hand would cost about $2.24 a unit, not 40 cents. Their margins would look worse, and inventory would be overstated.

Here we choose going forward, apply it, and confirm the change. SKU.io re-costs every layer, sold and unsold, in a few seconds. Or set a rule once, per type of cost change. Restate while the grace window is open, then book later bills going forward. For most sellers, that rule is the right default. One more thing.

None of these choices changes the cash return on the purchase order. It counts cash, and the freight left the bank on the same date either way. Only the month the profit lands in moves.

Now the question that matters most. How many times did the cash in this order come back, and how fast? The cash flow tab answers both, under Cash SKU Return. The cash return multiple is 1.83x. The cash came back in full after 134 days. The chart marks the exact day the cash was back in full.

Where did the units go? 1,994 sold, 496 still owned, a handful lost. Unsold stock counts at cost, so the multiple never assumes sales that have not happened. Every dollar out and back has a date. Deposit, balance, freight and duty go out. Amazon payouts come back as each settlement is paid.

Amazon pools a product’s units, so it never names the batch behind a sale. SKU.io attributes each sale first in, first out, like its cost of goods. Before the next order, switch to forecast. Enter when you pay, how long production and transit take, and sales per day. Add the payout per unit and how long Amazon holds the money. SKU.io fills these in from this order’s history, so you start from real numbers.

Adjust any of them, and save the forecast with the order. Out comes a projected cash return multiple and projected days to cash return. Change sales per day or the payout per unit, and the projection moves with it. That is the number to decide on before you send the deposit. Across every purchase order, IRR Analytics ranks suppliers and products. Switch off realized only to include orders that are still selling.

Sort by multiple or by days to see where your cash works hardest. This is the list to read before the next reorder.

Everything you just saw is also available to an AI assistant, through our MCP server. Copy the URL into Claude, ChatGPT or Cursor, and sign in with OAuth. Each person connects as themselves, and sees only what their role allows. There are 39 tools, and most of them look things up. Assistants can look things up by default. Turn on changes only when you want them to write.

Even then, nothing can be deleted, voided or canceled through an assistant. Every call is logged: who asked, which app, which tool, and what it touched. Ask it to record a receipt, a landed cost bill or a supplier deposit. Then check its work here, line by line. One purchase order, followed from the first deposit to the last payout. Every unit’s cost, every shipment and every fee on the record.

That is SKU.io for Amazon sellers who ship through AWD. To see it with your own products, book a call.