Before releasing China stock for US, UK or European orders, agree what each inventory quantity means. Supplier availability, expected inbound units, counted warehouse stock and units available for a new order are different records. A stock report needs a location, timestamp and clear status definitions to support a dispatch decision.
Match the exact SKU and location
Map the store variant to the supplier item and warehouse SKU. Record distinguishing size, colour, pack quantity and any finished bundle identifier. Do not use a parent product’s availability as evidence that every variant is ready.
Keep Guangzhou stock separate from inventory at any destination facility. A quantity in China does not establish local US, UK or European availability. For stock moving between facilities, identify which operator holds it and when the receiving quantity is confirmed.
Separate expected, held and available quantities
Record expected supplier deliveries separately from physically received stock. Define how inspection holds, damaged units, work in progress and order allocations appear in the report. Confirm whether allocated quantities are already excluded from the reported available balance so they are not deducted twice.
For an agreed example where on-hand stock includes both holds and allocations, available stock can be calculated as on-hand minus held minus allocated units. This example applies only when those categories do not overlap. Returned units awaiting assessment remain outside approved sellable stock.
Reconcile a receiving difference before adjusting stock
Compare the supplier dispatch record, carton references and warehouse receiving count for the same SKU and quantity unit. Check whether receipts are partial, counting is incomplete, products are held or units were assigned to a different variant.
Record the expected and counted quantities, the difference, evidence references, investigation owner and next review time. Ask for a recount or clarification within the agreed scope. Keep the original figures visible when recording an approved adjustment; a changed dashboard total alone does not explain the discrepancy. Responsibility and any claim process are confirmed against the actual agreement.
Agree how orders reserve and release stock
Define the event that allocates units to an order and the record confirming that allocation. Avoid using the same stock for a customer order and a bulk replenishment release. If several channels share inventory, confirm who controls the common available balance.
For cancellations or changes, release an allocation only after the operator confirms the order’s current status and approved action. Packed or dispatched quantities cannot simply be treated as unused stock. Link corrections to the order reference and keep duplicate order submissions identifiable.
Make the update method explicit
Agree whether reports use a file, portal or tested connection, how often updates are produced and who checks failures. Record the source timestamp and time zone, not only the time you downloaded the report. An automated connection does not make its source data current or accurate by itself.
Agree what happens when data is late, a SKU mapping fails or the reported balance is disputed. This may include manual confirmation or holding affected releases while the issue is reviewed. Any selling buffer must fit the actual stock and replenishment plan; it is not a guarantee against shortages. Store connections and real-time reporting are confirmed only for the tested project workflow.
Map Shopify transfer actions before changing stock
Shopify distinguishes accepting, rejecting and canceling transferred units. Accepted units become available at the destination subject to location stocking. Rejected units are recorded without changing inventory quantities. Cancellation is intended for units never shipped; for transfers between your locations, it makes those units available at the origin. Partial receiving keeps the transfer in progress.
When a count differs, first identify whether units were never dispatched, rejected on receipt, still in transit or held for inspection. Confirm the correct store action with your operational record; do not use cancellation simply to hide a shortage.
Shopify transfer receiving guidance, checked October 6, 2026.
Keep the adjustment explanation
Shopify records adjustment activity and supports reasons including count, correction, return restock and damage. Its product or variant history view covers the last 180 days; older changes are available through its inventory adjustment report. Agree how you retain receiving evidence and approvals beyond the dashboard view.
Shopify inventory adjustment history, checked October 6, 2026. Store behavior depends on the chosen app and workflow; this guidance does not establish an offered integration.
Compare the same facility and status scope
Before accepting a zero balance or a closing stock figure, confirm which facilities, SKUs and inventory statuses the report includes. A listing view, warehouse count, transfer record and storage invoice may describe different populations of stock.
Request a dated facility-level snapshot showing counted stock, holds, allocations and unresolved movements under the agreed definitions. Compare the report timestamp and time zone with the period being reviewed. A missing row should be recorded as unavailable information until its scope is clarified, rather than silently treated as zero.
If a storage charge remains while the visible stock total appears empty, identify the facility, product and billing period behind the line. Reconcile it with the underlying stock and movement records, retaining the original figures and explanation. This does not determine whether a charge is valid or resolve tax or account-closure requirements.
Public seller question: Inventory found at another facility after a displayed balance appeared empty. The record-planning lesson is separated from the seller’s account and tax questions.
Reserve shared components before counting bundle availability
Several finished products can draw from one component stock balance. Keep each assembly-job allocation identifiable so the same components are not offered to multiple sets or counted as both free parts and completed products.
For cancelled or reduced jobs, confirm whether the components are still loose, inside incomplete work or already consumed in finished sets. Release reservations or return recovered units only after the actual status and approved action are recorded.
Review shared-component allocation and job closure.
Review a representative stock cycle
Include receipt, inspection hold, approved stock, order allocation, cancellation, dispatch and a reviewed return in your pilot. Check the resulting balances and evidence at each agreed step. For bundles, reconcile components with completed sets so both are not counted as independently available.
Download the blank stock reconciliation brief (CSV). Use one row per SKU and facility snapshot. Link it to your fulfillment pilot, bundle records and order change process.
Discuss your inventory reporting scope
Community questions and editorial scope
Reviewed 2026-10-06. The discussions below raised questions about supplier updates, overselling and receiving discrepancies. The workflow here is our planning synthesis for China fulfillment; the posts do not establish China-specific prevalence or our service performance. Publicly visible content was reviewed, without complete comment-tree collection. Software endorsements, claimed savings, supplier accusations and liability conclusions are excluded.
- Keeping up with supplier stock reports
- Avoiding orders against unavailable supplier stock
- Reconciling a warehouse receiving count
From preparation to a clear record
Keep supplier, SKU, batch, and received quantities together in the stock record. Approve the selected balance before release.
