Export declaration: the data you need before the forwarder asks

An export declaration is the statement you make to your own customs authority about goods leaving the country: what they are, what they are worth, where they are going and under whose control. Almost none of it is new information. Every field is already sitting in a document you produced earlier, which is why the shipments that get held are rarely held because the exporter did not know something — they are held because the answer existed in three places and the three did not agree.

What goes into an export declaration

Work through it as a mapping exercise: field, source document, owner.

• Exporter identity and registration number — from your own trade registration, not retyped per shipment.
• Consignee and, where different, the party receiving the goods — from the order, not from the delivery address on the parcel label.
• Goods description in plain commercial language, matching the commercial invoice word for word rather than being paraphrased.
• Classification code and country of origin — from your product record, backed by whatever supported the certificate of origin if one was issued.
• Value and currency, on the same basis as the invoice, with the delivery terms stated so the authority knows what the number includes.
• Quantities, net and gross weight and package counts, which have to reconcile with the packing list and with the bill of lading.
• Licence or permit references for anything controlled, which is the field most often discovered at the last minute.

Where the delays actually come from

• Weights that differ between the packing list and the transport document, usually because one was estimated.
• A goods description written for the customer rather than for customs — a brand name where a material and function are required.
• A classification code copied from a similar product two years ago and never revisited after the product changed.
• Value stated without the delivery terms, so it is unclear whether freight and insurance are inside it.
• A controlled item nobody flagged, because the control applies to a component rather than to the finished product.

Filing through a forwarder or a broker does not move the liability. You are the declarant, the declaration is made on your data, and an error is yours to correct and yours to be penalised for. Treat the forwarder as a channel, not as an approver.

Keeping the data in one place

1. Hold classification, origin and controlled status on the product record itself, not on the shipment.
2. Give each of those three fields a review date, because products change and codes are reissued.
3. Record who decided a classification and on what basis — the reasoning is what you need years later, not just the number.
4. Reconcile weights once, at packing, and let every downstream document read from that figure.
5. Keep the filed declaration together with the invoice, the packing list and the transport document as one set per shipment.

Classification decides the paperwork. An ECCN tells you whether goods fall under export controls and which licence exception might apply, and getting it wrong is the expensive category of mistake.

Where the record lives

Ettex Records keeps the per-product trade data — classification, origin, controls, review date — as fields you can filter and sort, so preparing a declaration is a lookup rather than an archaeology exercise, and the shipment file is one place rather than an email thread. Ettex does not connect to any customs system and does not file on your behalf: the submission goes through your national system or your broker, and this is the data you hand them.