China Warehouse Exception Handling: What to Do When Goods Arrive Damaged or Incorrect

The right China warehouse exception handling process is to identify the mismatch, record evidence, notify the responsible parties, decide the next action, and close the case only after the seller confirms the outcome. This workflow applies when goods arrive damaged, the wrong SKU is received, quantities do not match, accessories are missing, or a parcel reaches the warehouse without a usable pre-alert.

Picture a small brand preparing an international shipment. The order is urgent, the supplier says everything was packed correctly, and the warehouse finds a crushed corner and two missing accessories during inbound inspection. If the issue is discovered after export, the seller may face replacement freight, a customer dispute, or an argument about where the damage happened. This guide explains how to keep a warehouse inbound discrepancy visible and actionable, then shows how BONDJET 邦达捷 can support the process for high-value and complex-SKU goods.

Key Takeaways
- A fulfillment exception process should stop the affected goods from moving forward until the seller gives a clear disposition.
- Every report should compare expected SKU, quantity, condition, accessories, and packaging with what actually arrived.
- Photos, carton labels, tracking numbers, weights, and timestamps create useful evidence without pretending to prove every cause.
- Possible decisions include hold, rework, return to supplier, partial approval, or seller confirmation, subject to the actual service arrangement.
- BONDJET 邦达捷 connects inspection records, SKU control, packaging review, and international dispatch so exceptions can be handled before shipment.

Why China Warehouse Exception Handling Matters Before Dispatch

An inbound problem becomes expensive when the seller learns about it after international handoff. At that point, the product may already be difficult to inspect, return, replace, or attribute. The warehouse is the most useful control point because the goods are still physically available and the next action can be chosen with better information.

Common exceptions include:

• Damaged goods at warehouse: crushed retail boxes, broken parts, torn packaging, water marks, or visible impact.
• Wrong SKU received: a different model, color, size, edition, or bundle arrives than the one listed in the pre-alert.
• Quantity mismatch: fewer or more units arrive than expected, or a carton count differs from the supplier's notice.
• Missing accessories: a base, cable, manual, certificate, mounting part, or other component is absent from a set.
• Unannounced parcel: the tracking number, sender, carton count, or SKU information is missing, so the warehouse cannot safely allocate the goods.
• Packaging concern: the item is intact, but the supplier packaging is not suitable for international handling or does not meet the seller's presentation requirements.

The key distinction is between an observation and a conclusion. “The outer carton has a torn lower corner” is an observation. “The carrier caused the damage” is a conclusion that may require more evidence. Good exception reporting records what can be seen, preserves relevant evidence, and leaves responsibility decisions to the parties and service terms that govern the shipment.

Suggested visual: Add a simple flow diagram showing Inbound check -> Exception report -> Hold -> Seller decision -> Rework / return / approve -> Close.

Step 1: Identify the Exact Exception

The first step is to compare the physical arrival with the expected arrival. Use the pre-alert, purchase order, supplier packing list, or dispatch instruction as the baseline. Do not rely on a product name alone when similar items share a carton.

For each affected parcel or unit, capture:

1. The domestic tracking number and supplier name.
2. The expected carton count and actual carton count.
3. The expected SKU, variant, quantity, and bundle relationship.
4. The visible condition of the outer carton and product packaging.
5. The presence or absence of accessories and set components.
6. Any label, seal, or marking that helps identify the shipment.

For a wrong SKU received case, record both sides of the mismatch: what the seller expected and what the warehouse found. “SKU A expected, SKU B received” is actionable. “Wrong product” is not specific enough for a supplier, warehouse, or seller to investigate.

For fragile or collectible products, condition needs more detail. A damaged corner on a shipping carton is different from a dented retail box, and a damaged retail box is different from a broken product inside it. The report should describe each layer separately. If the seller does not authorize opening sealed packaging, the report should state that the internal product was not inspected.

Step 2: Record Evidence That Can Be Rechecked

Evidence should make the situation easier to understand later. It does not need to be elaborate, but it should be consistent across shipments and clear enough for someone who was not present at receiving.

A practical evidence set

• Photos of the full carton and all visible sides.
• Close-ups of dents, tears, crushed corners, water marks, broken seals, or labels.
• Photos of the product, retail packaging, and accessories when inspection is authorized.
• The tracking number, carton reference, and receiving date.
• Expected and actual quantity by SKU.
• Weight or dimension records when they help explain a quantity or packaging discrepancy.
• A short written description using neutral, observable language.

Keep the evidence linked to a single exception reference. A folder of unnamed photos is difficult to use. A record such as EX-249-003, linked to the tracking number and affected SKU, lets the seller discuss one case without mixing it with another supplier shipment.

The record should also distinguish between “not found,” “not checked,” and “not applicable.” If an accessory is not found in the carton, say so. If the carton was not opened because the instruction prohibited opening, say that instead. This distinction protects the accuracy of the report and makes the next decision clearer.

Step 3: Notify the Seller and Pause the Affected Goods

Once the exception is documented, notify the seller through the agreed channel and place the affected inventory on hold when moving it forward could make the issue harder to resolve. A hold does not necessarily mean the entire inbound shipment stops. If one SKU is affected and the remaining units are verified, the seller may decide whether unaffected inventory can be received or dispatched separately.

The notification should answer five questions:

1. What arrived, and when?
2. What does not match the expected information?
3. What evidence is available?
4. What action has been paused?
5. What decision is needed from the seller?

Avoid sending only “please check” or a group of photos without context. A concise exception report reduces back-and-forth and gives the seller enough information to contact the supplier, approve a rework, or change the shipment plan.

This is also where responsibility boundaries matter. The warehouse can report the condition observed at receiving and preserve evidence. The supplier, carrier, insurer, or seller may have separate responsibilities under their agreement. Do not present a warehouse observation as a guaranteed claim result or compensation decision.

Step 4: Choose the Correct Disposition

The correct response depends on the product, the severity of the issue, the shipment deadline, the supplier relationship, and the agreed service scope. The seller should make or approve the disposition when the exception affects product condition, inventory ownership, or customer commitments.

The main options are usually hold, rework, return to supplier, partial approval, and seller confirmation. These are workflow choices, not universal promises. Fees, return arrangements, packaging materials, insurance, carrier rules, and timing should be confirmed for the actual service.

For high-value items, do not let urgency erase the decision point. A seller may approve dispatch with a documented cosmetic issue, but that approval should be explicit. The record should show who approved it, what condition was accepted, and whether the issue affects the customer-facing product or only the outer shipping carton.

Step 5: Close the Case and Update Inventory

An exception is closed when the agreed action is complete and the record reflects the final state. “Supplier contacted” is usually an intermediate status, not a resolution.

A useful closure record includes:

• Final disposition and approval source.
• Quantity released, held, reworked, returned, or written off.
• Updated SKU or location information.
• New photos or packing evidence after rework.
• Supplier or carrier reference, if a claim or replacement is opened.
• Any change to the outbound order, declared information, or packaging instruction.
• Date of closure and the person who confirmed it.

Then update the inventory system. A wrong SKU that remains in the expected SKU location can create a second failure during picking. An incomplete set that is marked available can lead to a customer receiving a product that was already reported as incomplete. Exception handling is complete only when the physical stock and the digital record tell the same story.

How BONDJET Supports a More Visible Exception Workflow

BONDJET 邦达捷 treats exception handling as part of high-value product fulfillment, not as an isolated customer-service message. Its workflow connects arrival inspection, photo records, SKU and accessory checks, inventory control, custom packaging, and international dispatch. That connection matters because the same evidence used to identify an inbound discrepancy may affect the packing method, shipment approval, or customer communication later.

For example, a collectible item may need an outer-box check, accessory confirmation, and seller instruction about whether sealed packaging can be opened. A fragile instrument may need a packaging review before the seller approves international handoff. A brand with several variants may need the SKU record corrected before the unit becomes available for picking. The appropriate handling depends on the product and the seller's requirements.

The BONDJET figure-seller case describes a documented workflow involving arrival inspection, photos, SKU and accessory checks, packaging reinforcement, and outbound verification. The BONDJET telescope case shows why fragile, high-value products may need custom packaging, tracking, and customs coordination. These examples illustrate process choices for their specific projects; they should not be read as a guarantee of zero errors, zero damage, fixed response times, or universal compensation.

If your team is still defining the whole flow, start with the BONDJET service overview and then discuss the product-specific requirements through the BONDJET contact page. Share the SKU list, expected inbound information, product photos, accessory rules, packaging expectations, destinations, and any approval limits. That gives the fulfillment partner enough context to propose a workable exception path before the first shipment arrives.

A China Warehouse Exception Report Template

You can adapt the following template for each exception:

Exception reference:
Date and receiving location:
Supplier:
Domestic tracking number:
Carton reference / expected carton count:

Expected:
- SKU / variant:
- Quantity:
- Accessories or bundle components:
- Packaging or condition requirement:

Observed:
- Actual SKU / variant:
- Actual quantity:
- Missing or additional components:
- Outer-carton condition:
- Product or retail-box condition:
- Photos and other evidence:

Immediate action:
- Held / separated / received with exception / other:

Decision required:
- Rework / return to supplier / partial approval / seller confirmation / other:

Final disposition:
Approval source:
Inventory record updated:
Closure date:

The template is intentionally simple. Its value comes from consistent use, clear photos, and a defined approval path. A small team can begin with a spreadsheet or shared form, provided each exception has one reference and the physical inventory status is updated when the decision changes.

Frequently Asked Questions

What should I do when the warehouse receives the wrong SKU?

Place the affected unit on hold, record the expected and actual SKU, photograph the labels and product, and ask the seller to approve the next disposition. The options may include supplier return, relabeling, separate inventory, or partial approval, depending on the product and service arrangement.

Should damaged goods at a warehouse be shipped anyway?

Only after the seller understands the condition and explicitly approves the shipment. A visible carton mark may be acceptable for one product and unacceptable for a collectible or gift-ready item. Record the accepted condition and any packaging action before dispatch.

Who is responsible for a warehouse inbound discrepancy?

Responsibility depends on when the discrepancy occurred and which agreements apply. The warehouse should document what it observed at receiving; the seller, supplier, carrier, insurer, and fulfillment partner may then review the evidence under their respective terms.

Conclusion: Make Exceptions Visible Before They Become Claims

Effective China warehouse exception handling is a control loop: compare the arrival with the expected record, capture evidence, notify the seller, hold or separate affected goods, choose a disposition, and close the case only after inventory and documentation are updated. This approach gives small brands a better chance to correct a wrong SKU, replace a missing accessory, improve packaging, or decide knowingly whether a shipment can proceed.

For high-value or complex-SKU goods, the process should connect inbound inspection with SKU management, packaging, and international dispatch. BONDJET 邦达捷 can help sellers structure that workflow around their products, destinations, and approval rules. Start by preparing your SKU list, inbound pre-alert format, inspection requirements, and exception report fields, then request a product-specific fulfillment discussion before the next shipment arrives.