How do you ship to EU FBA as a non-EU seller without confusing freight, customs, and importer of record status?
A freight forwarder books movement.
A customs broker handles declarations.
An importer of record carries the import-side responsibility stack.
Those roles can sit with one provider in some arrangements. They do not automatically collapse into one role just because one company says they can "handle everything." That is the mistake buyers keep making when they try to ship to EU FBA as a non-EU seller. ([Agence Octo methodology])
The Reddit question is useful because it shows the exact confusion pattern: a seller outside the EU wants to send inventory to Amazon, assumes a broker may be enough, and then discovers terms like EORI, IOR, VAT, and consignee are being used as if they mean the same thing. They do not.
Watch the stack, not any single label.
What should a non-EU seller check before shipping to EU FBA?
Use this before inventory leaves the factory.
| Screen question | What you are testing | Why it matters |
|---|---|---|
| Who is named as importer of record on the entry, and where is that named in writing in the broker instructions or shipment file? | Whether responsibility is explicit or implied | If nobody will name the IOR in writing, the shipment structure is weak. ([Agence Octo methodology]) |
| Which entity's EORI or import registration is being used, and does it match the consignee, Incoterm, and lane plan on the booking? | Whether the import identity is real and assigned | A shipment plan that depends on a "broker account" without naming the underlying entity needs more proof. ([Agence Octo methodology]) |
| Has the customs broker confirmed the filing structure in writing for this exact lane, Incoterm, consignee setup, and pickup timing? | Whether the plan survives contact with the actual filer | Broker silence late in the process is a common sign that the shipment design was never really cleared operationally. ([Agence Octo methodology]) |
This is a sourcing screen, not regulatory confirmation.
If the seller, factory, forwarder, and broker give four different answers to those three questions, the shipment is not ready.
What do the official and market signals say about importer of record for non-EU sellers shipping to EU FBA?
The European Commission's public EORI guidance, including its EORI explainer pages for economic operators dealing with EU customs authorities, states that an EORI number is used to identify economic operators and other persons in their dealings with customs authorities in the EU. As a sourcing signal, that suggests the import identity is not a casual field that can be improvised after cargo is booked. [Bucket 1 — official]
Amazon's public seller and logistics documentation for EU fulfillment flows, including seller-facing guidance on inventory delivery and customs-related seller responsibilities for cross-border shipments into Amazon's network, indicates that shipping inventory to Amazon FBA does not by itself establish the importer-of-record structure. Based on public guidance, that is not a safe planning assumption. [Bucket 1 — official]
Named carrier and intermediary materials, including DHL customs-services guidance and UPS brokerage or customs-clearance service materials, commonly distinguish transport service, consignee details, and importer responsibility. The exact service menu varies by country, lane, and provider, but the recurring pattern is specific enough to plan against: movement service is not the same thing as importer status. [Bucket 2 — named third party]
Practitioner-reported signals from Reddit seller threads, including r/AmazonFBA thread 1ticvdw, show the same operational failure mode again and again: the shipment is physically ready, but the named entities on the import side are still unclear, so the stock sits, gets reworked, or never moves. Seller reports do not prove the legal rule in every lane. They do show where planning breaks in the real world. [Bucket 3 — Reddit seller reports]
Evidence calibration: official guidance helps frame identity and responsibility signals; named third-party materials show recurring operating patterns; Reddit threads are practitioner-reported and directional, not dispositive for every lane or entity setup. ([Agence Octo methodology])
What are the red flags when a non-EU seller is shipping to EU FBA?
Walk away from vague language.
"Don't worry, our broker handles it" is not a shipment plan.
A weak import setup usually shows up in one of these forms:
- The forwarder says they can do DDP but will not identify the importer entity in writing. ([Agence Octo methodology])
- The broker is introduced late, after Incoterms and routing are already agreed. ([Agence Octo methodology])
- The factory offers a one-line answer on customs structure outside its normal manufacturing role. ([Agence Octo methodology])
- The seller has an Amazon destination, but no clear import-side entity map before dispatch. ([Agence Octo methodology])
- One party says an EORI is "pending," but no fallback routing plan, alternate filing path, or revised pickup timing exists. ([Agence Octo methodology])
Any one of those on its own is not proof the shipment will fail. Stacked together, they are the canonical pre-clearance confusion pattern.
What should non-EU sellers lock before pickup when shipping to EU FBA?
The useful question is not "Can this shipment move?"
The useful question is "Whose structure is this?"
Before cargo pickup, a buyer should be able to point to one written chain that matches across the commercial invoice, shipment booking, broker instructions, and consignee setup. ([Agence Octo methodology])
That means:
- One named importer-side entity
- One matching import identification path
- One broker-confirmed filing structure
- One clear handoff from factory documents to customs documents
Quick checklist:
- Named IOR entity confirmed in writing
- EORI or import registration path matched to that entity
- Broker confirmation tied to the exact lane, Incoterm, and consignee
- Commercial invoice, booking, and broker instructions aligned before pickup
If those four elements do not agree, the shipment is still in negotiation, even if the cartons are packed.
Where does Periscope fit when a non-EU seller is shipping to EU FBA?
Periscope is not a customs filing service.
It is the pre-shipment intelligence layer.
For EU FBA lanes, that means pressure-testing whether the supplier, forwarder, and broker are describing the same operating model before inventory is committed. The goal is not to replace licensed advisors. The goal is to catch the mismatch early enough to avoid dead stock, re-routing, and margin erosion. Teams using this kind of pre-shipment screen can also use Periscope supplier intelligence software to compare supplier and lane signals before pickup. ([Agence Octo methodology])