4 Step Carrier Central Playbook for Amazon FBA Delivery Appointments

If you use your own carrier, book the appointment in Carrier Central (or FAST where supported) right away and verify that your PO, ARN, and BOL data match your box labels. If Amazon does not respond, resubmit with a future delivery window and open a Seller Support case with timestamps attached. Appointments are processed by a queue tied to dock capacity, so clean data submitted early beats fast escalation every time.

TL;DR:

• Using your own carrier requires matching PO, ARN, BOL, and count data exactly before booking to avoid rejection and delays.
• Automated scheduling via APIs or Carrier Central depends on carrier partnership, but manual resubmissions with clean data outperform repeated follow-ups.
• Confirm all shipment identifiers against labels and plans prior to dispatch to prevent validation errors that impact appointment success.
• When requests are rejected or ignored, resubmitting with a new window and opening a case with timestamps improves chances of confirmation.
• Partnered forwarders with experience in Carrier Central submissions reduce paperwork errors and help maintain inbound schedules during peak seasons.

Step-by-step booking: Carrier Central, FAST, and SP-API scheduling flows

Carriers that are not partnered with Amazon request appointments through the Carrier Central portal. Some lanes support FAST for faster slot confirmation, and sellers with their own systems can automate parts of the process through the Selling Partner API. Picking the right path depends on whether your carrier is Amazon-partnered, which largely determines whether scheduling happens automatically or sits in a manual queue.

The sequence matters as much as the tool:

1. Create the inbound shipment plan in Seller Central and generate box labels before contacting the carrier.
2. Confirm the destination fulfillment center or AWD distribution center code shown on the plan.
3. Have the carrier submit the appointment request with the matching FC identifier, shipment IDs, and PO information.
4. Watch for a confirmation status before dispatching the truck.

For AWD DC deliveries using your own carrier, the carrier must book through Carrier Central, and shipments without a scheduled appointment can be turned away at the dock.

On the API side, scheduleSelfShipAppointment lets systems schedule or reschedule self-ship appointments programmatically, though some scheduling behaviors are marketplace-specific. Because of those marketplace gaps, many sellers still run manual Carrier Central submissions alongside automated calls rather than relying on one method exclusively. Amazon-partnered carriers typically get appointments auto-managed as part of the partnered network, while non-partnered carriers queue like everyone else and depend on clean, early submissions to get a slot.

Exact fields to provide: PO, ARN, PRO, BOL, counts, and SCAC rules

Portal rejections almost always trace back to a mismatched or missing field. Before submitting, confirm every identifier against the shipment plan and the physical labels on the pallets or cartons.

• Purchase order number or PO list, matched exactly to what is printed on the box labels.
• ARN or shipment ID tied to the inbound plan you created in Seller Central.
• PRO number and bill of lading (BOL) for full truckload or LTL freight.
• Carton, pallet, and unit counts that match what the trailer actually carries, flagged as palletized or floor loaded.
• SCAC or vendor code formatted to the carrier account on file, plus a contact phone number and USDOT or MOT identifier where required.
• Trailer number within the character limit the portal enforces.

Carrier Central’s support documentation lists specific field constraints, including SCAC formatting and trailer number length limits, and warns that appointment defects tied to incorrect data can affect a carrier’s performance metrics. A quick pre-submission check against this list catches the majority of validation errors before they cost you a slot.

When an appointment is ignored or rejected

Silence from the portal does not mean the shipment is lost, but it does mean you need to act rather than wait.

1. Resubmit the appointment request with a future-dated delivery window and double-check that PO, PRO, and BOL fields are corrected.
2. Open a Seller Support case immediately, attaching screenshots of both submission attempts with timestamps.
3. Log the case ID along with the carrier’s original and resubmitted confirmation numbers for your own compliance records.
4. If the shipment is time-sensitive, consider rerouting to an Amazon-partnered carrier or splitting the load to protect part of the inbound SLA.

Sellers report that Amazon does not proactively chase approvals for non-partnered carriers. Requests sit in a queue the FC works through based on dock capacity, which is why resubmission with clean data outperforms repeated follow-up calls. Late cancellations and last-minute edits count against a carrier’s weekly performance metrics and can eventually restrict delivery privileges, so treat every submission as final before you send it.

Pro Tip: Keep a shared folder per shipment with every portal screenshot, case number, and carrier confirmation, so a stalled appointment never depends on one person’s memory.

Lead times, peak-season scheduling, and practical tips to avoid stockouts

Ocean freight generally needs longer planning windows than air or parcel, and Amazon-partnered carriers tend to get priority handling that makes them a safer choice for shipments protecting a launch date or a promotion.

• Avoid combining purchase orders that have different delivery windows into one appointment request.
• Validate counts and label data against the shipment plan before the truck is loaded, not after.
• Build in contingency buffer days for any shipment feeding a top-selling ASIN.
• During peak season, stagger arrival dates across multiple appointments rather than concentrating volume on one date.
• Keep a backup shipment ready to book if your primary appointment stalls or gets rejected.

Documentation delays upstream, such as customs holds, compound appointment risk because a late-arriving container forces a rushed, error-prone submission instead of a planned one.

Carrier Central’s legal stance and what it means for seller risk management

Carrier Central’s legal pages state the appointment system is provided as is, with Amazon disclaiming warranties and treating appointments as non-binding. In practice, that means a confirmed slot is not a guarantee of receipt.

Document every submission attempt and keep portal timestamps and Seller Support case numbers on file. Build contingency plans for critical shipments rather than assuming a scheduled appointment removes receiving risk entirely.

How a managed forwarder reduces appointment friction and inbound risk

Much of the appointment chaos sellers deal with starts upstream: missing BOLs, mismatched counts, or paperwork that arrives after the truck does. ForwarderOne’s DDP service bundles customs clearance and documentation into a single workflow, which cuts down on the scramble to find a PRO number or correct PO list at the last minute. A service team member can track the shipment status to help avoid dock-side emergencies.

When evaluating any forwarder for appointment-sensitive freight, ask:

• How much portal experience does the team have with Carrier Central submissions specifically?
• Can they supply every required identifier (PO, ARN, BOL, counts) without back-and-forth?
• What is their track record on on-time delivery, and how do they document it?

A forwarder that handles documentation consistently reduces the resubmission loops that eat into your receiving window. For more on vetting one, see how to choose a freight forwarder.

Four operational changes to adopt this quarter

Standardize your appointment data before it ever reaches a carrier, and require a confirmation screenshot every time one is submitted. Build buffer shipments for anything tied to a top ASIN. When stock is tight, lean on a partnered carrier or a forwarder who can negotiate expedited review rather than hoping a manual resubmission lands faster. A reusable template mapping your TMS fields to Carrier Central’s fields will save more hours than any amount of follow-up calling.

Official portal pages and API docs for quick reference

• Amazon Carrier Central support for portal access and carrier appointment guidance.
• Amazon Selling Partner API: scheduleSelfShipAppointment for supported programmatic scheduling workflows.

FAQ

What does it mean when Amazon has a delivery appointment?

A delivery appointment is a scheduled window during which a carrier is expected to deliver a shipment to a specific fulfillment center or AWD distribution center. It is requested through Carrier Central or, for some marketplaces, through SP-API endpoints like scheduleSelfShipAppointment.

How do I make an Amazon delivery appointment?

Create your inbound shipment plan and box labels in Seller Central first, then have your carrier submit the appointment request through Carrier Central with matching PO, ARN, and BOL data. Amazon-partnered carriers often have appointments managed automatically, while non-partnered carriers request a slot that is processed based on dock capacity.

Is it better to do FBM or FBA?

The right choice depends on your margins, order volume, and how much control you want over fulfillment: FBA shifts storage and shipping to Amazon in exchange for fees, while FBM keeps more control but adds operational work. Sellers with appointment-sensitive FBA shipments often work with a forwarder like ForwarderOne to keep inbound freight moving reliably.

What does "delivery appointment scheduled" mean?

This status means the FC or AWD DC has accepted the carrier’s requested time window and the shipment is expected to arrive then. It is not a binding guarantee, since Carrier Central’s legal terms state the system is provided as is and appointments can still be changed or canceled.

What happens if my carrier never gets an appointment response?

Resubmit the request with a future delivery window and corrected data, then open a Seller Support case documenting both attempts. Appointments are processed through a queue based on dock capacity, so earlier, cleaner resubmissions tend to resolve faster than repeated escalation calls.