How to fill in declared value without causing problems

Both directions get you into trouble

The instinct is to declare low to reduce tax. That instinct causes more problems than it solves, because the declared value is also what an inspector compares against. Too low and the parcel gets held, which costs you time and often freight. Too high and you pay tax on a value the goods are not worth.

There is also a third failure, and it is the most common one operationally: the declared value does not match the commercial reality, usually because it was filled in by a rule of thumb rather than from a source.

Step one: find out what basis your channel uses

"Declared value" is not the same number everywhere. Some channels use the transaction price, some use a retail-referenced value, some leave it to the shipper's judgment within a range. The first question is therefore not "what number do I put" but "which number is this channel asking for."

Ask your forwarder for the basis, not for a recommended value. A forwarder quoting you a number is guessing on your behalf unless they tell you the rule behind it.

Write that basis down. A verbal answer is quite likely to come back as a different number a month later, and then you have nothing showing what you asked.

Step two: use a data source, not a rule of thumb

Where the number comes from	How reliable it is	Watch out for
The supplier's invoice or official website price	Good	Must match the product actually shipped
The platform's own listing price	Usable	Not the same as what you paid
Another product in the same category	Poor	Composition and spec differ, and it shows
A round number you picked	Poor	Obvious to an inspector, and hard to defend
Your own sales price overseas	Depends	Whether that is what the channel expects

The first row is the one to aim for. Everything else is an approximation, and approximations are what cause questions.

Step three: be consistent across the parcel

If a parcel contains several items, the declared values of the items should add up to the parcel's declared total. This sounds obvious and it is still the most frequent clerical error. So does the declared weight need to relate sensibly to the declared value — a very high value on a very light item invites attention.

Step four: decide who reviews it

If the value comes in automatically from your ERP, someone still has to review the mapping. If it comes from a form someone fills in, that form needs a check. Either way, name a person.

Yunque Post pulls orders in through official platform APIs across 17+ platforms, so values arrive from the platform rather than from a keyboard. That removes one whole class of error, but it does not remove the need to review them before you trust them. Youmanman Cloud Warehouse runs 14 value-added services including QC, and the review pass belongs in that inbound-side work rather than in the dispatch queue.

Step five: remember it can be changed, but not cheaply

A wrong value caught before the parcel is sealed is a one-minute fix. Caught after dispatch, it means a written amendment, and some carriers charge for that. Some cases cannot be amended at all. So the review has to happen at the point where it is still cheap, which is before the box is closed.

A pre-declaration checklist

Check	When	Why
Basis confirmed with the forwarder	Before first batch	The number changes depending on the answer
Value taken from supplier documentation	Per product	Removes approximation
Item values sum to the parcel total	Per parcel	Most common clerical error
Value and weight are plausible together	Per parcel	Prevents avoidable questions
Reviewer named and the review actually done	Per batch	Automation is not review
Value re-checked before sealing	Per parcel	Last cheap moment to fix it

FAQ

Q: Should I declare a low value to reduce tax? A: No. The declared value is compared against the commercial reality, and a figure that does not hold up causes holds and delays, which cost more than the tax you were trying to avoid. Use a value you can document.

Q: Can I use the same value for all my products? A: Technically you enter what you declare, but a single repeated number across unrelated products is not defensible. Use a value you can trace to a source per product.

Q: Where should the value come from? A: Supplier invoices or official site prices. The platform listing price is usable. Numbers borrowed from other products in the same category are the least reliable option.

Q: What happens if I get it wrong? A: If it is caught before sealing, it is a quick fix. After dispatch it needs a written amendment, and some carriers charge for it.

Q: Does an ERP-populated value save me work? A: It removes manual entry, which is a real saving. It does not remove the need to review, and a value that flows in automatically is only as good as the mapping behind it.

Not sure what basis your channel expects? Ask us on our contact page and we will check with you.