Harpy Glossary

PPV (Purchase Price Variance)

Amazon & D2C glossary · Harpy Media

PPV (Purchase Price Variance) is the gap between the price expected on a purchase order and the price invoiced — procurement’s report card on price control. On the vendor side of the marketplace, it is the discrepancy that halts payment: an invoice submitted at a unit cost higher than the price confirmed on the corresponding purchase order.

What is PPV?

PPV (Purchase Price Variance) is the gap between the price expected on a purchase order and the price invoiced — procurement’s report card on price control. On the vendor side of the marketplace, it is the discrepancy that halts payment: an invoice submitted at a unit cost higher than the price confirmed on the corresponding purchase order.

Most price claims trace to timing rather than intent: the platform’s ordering systems work from the price on file, so if a cost increase has not been registered before the next bulk order is generated, the PO will carry the old figure — and an invoice at the new figure will not match.

Why the mismatch stops payment, not just the line

Automated reconciliation matches invoice to order, and a variance triggers a claim rather than a payment. The invoice sits unresolved while the discrepancy is worked, which puts the affected cash out of reach and drags finance teams into manual dispute handling.

Repeated occurrences are the deeper problem. Each one costs administrative effort on both sides, and a vendor whose invoices routinely disagree with their orders becomes harder to transact with — which is not the footing any supplier wants its largest customer to have. Accuracy here is a supplier-reliability signal, not bookkeeping hygiene.

Keeping variance at zero

The routine is simple and entirely about sequencing: update the catalogue price before the order is generated, not after it ships. Where a cost increase cannot wait, communicate it in advance so the order reflects the new terms — a negotiated change the system accepts is free; an invoice that contradicts the order is a claim.

For sellers, the same discipline runs the other way with suppliers: validate invoices against purchase orders before approving payment, and treat recurring variances as a supplier-quality issue rather than a rounding annoyance. On both sides, the fix is process order — price first, order second, invoice third.

In practice

A vendor negotiates a cost increase from $40 to $45 per unit, updates the catalogue, and has the change accepted before the next order is placed. The purchase order is generated at $45, the invoice for the thousand units matches it exactly, payment processes without delay, and cash flow stays predictable through a period when raw-material costs were moving.

⚠️ Watch out. Raising the unit price in the accounting system but not in the platform’s catalogue. The next order arrives at the old price, the vendor accepts it, ships, and invoices at the new price — and the mismatch converts into a price claim, a delayed payment, and a dispute that costs far more time than updating the catalogue would have taken.
💡 Harpy tip. Sequence the paperwork: catalogue price first, purchase order second, invoice third. Confirm cost changes are accepted before the next order cycle, and reconcile invoiced prices against confirmed order prices before submission — because a clean invoice is paid automatically.

How Harpy Media helps

Vendor pricing hygiene is part of our 1P operations: cost changes registered ahead of order cycles, invoices reconciled against orders, and the administrative frictions that delay payments designed out of the process.

PPV FAQ

What is purchase price variance?

The difference between the price confirmed on a purchase order and the price subsequently invoiced. On Amazon’s vendor side, a higher invoiced price triggers an automatic price claim and delays payment on that invoice.

What causes price claims?

Most commonly a cost change that was not registered in the platform’s catalogue before the next purchase order was generated. The order carries the old price and the invoice carries the new one.

How do I avoid price claims?

Update the catalogue price before orders are generated, ensure any renegotiation is formally accepted, and verify that invoices match the confirmed order price before submitting them for payment.

Want these numbers watched for you, every week?

Book Free Consultation

New guides, straight to your inbox.

Practical D2C playbooks as we publish them. No fluff, no spam — unsubscribe anytime.