Track Supplier Sample Parcels Without Mixing Up Product Variants

Use a sample parcel register to connect supplier messages, package labels and product variants without treating delivery as sample approval.

China Unboxed · 2026-09-18 · AI-assisted practical guide; automated editorial checks.

All buyer and supplier scenarios in this guide are fictional illustrations of a suggested planning method.

Give every expected sample a stable internal reference, then connect that reference to the supplier's description, the parcel and the item received. Keep unknown identities unresolved instead of guessing from appearance. This suggested register answers a narrow administrative question: which requested sample did we receive? It does not decide whether the sample meets a specification, represents future production or should be approved for an order.

Separate the sample identity from the parcel identity

Start with one row for each requested product variant, not one row for each courier message. A parcel can contain several variants, and a supplier may send one request in separate parcels. Give each row an internal sample ID that stays unchanged when a delivery reference changes. Record the supplier's own reference alongside it rather than replacing it. Suggested fields include request date, supplier reference, variant description, requested quantity and the message that confirms what will be sent.

Consider a fictional buyer requesting two fabric swatches from Supplier A: a blue version and a grey version of the same product. The buyer assigns IDs A-BLUE-01 and A-GREY-01. These are clerical labels, not batch numbers or quality grades. The supplier later says both will travel together. Link both rows to parcel P-01, but retain the two sample IDs. The deliverable is a register that can describe two items in one box without collapsing their identities.

Ask the supplier to confirm the item-to-label mapping

Before dispatch, send the proposed mapping to the supplier and ask for confirmation in writing. A useful request is: Please confirm which supplier reference corresponds to each of our sample IDs, and show how each item will be identified inside the parcel. Treat a label as a communication aid, not proof that the contents are correct. Avoid labels that could damage an item or obscure an existing identifier; agree a practical identifying method with the supplier.

In the fictional example, Supplier A replies that its reference F-B corresponds to A-BLUE-01, but does not provide a reference for the grey swatch. Record the blue mapping as supplier-confirmed and leave the grey mapping open. Ask only the missing question: What is your reference for A-GREY-01, and which item label should we expect? Do not infer that a second unlabelled swatch must be grey. The output is a confirmed mapping plus one explicit unresolved question.

Record dispatch changes without replacing the original request

When the supplier sends dispatch details, add them as a new event. Record the date, the parcel reference as supplied and which sample IDs the supplier says are included. Preserve the earlier request so a later reviewer can distinguish what was requested from what was reportedly sent. If the supplier substitutes a variant or splits the parcel, record that proposed change separately. A dispatch notification should not silently update the requested product description or imply that a substitution was accepted.

Suppose Supplier A now says the grey swatch will follow separately in P-02. Keep A-GREY-01 linked to the original request and add a new dispatch event. Mark its earlier proposed link to P-01 as superseded, not deleted. A colleague opening P-01 can then see why only the blue swatch is expected. If the second parcel reference is missing, write awaiting dispatch reference rather than inventing a placeholder that resembles a real tracking number.

Log receipt separately from identification and approval

On receipt, record what the recipient actually observes: arrival date, visible parcel reference, item count and the labels present. Use separate fields for supplier-stated contents and recipient-observed contents. Where appropriate, retain a photo reference that connects an item label to its parcel record; avoid exposing personal addresses in shared copies. Do not use a single approved status for arrival, identity confirmation and product evaluation. Those are different decisions with different evidence and potentially different owners.

The fictional P-01 arrives with one swatch labelled F-B. The recipient records one item observed, label F-B and identity mapping awaiting confirmation by the assigned buyer. The buyer compares that label with the retained supplier message and links it to A-BLUE-01. This resolves the administrative identity question only. Whether the colour, material or other properties satisfy the buyer's requirements remains outside this register and must be handled through the appropriate sample evaluation process.

Keep exceptions visible until the responsible person resolves them

Create an exception row whenever the observed contents do not match the documented expectation. State the discrepancy without explaining it away: one item received without an identifier is more useful than probably the grey sample. Link the exception to the affected parcel and sample IDs, assign a follow-up owner and record the next question. Keep an unconfirmed item separate in the register from confirmed samples so its identity is not accidentally inherited from a nearby row.

If P-02 contains an unlabelled swatch, ask Supplier A to identify the item against the original request and explain what supporting information it can provide. Preserve the reply as evidence of the supplier's statement, not as an independent verification. If the buyer cannot establish an adequate mapping, the administrative conclusion is identity unresolved. The next action may be clarification or a replacement request. Do not change A-GREY-01's description merely to make the received item appear to match.

Hand over a traceable register, not an implied purchasing decision

When another colleague takes over, provide the register, the linked request messages and the unresolved exception list together. Explain the status labels in plain language: expected, dispatch reported, received, identity linked or identity unresolved. Keep any separate sample approval document under its own reference and owner. This prevents someone from treating a completed delivery row as permission to place a production order. A useful handover tells the recipient both what is known and what still needs a decision.

For the fictional case, A-BLUE-01 ends with identity linked and an evaluation reference still awaiting assignment. A-GREY-01 remains identity unresolved until its exception is addressed. Those outcomes are deliberately limited: the register has improved traceability without claiming product acceptance. Before closing the handover, ask the next owner to locate each sample's original request and latest event using only the recorded references. If that cannot be done, fix the missing link rather than adding a reassuring completion label.

Copyable planning worksheet

Examples below are fictional illustrations, not completed client records. Copy this table into your document and replace each example with your own evidence.

Scope and related resources

This is a suggested planning method, not a supplier certification, legal opinion or inspection standard. Confirm product-specific requirements with the appropriate specialist.

• Compare supplier quotations
• Factory visit agenda
• More practical worksheets

For help coordinating your China visit, discuss your project with China Unboxed. Scope and availability must be agreed before booking.