Table of contents
Platforms, payment rails, and parcel networks are shifting fast, and for cross-border sellers the pressure is landing in a familiar place: customs compliance. As marketplaces tighten their onboarding, as carriers digitise pre-advice, and as tax authorities scrutinise data trails, a missing or misaligned EORI number can turn a routine shipment into a costly delay. The question is no longer whether you “have an EORI”, but whether your strategy matches the way digital trade now moves, and whether you can keep pace as requirements evolve across Europe.
Marketplaces are policing borders, quietly
Compliance used to sit in the background, handled by freight forwarders and rarely visible to the customer. That separation is eroding, and big marketplaces increasingly act as gatekeepers because they carry reputational and operational risk when cross-border parcels jam at customs. The European Union’s post-Brexit reality has made this more tangible: UK-EU trade in goods now runs through full customs formalities, and EORI identification is a baseline requirement for many declarations, even when sellers think they are “just” using a platform and a carrier.
The scale of the stakes is easy to underestimate until you look at the volumes. Eurostat data shows the EU’s e-commerce turnover has grown sharply over the past decade, and while growth rates vary by country and year, the direction is consistent: more parcels, more small consignments, more frequent cross-border flows. Customs authorities, meanwhile, have been explicit about moving toward data-led controls, with more emphasis on electronic pre-arrival information, risk scoring, and consistent identifiers that connect traders, shipments, and declarations. In that environment, an EORI number is not a bureaucratic footnote; it is one of the keys that helps authorities link a business to its movements across borders, and it is increasingly expected upstream, long before goods touch a frontier.
That “upstream” shift matters because the friction now hits at account creation and listing expansion, not only at the moment a pallet leaves the warehouse. Sellers expanding into new EU markets can be asked for documentation earlier, and carriers may require accurate customs data to avoid handover failures and returns. The operational impact is measurable: each day of delay ties up inventory, adds storage charges, risks missed delivery promises, and can trigger platform performance penalties. In a world where conversion depends on fast shipping and reliable tracking, a compliance bottleneck becomes a commercial problem, and not merely a legal one.
One number, many scenarios, real pitfalls
It sounds simple, and that is why it goes wrong. An EORI is a trader identification number used in customs procedures in the EU and UK, but the way you need it depends on where you are established, where goods are moving, and who is acting as importer or exporter of record. Add the rise of marketplace fulfilment models, and the map gets messy quickly: stock can sit in multiple countries, returns can cross borders unexpectedly, and the party responsible for the customs declaration may differ from the party receiving the customer payment.
Consider the practical scenarios that trip businesses up. A UK company shipping direct-to-consumer to EU buyers typically needs a UK EORI for UK exports, and may need an EU EORI if it is acting as importer into the EU in certain setups, for example when it handles import formalities or holds stock in the Union. An EU seller shipping to the UK may face the mirror image. Then there are businesses established outside both the EU and UK, using marketplaces to reach European consumers; they may need representation arrangements depending on the import model, and they often discover late that a number issued in one jurisdiction does not automatically solve obligations in another.
The risk is not only “no EORI”, but also the wrong EORI used in the wrong place, or an EORI tied to an entity that is not actually the contracting trader, which can trigger mismatches in customs systems. Errors like that are disproportionately disruptive because they are hard to fix mid-flow, and because customs data increasingly needs to reconcile across multiple actors: shipper, declarant, consignee, carrier, and sometimes the platform itself. When those identifiers do not align, parcels can be held for clarification, returned, or subjected to additional checks, and while the legal framework varies by route, the operational result looks the same to the customer: a delay and a loss of trust.
What does a resilient strategy look like in 2026’s marketplace environment? It starts with treating EORI as part of your expansion planning, not as a last-minute checkbox, and it continues with clear internal ownership: which legal entity sells, which entity imports, which entity holds inventory, and how those roles change across fulfilment options. It also means ensuring that the data shared with carriers and customs brokers is consistent across invoices, shipping labels, commercial documentation, and electronic messages, because digitisation punishes discrepancies. If you need a practical entry point to understand how the process works and what information is typically required, you can try this site, then map what you learn to your own operating model and routes.
The data trail is tightening across Europe
Customs is becoming more digital, more interconnected, and more demanding about data quality, and that shift is accelerating under EU modernisation plans. The European Commission’s customs reform package, presented in 2023, proposed a new EU Customs Data Hub, a move intended to centralise and simplify data submission while strengthening risk management. Even before any full implementation timeline plays out, the direction is clear: authorities want earlier, cleaner, standardised information, and they are building systems that can cross-check it more efficiently.
At the same time, tax and customs changes over recent years have already reshaped parcel trade. The EU’s VAT e-commerce package in 2021 removed the low-value VAT exemption and expanded the Import One-Stop Shop, and while IOSS is a VAT mechanism rather than an EORI instrument, it has reinforced a broader trend: e-commerce compliance is increasingly systematised, and authorities expect digital identifiers that allow quick linkage between a seller, a transaction, and a shipment. For businesses, the practical consequence is that compliance errors are less likely to be “smoothed over” by manual workarounds, and more likely to be caught by validation rules, data matching, or automated risk filters.
Carriers are also part of the tightening net. Express operators and postal networks rely on electronic pre-advice and data sharing to move volumes efficiently, and when data is missing, the operational cost is high. That is why they push back requirements onto shippers, and why sellers feel the pressure earlier in the sales process. In many lanes, the difference between a parcel that sails through and one that stalls can be a handful of fields entered correctly: commodity description, value, origin, and the right identifiers for the actors involved. An EORI strategy that is treated as static, or delegated without oversight, struggles in this environment because the data trail is now continuous from checkout to clearance.
None of this means that every business will face the same burdens, and compliance must be tailored to scale, product category, and routing. But it does mean that digital marketplaces are not “hiding” customs any more; they are exposing it through stricter onboarding, performance expectations, and faster feedback loops when deliveries fail. The winners are often not the companies with the largest budgets, but the ones that build a repeatable process: documented responsibilities, validated data, and a clear plan for where identifiers are needed, updated, and stored across systems.
Keeping pace without paralysing the business
Speed is the promise of digital commerce, but the route to speed is often boring: process discipline. The most effective approach is to treat customs identifiers and documentation like product data, something maintained with the same seriousness as pricing or inventory. That begins with an audit of routes and responsibilities: where you ship from, where you ship to, where returns go, whether you use marketplace fulfilment, and which party is importer of record on each lane. From there, you can identify whether you need an EORI in the UK, the EU, or both, and whether different legal entities inside your group create additional requirements.
Next comes execution: aligning your checkout, invoicing, and shipping tools so the right identifiers flow automatically to carriers and brokers. Many businesses only discover misalignment when a shipment is held, but the preventative fix is usually straightforward: make the “single source of truth” explicit, lock down who can edit core compliance fields, and test data outputs when you add a new warehouse, a new marketplace channel, or a new carrier integration. It also pays to create escalation playbooks. When something is stopped at the border, minutes matter; you need to know who contacts the broker, who provides supporting documents, who authorises duties and VAT payments, and who communicates with the customer and the platform.
Finally, keep an eye on change, and not just legal change. Marketplaces update their seller policies, carriers adjust data requirements, and authorities roll out system upgrades; each can produce new failure modes even if the law is unchanged. Building a quarterly review into your operations, especially if you are expanding into new countries or adding SKUs with different compliance profiles, can prevent “surprise” disruptions. This is also where training matters: teams in customer service and warehouse operations should know what an EORI is used for, what information cannot be improvised, and what documents must match, because the fastest way to create a customs problem is to patch a missing detail under pressure.
What to budget, what to prepare, when to act
Plan EORI work like a launch task: assign an owner, gather company details early, and allow lead time before peak season, because the real cost is not the application itself but the disruption if you wait. Budget for broker support, data clean-up, and system changes, and check whether any local schemes or guidance reduce friction for SMEs. Above all, test new lanes before scaling.
Similar articles


