Amazon Carrier Central: How Inbound Delivery Appointments Get Booked
Amazon Carrier Central is the Amazon-run portal where a carrier — not the seller — requests the appointment to deliver freight into an Amazon facility, and if you ship on an Amazon partnered carrier you never touch it. The site’s own instruction to carriers is one line: “To schedule your inbound freight delivery please request an appointment with your earliest available time” (data checked 2026-08-05, from the official portal at carriercentral.amazon.com).
This guide covers only the booking step — deciding who books, getting the carrier registered, supplying the right identifiers, and diagnosing a booking that will not go through. Everything that happens after the truck leaves, from Shipped through Checked in to Closed, is mapped separately in how to track Amazon FBA shipments end to end. Booking is the leg upstream of that chain, and it is the leg with the least public documentation, because most of the detailed help articles sit behind a Seller Central login.
What Amazon Carrier Central Is — and What It Is Not
Carrier Central is a scheduling front door, nothing more. Amazon’s own legal notice on the portal says the site is maintained by “Amazon.com, Inc. or its affiliates” and exists “solely to facilitate scheduling of courier appointments for deliveries to Amazon,” and that users agree they “will not use this website for any other purpose” (checked 2026-08-05, Carrier Central legal disclaimer).
Two consequences of that wording are worth internalising before you plan a delivery around a slot:
- A confirmed slot is not a contract. The same page states that “Scheduled appointments do not constitute a legally binding obligation on Amazon” and that “Amazon may cancel appointments at any time.” Build slack into your inbound plan accordingly.
- It is a carrier tool, not a seller tool. Registration is keyed to a carrier identity: the portal validates a “SCAC/Vendor code” field, which means the account belongs to a freight carrier or a vendor, not to a marketplace seller account.
What Carrier Central does not do: it does not create your shipment plan, generate your box or pallet labels, or decide which fulfillment center you ship to. Those all happen upstream in the Send to Amazon workflow.
Who Books: Amazon Partnered Carrier vs Your Own Carrier
This is the fork that decides whether Carrier Central is your problem at all. Amazon’s own guidance on LTL shipping is explicit in both directions (checked 2026-08-05, from Pay less to stock more with Amazon LTL carriers):
| Your setup | Who schedules the appointment | Amazon’s wording (verbatim) |
|---|---|---|
| Amazon partnered carrier (PCP) | Amazon | “Amazon manages scheduling a delivery appointment at the destination facility on your behalf” |
| Non-partner / self-arranged carrier | You or your carrier | “If you choose to use a non-partner carrier, you or your carrier must schedule a delivery appointment at the receiving Amazon facility in advance” |
The Partner Carrier program covers more modes than many sellers assume: it spans “small parcel deliveries (SPD) and less-than-truckload (LTL), full-truckload (FTL), and intermodal (IM) shipments,” and is open to sellers using FBA, Multi-Channel Fulfillment and AWD within the 48 contiguous states. You pick a partner carrier in step 2 of Send to Amazon for SPD, or step 4 for LTL, FTL and IM (checked 2026-08-05, Partner Carrier program).
Mode matters too. Amazon defines SPD as “Ship inventory as individual boxes” and LTL as “Ship inventory as pallets” (checked 2026-08-05, How to send your inventory to Amazon Fulfillment Centers). Parcel volumes move on the carrier’s normal network and do not need a dock slot. Palletised freight does, and Amazon states the dependency plainly: “For each pallet shipment, you must provide a valid BOL to the carrier so they can schedule a delivery appointment.”
So the practical rule is: SPD, no appointment; palletised freight, always an appointment — booked by Amazon if partnered, by your carrier if not.
What Your Carrier Needs Before They Can Request a Slot
You cannot request the slot yourself, but you can be the reason your carrier fails to. The public Carrier Central interface enforces a set of field-level rules, and the error strings are the closest thing to published requirements that exists outside the login wall (checked 2026-08-05, from carriercentral.amazon.com and its help page):
| Field | Rule as stated by the portal |
|---|---|
| SCAC / Vendor code | “SCAC/Vendor code cannot be empty”; “SCAC cannot be longer than 5 characters”; “SCAC can only consist of letters and numbers” |
| Contact name | “Contact name cannot be longer than 100 characters” |
| Contact email | “Contact email cannot be empty and must be in an email format” |
| Contact phone | “Contact phone must be between 5 and 15 digits” |
| Shipment identifiers | “Either PRO or BOLs must be present” |
| Shipment count | “Please add at least one shipment” |
Read the SCAC line carefully: without one the portal will not take a registration, and the code has to fit the five-character alphanumeric rule above. If your quoted rate came from a broker, ask whose SCAC will appear on the booking before the freight is tendered — not after.
Your side of the handoff is the paperwork. Amazon’s instruction to sellers is to hand over both documents at collection: “During pickup, ensure you provide your assigned partnered carrier both the BOL and the Amazon reference number, or ARN.” The pallets have to be dock-ready on the same trip — Amazon specifies pallets “40 × 48 inches and made of wood with four-way access,” wrapped in “clear plastic stretch wrap,” with a pallet ID label “squarely on each of the four sides” (checked 2026-08-05, Pay less to stock more with Amazon LTL carriers and How to send your inventory to Amazon Fulfillment Centers). If your labels are still in question, start with Amazon barcode requirements.
ISA, ARN, BOL, POD: Which Identifier Does What
These four acronyms get used interchangeably in carrier emails and they are not interchangeable. Amazon Freight publishes plain-language definitions of the first two (checked 2026-08-05, Amazon Freight terms all shippers should know) and the second two (checked 2026-08-05, More freight and transportation terms all shippers need to know):
| Term | Amazon’s definition (verbatim) | Who produces it |
|---|---|---|
| ISA (Inbound Scheduled Appointment) | “When a carrier creates an inbound shipment to an FC, they receive an ISA. This gives all the details of your pickup and drop off dates and times.” | Amazon, on booking |
| ARN (Amazon reference ID) | “This is a code that you can simply think of as a PO.” | Amazon, with your shipment plan |
| BOL (bill of lading) | “a legally binding document that must be filled out before a carrier hauls the freight. It details the type, quantity, and destination of the goods in the load and serves as a receipt once the carrier delivers the freight.” | You / your carrier, before pickup |
| POD (proof of delivery) | “confirms that the freight was delivered without visible damage and includes details such as delivery time, delivery address, and the consignee’s name.” | The receiving facility, at delivery |
The sequence runs ARN → BOL → ISA → POD. The ARN exists as soon as your shipment plan does; the BOL is written before the truck loads; the ISA comes back only after the carrier’s request is accepted, which is why chasing “the ISA number” before confirmation is a wasted phone call; the POD is generated at the dock and is the document you will want weeks later if units go missing.
One documentation caveat: Amazon’s article on carrier requirements for delivering shipments (help reference G200978420) sits behind a Seller Central sign-in, so its FBA-specific field list is not quoted here. Pull it from your own Seller Central Help search, or ask your carrier for their copy.
When the Booking Will Not Go Through
Beyond field validation, Carrier Central gates which carriers may book at all. The portal states that “No Call No Shows or Cancellations within {0} hours of Scheduled Arrival Time are considered a defect against the carrier” and that carriers must hold an appointment defect rate below a stated threshold, and separately that “Amazon requires a Carrier Controllable FPY rate of {0}% or better to be eligible to deliver to Amazon Facilities.”
Note the {0} in both sentences. Those are unfilled template placeholders in the public page — the actual hour window and the actual percentage thresholds are rendered only inside a logged-in carrier session, so no public number exists for either threshold. Treat any blog quoting a specific figure as unsourced unless it shows the logged-in page.
Working through a failed booking in order of likelihood:
- No slots on your date. Requesting “the earliest available time” is the portal’s own framing; a specific date is a preference, not an entitlement. Widen the window before escalating.
- Carrier not eligible. A defect-rate or FPY suspension is invisible to you and visible to them. If a second carrier can see slots at the same site on the same day, the problem is carrier-side.
- Identifier mismatch. The portal will refuse a request with neither PRO nor BOL attached. A transposed ARN is the same failure with a friendlier error.
- Wrong destination. Amazon assigns the receiving facility in your shipment plan; a carrier booking against a different site is booking someone else’s freight.
- Amazon-side cancellation. Permitted at any time by the terms above. Rebook and re-tender; there is no appeal path published for it.
Escalation goes through the carrier, not through you. Carrier Central’s help page carries a “Case / Enquiry You May Have” contact table addressed to carriers; your leverage is to make your carrier open that case with the ARN and BOL in hand. If the freight cost itself is what is under review, Amazon shipping cost calculator covers the rate side.
If the Delivery Is Refused or Units Go Missing
A refused delivery and a short-received shipment look the same from Seller Central for the first few days, and they are resolved differently. The tell is the POD. If the carrier can produce a POD, the freight reached the dock and this is a receiving discrepancy. If they cannot, it never got in, and the conversation is with the carrier.
For the receiving-discrepancy branch, the timing is fixed by shipment status. Amazon closes an inbound shipment once all units are confirmed received, or after 45 or more days for domestic shipments and 75 or more days for international ones; reconciliation opens from the Action required dropdown once the shipment reaches Closed (checked 2026-08-05, How to track FBA shipments). The status-by-status diagnosis lives in the FBA shipment tracking guide; the claim mechanics are in the Amazon FBA reimbursement guide.
If you would rather audit reimbursement records in bulk than chase them one shipment at a time, ReimburseOps takes an uploaded FBA reimbursements CSV and flags under-reimbursed and inconsistently valued records against your cost file. It is subscription-priced — a free tier that shows only part of the flagged list and no CSV export, and a $19/month plan that adds export and monthly re-scans — and it takes no percentage of what you recover. It does not connect to Seller Central and does not file claims for you, so it complements the reconciliation flow above rather than replacing it (checked 2026-07-27).
The Pre-Booking Checklist
Run this before the freight is tendered, not after:
- Confirm the mode: parcel-sized boxes (SPD) need no appointment; pallets do.
- Decide partnered vs non-partner, and write down which party owns the booking.
- If non-partner: confirm the carrier holds a valid SCAC and an active Carrier Central account.
- Have the ARN and the shipment’s destination facility in front of you at tender.
- Give the carrier a printed BOL at pickup, alongside the ARN.
- Confirm pallets are 40 × 48 four-way, stretch-wrapped, with four pallet ID labels.
- Ask the carrier to send you the ISA once it is confirmed, and the POD after delivery.
- Keep both documents until the shipment status reaches Closed.
Frequently Asked Questions
Can a seller book an Amazon Carrier Central appointment directly?
No. The portal validates a SCAC or vendor code, so the account belongs to a carrier or vendor. Sellers using a non-partner carrier are told by Amazon that “you or your carrier must schedule a delivery appointment at the receiving Amazon facility in advance,” and in practice that means instructing your carrier to do it (checked 2026-08-05).
Do small parcel shipments need a Carrier Central appointment?
No. Amazon defines SPD as shipping “inventory as individual boxes,” which move on the carrier’s regular network. The appointment requirement attaches to palletised freight: “For each pallet shipment, you must provide a valid BOL to the carrier so they can schedule a delivery appointment” (checked 2026-08-05).
What is the difference between an ISA and an Amazon reference ID?
The ARN is your shipment’s identifier, which Amazon likens to a PO. The ISA is the appointment itself, issued after booking — Amazon’s definition is that a carrier “creates an inbound shipment to an FC” and “they receive an ISA,” giving “all the details of your pickup and drop off dates and times” (checked 2026-08-05).
How far in advance must the appointment be booked?
Amazon’s public wording is “in advance” for non-partner carriers, with the portal asking carriers to request “the earliest available time.” No specific lead time is published on any page readable without a login, so treat named figures elsewhere as unverified (checked 2026-08-05).
Can Amazon cancel a confirmed appointment?
Yes. The Carrier Central legal disclaimer states that “Scheduled appointments do not constitute a legally binding obligation on Amazon” and that “Amazon may cancel appointments at any time” (checked 2026-08-05).
Conclusion
The single decision that determines how much Carrier Central affects you is partnered versus non-partner. On a partnered carrier, Amazon books the slot and the portal is invisible. Off it, the appointment becomes a carrier obligation you can only influence through paperwork — a valid SCAC, an ARN, a BOL, and a realistic date window.
Everything published without a login is thin, and the thresholds that actually gate carrier eligibility are not public at all. Hold the ISA and the POD for every palletised inbound, and the disputes that follow become documentation problems instead of arguments. From there, follow the shipment through end-to-end FBA tracking.