China Fulfillment Warehouse Inventory Status Code Handbook: unified terminology for the inventory status code handbook China fulfillment warehouse team

Why You Need a Set of Inventory Status Codes

When overseas brands, importers, or e-commerce sellers purchase from multiple suppliers in China and consolidate goods into a China fulfillment warehouse, inventory figures are often maintained by multiple teams: procurement tracks supplier shipping progress, operations tracks sellable quantity, and the warehouse tracks physical location and processing status. If everyone's idea of "in stock" doesn't mean the same thing, problems arise such as overselling, duplicate replenishment, or orders being locked and unable to be released. This article provides a practical inventory status code manual, using statuses such as pending receipt, available, locked, QC exception, pending processing, and shipped to establish an inventory definition that teams can understand. It does not depend on any specific system and can be implemented with spreadsheets, shared documents, or warehouse work orders.

Please note: this article does not cover specific system integration capabilities, nor does it promise any inventory accuracy figures. The value of status codes lies in giving the team a shared language for communication; for specific execution methods, please refer to the operating procedures you have confirmed with the warehouse.

Core Status Definitions

We recommend keeping inventory statuses to six main statuses to avoid having too many statuses for the team to remember. Each main status can carry a reason code, but the main statuses themselves should remain stable.

Status Transition Rules

Status codes are only meaningful when the transition rules are clear. We recommend clarifying the following basic rules:

• Pending receipt can only be converted to available or quality-check exception through warehouse receiving operations; operations staff cannot manually change it to available;
• Converting available to locked must be linked to a specific order number or outbound batch number; locking without an order is not allowed;
• Converting locked to shipped requires picking and packing confirmation; this step cannot be skipped;
• Quality-check exceptions and pending items must have a reason code and an assigned owner; they cannot be left hanging long-term;
• The shipped-out status cannot be rolled back. If a return occurs, a new return record should be created rather than changing it back to available.

These rules can be posted as a status flow diagram in a shared document, so that procurement, operations, and the warehouse all communicate based on the same diagram.

Reason Codes: Making Exception Statuses Traceable

In addition to the main statuses, it is recommended to add reason codes for quality inspection exceptions and pending handling. You don't need many reason codes, but they should distinguish the handling actions. For example:

• Quantity discrepancy: the quantity shipped by the supplier does not match the quantity received;
• Outer carton damaged: the outer carton was damaged in transit, and the condition of the inner goods needs to be confirmed;
• Label issue: SKU label is missing, blurry, or does not match the actual item;
• Pending relabeling: needs to replace the destination country label or retail label;
• Pending repackaging: needs to be repackaged according to order requirements;
• Pending instruction: waiting for the customer to confirm how to handle it.

The reason code should be recorded next to the inventory record, along with the initiation time and the person responsible. This way, during weekly meetings or reconciliation, the team can filter directly by reason code instead of asking one by one.

Team Communication Templates

To ensure procurement, operations, and the warehouse use the same set of standards, it is recommended to use a fixed template in daily or weekly communication. For example:

• Pending receipt today: list the supplier shipment numbers and carton counts expected to arrive at the warehouse;
• Available today: list the SKUs and quantities that have completed receiving and been converted to available;
• Locked today: list the SKUs and order numbers that have been allocated to orders;
• Quality inspection exceptions today: list the abnormal SKUs, reason codes, and items pending confirmation;
• Pending today: list the SKUs that need relabeling, repackaging, or are awaiting instructions;
• Shipped today: list the batches that have completed picking and packing and have been scheduled for transport.

The template doesn't need to be complex; the key is to communicate daily using the same fields. Over time, the team will develop a consistent understanding of the boundary between "available" and "locked."

Exception Handling Checklist

When inventory status becomes abnormal, you can confirm item by item using the following checklist:

• Which main status is the abnormal SKU currently in, and what is the reason code;
• Whether there are already photos or quality inspection records as supporting evidence;
• Who needs to make the decision: procurement, operations, or the end customer;
• After the decision, should the status change to available, pending processing, or returned to supplier;
• Whether orders that have locked this SKU need to be notified for adjustment;
• Whether historical statuses need to be retained in inventory records to avoid overwriting original records.

The key to exception handling is to preserve history rather than directly overwriting old statuses. Preserving historical statuses helps with subsequent reconciliation and dispute retrieval.

Integration with warehouse operations

Status codes must ultimately be reflected on warehouse operation orders. It is recommended to mark the corresponding status code on receiving orders, quality inspection orders, relabeling orders, picking orders, and outbound orders, so that warehouse staff know which status the current action will move the inventory to during execution. ImagineShip can provide services such as supplier receiving, consolidation, basic quality inspection and photography, warehousing, relabeling, repackaging, inventory organization, picking and packing, and arranging international transportation. Specific operation fields and status definitions can be confirmed with the team before cooperation. You can viewWarehousing and fulfillment service description, or submit product and order requirements throughContact UsCommunicate your inventory management needs.

Frequently Asked Questions

Do the status codes need to match the e-commerce platform backend?

Exact consistency is not required, but establishing a mapping relationship is recommended. The platform's "available for sale" usually corresponds to "available" in this article, and the platform's "shipped" may correspond to "outbound" in this article. The mapping relationship should be clearly documented to avoid confusion within the team.

How long can the locked status be retained?

There is no universal answer; it depends on the order processing pace. It is recommended to set an internal review cycle, for example, checking weekly for orders that have been locked for a long time but not shipped, to confirm whether they need to be released or continue to wait.

Can a QC exception be changed directly to available?

Not recommended. For quality inspection exceptions, the responsible person should first confirm how to handle them, then convert them to available, pending, or returned. Directly changing to available will conceal the problem and affect the quality of subsequent orders.

Customs Clearance and Tax Reminders

Customs Clearance and Tax Reminders

Import rules in various countries are subject to change; required documents and applicable fees depend on the product, declaration information, shipping method, and destination. Before shipping, please refer to the latest requirements published by the destination country's customs or tax authority, and provide product information truthfully.