Amazon FBA prep from China should be planned before the supplier ships mixed SKUs. In this scenario, 12 SKUs were received, checked with basic QC photos, separated by SKU, matched to FNSKU/carton-label rules and prepared for FBA route review.
Amazon FBA Prep Case Quick answer
Amazon FBA prep from China case study
Amazon sellers whose supplier goods are still in China before FBA delivery. Orders that need SKU separation, label visibility checks and carton measurement before freight. Sellers combining buying support, warehouse checks, FBA prep scope and DDP/freight route review.
Sellers missing Amazon marketplace, FBA warehouse code or address, SKU/FNSKU data or carton rules. Requests that need complex kitting, poly bagging, insert handling or detailed inspection without a separate quote. Restricted or branded-sensitive goods sent without disclosure or compliance documents.
Product links, quantity per SKU, Amazon marketplace and FBA warehouse code or address. FNSKU files, carton-label rules, SKU separation notes and whether simple labeling is needed. Carton count, gross weight, L/W/H, cargo value and restricted-cargo notes.
Warehouse intake records, SKU count, basic QC photos and visible product condition. FNSKU/carton label readability, SKU separation, carton data and packing strength. Whether FBA prep, DDP, standard freight or manual route review is the right next step.
Confirm label and SKU data before warehouse work begins. Separate standard prep from extra tasks such as relabeling, poly bags, inserts, pallets or carton replacement. Use final carton data and FBA address before route review.
Warehouse intake photos, SKU count sheet and basic QC photos. FNSKU/carton-label review notes and final carton measurements. FBA prep scope, freight quote handoff and tracking support message.
Case facts
| Fact | Scenario detail |
|---|---|
| Buyer scenario | Amazon seller prepared 12 SKUs from China suppliers before FBA warehouse delivery. |
| Product type | Mixed small goods requiring SKU separation and label visibility checks. |
| Source platform | Supplier order plus FNSKU and carton-label files from the seller. |
| Shipping route | FBA DDP or freight route screened after carton and label review. |
JTLGO actions
- JTLGO checked received SKUs against the seller list and captured basic QC photos.
- FNSKU and carton-label visibility were reviewed before carton closure.
- Cartons were measured after standard repacking and SKU separation.
- Extra FBA prep tasks were separated from standard buying support to avoid fee confusion.
Manual review triggers
- FBA warehouse code, SKU/FNSKU, carton labels or final carton data is missing.
- The order needs relabeling, kitting, bundling, poly bags, inserts, target carton sizes or pallets.
- Cargo is battery, liquid, powder, magnetic, branded-sensitive, oversized or certificate-sensitive.
Result
The seller received a FBA handoff package with SKU status, QC photos, label notes, carton data, prep-scope boundary and freight route review input.
What other buyers can learn
- FBA prep must start from SKU/FNSKU and warehouse-code data, not only product photos.
- Standard buying support and extra FBA prep tasks should be priced separately.
- FBA delivery needs tracking and exception handoff because Amazon intake can lag carrier delivery events.
FAQ
What is included in basic FBA prep review?
It can include intake records, basic QC photos, SKU separation, label visibility checks and carton measurement.
Does the USD 10 / 3% fee include every FBA prep task?
No. Standard buying support follows the USD 10 / 3% rule, while labeling, kitting, poly bags, pallets and special packing are quoted by scope.
What information is required before FBA prep?
Send product links, SKU quantities, FNSKU files, warehouse address or code, carton-label rules and cargo attributes.
Recommended next steps
Amazon FBA Prep Open the related JTLGO workflow Amazon FBA from China Hub Open the related JTLGO workflow Amazon FBA DDP Shipping Open the related JTLGO workflow China Order Fulfillment Open the related JTLGO workflow Pricing Open the related JTLGO workflow Contact JTLGO Open the related JTLGO workflow