Compliant declaration: how to get it right so shipments are not held
Most holds originate in the paperwork. Here is a five-field declaration self-check, how to sequence restricted categories, and one QC step that catches problems before dispatch.
Five fields, and most holds come down to them
A declaration is not a complicated document. It is a small number of fields, and each one has an obvious way to be wrong. When a shipment is held, the reason is nearly always in one of these:
| Field | What goes wrong | The fix |
|---|---|---|
| Description | Vague, or not what is in the box | Name the actual contents in plain terms |
| Quantity | Counts the units but misses accessories | Count what is physically in the carton |
| Value | A round arbitrary figure, or under-declared | Match the real transaction |
| Origin | Generic or missing | State where the goods are from |
| Category | Wrong heading for the product | Use the heading your channel expects |
Under-declared value deserves its own note. It feels like a saving and it is not. Duty is still assessed; what changes is that you have converted a duty question into a seizure question, and you have less room to argue about the outcome.
Make the description match the box
This is the single most common cause. "Samples", "gifts", "samples and gifts" and "personal belongings" are not descriptions. They are statements that invite a question.
A usable description names the product and what it is made of or contains, in words a customs officer can match to what they see when they open the box. Where a channel expects a particular wording for a category, use that wording rather than your own.
The practical test: read your description next to the actual carton contents. If a stranger could not tell whether they match, rewrite it.
Count what is in the carton
Accessories are where counts go wrong. Two cables in the box, one unit declared. A gift with a spare tip. A set shipped as separate SKUs but declared as one.
This is a physical count, not an estimate, and the person who does it should not be the person who wrote the order. Inbound QC exists for exactly this reason: at Youmanman Cloud Warehouse it is one of 14 value-added services performed at inbound rather than occupying back-end time, so a mismatch gets caught while the goods are still together and can be fixed.
Handle restricted goods in the right order
Restricted categories are not a declaration problem. They are a "should this ship at all on this channel" problem, and asking that question earlier saves everything downstream.
The order that works:
- Decide whether the product is permitted on your channel at all
- Then check the packaging requirements for that category
- Then write the declaration in the wording that channel expects
Doing it in the wrong order — writing the declaration first, then checking restrictions — means rewriting the paperwork and possibly repacking.
| Category | The specific issue to resolve |
|---|---|
| Batteries and battery devices | Many channels restrict these or require specific handling — confirm before packing |
| Liquids | Per-item volume limit, plus leak-proof packing |
| Powders and pastes | Restricted on more channels than most sellers expect |
| Aerosols and compressed cylinders | Commonly prohibited |
| Blades | Commonly prohibited |
| Live plants and animals | Prohibited |
| Tobacco and alcohol | Prohibited |
Check before you pack, not after. The Cloud Warehouse facts page lists the restricted categories we handle and which ones need a channel check first.
One QC action catches most problems
There is a single check that would prevent a large share of holds, and it takes minutes per carton:
- The description on the declaration matches what is physically in the carton
- The quantity matches the physical count including accessories
- The value matches the actual transaction
- The category heading is the one your channel expects
- The carton is labeled in the format required, and the label is flat and scannable
That last one catches a separate class of problem: a parcel that is entirely compliant but gets set aside because the label cannot be read.
Keep one version of the answer
The failure mode is not one bad declaration, it is five slightly different declarations for the same product. Different people, different days, different wording.
Fix it with a small document that anyone can read:
- One list of every SKU with its category
- The exact description wording for each category
- Which channel each category travels on
- Who signs off when a new SKU is added
If the answer to "what do we declare for this" requires asking a person, the answer will eventually be wrong.
Where it lands operationally
All of this becomes one question in practice: can your warehouse receive goods, check them, and produce a declaration that survives being opened?
Youmanman Cloud Warehouse runs 14 value-added services at inbound — QC, labeling, relabeling, hangtag swapping, vacuuming, photography among them — so the check happens before the parcel leaves rather than after it is held. Over 100 international routes cover the US, Europe, Japan, Southeast Asia, the Middle East, Latin America and Australia, and shipping starts from one piece. Small-item storage is waived for the first 90 days along with the system usage fee; line-haul freight is settled normally.
Yunque Post connects to 17+ platform official APIs, so category and SKU data comes from the order system rather than being retyped — and retyped data is where description drift starts. Storage runs up to 180 days, which gives room to fix a product line before committing to another production run.
FAQ
Q: What description should I use? A: One that names what is actually in the box, in plain terms. Where your channel expects a specific wording for a category, use that. Read it next to the physical contents and ask whether a stranger could tell they match.
Q: Is under-declaring value risky? A: Yes. Duty is still assessed, but the problem changes from a duty question into a seizure question. Consistency costs less.
Q: How do I handle batteries and liquids? A: Check channel rules first, not declaration wording. Batteries are restricted on many channels. Liquids have a per-item volume limit and need leak-proof packaging. Confirm both before packing.
Q: Should accessories be declared? A: Yes, count what is physically in the carton. Two cables in the box means two cables declared. This is a physical count, not an estimate.
Q: What is the single most useful check? A: Read the declaration next to the actual carton contents before dispatch. Most holds would not happen if someone did this once per carton.
Want a compliance review of your documentation? Send your product list, categories and shipping channel through our contact page and we will go through it with you.