Offered lot and product identityDestination and carrier reviewPacking and document handoverReceiving checks and exceptions

How to Build a Useful Receiving Exception File

An exception file should begin with what the receiving team directly observed. Examples include an unexpected item count, an unreadable label, damaged secondary packaging or a mismatch between the packing list and the contents.

Describe the observation before proposing a cause

An exception file should begin with what the receiving team directly observed. Examples include an unexpected item count, an unreadable label, damaged secondary packaging or a mismatch between the packing list and the contents. Identify the affected shipment, package and item. Avoid assigning a transport, packing or product cause before the evidence has been reviewed. A clear observation is more useful than an early accusation because it gives the responsible teams a shared factual starting point for investigation and resolution.

Collect evidence that can be reconciled

Include photographs showing the relevant package identifier and the observed condition, together with the packing list and receiving date. Where several items are affected, identify them separately. Preserve original images rather than relying only on heavily cropped or annotated versions. Record whether the package had been opened, moved or repacked before the observation was made. These details help reviewers understand the context. They do not independently prove a cause, but they reduce ambiguity and make it easier to compare receiving evidence with the dispatch record.

Keep handling and disposition decisions explicit

Follow the receiving organization's procedures for affected material while the issue is reviewed. Record who can decide whether an item may be used, returned, replaced or examined further. If a laboratory assessment is proposed, define the specimen and question before sending it. Do not assume that an unchanged appearance proves suitability or that visible damage to an outer box establishes damage to every item. The response should be proportionate to the observed issue and supported by the relevant product and package information.

Document the resolution and the remaining limits

The final record should state what was clarified, which action was agreed and whether any question remains unresolved. Connect replacement or follow-up shipments to the original exception rather than deleting the first record. Where the review identifies a process improvement, such as clearer item labels or better document matching, assign an owner for the change. A useful exception file supports a specific resolution and a better next dispatch; it should not become a collection of unsupported explanations that cannot be checked against the shipment history.

References for this page

Verify an official batch report

Search the Celsentra COA library by product or lot. Compare the report identifier with the physical pack and the material you requested.

Open official COA library

Request a China Dispatch Review

Share the cosmetic material, quantity, destination, available lot details and the documents your team needs at receiving.