Amazon prep intake checklist: what a 3PL needs before touching your first unit
Amazon Prep Intake Checklist: What a 3PL Needs Before Touching Your First Unit
Before a 3PL can prep a single unit for Amazon, it needs a complete set of product identifiers, packaging specifications, label assets, carton logic, and acceptance criteria. Starting prep without these inputs doesn’t create speed — it creates variation that produces inbound rejects.
The intake checklist exists for a simple reason: every assumption a prep team makes in the absence of a complete brief translates into either a rework loop or a compliance failure. Both are expensive. Both are preventable. Neither shows up in the prep rate.
Why Intake Completeness Matters Before Day One
The failure mode in Amazon prep is almost never a floor execution problem. It’s a specification problem — missing, incomplete, or outdated inputs that force the prep team to guess, improvise, or stop and ask. Each of those paths has a different cost, and none of them produce a correct unit without some additional work.
A unit prepped to a specification that was assumed, not confirmed, produces one of three outcomes. It passes because the assumption was right — this provides false confidence that the intake process works. It fails at Amazon receiving — this generates a defect, a chargeback, or an unplanned removal that costs more than the prep. Or it fails after delivery — a customer receives a unit with missing parts, incorrect labeling, or packaging that doesn’t meet the enforced standard, producing a return or an account health flag. The third outcome is the most expensive and the hardest to trace back to the intake gap that caused it.
Prep specification: A complete written brief defining how each SKU must be prepared for Amazon inbound, including unit-level identifiers, packaging requirements, labeling positions and assets, carton configuration logic, and the acceptance criterion for a completed unit. Without a prep specification, prep is not a controlled process — it’s informed guessing.
The intake process sets the specification before the first unit is touched. It is not a formality. It is the control point that determines whether prep produces consistent, compliant output or a variable one.
Block 1: Product Identifiers
The first category of intake inputs establishes the identifier hierarchy for each SKU. This is the foundation for every labeling and scanning step in the prep workflow.
FNSKU (Fulfillment Network Stock Keeping Unit): The Amazon-specific barcode that ties a unit to a specific seller’s inventory in the FC. Every unit entering Amazon under FBA must carry an FNSKU label. FNSKU values are unique per seller per ASIN — the same product sold by two different sellers has two different FNSKUs, and the same seller’s product in two different conditions (New, Used-Like New) has two different FNSKUs.
For each SKU in scope, the intake requires: the FNSKU value and a print-ready label file or a confirmed print template with dimensions and font size. It also requires the manufacturer barcode configuration — whether the FNSKU is applied over the manufacturer barcode (as is typically required) or whether the manufacturer barcode is suppressed at source. And it requires the ASIN, parent ASIN if variational, and the product condition code (New being most common for prep flows).
Identifier drift — where the FNSKU in the prep team’s system doesn’t match the FNSKU printed on the label, or where a new variant is added without a corresponding identifier update — is the single most common cause of inbound plan mismatches. A unit scanned into a plan it doesn’t belong to creates a receiving discrepancy on Amazon’s side that generates a defect and may trigger a hold. The only prevention is verification: the FNSKU on the label is confirmed against the inbound plan before the first carton is closed.
Block 2: Packaging Requirements and Materials
Packaging requirements define how each unit must be physically prepared for Amazon’s fulfilment environment. These requirements vary by product type and are enforced at receiving and at the FC.
The intake must confirm the packaging category for each SKU. Common categories relevant to prep include: poly-bagged (loose items that require a suffocation warning if the bag opening exceeds a defined size), bubble-wrapped or padded (fragile items that require protection meeting a drop test standard), boxed or double-boxed (items that ship in their original packaging but require an outer carton for FC handling), sets or multi-packs (two or more units sold as a single item, with a “Sold as Set” sticker and packaging that prevents separation), and expiry-dated items (products with a best-before or use-by date that must be visible and meet Amazon’s minimum shelf life requirements at receiving).
For each packaging category, the brief must specify the exact material: bag thickness if poly-bagging, bubble density and wrap coverage if padded, box dimensions and flute grade if double-boxed. A prep team working with “bubble-wrap it” as their specification will produce a range of outcomes. A prep team working with “two layers of 5/16” bubble, secured with tape at each seam, must not rattle when shaken” produces a consistent output.
The intake also confirms which packaging step requires a QC check before the unit moves to labeling. For fragile items, the check is typically a rattle test. For sets, it’s a component count. For expiry items, it’s a date check against the minimum shelf life requirement. The checkpoint exists not to slow the floor but to catch errors at the step where they’re cheapest to fix.
Block 3: Label Assets and Placement
Label assets are the physical outputs of the identifier block. The intake confirms that the correct assets are available in the correct format before prep begins, and that placement instructions are written, not assumed.
Label assets checklist for each SKU: FNSKU label file in a format compatible with the label printer in use (ZPL for Zebra, PDF for thermal, confirming dimensions), any additional Amazon-required labels (suffocation warning, fragile, this way up, sold as set, do not separate), and any seller-required inserts or cards that the prep spec includes.
Placement rules must be explicit. The FNSKU label placement on a unit is not a judgment call — it needs to cover the manufacturer barcode without obscuring expiry dates or regulatory markings, and it needs to be scannable from the orientation the FC scanner will encounter it. For items with multiple barcodes, the brief must specify which barcodes get covered and which stay visible.
The most common placement error in prep flows is applying the FNSKU label in a location that passes visual inspection but fails an FC scanner because the angle or surface creates a scan ambiguity. Catching this requires a scan test during the pilot run — not an assumption that if the label prints correctly, it will scan correctly in every context.
Label version control is a separate requirement. When an FNSKU changes — because the condition code changes, because a variant is restructured, because the seller account changes — the label file in use must be updated before any new units are prepped. A prep team working from a stale label file applies labels that route units to the wrong inventory state or plan. Version control means the label file is tied to a specific product version, updates require a formal change request, and the outgoing version is archived, not just overwritten.
Block 4: Carton Logic and Inbound Plan Configuration
Carton configuration is where prep outputs connect to Amazon’s inbound receiving process. Errors at this level don’t just create a single bad unit — they create an inbound plan discrepancy that generates receiving delays, defects, and sometimes a full reconciliation request.
The intake must confirm carton configuration rules for each SKU: units per carton (a fixed number, not “as many as fit”), carton weight and dimension limits, and whether the product requires single-SKU cartons or can be mixed-SKU. Amazon’s inbound plans are built around declared carton contents — a carton sent with 24 units declared but 22 physical creates a receiving discrepancy that must be investigated before the inventory is confirmed available.
Box content accuracy is the companion requirement. Every carton must have a box content label that accurately reflects what is inside — not what was intended, not what was in the last shipment, but what is physically in that specific carton at the moment it’s closed. For prep flows with high SKU counts or mixed cartons, box content labels are generated from a scan, not printed from a template — this is the only way to confirm that the physical contents match the declaration.
Inbound plan configuration also requires the prep team to know which shipment plan the units belong to before cartons are closed. A unit that gets into the wrong plan — because an inbound plan was modified after prep started, or because two overlapping plans share the same SKU — requires a full unpick or a rework at the destination. The control is simple: inbound plan confirmation before prep starts, not after the first carton is closed.
Block 5: Approvals, Change Control, and the Pilot Run
Intake is not complete until the specification has been reviewed and approved by someone on the seller’s side with authority to sign off. This is the last control before production begins.
The approval record serves two purposes. First, it confirms that the specification the 3PL will work from is the one the seller intends — not an assumption, not a verbal summary, but the written brief as documented. Second, it creates a version record: if the specification changes, the change is against a documented baseline, and both parties know what changed and when.
Change control applies to the specification after approval: new variants, label version changes, packaging modifications, carton logic adjustments. Each change requires a formal update to the spec, a review, and a re-approval before the new version goes into production. A verbal update passed informally — “just use a bigger box for the new size” — has no version record, creates ambiguity for the prep team about which version they’re working from, and produces the kind of error that’s very difficult to trace after the fact.
The pilot run is the final step before full production. Before prepping any volume, a small batch of units — typically 5 to 10, depending on SKU complexity — is prepped to the full specification and reviewed for compliance. The review covers: FNSKU label placement and scan confirmation, packaging completeness and protection standard, box content accuracy, carton weight and dimension, and any SKU-specific requirements from the brief. The pilot run is not a test of the team — it’s a test of the specification. If the pilot reveals a gap, the specification is updated before production begins.
A pilot run that passes produces two outputs: confirmation that the specification is complete and the team is aligned, and a reference sample that can be used for ongoing QC as production scales.
Frequently Asked Questions
Q: What happens if prep starts before the intake is complete? A: Prep without a complete specification defaults to assumptions. Assumptions in Amazon prep produce one of three outcomes: the unit happens to be correct (which provides false confidence), the unit fails at Amazon receiving and generates a defect or removal, or the unit passes receiving but fails after delivery. All three outcomes are worse than the delay caused by completing the intake properly before the first unit is touched.
Q: How specific do carton configuration rules need to be? A: Specific enough that the prep team has no decision to make on the floor. Units per carton should be a fixed number, not a range. Weight and dimension limits should be explicit, not inferred from the product size. Whether a carton can be mixed-SKU should be stated, not assumed from what was done previously. Any ambiguity in the carton spec will be resolved by the prep team using judgment — and judgment produces variation, which produces inbound discrepancies.
Q: What is a pilot run and why is it required before full production? A: A pilot run is a small batch of units — typically 5 to 10 — prepped to the full specification and reviewed against every point in the brief before production begins at volume. It tests the specification, not the team. If a label placement rule is wrong, the pilot catches it on 10 units rather than 500. If a packaging step was ambiguous, the pilot surfaces it before it becomes a pattern. Skipping the pilot saves time once. Catching a specification error in production costs time every time the error repeats until it’s fixed.
Q: Who should approve the intake specification before prep begins? A: Someone on the seller’s side with operational authority — meaning they can confirm that the FNSKU values are correct, the packaging requirements match what Amazon has enforced for this product, the carton configuration aligns with the active inbound plan, and the label assets are the current versions. This is not a task for whoever is available to sign off; it’s a task for whoever will own the consequences if the specification is wrong.
Q: What happens when an FNSKU changes after prep has already started? A: All prep stops for that SKU until the new label file is confirmed, the change is documented, and the outgoing label version is archived. Any units prepped under the old FNSKU that are not yet in transit need to be assessed — if they’re going into a plan built for the old FNSKU, they may need to be relabeled. Units that are already in transit under the old plan are typically fine if the old FNSKU is still valid; if the FNSKU changed because of an account or condition code change, a removal or reconciliation may be required. FNSKU changes should trigger a formal change request, not an informal label swap.
Q: How long does a complete intake typically take? A: It depends on the number of SKUs, the complexity of the packaging requirements, and whether the seller has all the required assets ready at the start. A simple single-SKU intake with a standard packaging requirement and ready label files can be completed in a day or two. A multi-SKU intake with variational FNSKUs, mixed packaging categories, and label assets that need review typically takes a week or more. The time investment at intake is recovered in the absence of rework, rejects, and inbound plan discrepancies in production.
If you’re preparing to onboard Amazon prep with a 3PL — or reviewing your current prep setup to identify spec gaps before your next inbound — share your product profile and channel setup. We’ll map the intake requirements and identify where the specification is incomplete before the first unit is touched.