WhatsApp
8618665916878
Latest company news about Six Fields a Store Order Has to Carry Before a China Warehouse Can Pick It
2026-10-21 22:41:34

Six Fields a Store Order Has to Carry Before a China Warehouse Can Pick It

Sellers describe a store as "connected to the warehouse" and usually mean one of three different things. A live app that pushes orders, a nightly spreadsheet, or an integration that pulls on a timer. Each shape fails in its own way, and every one of those failures lands in the same place: a picker standing in front of a shelf with instructions that do not resolve. From our side of the goods-in desk in Dongguan, the difference between a smooth queue and a stuck one comes down to six fields.

The six that decide whether a line can be picked

First is the seller SKU exactly as it appears on the store, not the supplier's internal code. Our team maps one to the other at intake; when the store-side value changes on a product edit and nothing tells us, the order arrives as a question. Second, quantity per line rather than per order, because a two-item order is one pick list and a fifteen-item order is a carton-counting exercise. Third, a destination address that separates street, unit, city, region and postal code into their own boxes instead of one pasted string. Fourth, the shipping product the customer paid for, since that choice selects the lane and therefore the paperwork. Fifth, any instruction that changes the physical parcel: gift note, insert, bundle, or a request that the sender identity stay off the outside. Sixth, the timestamp the store recorded for payment, which is what your handling clock runs on and not the moment the file reached us.

What each sync shape breaks

An app push is the tidiest and still loses edits: a customer who changes an address inside the platform after the order was sent leaves the warehouse holding the old version. A nightly file is honest but slow, and a payment received after the nightly export window waits for the next pre-dawn run and then for the China to United States air lane cut-off it will now miss. A timer pull sits between the two and its risk is silent duplication: when the job runs twice after a token refresh you get two work orders for one payment, and the second one ships unless someone reconciles. Whichever shape you run, reconcile on the store order number, never on arrival time.

The fields that are yours to decide, not ours

Declared value per item, the commodity code your broker selected, and whether you want the parcel to travel under a sender name that is yours are commercial choices. We can carry them out, and we do record them per line, but we do not invent them. Where an order arrives with no declared value we hold it in an exceptions queue rather than guess, and it waits for you. Semi-sensitive and regulated goods sit in the same queue for a different reason: those lines need a channel answer before anything is picked, so treat them as subject to channel confirmation instead of assuming a lane will take them.

One order at a time changes the arithmetic

A queue of single-line orders is not a small version of a bulk order; it is a different operation. Binning, pick paths, packing material choice and the daily handover all get tuned for volume per parcel instead of parcels per shipment. Our one-piece-at-a-time page sets out how we run it, including where a labeling job gets inserted when the store SKU and the physical item do not match out of the factory.

Five checks before you send real volume

Send one order per shipping product and watch what the exception report says. Send an address with a unit number and a postal code that belongs to a different region. Send a cancellation ten minutes after payment and confirm the warehouse actually stopped. Send a line with no stock and see whether the rest of the order ships or the whole thing waits. Then send fifteen orders in one afternoon and compare the dispatch list against the store list line by line. Those five pass, and the sync is real. If any of them is a surprise, you have found it cheaply.

What "same day" honestly means here

Goods that are already in the building, an order that reaches us before the afternoon cut-off, a shipping product with space that evening, and a clean address: four conditions, and all four have to hold. Our desk publishes the cut-off as 16:00 China time for lines running that routine, which is the number worth building your own promise date around rather than a vague "24 hours". Miss it and the order is first out tomorrow, which is fine as long as everyone is measuring the same clock.