2026-07-05 / 4 min read / sample value / commercial invoice / value basis

Supplier Combines Sample and Production Value

By Trado Asia editorial desk · Published 2026-07-05 · Updated 2026-07-18

Sample and production values should be separated when invoices, payments, or import records depend on them.

What to check in the order file

For combined sample and production value, that document is usually near sample invoice, production invoice, payment proof, commercial invoice, value note, packing list, and broker question.

A supplier may combine sample and production value to simplify paperwork or apply a prior sample payment to mass goods.

Sample and production values should be separated when invoices, payments, or import records depend on them. Another member of the team should be able to verify the answer from the file before production, inspection, or shipment approval. Make this result visible in the supplier combines value decision record.

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 save the earlier version beside the record the importer plans to use. The comparison should show who supplied the revision, when it arrived, and which order step depends on it. The commercial invoice file should show how this point was resolved.

Familiar commercial explanations can hide a real mismatch. Ask which company, document, quantity, model, payment, or shipment the answer covers, and record when the answer applies only to this order. Carry the result into the value basis instruction used by the next team.

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, order owner decision, and next checkpoint. Put that result in the sample value note for the current PO.

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

Make the decision before the next handoff

Use the checklist as a closing test: separate sample value, match payment proof, update invoice lines, and explain credit or offset. 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 value basis file should show how this point was resolved.

Give the exception an end point, such as receipt of a corrected record, payment confirmation, inspection, broker acceptance, warehouse receipt, or claim settlement. Put that result in the sample value note for the current PO.

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

If the issue returns, begin with the prior note. It should show which file to request first and which assumption caused the earlier delay. Keep the supporting file beside the supplier combines value entry in the order folder.

Retain 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. Name this point in the sample value closeout rather than leaving it in chat.

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. Put that result in the commercial invoice note for the current PO.

Close the record for the next order

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. Use the value basis record to show who accepted the result and on what date.

When the same exception affects several orders, add the field to the vendor baseline. Repeated problems belong in onboarding, PO wording, inspection scope, payment sign-off, or broker instructions. Carry the result into the supplier combines value 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. Link the answer to the commercial invoice checkpoint for this order.

The closeout needs both completion and limits. Completion means the controlling file is stored and the next owner has it; the limit states what the importer did not verify or approve. Make this result visible in the value basis decision record.

On the next order, read this note before a payment or shipment repeats the same condition. A clean record should shorten the review without hiding the original exception. Keep the supporting file beside the sample value entry in the order folder.

Separate sample value. Keep the original sample value file and the reviewed copy. Notes for supplier combines value belong on the reviewed copy, while the supplier file remains available for another team to examine. Use the supplier combines value record to show who accepted the result and on what date.