Ecommerce fulfillment from China should be designed as five connected stages: receiving, storage, order processing, shipping, and returns. It is ready to operate only when product data, inventory status, packing rules, delivery choices, customer information, and exception ownership remain consistent across those stages. The right question is not “Can this warehouse ship orders?” but “Can every order be traced and controlled?”
Define the scope before sending inventory
Ecommerce fulfillment can serve a marketplace, an independent store, social commerce, wholesale replenishment, or several channels at once. Each channel may use different product identifiers, order fields, cancellation rules, packing requirements, and customer promises.
Create a scope document that states:
- legal seller and contracting entity;
- sales channels and destination markets;
- product catalog, variants, sets, and restrictions;
- expected inbound form and supplier booking method;
- customer-order profile and packaging requirements;
- required shipping services and tracking data;
- duties, taxes, importer, and destination-charge policy;
- customer-service, return, and refund responsibilities;
- reporting, evidence, approval, and escalation rules.
This document becomes the reference for onboarding, testing, and later changes. Without it, each team may interpret “fulfillment” differently.
Stage 1: Receive inventory against expected data
Receiving begins before the truck reaches the warehouse. Suppliers should use an advance notice or purchase-order reference that identifies expected SKUs, quantities, carton marks, and delivery details. The warehouse should record arrival separately from completed receiving.
Agree on the receiving depth. Carton-level receipt, unit count, visual condition check, dimensional capture, and detailed inspection are different services. When the actual goods do not match the expected record, isolate the affected stock, record the evidence, and obtain an approved decision before it becomes available for sale.
The receiving record should connect supplier delivery information to the warehouse SKU and later outbound orders. This link is especially important when several factories send similar products.
Stage 2: Store inventory with usable status
Storage is more than assigning a shelf. The inventory record should show what is physically present and what can actually be promised to customers. Useful statuses include available, allocated, held, damaged, awaiting inspection, and awaiting rework.
Define the identifier for every SKU, variant, batch, and set. Establish rules for products with expiry dates, serial numbers, restricted handling, or condition differences where applicable. The warehouse should also know whether stock can be combined across channels or whether a quantity is reserved for a particular storefront.
Inventory checks need an agreed frequency and correction workflow. A count adjustment should identify the reason, approver, affected orders, and resulting balance rather than silently changing a number.
FulfillNexa by SBT's Ecommerce Fulfillment scope includes receiving, storage, order processing, shipping, and exception coordination. Its confirmed 8,000 m² Dongguan warehouse has multiple loading bays and is positioned for ecommerce warehouse management and one-piece fulfillment, including apparel and toys. Product acceptance, operating capacity, and channel connections must still be confirmed during shipment-specific onboarding.
Stage 3: Process orders from one source of truth
An order-release rule determines when the warehouse may act. Required data normally includes a unique order number, channel reference, SKU and quantity, recipient information, destination, selected service, packing instruction, declaration input where needed, and any hold or priority flag.
Map changes as carefully as new orders. Decide what happens when a customer edits an address, cancels after picking begins, orders an unavailable unit, or places two orders that might be combined. The system or file process must prevent duplicates and keep an audit trail of accepted changes.
For multichannel operations, create a canonical SKU map. A marketplace listing code and a store variant name may refer to the same physical item, but the warehouse should pick against one controlled identity. Test the mapping before live orders arrive.
Stage 4: Pack and hand off shipments
Packing rules should be specific to the SKU, destination, and sales promise. Define the sales unit, set completeness, protective material, carton or mailer type, inserts, branding, label position, prohibited substitutions, and evidence required for selected orders.
The finished parcel should be matched to the correct order before carrier handoff. Confirm weight and dimensions when they affect service selection or declarations. Record the carrier, service, tracking reference, handoff event, and any change from the original routing instruction.
International shipping also requires product and destination checks. A fulfillment workflow does not establish that an item is transportable or legally admissible. Batteries, liquids, foods, cosmetics, children's products, medical goods, branded goods, and other regulated or restricted items may require separate documentation and carrier review.
Do not turn an estimate into a guarantee. Customer-facing delivery information should be based on the actual service, origin, destination, product, and current operating conditions.
Stage 5: Resolve returns and exceptions
Returns are inventory movements with customer and financial consequences. Decide where customers send goods, what authorization is needed, how condition is inspected, what evidence is captured, and who approves restock, refurbishment, consolidation, disposal, return to supplier, or another disposition.
Exceptions can also occur before delivery: supplier shortage, wrong variant, failed address validation, damaged packaging, missed carrier collection, customs query, or missing tracking event. Each event needs an owner, response time agreed between the parties, permitted actions, approval threshold, and communication path. Avoid vague statements such as “the warehouse will handle it.”
Build reporting around decisions
Reports should help teams act. A useful operations view connects inbound discrepancies, current inventory status, open orders, released parcels, tracking exceptions, returns awaiting a decision, and unresolved approvals. Definitions matter more than a large dashboard: every status should tell the reader what has happened and what must happen next.
If an integration is required, test field mapping and failure recovery. If files are exchanged manually, lock the template, naming convention, schedule, and duplicate controls. In either case, keep personal and commercial data limited to what the workflow requires and define access responsibilities.
Ecommerce fulfillment onboarding checklist
- Document channels, countries, product scope, and customer promises.
- Create a canonical SKU and variant map.
- Send expected inbound data before supplier delivery.
- Define receiving, inspection, and discrepancy depth.
- Agree on inventory statuses and adjustment approvals.
- Map order creation, edit, cancel, split, combine, and hold events.
- Approve SKU- and destination-specific packing instructions.
- Confirm shipping inputs, tracking output, and handoff evidence.
- Identify restricted products for separate compliance and carrier review.
- Design the return address, inspection, refund-decision, and disposition flow.
- Assign owners for inventory, order, carrier, customs, and return exceptions.
- Test representative orders and failure scenarios before launch.
- Review the workflow whenever a channel, product, destination, or service changes.
Choose a provider by testing the full cycle
Ask a prospective fulfillment provider to demonstrate one product moving from advance notice through receipt, available inventory, order release, packing, shipment, tracking, and return disposition. Review the records produced at each step and note where your approval is required.
China-origin ecommerce fulfillment is a good fit only when its inventory position and shipping options support the seller's real customer proposition. A controlled five-stage workflow makes that fit measurable and gives both teams a shared method for resolving the exceptions that inevitably occur.
Matching the fulfillment model to the order profile
The five stages do not change between channels; the release rules inside stage three do. A marketplace order, an independent-store order and a wholesale purchase order all consume the same physical stock, and Amazon's inventory management guidance frames the same problem from a seller's side: the constraint is committed quantity, not shelf quantity. Pick the model by asking which party is allowed to promise what.
| Order profile | Working model | What has to be true first |
|---|---|---|
| One SKU, one channel, steady volume | Direct China fulfillment, single pool | One authoritative stock record and one release rule |
| Same SKU across marketplaces | Single pool with per-channel caps | Committed-versus-available split maintained per channel |
| Slow movers plus a few fast movers | Hybrid: origin stock, destination for the leaders | A reorder point defined per SKU, not per category |
| Bundles and kits | Kitting at the origin warehouse | Bill of materials version control and kit-level identity |
| Heavy customization per order | Origin fulfillment with a packing spec per SKU | Approved artwork, label and packing files at pick time |
Read the channel-capping model in multichannel inventory control, and the exception path in the cross-border returns decision tree. Amazon's ecommerce fulfillment overview and its guide to packing and shipping orders are the neutral references behind the stage definitions above.
FAQ
Can one fulfillment setup serve a marketplace, an independent store and wholesale at the same time?
Yes, but each channel needs its own order-release rule, stock commitment and service promise before inventory is committed. Sharing one physical pool of stock does not remove the need to decide what each channel is allowed to sell.
What has to exist before goods reach the warehouse?
An advance notice or purchase-order reference that identifies the expected SKUs and quantities, so receiving compares the delivery against data instead of describing whatever arrives.
What makes stored inventory usable rather than simply present?
The record has to separate what is physically on site from what can actually be promised to a customer, keeping allocated, held and damaged stock distinct from available quantity.
How should a seller judge a fulfillment provider?
Ask them to demonstrate one product moving through the full cycle - advance notice, receipt, available inventory, order release, packing and handoff - rather than reviewing a brochure.
What stops one SKU from being oversold across channels?
A single source of truth that distinguishes physical stock from committable stock, plus a reservation step at order intake. Without the reservation, two channels can each be promised the same unit while it is still on the shelf, and the failure only surfaces at pick time.
Fuentes y enlaces de verificación
Las reglas operativas pueden cambiar. Consulte las fuentes primarias enlazadas y confirme los requisitos específicos del envío antes de reservar.
- Amazon — Ecommerce FulfillmentFuente oficial
- Amazon — Inventory Management Techniques and Best PracticesFuente oficial
- Amazon — How to Pack and Ship Ecommerce OrdersFuente oficial