Does Amazon WePay Reduce Shortage Claims?
No. WePay changes who coordinates your carrier — not what happens at the receiving dock. Shortages originate inside Amazon's fulfilment centres, at the point where an associate opens a box and counts its contents. No carrier programme changes that process.
| Programme | What it is | What Amazon promised | What it changed |
|---|---|---|---|
| LPR / Auto-Receive | Licence plate scanning at the dock | Automated receive, fewer errors | Moved the counting from dock to stow associate |
| PICS | Pan-EU inbound consolidation, 2.5–4.5% of inbound value | Fewer handoff errors, reduced shortages | Vendor-side efficiency gains only |
| IPCP | Preferred carrier slots (e.g. Palletline UK) | Priority access, fewer delays | Peak slot availability — not shortage reduction |
| WePay / Collect | Amazon coordinates carrier selection (UPS, FedEx, DPD, Amazon Freight) | More visibility, fewer inbound errors | Carrier coordination — not the receive process |
What is Amazon WePay / Amazon Collect?
WePay — called Amazon Collect in some markets — is a freight programme where Amazon coordinates carrier selection on your behalf. Instead of booking shipments through your own TMS or directly with a carrier, you hand that decision to Amazon. Amazon assigns a carrier from its pool — UPS, FedEx, DPD, Amazon Freight — coordinates the pickup, and manages the inbound journey to their fulfilment centre.
Amazon's pitch: more visibility over inbound shipments, fewer appointment-related errors, and — by implication — fewer shortages.
It sounds logical. Amazon owns the logistics chain. More control on their end means fewer errors at receive?
It doesn't, at least not to the extent claimed. The reasons are structural.
What WePay Actually Changes — and What It Doesn't
The vast majority of shortages are created at the stow stage inside an Amazon FC. A receive associate scans your shipment at the dock. A stow associate then opens the box, counts the contents, and receives the inventory into the system. That's where errors enter: wrong label scans, miscounts, mixed cartons, case pack confusability.
WePay improves the journey of your goods to the FC. It might solve one-off errors such as cancelled or duplicate appointments. It does not change what happens after your goods arrive.
I've seen this first-hand. On a WePay shipment, eight pallets from a single ASN were received across six separate appointments — sometimes mixed with cartons from other ASNs. Shortages followed. Because we were using Amazon's carrier programme rather than managing our own logistics, we had less visibility to contest them, not more. We eventually resolved the claims — but through a one-off process that wasn't scalable.
Amazon's US market has run a Collect programme for years. Shortages haven't gone away. Talk to your Amazon ecosystem contacts in the US. Ask them.
Amazon Has Made This Promise Before
WePay is the latest version of a pattern I've watched for nearly a decade.
LPR / Auto-Receive. I ran Kaizens with 20+ vendors to implement licence plate receiving. The investment was real: IT infrastructure, new printing mechanisms, process redesign, labelling labour absorbed into already-tight margins.
The promise: dock associates would scan a single label and receive all contents automatically.
What actually happened: the cognitive work moved. The dock associate no longer counted the items — the stow associate did. Different person, different location inside the FC, same human counting error. The root cause — a person opening a box under throughput pressure — was untouched. Auto-Receive, as it's now called, carries the same limitation.
PICS. I've negotiated tens of PICS contracts. One in particular stands out: a vendor carrying £2.5 million in initial shortage claims. After Smart Match reconciliation, final shortages stood at £1.1 million. PICS delivered a further 20–30% reduction.
But the reduction came almost entirely from vendor-side efficiency gains — better consolidation, less paperwork, fewer handoff errors before goods reached Amazon. Shortages driven by Amazon's own receive process continued. And the vendor was paying 3%+ of inbound value for the privilege. The honest question: is 20–30% worth 2.5–4.5% of COGS when the shortages you can't control keep happening?
IPCP. Carriers with dedicated FC appointment slots. Genuine value for peak season access. But the carrier has no stake in your shortage outcomes. A preferred slot gets your goods to the dock on time — it doesn't change what happens after the associate opens the box. In some cases IPCP can worsen shortages: staged inventory split across multiple Amazon appointments creates more opportunities for matching errors, not fewer.
Should You Use WePay?
WePay has legitimate uses. If carrier selection is a bandwidth problem, handing it to Amazon makes sense. If appointment availability during peak is your constraint, it's worth evaluating. But if the pitch includes a shortage reduction promise, push back before signing — because that is the one outcome Amazon's inbound programmes have not delivered.
WePay is a premium service. Like PICS, vendors pay a freight allowance to Amazon — a percentage of net sales — on top of whatever operational changes the programme requires. Before signing up, challenge Amazon directly: by how much will your shortage rate drop, and in what timeframe? Get a specific number. If they can't give you one, that tells you everything you need to know about the shortage promise.
Amazon's inbound programmes have carried the same promise across different packaging for nearly a decade. Each one moves something. None has addressed the process that creates shortages.
The stow associate is still opening the box. The count is still done by hand. That hasn't changed.
If you're looking for a solution to shortages, the answer isn't a different inbound programme — it's a system that handles them well.
PACMAN ingests your full history — ASN logs, EDI transmissions, FC receive records, carrier data, warehouse records, dispute files — and cross-references them at PO and ASIN level. Every touchpoint tracked. Every discrepancy surfaced. The result is watertight, data-backed cases — not best-effort disputes assembled from whatever's easiest to pull.
We can show you what's in your data within a week. Our AI team works 24/7 — first filings start at 4 weeks, clearing your entire 5-year backlog in 10 weeks without compromising quality.