Harpy Glossary

ARN (Amazon Reference Number)

Amazon & D2C glossary · Harpy Media

The ARN (Amazon Reference Number) is the unique tracking ID Amazon assigns to every inbound shipment — the key linking your freight, its paperwork, and Amazon’s receiving records into one auditable thread.

What is ARN?

It sounds like bureaucracy until the day it isn’t: the ARN is what you cite when a container is half-received, when a carton goes missing between dock and shelf, and when reconciliation says Amazon has 400 fewer units than you shipped. No ARN, no conversation — it’s the shipment’s legal identity inside the machine.

Where it sits in the inbound chain

Your shipment plan generates the ARN alongside the shipment ID; it travels on the BOL and the ASN as the reference receiving scans against. Every carton scanned at the dock ties back to it; every discrepancy report, reimbursement claim, and receiving query quotes it. The operational habit that matters: the ARN lives in ONE place per shipment — your freight log — connected to the PO, container number, BOL, and expected units. When something goes sideways, the person with that log resolves in hours what takes others weeks of email archaeology.

The reconciliation connection

Units you ship minus units Amazon scans in, per ARN, is the raw material of reimbursement recovery. Amazon’s inventory ledger organizes reality by reference number; your claims must speak that language. Vendors and sellers who reconcile per-ARN monthly find lost inventory fast, while the trail is warm and the records still exist. The ones who reconcile “eventually” discover that claims age poorly — evidence windows close, warehouses cycle, and the burden of proof quietly moves to whoever still has documents.

In practice

A seller’s LTL arrives with 22 pallets; receiving logs 21. Because the ARN, BOL, and pallet-level SSCC list live in one freight log, the claim files the next morning with photos, the missing pallet’s contents, and the driver’s signature count. Amazon’s receiving team finds the pallet staged in the wrong zone — credited and sellable within a week. Total effort: one morning. The alternative timeline runs months.

⚠️ Watch out. A brand learns its shipments have been under-received “by a few percent” for two quarters — discovered only when a finance review finds inventory value doesn’t reconcile. The claims effort now spans dozens of ARNs with cold trails; half the evidence windows have closed. The money was recoverable monthly; it became a write-down quarterly.

💡 Harpy tip. Log every ARN with its PO, BOL, SSCC list, and unit counts at shipment time — and reconcile received-vs-shipped per ARN monthly. Reimbursement recovery is a records game, and the house wins against the disorganized.

How Harpy Media helps

Inbound reconciliation is standing ops for us — per-ARN, monthly, with claims filed while evidence is fresh. Amazon’s ledger is honest when you check it; the checking is the job.

ARN FAQ

What is an Amazon Reference Number?

The unique ID assigned to each inbound shipment, linking freight paperwork to Amazon’s receiving records.

Where do I find my ARN?

On your shipment plan in Seller/Vendor Central — and it should appear on your BOL and ASN as the receiving reference.

Why does the ARN matter for reimbursements?

Claims reconcile shipped vs received per reference number — the ARN is the thread your evidence must follow to get recovered.

Want these numbers watched for you, every week?

Book Free Consultation