Amazon Inbound Carton Data Handoff: Supplier to 3PL Checklist

Amazon Inbound Carton Data Handoff: Supplier to 3PL Checklist

Your supplier sent a packing list. Your 3PL needs it in a different format. Amazon’s shipment plan needs carton-level data, not just SKU totals. Somewhere between the factory floor and the FBA receiving dock, the carton content data has to be re-keyed — and every re-key is a chance for a typo, a swapped SKU, or a wrong quantity.

If the data handoff is sloppy, the 3PL applies the wrong labels, the shipment plan shows the wrong cube, and Amazon flags the inbound at receiving — or worse, accepts it and charges you for the wrong inventory.

This guide walks through how to move carton-level data from a China supplier, through a 3PL prep center, and into an Amazon shipment plan in a way that survives every handoff.

Important: This article is operational guidance, not legal advice. Whether a specific carton-data format is sufficient, who bears the cost of a relabel or a rejected shipment, and what an Amazon FBA receiving decision will or will not cover depends on your seller-account agreement, Amazon’s policies at the time, applicable law, and the actual facts. No checklist can guarantee FBA acceptance, account-health protection, or any other outcome. For anything material, ask an appropriately qualified independent adviser to review the actual evidence.

Quick Answer: What Is the Amazon Inbound Carton Data Handoff?

The carton data handoff is the structured transfer of carton-level information from the supplier’s master packing list to the 3PL prep center to the Amazon shipment plan. It typically includes:

• SKU (FNSKU or ASIN) — the unit identifier Amazon expects.
• Quantity per carton — how many units of each SKU are in each carton.
• Carton count per SKU — how many cartons contain each SKU.
• Carton dimensions and weight — for Amazon’s carton-level weight and cube requirements.
• Label type per SKU — who is applying the label (supplier, 3PL, or seller), and where it sits on the carton.
• Prep requirements per SKU — polybag, bubble wrap, suffocation label, fragile sticker, expiration date, set packaging.
• Pallet configuration — how cartons are stacked, wrapped, and labelled on the pallet.

The handoff is the workflow that turns the supplier’s master packing list into data the 3PL can prep against and Amazon can receive against — without re-keying by hand at each step.

Why the Handoff Breaks in Practice

Most Amazon inbound carton data problems are not caused by bad suppliers or careless 3PLs. They are caused by three different data shapes that have to be reconciled at each handoff:

1. Supplier’s master packing list — usually a Chinese-language Excel or PDF with carton numbers, SKU codes (often internal codes, not FNSKU), quantity per carton, and total cartons.
2. 3PL’s prep template — usually an English-language spreadsheet with FNSKU, quantity per carton, prep requirements, label assignment, and a specific column layout.
3. Amazon’s shipment plan — built in Seller Central or via SP-API, requiring FNSKU, quantity per outer carton, expiration date (where applicable), box content info, and carton-level weight and dimensions.

Each transition is a chance to introduce a typo, a unit mismatch (eaches vs. cartons), a wrong FNSKU, or a missing prep requirement. Multiply by 50 SKUs and 200 cartons, and the error surface is large.

The Four Handoff Steps

A practical handoff has four steps. Each step has a defined input, a defined owner, and a defined output.

Step 1: Supplier → Agent (China-side)

• Input: the factory’s master packing list, usually as a Chinese-language Excel or PDF.
• Owner: the supplier’s merchandist or the buyer’s China-side agent.
• Output: a reconciled carton-level spreadsheet with SKU, quantity per carton, carton count, carton dimensions, carton weight, and any prep the supplier has already done.
• Risk to manage: internal SKU codes (not FNSKU), Chinese-language column headers, missing weight or dimension data, and inconsistencies between the master list and the actual sealed cartons.

Step 2: Agent → Buyer / Seller (commercial owner)

• Input: the reconciled carton-level spreadsheet from Step 1.
• Owner: the buyer-side team or the seller-side operations lead.
• Output: an FNSKU-mapped version of the spreadsheet, where each supplier SKU is paired with the correct FNSKU, prep type, label assignment, and any Amazon-specific requirement (e.g. expiration date, lot number, made-in-country, battery declaration).
• Risk to manage: FNSKU typos, wrong prep types, missing or wrong expiration dates, lot numbers that do not match Amazon’s expected format.

Step 3: Buyer / Seller → 3PL Prep Center

• Input: the FNSKU-mapped spreadsheet from Step 2, ideally in the 3PL’s preferred template.
• Owner: the seller-side operations lead or the 3PL account manager.
• Output: the 3PL’s confirmed prep plan: which cartons need labels, which need polybags, which need set packaging, and which can ship as-is.
• Risk to manage: the 3PL’s prep plan diverging from the seller’s intent (e.g. 3PL assumes supplier applied labels when supplier did not), or the 3PL’s template requiring fields the seller did not populate.

Step 4: 3PL → Amazon Shipment Plan

• Input: the 3PL’s prep-stage carton manifest, with the final FNSKU-to-carton mapping after prep and labeling.
• Owner: the 3PL or the seller (depending on who has seller-central access).
• Output: the Amazon shipment plan with carton-level weight, dimensions, and box content info populated.
• Risk to manage: the shipment plan showing the wrong cube, missing box-content info, or a quantity that does not match what the 3PL actually loaded.

The data must survive all four steps without silently breaking.

The Eight Data Fields That Must Survive the Handoff

For a typical Amazon FBA inbound, eight data fields must remain consistent from the supplier’s master packing list to the Amazon shipment plan. If any of them silently change, the inbound is at risk.

1. FNSKU — the unique Amazon identifier; never the supplier’s internal SKU or the ASIN alone.
2. Quantity per carton — must be the actual count, not an estimate or a “per inner box” number.
3. Carton count per SKU — must match the master packing list and the actual sealed cartons.
4. Carton weight — must be within Amazon’s tolerance for the chosen shipment plan; if not, the carton may be reclassified or rejected.
5. Carton dimensions — must be within Amazon’s tolerance; oversized or underweight cartons are a frequent rejection cause.
6. Label type and placement — FNSKU label, suffocation label (if polybagged), made-in-country, expiration date, fragile sticker, orientation arrows.
7. Prep type — polybag, bubble wrap, set packaging, adult-only marking, battery documentation.
8. Hazardous or restricted status — anything that triggers Amazon’s dangerous-goods review or restricted-product review must be flagged before the shipment plan is created.

For each field, the rule is the same: the value at the Amazon shipment plan must equal the value on the actual carton, must equal the value on the supplier’s master packing list, and must equal the value the 3PL prepped against.

Worked Example: A 12-SKU Apparel Order

Imagine a buyer is importing a 12-SKU apparel order from a China trading company, prepping through a US-based 3PL, and shipping to Amazon FBA. Here is how the four handoff steps map to a single SKU:

• Supplier SKU: TC-220-RED-M
• FNSKU: X001ABC123
• Quantity per carton: 24
• Cartons for this SKU: 4
• Carton weight: 8.2 kg
• Carton dimensions: 50 × 40 × 30 cm
• Label type: 3PL applies FNSKU; supplier applies made-in-country
• Prep: polybag with suffocation label (each unit)
• Hazardous: no

The data must be:

If any cell changes silently between Step 1 and Step 4, the inbound is at risk.

Common Failure Modes and How to Catch Them

The data handoff is most fragile at three points: the supplier-to-agent transition, the agent-to-3PL transition, and the 3PL-to-Amazon transition.

Failure 1: FNSKU mismatch at the 3PL

• What it looks like: the 3PL applies labels from a previous shipment, or labels for a different FNSKU than the seller’s shipment plan expects.
• How to catch it: the seller-side team reconciles the 3PL’s prep-stage carton manifest against the seller-central shipment plan before the inbound ships. A simple VLOOKUP or a CSV diff is enough.

Failure 2: Quantity per carton drift

• What it looks like: the supplier packed 24 units per carton but the master list shows 20, or the 3PL repacked to 30 to optimize cube and did not update the shipment plan.
• How to catch it: the 3PL’s prep-stage carton manifest must match the actual sealed cartons, not the original master list. A photo-based QC photo evidence packet makes the actual count visible.

Failure 3: Carton weight or dimension outside Amazon tolerance

• What it looks like: Amazon’s shipment plan rejects the carton for being over the max weight or over the max dimension for the chosen box type.
• How to catch it: the seller-side team runs Amazon’s “estimate” or “packaging” template before the cartons are sealed, not after. Re-trying the shipment plan at the last minute is a common cause of inbound delays.

Failure 4: Missing prep (polybag, suffocation label, set packaging)

• What it looks like: the supplier did not apply the polybag; the 3PL assumed the supplier had; Amazon flags the inbound at receiving for missing prep.
• How to catch it: the seller-side team explicitly states which prep the 3PL is responsible for, in writing, in the handoff spreadsheet. Verbal assumptions are not prep instructions.

Failure 5: Expiration date or lot number error

• What it looks like: the supplier applied an expiration date in the wrong format, or the lot number on the unit does not match the lot number on the carton.
• How to catch it: the seller-side team specifies the exact format Amazon expects (typically MM/DD/YYYY for US FBA), and the 3PL verifies a sample carton before running the full prep.

How the Handoff Connects to the Broader Workflow

The carton data handoff is one piece of the FBA prep workflow. It works best when it connects to:

• The approval responsibility matrix that names who owns each FBA prep and labeling decision. See the China sourcing approval responsibility matrix.
• The FBA prep and labeling checklist for 2026, which lays out who owns prep and labeling after Amazon ended its US FBA prep and labeling services. See the Amazon FBA prep and labeling 2026.
• The deviation log that catches mid-production spec, material, or label changes before they reach the 3PL. See the China supplier sample change deviation log.
• The supplier verification record that justified working with this supplier in the first place. See the 1688 supplier verification checklist.
• The inspection report that confirmed the SKU and quantity before prep. See the 1688 inspection service guide.

The carton data handoff is the connective tissue between the supplier-side workflow and the Amazon-side workflow. Without it, each side sees the order differently.

Carton-Data Handoff Checklist (Pre-Shipment)

Use this checklist as the operational pass/fail list before the inbound leaves the 3PL dock. Tick each item; if any item is not ticked, do not move the shipment forward.

Supplier side
– [ ] Master packing list delivered (Excel or PDF) with carton number, supplier SKU, quantity per carton, total cartons, gross weight per carton, dimensions per carton.
– [ ] Chinese-language column headers translated or paired with an English-language header row.
– [ ] Internal SKU codes flagged so the agent knows which column maps to FNSKU.
– [ ] Prep the supplier is responsible for (e.g., polybag, made-in-country label, inner box) called out in writing.

Agent / China-side
– [ ] Supplier SKU → FNSKU mapping populated, with prep type and label assignment per SKU.
– [ ] Carton count cross-checked against the supplier’s production report and the buyer’s PO.
– [ ] Carton weight and dimensions reconciled; any carton over the chosen Amazon box-type limit flagged before sealing.
– [ ] Expiration date format and lot number format specified for the 3PL in writing.

Buyer / Seller side
– [ ] Amazon shipment plan created or assigned; FNSKU mapping in the plan matches the 3PL prep template.
– [ ] Box content info and any program-specific fields (AWD, SEND, etc.) populated against current Amazon guidance at the time of shipment.
– [ ] Final FNSKU label file supplied to the 3PL with placement rules per SKU.

3PL prep center
– [ ] Prep-stage carton manifest matches the seller-side FNSKU mapping and the Amazon shipment plan row-for-row.
– [ ] Sample carton prepped and verified against the spec sheet before the full run.
– [ ] Photo evidence of prepped cartons (FNSKU label, expiration date, polybag, suffocation label) attached to the shipment file.
– [ ] Final pallet wrap, label placement, and loading photo captured before the truck leaves.

Final reconciliation (before truck leaves the 3PL)
– [ ] Carton manifest CSV diffed against the Amazon shipment plan — zero row mismatches.
– [ ] Total carton count per SKU in the manifest equals the actual sealed cartons on the pallet.
– [ ] Pallet-level FNSKU label file attached to the shipment record.

If any box above is unchecked, the carton data handoff is not complete. Send it back, do not forward it.

What the Handoff Will Not Do

A carton data handoff is a workflow, not a guarantee. It will not:

• Force Amazon to accept a non-compliant inbound.
• Override the seller-account agreement or Amazon’s policies at the time.
• Substitute for an independent prep or inspection when those were the right tools.
• Eliminate the need for a real Amazon shipment plan and a real FNSKU label file.
• Recover an inbound that was already rejected at the FBA dock.

What the handoff will do is make the ordinary workflow much more likely to succeed, and make any extraordinary problem much easier to diagnose and respond to.

How Style Sourcing Can Support the Carton Data Handoff

Style Sourcing does not replace your decision-making, your seller-central access, or your 3PL relationship. Within the China-side workflow, the team can:

• Reconcile the supplier’s master packing list into a clean, English-language, carton-level spreadsheet.
• Coordinate the FNSKU mapping with the seller-side team before the 3PL handoff.
• Build a 3PL-ready template that matches the prep center’s preferred format, with FNSKU, quantity per carton, prep type, and label assignment populated.
• Coordinate with the 3PL to verify a sample carton before the full prep run, especially for expiration dates, lot numbers, and made-in-country labels.
• Help organize the carton data, the prep-stage manifest, the loading photo, and the FNSKU label file into one evidence file per shipment.

For anything material — especially any account-health, fee, chargeback, or compliance question — ask an appropriately qualified independent adviser to review the actual evidence.

Frequently Asked Questions

Does the supplier need to know the FNSKU?

Usually no. The supplier works with the buyer’s SKU (their internal code or the seller’s commercial SKU). The FNSKU mapping happens at the agent or seller side. What the supplier must know is which units go into which cartons, and which prep they are responsible for (e.g. polybag, made-in-country label).

What if the 3PL has its own template?

Use the 3PL’s template, but populate it with the seller-side FNSKU mapping and prep requirements. The 3PL’s template is the operational format; the seller’s intent is the content.

What is the most common handoff error?

In our experience, the most common error is a quantity-per-carton mismatch — the master list says one number, the 3PL repacks to another, and the Amazon shipment plan reflects the original number. A photo-based QC photo evidence packet at the master-list stage makes the original count visible and reduces this error.

How is this different from the FBA prep checklist?

The prep checklist covers who applies labels and prep. The carton data handoff covers how the underlying carton-level data moves from the supplier to the 3PL to Amazon without silently breaking. The two are linked — see the Amazon FBA prep and labeling 2026 guide for the prep and labeling structure.

What if the seller is also the buyer and the agent?

The roles collapse, but the data still has to survive the same transitions: master packing list → FNSKU-mapped spreadsheet → 3PL prep template → Amazon shipment plan. The owner of each step may be the same person, but the data shapes are still different and the error surface is the same.

Can the 3PL create the Amazon shipment plan?

Often yes — many 3PLs have seller-central access or SP-API integrations. Whether the 3PL creates the plan or the seller does, the seller-side team must verify the final carton manifest against the actual sealed cartons before the inbound ships.

Does the carton data handoff apply to AWD, SEND, or other Amazon programs?

Yes, with program-specific tweaks. AWD (Amazon Warehousing and Distribution) and SEND (Supply Chain Network) have their own carton-level data requirements; the four-step structure (supplier → agent → 3PL → Amazon program) still applies, but the field names and tolerances differ. The structure is the same; the field map is program-specific.

What if Amazon’s policies change mid-shipment?

Re-run the carton data reconciliation against the new policy, especially for prep, labeling, and weight or dimension tolerances. The handoff is a snapshot; Amazon’s policies are a moving target. The reconciliation must happen at the moment of the shipment, not at the moment of the order.

Source and Evidence Note

This article draws on operational patterns observed across Amazon FBA prep and labeling orders coordinated through Style Sourcing’s China-side workflow. The four-step handoff structure (supplier → agent → 3PL → Amazon) is a synthesis of common practice; specific field names, formats, and tolerances should be verified against Amazon’s current seller-central guidance at the time of shipment. The eight data fields listed are illustrative, not exhaustive; sellers should adapt the field list to their category, program, and Amazon’s policies at the time.