What is the difference between an order number and a tracking number?
The order number is issued by the seller or marketplace the moment payment clears; the tracking number is issued by the carrier the moment a shipping label is created. They live in two separate systems, and neither can resolve the other's identifier. A carrier tracking page returns no result for an Amazon order ID such as 113-1234567-1234567, and a shop's order lookup returns no scan events for a carrier barcode number. One purchase always produces exactly one order number, and anywhere from zero to several tracking numbers, depending on how many parcels the order is split into and whether it has been handed to a carrier yet.
Who issues each number, and at which moment
The order number is created within seconds of checkout by the seller's commerce platform, before any parcel exists. It indexes the commercial record: the items, the prices, the payment method, the billing and delivery addresses, and the buyer's account. Amazon's Selling Partner API documents its version of that identifier as "An Amazon-defined order identifier, in 3-7-7 format", meaning three digits, then seven, then seven, separated by hyphens (Amazon Selling Partner API model, Orders v0). Shopify stores number their orders sequentially from 1001 by default. Marketplace order histories such as Amazon show that number at the head of every order.
The tracking number is created later, by the carrier's system, at the point the shipper buys or prints a label. It indexes a logistics record: one parcel, its service class, its weight, its destination postcode, and the chain of scans it will collect. The carrier generates the number even when the parcel has not been packed, which is why it can exist for days before anything moves.
Guest checkouts make the split obvious. A buyer who ordered without creating an account has no order history to open, so the order number in the confirmation email is the single handle on the purchase, and it is the value the shop's guest lookup form asks for.
The practical consequence is that the two numbers answer to two different organisations. The seller can reissue an order, refund it, or split it into more shipments; only the carrier can add a scan to a tracking record.
The two identifiers side by side
Eight attributes separate the two numbers, and only one of them, the count per purchase, varies from order to order. Order formats differ by issuer rather than by rule, so a shop is free to number its orders however it likes, while carrier numbers follow published structures described in what a tracking number looks like.
| Attribute | Order number | Tracking number |
|---|---|---|
| Issued by | The seller, marketplace or shop platform | The carrier that will move the parcel |
| Created at | Checkout, within seconds of payment | Label creation, commonly 1 to 3 business days later (estimate) |
| Typical form | Structured or sequential: Amazon's 3-7-7 pattern, or Shopify's #1001 series | A carrier barcode number, commonly 10 to 22 characters, often with a letter prefix |
| How many per purchase | Exactly 1 | 1 per parcel, so 0 before dispatch and several after a split |
| Answers | What was bought, for how much, by whom, to which address | Where the parcel was last scanned, and what happened to it there |
| Appears in | The order confirmation email, the account order history, the packing slip | The shipping confirmation email, the label itself, the carrier receipt |
| Queried at | The seller's account pages and support forms | The carrier's tracking system and multi-carrier trackers |
| Stops working | Rarely: it stays in the account order history | 90 days after delivery at FedEx, unless extended retention is purchased |
The two numbers also arrive in two different emails. The order confirmation lands within minutes of payment and carries the order number, the items and the total; the shipping confirmation lands at dispatch and carries the carrier name and the tracking number. A buyer holding only 1 email is usually holding only 1 of the 2 numbers.
The letters at the front of a carrier number belong to that published structure rather than to a shop convention, and they identify the service or the origin postal operator, as set out in what the letter prefixes mean.
Why the tracking number arrives days after the order number
A tracking number exists from the second a label is generated, which is usually well before the parcel is in the carrier's hands. USPS gives that stage its own status and defines it in plain terms:
"A shipping label has been created with a USPS Tracking® number. The package has not yet been given to USPS." (USPS, Where is my package? Tracking Status Help, accessed July 2026.)
During that window the number is valid but returns a single event, and the shipping confirmation email may not have been sent yet, so the buyer holds an order number and nothing else. Sellers that batch their dispatch print labels once a day, which is why the gap between the two numbers is typically 1 to 3 business days rather than minutes (USPS tracking status help). The first movement scan converts the record into a real journey, and only then does the status advance to something like in transit.
An order that still shows no tracking number after several days has usually not been dispatched. That is a question for the seller, because no carrier holds a record of a label nobody has bought.
Why one order can carry several tracking numbers
A single order number survives any number of shipments, because the commerce platform models the purchase and the parcels as separate objects. Shopify's Admin API describes the shipment layer attached to each order:
"A list of shipments for the order. Fulfillments represent the physical shipment of products to customers." (Shopify, Admin GraphQL API reference, Order object, accessed July 2026.)
Each of those fulfillments carries its own tracking information, so a 3-item order fulfilled from two warehouses produces one order number and two tracking numbers (Shopify Admin GraphQL API, Order object). Marketplaces behave the same way when items come from different sellers: the buyer sees one order in the account and one shipping confirmation per consignment.
Three further situations add tracking numbers without changing the order number. A label that is voided and reprinted produces a new number, because carriers do not reissue a cancelled barcode. A replacement sent after a loss or a damage report ships on its own label. A parcel returned to the seller travels back under a separate return label, which is why a return has a tracking number that has nothing to do with the outbound one.
The one case where the order number reaches the carrier
Carriers can search by the shipper's own reference, and a purchase order or order number is one of the values shippers store there. FedEx lists the supported reference types as a "purchase order (PO) number, customer reference, invoice, Bill of Lading (BOL), part number", plus the Transportation Control Number for eligible services. The lookup is not open to anyone holding the number:
"reference value, destinationPostalCode, destinationCountryCode, Ship date begin and end date" (FedEx Developer Portal, Track API documentation, data required to track by reference without an account number, accessed July 2026.)
That is 4 pieces of information for a reference search against 1 for a tracking number search, and it only works if the shipper wrote the reference onto the shipment in the first place (FedEx Track API documentation). Most consumer orders carry no such reference, because warehouse systems use their own internal picking codes instead. Treating the order number as untraceable at the carrier is therefore the safe default, with reference search a business-shipping feature rather than a consumer one.
Multi-carrier trackers inherit the same limit. They query carrier systems by barcode number, so an order number entered into 1 of them matches nothing, no matter how many carriers the tracker covers.
Which number the seller needs, and which the carrier needs
Support requests fail most often because the wrong one of the 2 numbers is quoted. A seller's support desk keys on the order number, because that is the only identifier tied to the payment, the items and the buyer's entitlement to a refund or a replacement. A carrier's support desk keys on the tracking number, because its systems index parcels rather than purchases, and it has no visibility of who bought what.
The split also decides who can act. The carrier's contract is with the shipper, so a claim for a lost or damaged parcel is normally filed by the sender, and the recipient's route to a remedy runs through the seller and the order number. Marketplace buyer protection works the same way: the case is opened against the order, and the tracking number is attached as evidence of what the carrier recorded.
A message to either party should therefore carry both numbers where both are known, each labelled for what it is, because a 3-7-7 string pasted into a carrier form returns nothing at all. A complete first message to a seller names the order number, the item, the tracking number if one was issued, and the date of the last scan, which removes 1 round trip from the exchange.
How long each number keeps working
Tracking numbers expire from carrier systems; order numbers do not. FedEx states a fixed retention window for its own records:
"Tracking information is available for 90 days after delivery for FedEx Express, FedEx Ground, and FedEx Custom Critical." (FedEx Developer Portal, Track API documentation, accessed July 2026.)
Signature proof of delivery is held longer, up to 16 months for FedEx Express and FedEx Ground shipments. USPS sells an extension of its retention rather than granting it by default, describing USPS Tracking Plus as a service that retains "scan data or scan and signature data for Your packages beyond the Postal Service's standard data retention period, for up to ten years" (USPS Tracking Plus terms and conditions).
Order numbers face no equivalent clock. They stay in the account order history and on the invoice, which makes the order number the identifier worth keeping for warranty claims, tax records and disputes raised months after delivery. Carriers also recycle barcode numbers once a retention period has passed, so an old tracking number can eventually return a different parcel's events or no result at all.
What neither number proves on its own
A tracking number confirms that a labelled parcel of a stated weight moved through 1 or more sorting points. It does not confirm what is inside it, who paid for it, or which items from an order it contains, because the carrier receives no contents list for a domestic parcel. A delivered scan is therefore evidence that a package arrived, not evidence that the right goods arrived.
An order number proves the opposite half. It confirms that a purchase exists, what it contained and what was paid, and says nothing about whether anything left the warehouse. An order marked as shipped in an account, with no carrier scan behind the number, is a seller statement rather than a carrier record.
Disputes turn on that gap. The order number establishes the entitlement, the tracking number establishes the movement, and a case is only complete when both are on the table.
Identifiers that get mistaken for these two
At least 5 other reference numbers appear on the same emails and documents, and 2 of them sit close enough to the order number to cause real confusion. Shopify's confirmation number is the clearest example, because it appears exactly where a buyer expects the order number:
"A customer-facing order identifier, often shown instead of the sequential order name. It uses a random alphanumeric format (for example, XPAV284CT) and isn't guaranteed to be unique across orders." (Shopify, Admin GraphQL API reference, Order object, confirmationNumber field, accessed July 2026.)
| Identifier | Issued by | What it identifies | Usable at a carrier |
|---|---|---|---|
| Order number | Seller or marketplace | The whole purchase | No |
| Order confirmation number | Shop platform | The same purchase, in a random form such as XPAV284CT | No |
| Invoice number | The seller's accounting system | The billing document, not the shipment | No |
| Item number, ASIN or SKU | Marketplace or seller catalogue | The product line, not the order | No |
| Shipment reference or PO number | The shipper, stored in the carrier's record | The consignment as the shipper labels it | Yes, with 3 extra data points |
| Return authorisation number | Seller | The return case, not the outbound parcel | No |
| Tracking number | Carrier | 1 parcel | Yes |
The test that settles every one of them is the issuer. If the number came from the party that took the money, it belongs in a message to the seller. If it came from the party that took the parcel, paste it into the tracker at the top of this page and the scan history will load.