EORI numbers for ecommerce inventory entering the EU

Name the importing party

Before stock leaves the origin country, the brand should identify the entity that will act in the customs process. That may be the seller, an EU entity, or another appointed party depending on the structure. The warehouse address alone does not answer this question.

The importing party decision affects who supplies the EORI number, who appears in customs records, and who should work with the broker. A fulfilment provider can receive goods after release, but it should not be treated as the importer unless a separate, explicit arrangement and adviser review support that role.

• Record the legal entity connected to the shipment.
• Confirm whether the EORI belongs to that entity.
• Do not use a warehouse address as a substitute for role clarity.

Decide where the declaration is made

Goods may enter through a port, airport, or other customs point before reaching the fulfilment warehouse. The declaration location can differ from the final storage location. The operations team should understand that route because delays often happen before the warehouse can see or control the inventory.

The broker or customs adviser should confirm what information is needed for the chosen route. The warehouse may need inbound booking details, carton counts, and expected arrival timing, but it may not be the party submitting the declaration.

• Map port of entry, clearance step, and final warehouse.
• Give the broker shipment data before departure where possible.
• Tell the warehouse when customs release is expected.

Create a clean data handoff

The EORI number is only one field in the import file. Brokers also need product descriptions, values, origin, commodity codes, invoice details, transport documents, and contact information. Missing or mismatched data can stop a shipment even when an EORI number is valid.

Use a pre-shipment checklist owned by one person. That owner should collect the EORI, commercial invoice, packing list, product master data, and warehouse inbound reference. This prevents each party from assuming someone else has sent the missing field.

• Use consistent entity names across documents.
• Match SKU data to carton and pallet information.
• Keep broker contacts visible to the warehouse team.

Separate customs work from receiving work

Customs clearance and warehouse receiving are different steps. Clearance decides whether goods can enter the customs territory under the declared process. Receiving checks whether the physical stock that arrives matches the inbound booking and can be put away.

A clean EORI process will not fix poor carton labels, missing SKU data, or unannounced mixed cartons. Likewise, a correct warehouse booking will not fix an importer role problem. Treat the two workstreams as connected but separate.

• Give the warehouse the inbound reference, not only customs documents.
• Define discrepancy rules for overages and shortages.
• Keep customs holds outside promised launch dates.

Avoid common assumptions

A common mistake is assuming that the 3PL can provide an EORI number as part of ordinary fulfilment. Another is assuming that one successful shipment proves the structure is correct for every product, port, or country. Both assumptions can create avoidable risk.

Another mistake is treating EORI as a tax registration or product compliance approval. It is not a replacement for VAT review, product safety review, labelling checks, or importer responsibility analysis. Qualified customs and tax advisers should confirm how the brand's facts apply.

• Do not confuse EORI with VAT registration.
• Do not confuse customs clearance with product approval.
• Do not assume a broker can repair missing commercial decisions.

Build an operational owner map

The practical output should be an owner map. It lists who supplies the EORI, who appoints the broker, who approves commodity data, who books the inbound, who receives customs updates, and who tells the warehouse when release is complete.

This map is useful because most import delays are cross-functional. Purchasing, finance, logistics, compliance, and customer launch teams all need different parts of the answer. A short owner map keeps the import movement from becoming a chain of private messages.

• Name one shipment owner before goods depart.
• Store final customs data where finance can retrieve it.
• Review the handoff after the first inbound is closed.

Information to include in a fulfilment brief

• An EORI number belongs in a wider importer and customs data handoff.
• The warehouse address does not decide who imports the goods.
• Customs clearance and warehouse receiving are connected but separate processes.
• A valid EORI does not replace VAT, product, or legal review.
• Broker files need consistent entity names, product data, and shipment documents.
• A simple owner map can prevent import tasks from falling between teams.

VareYa can scope the warehousing and fulfilment work from a clear operating brief. Customs, tax, product and legal responsibilities should be checked with qualified advisers before inventory moves.

Questions teams often ask

Related VareYa Knowledge Center guidance

• How to send inventory to a European fulfilment partner
• Bonded warehouse considerations for ecommerce brands
• Ecommerce warehousing in the Netherlands
• IOSS versus local EU inventory for ecommerce orders
• DDP versus DAP for ecommerce shipments to Europe
• EU VAT operational checklist before appointing a 3PL