Why Quality Inspection Exceptions Need an Approval Process
When sourcing from multiple suppliers in China, goods first enter the fulfillment warehouse, then are shipped out by order or batch. Once the quality inspection step finds a quantity shortage, visible damage, or a labeling error, if the warehouse decides on its own to "ship it out first and deal with it later" or "hold it back without notifying anyone," it pushes the risk onto the overseas customer: the buyer receives missing items, the platform rules the goods not as described, and return costs rise. The core problem that inspection exception approval workflow China fulfillment needs to solve is just one:After an exception is found, who records it, who pauses it, who decides, and how it's documented.
This process doesn't rely on the warehouse making business judgments for the customer. The warehouse's job is to record faithfully, pause promptly, and lay out the options clearly; the handling decision is made by the customer (brand owner, importer, e-commerce seller). Below is a set of work instructions you can put into practice directly.
Step 1: Define What Counts as an "Exception"
An exception isn't a "bad feeling" — it's a deviation that can be judged against a standard. We recommend agreeing on exception levels with the fulfillment warehouse before cooperation begins, so you don't have to discuss it from scratch every time.
| Level | Typical scenarios | Default action |
|---|---|---|
| Level A: Affects sales | Quantity shortage, entire carton missing, model does not match the purchase order, critical label errors | Immediately pause picking and packing for that SKU, wait for the customer's decision |
| Level B: Affects experience | Outer box crushed, inner packaging damaged, minor stains, non-critical labels blurry | Take photos and record, can continue working on other SKUs, summarize and confirm before outbound |
| Level C: Notification only | Minor creasing on the outer box, replaced sealing tape, differences in pallet appearance | Record in the receiving report, do not pause separately |
The grading standards must be written into the operating agreement between both parties, and it must be made clear that "the purchase order, the supplier's packing list, and the specifications provided by the customer shall prevail." The warehouse does not judge the authenticity of goods, nor whether they comply with the regulations of the destination country; these are matters between the customer and the supplier.
Step 2: Evidence Recording Checklist
The value of an exception record is that it lets the customer make a decision without seeing the physical item. It is recommended that each exception include at least the following:
- Order number / purchase order number / SKU code, and the corresponding supplier name
- Time of discovery and stage of discovery (receiving, quality inspection, picking, packing)
- Exception type and level, using unified codes to avoid ambiguity in text descriptions
- Compare the actual received quantity with the document quantity, and note the number of discrepant pieces
- Photos: all six sides of the outer box, shipping marks, inner packaging, the product itself, and close-ups of labels; photos must clearly show batch or serial information
- Whether it has been opened, the extent of opening, and whether it affects resale
- Current cargo status: pending area, quarantined, returned to original box
Photos and written records should be attached under the same exception ticket number, so customers can view them all at once instead of having them scattered across chat records.
Step 3: Pause and Isolate
After confirming it as a Level A exception, the warehouse should perform the following actions:
- Move the batch to the pending area or quarantine area, physically separated from normal inventory
- Mark the SKU as "exception pending decision" in the inventory system to prevent it from being mistakenly picked by the picking and packing process
- Suspend related operations under the same purchase order that have not yet been shipped, but do not affect normal outbound operations for other suppliers or other SKUs
- If the exception involves a label issue for an entire batch, the hold scope should be expanded to all goods in the same batch, rather than only holding the few items that were sampled
A hold is not an indefinite seizure of goods. A response deadline should be set for exception orders; for example, if no customer decision is received within a certain number of working days after the notice is sent, the warehouse handles it according to the agreed default action (such as continuing temporary storage and sending another reminder, or executing rules pre-authorized by the customer). The default action must be confirmed in writing before cooperation begins and cannot be decided by the warehouse on an ad hoc basis.
Step 4: Present Handling Options to the Customer
When notifying the customer, in addition to the evidence, you should also provide selectable handling options for the customer to simply check off, reducing back-and-forth communication. Common options include:
- Ship as usual: the customer accepts the discrepancy; the warehouse records it and continues picking and packing
- Partial outbound: ship the normal portion first; keep the problematic portion in the warehouse pending restocking or exchange
- Return to supplier: arrange the return per customer instructions; the return address and contact person are provided by the customer
- Relabel / repackage: after the customer confirms they can handle the label or packaging issue themselves, the warehouse operates per instructions
- Continue temporary storage: awaiting the result of negotiation between customer and supplier; the warehouse keeps the goods in isolated status
- Destruction or disposal: executed only after written confirmation from the customer, and the execution results are recorded
The warehouse only executes the options confirmed by the customer, does not pursue accountability with the supplier on the customer's behalf, and does not make compliance judgments about the supplier.
Step 5: Approval Workflow and Record-Keeping
An executable flow sequence is as follows:
- Quality inspection or receiving personnel create the anomaly ticket, with evidence attached
- The warehouse supervisor reviews the level and photo completeness
- The anomaly ticket is sent to the contact person designated by the customer (it is recommended to also designate a backup contact)
- The customer selects a handling option on the anomaly ticket and confirms
- Executed by the warehouse; after execution, the results are filled in: actual outbound quantity, return order number, relabeling quantity, remaining inventory status
- The anomaly ticket is closed and archived, serving as the basis for subsequent reconciliation and supplier communication
The purpose of keeping records is: when the same type of anomaly occurs repeatedly with the same supplier, the customer can use the historical records to negotiate with the supplier, rather than relying on impressions. The warehouse side should also regularly summarize the distribution of anomaly types for customers to evaluate supplier performance.
Common Questions and Boundaries
Can the warehouse decide on its own that "this defect doesn't affect sales"?
It cannot be used as a final conclusion. The warehouse can provide observational descriptions, but whether the goods are "sellable" is decided by the customer. This is especially true for sellers selling on platforms, as only the customer knows the platform rules and buyer expectations best.
If an exception causes a delay in outbound shipment, how is responsibility determined?
This is a commercial agreement and should be clearly stated before cooperation: whether storage fees are incurred during the suspension period and who bears them shall be subject to the agreement between both parties. This article does not provide a conclusion on fees.
What if the customer doesn't reply for a long time?
It is recommended to agree on the reminder cadence and default actions before cooperation. For example, send one reminder after the first notification, and if there is still no reply beyond the agreed deadline, handle it according to preset rules. If there are no preset rules, the warehouse should keep the goods in temporary storage and continue recording, and must not ship or return them without authorization.
When an exception involves labeling and destination-country requirements, what can the warehouse do?
The warehouse can perform relabeling and repackaging according to the label files provided by the customer, and take photos as evidence. Whether the label content complies with the destination country's customs or market regulatory requirements must be verified by the customer, and the destination country's official requirements shall prevail. Involvingcustoms clearanceFor taxes and fees, please check the latest official requirements of the destination country's customs or tax authority.
Connecting the process to fulfillment operations
Quality inspection exception approval is not a standalone step; it is connected with receiving verification, inventory status, picking and packing, and international shipping arrangements. SKUs with open exception tickets should not enter the outbound process; for those confirmed to ship as usual, the exception ticket number should be noted in the outbound record for future traceability.
If you are setting up receiving, quality inspection, warehousing, and outbound processes on the China side for multi-supplier sourcing, you can check out ourWarehousing and Fulfillment Services, to understand the scope of operations for receiving, basic quality inspection and photography, relabeling, repackaging, inventory organization, picking and packing, and arranging international shipping; specific categories, exception grading, and default actions can be discussed before cooperation throughContact UsConfirm item by item.
