/ 4 min read / sample evidence / quality dispute / factory record

Pre-Shipment Sample Retained at Factory

A retained sample can support disputes only if the buyer controls labeling, photos, and storage evidence.

What to check in the order file

Pre-Shipment Sample Retained at Factory belongs in the buyer file before the order turns into a dispute.

Start with the live decision. For retained pre-shipment sample, the buyer needs to decide whether the retained sample can prove the approved product standard later.

Check the sample label, approval photo, production lot, factory storage photo, inspection report, PO, and supplier retention statement.

A supplier may say a golden sample remains at the factory, but the file lacks date, label, or lot connection. The forwarder follows the booking. The warehouse receives cartons.

Ask one control question: could the buyer connect the retained sample to the exact order and production batch.

Which company made the request? Which document changed? Which risk remains open? If the folder answers those questions, Pre-Shipment Sample Retained at Factory becomes a repeatable control instead of another small exception that nobody can reconstruct later.

A retained sample can support disputes only if the importer controls labeling, photos, and storage evidence. Another member of the team should be able to verify the answer from the file before production, inspection, or shipment decision. State the remaining limit in the pre shipment factory note before the file is closed.

Make the decision before the next handoff

Open the approved sample or specification, product photos, test or certificate scope, label artwork, inspection record, and invoice model together. Mark the first changed field and retain the earlier version beside the file the order owner plans to use. The comparison should show who supplied the revision, when it arrived, and which order step depends on it. Attach the evidence to the quality dispute version that now controls the order.

Familiar commercial explanations can hide a real mismatch. Ask which company, file, quantity, model, payment, or shipment the answer covers, and record when the answer applies only to this order. Use the factory record record to show who accepted the result and on what date.

Assign the file to the product owner, quality reviewer, and sourcing contact. The owner does not need every chat message, but does need the final record, vendor answer, purchasing team decision, and next checkpoint. Put that result in the sample evidence note for the current PO.

The unresolved risk is that the goods may differ from the version, material, model, marking, or evidence that the importer approved. State whether the exception covers one shipment, one payment, one model, or the wider counterparty relationship. A one-order decision should not silently become standing sign-off. Name this point in the pre shipment factory closeout rather than leaving it in chat.

Use the checklist as a closing test: label the retained sample, take dated photos, link to po and lot, and record storage location. Record who completed each step and save the evidence beside the record it supports instead of leaving a general note that the supplier was checked. The factory record file should show how this point was resolved.

Give the exception an end point, such as receipt of a corrected file, payment confirmation, inspection, broker acceptance, warehouse receipt, or claim settlement. Link the answer to the sample evidence checkpoint for this order.

Public guidance can frame the sample evidence check, but it cannot establish the facts of this order. The order owner's PO, invoice, beneficiary record, packing list, product evidence, broker reply, and shipment file remain the deciding records. Carry the result into the quality dispute instruction used by the next team.

Close the record for the next order

If the issue returns, begin with the prior note. It should show which record to request first and which assumption caused the earlier delay. Attach the evidence to the pre shipment factory version that now controls the order.

Save the revision path visible. The folder should show which version was rejected, which version controls, and whether anyone outside sourcing still holds an obsolete copy. State the remaining limit in the sample evidence note before the file is closed.

Record one of three outcomes: approve, approve with a stated condition, or hold. Name the evidence supporting that outcome and the event that would force the purchasing team to reconsider it. The next reviewer should find the answer under quality dispute without reopening the whole case.

Send the controlling record to every team that will act on it. Approval is incomplete when finance, logistics, the warehouse, or the broker continues from an older version. Carry the result into the factory record instruction used by the next team.

When the same exception affects several orders, add the field to the counterparty baseline. Repeated problems belong in onboarding, PO wording, inspection scope, payment decision, or broker instructions. Carry the result into the pre shipment factory instruction used by the next team.

Preserve evidence in the format closest to the original event: source PDF, email, photo, receipt, broker reply, or warehouse record. A summary should point back to those files rather than becoming the only record left in the folder. The next reviewer should find the answer under quality dispute without reopening the whole case.

Working checklist

  • Label the retained sample.
  • Take dated photos.
  • Link to PO and lot.
  • Record storage location.
  • Use sample in dispute review.

Sources used for this guide