Marketplace vs Own-Site Multi-Country Selling: How Fulfilment Requirements Differ
17.08.2026
DAC7 Digital Platform Reporting: What Multi-Country Sellers Must Provide to Marketplaces
17.08.2026
FLEX. Logistics
We provide logistics services to online retailers in Europe: Amazon FBA prep, processing FBA removal orders, forwarding to Fulfillment Centers - both FBA and Vendor shipments.
A seller running stores across Germany, France and Spain sets a 14-day return window for one market and assumes local custom lets them shorten it elsewhere. It does not. The Consumer Rights Directive gives every EU consumer the same 14-day right of withdrawal on distance and off-premises contracts, regardless of which member state receives the parcel. There is no shortest-common-denominator version a multi-country seller can apply. The rule is harmonised at 14 days as a floor, not a suggestion tied to local habit or marketplace defaults. This matters operationally because return windows, refund timing, and now an online cancellation mechanism all sit downstream of this single EU-wide baseline. Get the baseline wrong in one market and the exposure is not theoretical: it shows up as refund disputes, marketplace policy violations, or a returns processing service that cannot reconcile what each country actually requires.
What the 14-Day Period Actually Covers
Article 9 of the Consumer Rights Directive gives consumers 14 days from delivery to withdraw from a distance or off-premises purchase, and they do not need to give a reason. That period runs from the day the consumer (or a third party they designate) physically receives the goods, not from the order date or invoice date. For split shipments, the clock generally starts once the last item in the order arrives, which matters for sellers who ship multi-item baskets from different warehouses.
The consumer does not need to justify the return, and a trader cannot impose extra conditions such as requiring original packaging in perfect condition beyond what is reasonable for inspecting the goods. This is the mechanic that most often trips up sellers building their own return address in Spain or a national returns hub: the intake process has to accept a withdrawal notice without demanding proof of fault, because none is required under this right.
Who Bears the Return Postage
Article 14 puts the direct cost of returning goods on the consumer by default. That default only holds if the seller has clearly disclosed it before the order was placed. If the trader fails to inform the consumer that they will bear the return cost, the trader ends up covering it instead, regardless of what the checkout page assumed.
This is a disclosure test, not a generosity test. A seller can legally pass return shipping cost to the buyer across every EU market they sell into, but only if the terms and checkout flow state this clearly before purchase. Silence, vague wording, or a policy buried three clicks deep does not satisfy the requirement.
What Breaks When Disclosure Is Missing
A seller who assumes 'customer pays returns' without confirming this is stated pre-purchase in every storefront and marketplace listing can end up absorbing return postage on disputes they thought were the buyer's cost. Multiply that across markets and the leak compounds, because checkout templates, marketplace-hosted listings, and localised terms pages do not always carry the same disclosure.
The operational consequence lands in the refund reconciliation queue: someone has to decide, market by market, whether the seller failed to disclose and therefore owes postage. Without a documented answer, customer service teams either overpay refunds as a safety default or underpay them and generate disputes, both of which cost more than fixing the disclosure gap once.
A practical control point: before adding a new EU storefront, check that its checkout and terms pages state, in plain language, who pays return shipping and under what conditions. This single check prevents the most common cross-border withdrawal dispute. It also gives a returns processing service a clean rule to apply at intake rather than making a judgment call per parcel. Sellers using pre-Amazon storage or a shared EU return address should confirm the disclosure text matches what each national storefront actually displays, since templates copied between markets can drift out of sync over time without anyone noticing until a refund dispute forces the review.
The Exceptions Are EU-Wide, Not a Local Custom
Article 16 sets out a fixed list of exceptions that apply the same way in every member state: goods made to the consumer's specifications or clearly personalised, perishable goods, sealed goods that cannot be returned for health or hygiene reasons once unsealed, sealed audio, video or software once unsealed, and digital content where the consumer expressly agreed to lose the withdrawal right once delivery started.
These exceptions are narrow and specific. A seller cannot invent a broader exception because a national market seems to expect one, and cannot assume that a marketplace's own return policy overrides the statutory list. If a product genuinely falls under one of these categories, it needs to be flagged clearly at the point of sale so the exception is enforceable later, not just assumed by the warehouse team handling returns processing.
What to Check Before Assuming an Exception Applies
Confirm the product is genuinely personalised or made-to-order, not just customisable in a minor way. Confirm hygiene-sealed items are labelled as such before shipping, since the exception depends on the seal being intact when the consumer received it. Confirm perishable-goods handling matches the category, and confirm any digital content consent was captured and stored, not just assumed.
What Goes Wrong When Exceptions Are Assumed
A generic sticker on packaging is not proof of a hygiene seal in a dispute. A product marketed as 'customisable' but sold in standard configurations does not automatically qualify as made-to-order. When an exception is applied incorrectly, the seller ends up refusing a legally valid withdrawal, which becomes a chargeback, a marketplace complaint, or a regulator inquiry rather than a routine return.
Local Variation Sellers Often Miss
The 14-day period is a floor, not a ceiling. Some member states extend withdrawal rights beyond the EU minimum in specific contexts; Lithuania, for example, grants a right of withdrawal in certain in-store purchase scenarios that go beyond what the EU-wide rule requires for distance selling. This is a country-specific extension to check market by market, not a universal EU rule to build into every storefront by default. A multi-country seller cannot standardise on the shortest policy and assume it covers every market, because a local extension can sit on top of the harmonised baseline without contradicting it.
The New Withdrawal Button Requirement
A newly added Article 11a under the Distance Marketing Directive amendment introduces a binding requirement that many multi-country sellers do not yet have on their radar: traders selling online to EU consumers must provide an online withdrawal function that is easy to find, clearly visible, and available throughout the entire 14-day period. This is not a best-practice suggestion. It is a compliance deadline set for 19 June 2026, and it applies to the seller's own website or interface, not only to marketplace-hosted listings.
For sellers operating multiple storefronts, this means the withdrawal function needs to exist and function identically across every domain and checkout flow they run in the EU, not just the largest market. A seller who built one polished cancellation flow for their flagship site and left older regional sites with a contact-form-only return process will need to close that gap before the deadline, since Article 11a does not distinguish between primary and secondary storefronts.
What to confirm before 19 June 2026:
- An online withdrawal button or function exists on every EU-facing storefront the seller operates.
- The function is visible without requiring the buyer to search through account settings or contact support.
- It remains available and functional for the full 14-day withdrawal window on every order.
- It works consistently across desktop and mobile checkout paths.
Operational gaps to check at intake:
- Whether the return address in each market matches the disclosed return process the consumer agreed to.
- Whether refund timing rules are documented per market, not assumed from one template.
- Whether excepted categories (personalised, sealed, perishable) are flagged before shipping, not after a return arrives.
- Whether carton compliance and sellable-status checks are recorded at receiving to support refund decisions.
Sequencing the Fix Across Markets
The practical starting point is not the withdrawal button; it is confirming the 14-day baseline and return-cost disclosure are correct in every market first, since a compliant cancellation function built on top of an incorrect disclosure just automates the wrong outcome faster. Once disclosure and exception-handling are verified market by market, the online withdrawal function becomes the next build item, with enough runway before the 2026 deadline to test it against real order volume rather than launching it untested.
Ownership matters here. Someone on the seller's side needs to own the legal-text layer (checkout disclosure, terms, exception labelling), while the operational layer, receiving returns, verifying exceptions, processing refunds, sits with whoever runs returns processing for that market. When those two owners are not clearly separated, disputes get resolved inconsistently because the warehouse team is making legal interpretations it was never asked to make.
In practice, a seller running FBA prep services alongside its own DTC storefronts often discovers the gap here: Amazon's own returns mechanics do not automatically satisfy Article 11a for the seller's independent website. The two channels need separate verification. A returns workflow built for Amazon FC forwarding and marketplace returns does not cover a self-hosted checkout unless someone has explicitly checked that the same withdrawal function and disclosure text exist there too.
Baseline
14 days from delivery, no reason required, applies uniformly across every EU market a seller sells into.
Disclosure
Return postage defaults to the consumer only if the seller discloses this clearly before purchase in every market.
2026 Deadline
An online withdrawal function must be visible and functional on every EU storefront by 19 June 2026.
What to Lock Down Before the Next Market Launch
The decision a multi-country seller needs to make is not whether the 14-day right applies; it does, everywhere, without exception for local custom. The decision is whether the current setup, checkout disclosure, exception labelling, refund reconciliation, and the coming withdrawal button, is verified per market or just assumed from the largest storefront. Treat this as a checklist to run before adding any new EU market, not a one-time compliance project. A returns processing service that can apply consistent rules across markets removes the guesswork from refund disputes, but it only works if the underlying legal-text layer, checkout disclosure and exception flags, is correct first. Confirm those, then build or audit the online withdrawal function well ahead of the 2026 deadline rather than in the final weeks before it applies.
This explainer covers the mechanics of the EU withdrawal right as currently in force; it is not legal advice, and sellers should confirm their specific obligations with qualified counsel, particularly around the 2026 withdrawal-button deadline and any country-specific extensions like the Lithuanian example noted above. Contact the FLEX. team if the operational side needs work ā consistent return address handling, refund-ready receiving, and returns processing services that apply the same rules across every EU market, without touching the legal decisions that remain the seller's responsibility.
