Shipping Free Samples: Keep the Customer Price Separate From Customs Valuation

If your shop or operations app sends goods without charging the recipient, do not make the customer price the only value available to the shipping workflow. A free sample can have no amount payable by that customer while still needing an evidenced customs valuation. Decide how your app records that difference before connecting it to a carrier or declaration service.

This is a commissioning guide, not a method for determining a customs value or obtaining duty relief. The example below uses HMRC guidance about imports to the UK. Other destinations and particular goods need their own qualified customs review. A label saying “sample” is not an automatic decision about tax or admissibility.

Record the commercial reason before choosing a value

Imagine a fictional supplier sending a demonstration item to a potential UK buyer. There is no sale and no customer payment. A different parcel contains paid goods with extra testers included under the sales agreement. Both might show a free line in the shop, but that does not establish identical valuation treatment.

Ask the app to record why the goods are being sent and how the free item relates to any underlying agreement. Distinguish a standalone no-charge dispatch from an item included in a paid transaction. Preserve a reference to that agreement rather than reducing the distinction to a checkbox called “free”.

HMRC's official Free charge goods guidance explicitly distinguishes these situations. It also notes that no-charge goods need not be low-value goods: equipment can be supplied without payment too. Do not make “free” a synonym for negligible value in the product catalogue.

Keep the approved valuation and its evidence separate

For goods supplied without a sale or other consideration, HMRC says Method 1 cannot be used because there is no price paid or payable by the importer to the supplier. Its guidance includes a qualification for goods imported pre-sold with evidence of that sale and discusses other valuation methods. The app should route the actual facts for review, not select a method merely because an order total is zero.

In the project brief, ask for separate fields or records for the customer charge, the customs value and currency, the approved valuation basis, supporting evidence and the person responsible. A value entered for customs should not quietly create customer debt or increase sales revenue. Conversely, a sales discount must not silently overwrite an already reviewed declaration value.

Have the customs specialist decide which adjustments and supporting documents are required. HMRC's page also discusses transport-related costs in the UK customs value. Do not implement a generic “use catalogue price” shortcut and assume it represents the complete declared amount.

Do not add a second value to every bundled free item

A rule that assigns a separate extra value to every zero-priced line can be wrong too. For the arrangements described in its guidance, HMRC treats certain free replacements in the same shipment as covered by the sale price for the total quantity. It also explains the treatment of samples and testers included in the contracting arrangements for paid goods.

The software requirement is therefore an explicit, reviewed treatment of the shipment, not an automatic nominal amount per free item. Retain the quantities, item descriptions and contractual connection so the specialist can explain the chosen basis. This article does not prescribe the valuation of your actual bundle or extend those UK examples to every promotion.

Separate document readiness from a created shipping label

A carrier label can exist while the supporting customs information is still awaiting review. Ask the app to show which shipment facts and document version were approved. If the contents change after approval, require the agreed reassessment rather than treating a printable label as proof that the declaration is ready.

Define who can resolve missing evidence and how staff retrieve the approved export information without altering the customer invoice. If the provider accepts data electronically, demonstrate what was actually submitted. A local PDF is not proof that the carrier or declaration service received the same values.

Accept the workflow with different no-charge cases

Use synthetic shipments without dispatching real goods. Demonstrate a standalone sample, paid goods with contractually included testers, a missing valuation basis and a changed quantity after approval. Compare the sales amount, reviewed customs information and provider submission separately.

Have the customs specialist approve the treatment of each test case. Check that a free sample does not generate an unintended receivable, and that a zero customer price does not erase the customs review requirement. Bring blank sample-dispatch and supporting-document examples to a shipping-app project discussion. The useful result is a traceable handover of reviewed facts, not a declaration generated from an unexplained zero.