Amazon Unconfirmed PO Units Chargeback: Ship Only What You Confirmed

Executive Summary & Quick Answer

Executive summary: In most retail programs, shipping a little extra reads as generosity. In Amazon Vendor Central it reads as unplanned freight, and it has a price: the Unconfirmed PO Units chargeback applies whenever Amazon receives units it did not have a confirmed order for — units beyond the confirmed quantity, or shipments that moved before any confirmation was submitted at all. The FC's capacity planning runs on confirmations, and unconfirmed units are noise in that plan. The counterintuitive lesson for vendors: at Amazon, over-shipping is a compliance failure, not a favor. Charges appear in the operational performance dashboard; disputes go through Vendor Central support cases.

Quick answer: Amazon's Unconfirmed PO Units chargeback is a Vendor Central operational fee applied when a vendor ships units never confirmed against a purchase order — Amazon receives items without a confirmed order. Triggers include overage beyond the confirmed quantity and shipping before confirmation. Amazon charges per unconfirmed unit received; prevention is confirmation discipline.

---

Deep Dive: The Confirmation Is the Contract

The EDI 850 purchase order is Amazon's request. Your confirmation is the binding answer — and from that moment, the confirmed quantity is the only quantity Amazon expects on the truck. Every unit above it, or every unit shipped before a confirmation exists, arrives at the FC as freight with no order behind it.

EDI 850 (PO: 1,000 units)
        │
   you confirm 800  ◄── the contract is now 800
        │
   you ship 900
        │
   FC receives:  800 confirmed ✓
                 100 UNCONFIRMED ✗ ──► per-unit chargeback

The record lists three routes into the same fee:

Route	What happened	The mindset behind it
Overage beyond confirmed quantity	Shipped more than you confirmed	"Round up to full cases / they'll take it"
Confirmation never submitted	Shipped against the raw PO	"The PO is the order — why confirm?"
Units beyond what was confirmed on the PO	Line-level over-shipment	Warehouse ships to stock, not to the confirmation

The instructive pairing is with PO On-Time Accuracy. That chargeback punishes confirming units you fail to deliver; this one punishes delivering units you failed to confirm. Together they define the target: shipped = confirmed, exactly. Under-ship your confirmation and you're exposed on one side; over-ship it and you're exposed on the other. Amazon is pricing deviation in both directions, and the only safe operating rule is to treat the confirmed quantity as a hard pick constraint, not a suggestion.

A subtle operational trap: case-pack rounding. A confirmed 800 units in 24-packs doesn't divide evenly, and the warehouse "helpfully" ships 33 full cases (792) or 34 (816). One direction shorts the order; the other manufactures unconfirmed units. The confirmation itself should be case-pack-aligned before it's submitted.

---

Business & Financial Impact

• Fee structure: a per-unit fee for unconfirmed units received, per Amazon's vendor terms. The record publishes no dollar figure — verify your rate in your agreement.
• Self-inflicted and silent: overage feels virtuous on the dock, so nobody flags it; the first signal is the dashboard line item.
• Systematic when procedural: if your team skips confirmations as policy, every shipment is exposed, not the occasional one.
• Payment ambiguity on the extras: units Amazon had no confirmed order for are units outside the ordinary PO settlement path — cost and reconciliation headaches beyond the fee itself.
• Dispute posture: the confirmation record in Vendor Central is the evidence, and it's Amazon's own system. Disputes via support cases succeed mainly when you can show the units were confirmed — timing and record-keeping are everything.

---

Root Causes (Ranked)

1. Confirmation skipped as a process step. Teams ship against the 850 directly, treating confirmation as optional ceremony.
2. Case-pack and pallet rounding up. Warehouses complete cases and layers past the confirmed number.
3. Warehouse decoupled from the confirmation. Pick tickets generated from the PO or from stock, so the floor never sees the confirmed quantity.
4. Late confirmation. Submitted after the truck left — units were unconfirmed at the moment that mattered.
5. Line-level slippage. Aggregate totals look right while individual lines over-ship their confirmed quantities.

---

Step-by-Step Prevention Workflow

1. Make confirmation a hard gate. No pick ticket, no dock booking, no ASN until the PO is confirmed in Vendor Central. Sequence, not habit.
2. Confirm case-pack-aligned quantities. Resolve rounding at confirmation time, when it's a data edit — not at pick time, when it becomes freight.
3. Drive the pick from the confirmation. The warehouse fulfills the confirmed quantity, line by line; the raw PO never reaches the floor.
4. Audit shipment vs confirmation before release. A line-level diff: any unit above any confirmed line quantity holds the shipment.
5. Kill the overage reflex. Write it into the SOP explicitly: extra units are a chargeback, not a courtesy. Surplus stock waits for the next PO.
6. Reconcile weekly. Match dashboard charges against confirmation timestamps; dispute charges on units you can prove were confirmed pre-shipment.

850 in ──► confirm (case-aligned) ──► pick FROM confirmation ──► line-level diff
                                                                      │ over?
                                                                      ▼
                                                              hold — never ship it

---

Unconfirmed Units in the Amazon Chargeback Family

Chargeback	What Amazon is grading	Where the failure lives
Unconfirmed PO Units	Shipping only confirmed units	Order confirmation process
PO On-Time Accuracy	Fulfillment within the PO window	Planning and logistics
ASN Accuracy	Ship-notice data vs receipt	EDI pipeline
Carton Content Accuracy	Carton detail vs physical cartons	Pack station and labels
Prep	Physical prep requirements met	Packaging line

Related: PO On-Time Accuracy

---

Supplier Checklist

• PO confirmation in Vendor Central gates all downstream steps
• Confirmed quantities case-pack-aligned at confirmation time
• Pick tickets generated from the confirmation, not the raw PO
• Line-level shipment-vs-confirmation diff before release
• "No overage" rule written into the shipping SOP
• Weekly: dashboard charges reconciled against confirmation timestamps

---

FAQs

What is Amazon's Unconfirmed PO Units chargeback? A Vendor Central operational chargeback applied when a vendor ships units that were never confirmed against a purchase order — Amazon receives items it did not have a confirmed order for.

How much is the fee? A per-unit fee for unconfirmed units received, set by Amazon's vendor terms. No universal dollar amount is published — verify your rate in your own agreement.

Does shipping a few extra units really trigger it? Yes. Overage beyond the confirmed quantity is a listed cause. At Amazon, extra units aren't a courtesy — they're unconfirmed freight with a per-unit price.

What if I confirmed the PO but after the shipment left? Confirmation not submitted before shipping is a listed cause. The confirmation has to exist before the units move, which is why it should gate pick and dispatch.

How does this differ from the PO On-Time Accuracy chargeback? They're mirror images: PO On-Time charges confirmed units that miss the delivery window; Unconfirmed Units charges received units that were never confirmed. The safe zone is shipping exactly what you confirmed, on time.

How do I dispute the charge? Through a Vendor Central support case, showing the units were confirmed before shipment — confirmation records and timestamps against the shipment's line detail.

---