Seller of Record vs. Merchant of Record for Physical Goods: What EU Expansion Actually Requires

If you’re a non-EU brand researching how to structure EU sales operations, you’ve likely run into both terms: Seller of Record (SoR) and Merchant of Record (MoR). They are often used interchangeably. They shouldn’t be, particularly if you’re shipping physical goods. The distinction matters a great deal when you are deciding who is legally accountable for VAT collection, customs import duties, Importer of Record obligations, and EPR registration inside the EU.

Almost every comparison article on this topic, including those from Stripe, Paddle, and similar platforms, was written from a digital goods and SaaS perspective. That framing made sense when these terms first emerged. It does not map cleanly onto physical goods crossing EU borders. When you add customs clearance, an Importer of Record requirement at the EU frontier, per-country EPR registrations for packaging and electronics, and Amazon’s marketplace deemed-supplier rules, the MoR model as understood in the SaaS world leaves significant gaps.

This post breaks down what each model actually means for physical goods in the EU expansion context, where they differ in practice, and how to think about the right operating structure for your business.

Starting with definitions, not marketing terms

Neither term has a single legal definition in EU law. What exists in EU regulation is a set of obligations: who is the VAT-registered seller, who is the Importer of Record, who is the responsible person under product safety regulations, and who is the marketplace “deemed supplier.” The labels SoR and MoR are frameworks that attempt to describe who absorbs those obligations.

Where the models overlap, and where they break down

For digital goods and SaaS, a Merchant of Record model is genuinely useful. You pay a platform like Paddle or FastSpring a percentage of revenue, and they handle VAT across EU jurisdictions, issue invoices, manage compliance filings. The product never crosses a border. There is no Importer of Record. No EPR registration. No customs clearance. It works.

For physical goods, the model has to do significantly more work. Goods have to be imported. Someone has to be named on the customs entry as the Importer of Record. VAT has to be paid at point of import, or deferred via a fiscal representative. If the goods are in categories like electronics, packaging, or batteries, Extended Producer Responsibility (EPR) registrations are required in each EU member state. If you’re selling on Amazon EU, Amazon now enforces “deemed supplier” rules that require a VAT-registered entity in the supply chain.

SoR vs. MoR: What each model actually covers for EU physical goods

The EU obligations that most brands underestimate

If you’re entering the EU market from outside the bloc, the compliance surface is wider than most founders expect. Here are the pieces that consistently catch brands off guard:

Each of these requires a different piece of infrastructure, a different filing, or a different registration. The operational problem isn’t understanding what’s needed. It’s that most brands try to assemble this across four or five disconnected providers, each managing their own slice with no shared accountability for the whole.

The operating model problem, not a software problem

Here’s where most conversations about SoR vs. MoR go wrong: they frame the decision as a software or platform choice. Which tool do you subscribe to? Which API do you integrate?

That framing works for billing infrastructure. It does not work for EU market entry. What you actually need is an operating structure: a legal entity or contractual arrangement that can absorb EU obligations on your behalf, interact with customs authorities, hold VAT registrations, and be named on the relevant compliance documents.

The difference isn’t cosmetic. When a customs authority queries your import documentation, there needs to be one named entity that responds. When Amazon requests your VAT certificate for Germany, there needs to be a registered seller entity. When an EPR body in France issues a compliance notice, there needs to be a registered producer. A SaaS platform that handles billing does not cover any of these scenarios.

Which model is right for your expansion?

The honest answer depends on what you’re selling and how you plan to sell it.

How a Seller of Record structure actually works for physical goods

To make this concrete: when a non-EU brand engages EuroSOR as its EU Seller of Record, here is what the operating structure looks like in practice:

The entire chain, from import to final sale, is managed under one accountable operating layer. The brand retains ownership of the product and the customer relationship. EuroSOR takes accountability for the compliance structure that makes selling in the EU legally viable.

Common questions: answered for physical goods brands

Summary: What to take away from this

The SoR vs. MoR question comes down to one practical distinction: what kind of goods are you selling, and what does the EU require from a legal standpoint to sell them compliantly?

For digital goods, MoR platforms do the job. For physical goods entering the EU, whether through DTC, marketplaces, or distributor channels, you need an operating structure that covers import, VAT, EPR, and marketplace compliance as a unified system. That is a Seller of Record function, not a billing tool.

The fragmented approach of stitching together a customs broker, VAT agent, EPR service, and 3PL is not wrong in principle. But it creates coordination overhead, gaps in accountability, and real operational risk at exactly the point when your EU business is growing and needs to run cleanly.

The value of a proper SoR structure is not that it’s cheaper than the sum of its parts (though often it is). It’s that it replaces fragmentation with accountability: one entity, one relationship, one operating layer.