---
title: "How to manage wholesale purchase orders for FBA"
description: "Track an Amazon wholesale purchase order through five states — draft, submitted, confirmed, shipped, received — and reconcile it against the supplier invoice."
question: "How should I track purchase orders for Amazon wholesale?"
cluster: wholesale-operations
published: 2026-08-21
updated: 2026-08-21
tags: [purchase-orders, wholesale-operations, cost-accounting]
related: [landed-cost-for-amazon-wholesale, allocate-freight-across-po-lines, best-purchase-order-software-amazon, fifo-cogs-for-amazon-sellers]
---

A wholesale purchase order should be tracked as a five-state record — draft, submitted, confirmed, shipped, received — with the cost captured at every state change. The purchase order, not the supplier's catalog, is the only document that ties a real price to a real quantity on a real date.

Most Amazon wholesale sellers start with one spreadsheet tab per order and find the gap at reorder time: the catalog says one price, the invoice said another, and the shipment arrived short. Purchase order discipline exists to close that gap before it reaches cost of goods sold.

## The five states of a wholesale purchase order

A wholesale purchase order moves through five states, and each state adds information that cannot be reconstructed later if it is not captured at the time. Skipping the confirmed state is the most common shortcut, and it is the one that costs the most, because a supplier's order confirmation is where substitutions, backorders and revised prices first appear in writing.

**Table: purchase order states and what to capture at each, wholesale FBA**

| State | Capture at this state | Why it cannot wait |
|---|---|---|
| Draft | Supplier, SKUs, quantities, quoted unit price, price break tier, MOQ, expected freight terms | The quote is the basis for the ROI you approved the buy on |
| Submitted | Date sent, PO number, who sent it, the exact document the supplier received | Disputes are settled by the document, not by memory |
| Confirmed | Supplier's acknowledged price, acknowledged quantity, backorders, substitutions, ship date | This is where the supplier's price silently differs from the quote |
| Shipped | Carrier, tracking, freight charge, ship-from location, cartons and weight | Freight arrives on a separate invoice and gets lost otherwise |
| Received | Units actually counted in, damage, shortages, receipt date | Cost of goods sold is priced per received unit, not per ordered unit |

## The purchase order is the only reliable record of true unit cost

The purchase order is the only record of true unit cost because four different numbers claim to be the price, and only the purchase order links them. The catalog price is a quote that was already stale when the file was published. The confirmed price is what the supplier agreed to. The invoice price is what the supplier actually charged. The received quantity determines how those dollars spread across units.

Cost of goods sold needs cost per received unit. That number exists nowhere else. A catalog row cannot produce it because a catalog row has no quantity. An invoice cannot produce it alone because an invoice does not know what was short-shipped or damaged. Only a purchase order carries all four together, which is why [FIFO cost of goods sold for Amazon sellers](/docs/fifo-cogs-for-amazon-sellers) has to be built on purchase order receipts rather than on a price list.

## Reconciling a partial shipment against the supplier invoice

Reconciling a partial shipment means running a three-way match between the purchase order line, the receipt, and the invoice line, then classifying every difference. Wholesale suppliers short-ship constantly — a case allocated to a larger customer, a discontinued SKU, a warehouse pick error — and the reconciliation is where the real cost gets set.

Four variances show up, and each is handled differently:

- **Price variance** — invoiced unit price differs from the confirmed price. Update the line, do not overwrite the original quote; the difference is the audit trail.
- **Quantity variance** — fewer units received than invoiced. Claim it, and hold the line open until credited.
- **Short-ship with backorder** — units are coming on a second shipment. Split the line so each delivery carries its own freight.
- **Short-ship closed** — the supplier will not fulfil the balance. Close the line at the received quantity and re-spread freight immediately.

## The short-ship freight problem

Short-shipping breaks freight allocation, because freight was billed against the whole shipment and is usually spread across the units you ordered rather than the units that arrived. Consider a purchase order for 600 units across five lines with $850 of inbound freight. Spread across the 600 ordered units, freight is $1.4167 per unit. If only 480 units arrive, the true figure is $850 ÷ 480 = $1.7708 per unit.

That is a 25% understatement of freight on every unit you actually own, and $170 of freight that lands on no unit at all — it quietly disappears from cost of goods sold and reappears as an unexplained gap between reported profit and the bank balance. The rule is simple: freight is re-spread at receipt, across received units only, and a backordered balance carries the freight of the shipment it eventually arrives on, never a share of the first one. [How to allocate freight across purchase order lines](/docs/allocate-freight-across-po-lines) covers which driver to spread it on.

## Purchase order tools built for Amazon sellers

Several tools do Amazon-side purchase orders well, and two are worth naming honestly. RestockPro generates purchase orders directly from FBA restock suggestions, stores supplier lead times and performance history, and publishes its full price ladder starting at $49 per month (eComEngine pricing page, checked 2026-08-03); it states plainly that it does not support merchant-fulfilled SKUs. Extensiv Order Manager auto-generates purchase orders from a published, auditable reorder formula and tracks FBA and FBM velocity separately, though its pricing is contact-sales only with four unpriced plan tiers (Extensiv site, checked 2026-08-03).

The gap across that whole category is consistent: none of the major inventory and purchase order platforms checked on 2026-08-03 ingests a supplier price-list file or matches catalog rows to ASINs, and none has a CRM — no contacts, no organizations, no application pipeline. Every one of them starts from the assumption that the supplier account already exists.

## How Forge Command records a purchase order

Forge Command treats the purchase order as a first-class object with templates, a PDF designer, supplier email on submit, attachments and attachment matching, freight allocation, landed cost, per-SKU cost seeding, SP-API enrichment of purchase order lines, and a derived "most recent cost" field that answers what you actually paid last time. Margin math runs through one shared function, so the ROI shown on a purchase order, on the Wholesale tab and on the Products tab cannot disagree with each other.

Forge Command is wholesale-first and Amazon-first, and it is a young product from a small operator: there is no published pricing, no SOC 2, and no formal SLA. Sellers who need a mature multichannel order management system with an implementation team should buy one. Sellers whose problem is that the purchase order, the supplier relationship and the catalog live in three unconnected places are the ones this is built for. See [the best purchase order software for Amazon sellers](/docs/best-purchase-order-software-amazon) for the wider field.

## Frequently asked questions

### Should a purchase order be created before or after the supplier quotes

Create the purchase order in draft as soon as the quote arrives, and record the quoted price on the draft. The draft is where the buy decision and its ROI assumption are stored, so a later price change is visible as a variance rather than as the new normal.

### What quantity should cost of goods sold use, ordered or received

Received. Cost of goods sold is the money spent divided by the units you actually own, and freight, prep and duty all have to be re-spread across received units when a supplier short-ships. Using ordered quantity understates unit cost on every line that came up short.

### How long should purchase order records be kept

Keep them permanently. A purchase order is the evidence behind a cost basis, a supplier dispute, a trade reference and an Amazon invoice-authenticity request, and the reorder decision two years from now depends on knowing what the supplier actually charged rather than what the current catalog says.

### Does a purchase order need to match the Amazon inbound shipment

No, and forcing them to match causes errors. One supplier purchase order often becomes several FBA inbound shipments, and one inbound shipment often combines several purchase orders. Link them many-to-many and keep the cost on the purchase order, where [landed cost per unit](/docs/landed-cost-for-amazon-wholesale) is calculated.