Good fulfillment starts before the first supplier carton reaches the warehouse. The receiving team needs to identify what arrived, the order process needs to know what can be sold, and the packing team needs to know what belongs in each parcel. A product title and a supplier invoice rarely answer every question.
Use this checklist to prepare a handoff for a China warehouse. It is a starting structure for an operating review, not a guarantee that every product, order platform, or shipping route is supported.
1. Create one identity for each sellable variant
Give every meaningful variant its own stable SKU. A different size, device model, color, or bundle configuration should be distinguishable in the records used by the store, supplier, and warehouse.
If those systems use different codes, provide a mapping instead of expecting the receiving team to infer a match. Keep the history of changed or retired codes so that old supplier labels do not silently point to a new product.
| Field | What to provide | Why it matters |
|---|---|---|
| Internal SKU | A unique identifier for the variant | Connects receiving, stock, and customer orders. |
| Supplier reference | Supplier code and purchase reference | Makes inbound differences traceable. |
| Product identity | Plain description, model, size, and color | Distinguishes similar-looking products. |
| Reference images | Clear, approved images of the variant and label | Supports practical identification. |
| Barcode or label rule | Actual format and placement, where used | Prevents inconsistent identification. |
| Unit information | Dimensions and weight with units stated | Supports handling and preliminary planning. |
| Finished packout | Packaging reference, dimensions, and weight | Supports route and handling review. |
| Stock status | Rules for available, held, damaged, or review stock | Prevents uncertain units entering orders. |
| Bundle components | Component SKUs, quantities, and versions | Defines when a complete set exists. |
| Product restrictions | Relevant materials, features, and known limitations | Flags issues requiring specialist or route review. |
2. Prepare the supplier delivery record
For each expected arrival, provide the supplier, delivery or purchase reference, component SKUs, expected quantities, carton details, and ready or arrival information. Agree how changes will be communicated if the supplier splits a delivery or substitutes packaging.
Do not combine several suppliers into one untraceable note. Receiving records should make it possible to identify where a shortage, damage report, or unexpected variant came from. The supplier consolidation overview explains the intended workflow for multi-supplier inventory.
3. Define checks that can actually be performed
“Check quality” is not a complete instruction. State the observable checkpoints, acceptable references, check depth, and action for an uncertain result. Distinguish a carton count, an appearance check, a sampled inspection, and an agreed unit-level procedure.
A visual check is not material certification or a substitute for required product testing. If compliance, labeling, or declarations require specialist review, identify the responsible party before the shipment. Do not invent descriptions or values to make an order easier to route.
The phone-case SKU scenario illustrates why a close visual match may still be insufficient for release.
4. Write the packing and exception rules
Provide the approved packaging sequence, insert version, multi-item handling, and any campaign conditions. Explain whether substitutes are permitted and who can authorize them. A reference photo is helpful, but it should support written instructions rather than replace them.
Document what happens when an order lacks a component or an address needs review. Decide whether to hold the entire order or follow a separately approved partial-shipment process. Record the processing stage after which a requested change may no longer be possible.
5. Test the order handoff before live release
Confirm the available intake method for your store or order system. Use clearly marked test orders to check variant mapping, a multi-item packout, unavailable stock, a change request, and the agreed tracking handoff. Do not send tests into live dispatch by accident.
The test should establish which record is authoritative and who owns each exception. It should not assume that an integration handles every update just because it can import a new order.
6. Keep the approved version visible
Assign an owner to the SKU file and record when a product, label, or packout rule changes. Confirm the transition between old and new stock before the change is applied. A current instruction with no effective date can be as confusing as an outdated one.
Use a secure, agreed channel for customer-level order information. For an initial inquiry, a redacted example is normally sufficient to explain the workflow without exposing personal data.
Review Fulnexa's operating standards and request an onboarding review with your draft SKU file. The aim is to agree a usable handoff before goods move, so that unclear instructions can be resolved while decisions are still easy to change.