Amazon Made the Netherlands Mandatory for Pan-EU FBA on September 3. Belgium Is Next.

As of September 3, every product enrolled in Pan-European FBA needs an active offer on Amazon.nl. Not just new enrollments. Every ASIN in the program, including the ones that have been sitting there since 2019. Belgium becomes a required market on February 26, 2027.

The recommendation, up front: pull your full Pan-EU enrolled ASIN list this week, reconcile it against your live Amazon.nl offers by SKU, and fix the gaps before Q4 volume starts. This is a two-hour audit that protects your European fulfillment economics. It is also the kind of quiet requirement that does not announce itself with a suspension email.

What actually changed

The requirement is narrow and specific. To keep Pan-EU FBA benefits, every enrolled product needs an active offer on Amazon.nl using the same SKU as your other European listings. The required store list is now France, Germany, Italy, Spain, and the Netherlands.

Three things did not change, and sellers are conflating all three:

You do not have to store inventory in the Netherlands. The storage-placement rules are untouched. You still enable at least two countries for Amazon to distribute your stock, and that can be any combination of France, Germany, Italy, Spain, or Poland. Enabling Germany alone on the placement side covers you for the September change with no distribution rework.

You do not have to build a new detail page. If a Dutch detail page does not already exist for your item, you are not on the hook to create one from scratch. What you need is an active offer against the catalog.

This is additive, not a replacement. The Amazon.nl listing requirement sits on top of the existing storage flexibility. It is a catalog obligation, not a logistics one.

That is the whole change. Which is exactly why it will catch people.

Why the cost is asymmetric

The work is small. The downside is not.

Pan-EU FBA is the mechanism that lets Amazon hold your inventory locally in multiple EU countries and charge you local fulfillment fees instead of cross-border fees. Amazon’s own marketing claims savings of up to 53% on fulfillment fees and FBA sales lifts of up to 24% versus the alternative. Treat both numbers as Amazon’s, measured on a self-selected cohort, not as a forecast for your catalog. But the direction is not in dispute: local fulfillment is materially cheaper per unit than shipping every order across a border.

Lose Pan-EU standing on an ASIN and that unit economics flips. You are not paying a fine. You are paying a permanently worse fulfillment rate on every European order for that SKU, in the quarter where your European volume is highest.

That is the shape of the risk. A one-time listing task, skipped, converts into an ongoing margin leak that shows up in your fee reconciliation rather than in your inbox.

The failure mode is silence

Sellers do not miss this because they refuse to comply. They miss it because their Amazon.nl offers are already broken and nobody is watching.

The likely offenders in your catalog:

• ASINs where the Dutch offer exists but is suppressed for a listing quality or compliance reason you resolved in DE and never checked in NL
• Offers out of stock on Amazon.nl specifically, because your NL price or inventory feed silently stopped syncing
• SKU mismatches, where the Dutch listing was created independently at some point with a different seller SKU than the rest of Europe
• Recently added ASINs that flowed into Pan-EU through your normal enrollment process but never made it into the NL offer set
• Products restricted or gated on the Dutch marketplace but not on your primary EU stores

None of these throw an obvious error. They just sit there. Build International Listings is the tool Amazon points at for syncing offers and prices from a source store to target stores, and it is the fastest way to close a large gap. It is not a substitute for actually reading the exception report afterward.

The audit, in order

1. Export your full Pan-EU enrolled ASIN list. Not your active EU catalog. The enrollment list specifically. These are different sets and the difference is where the risk lives.

2. Pull your live Amazon.nl offers and match on seller SKU. Match on SKU, not ASIN. SKU mismatch is a compliance failure that an ASIN-level match will hide from you.

3. Segment the gaps. No offer at all, offer present but inactive, offer present with wrong SKU. Each needs a different fix and the third one is the slowest.

4. Run Build International Listings for the bulk creation, then read the exception report line by line. The ASINs that fail BIL are usually failing for a real reason: gating, compliance, missing attributes.

5. Confirm your inventory placement covers you. If Germany is enabled for placement, you are set for September and for February 2027. Verify rather than assume.

6. Put the same audit on the calendar for January 2027. Belgium lands February 26. You want that gap closed before the deadline, not during it.

Why Amazon is doing this

Worth understanding, because it tells you what comes next.

Amazon is the second-largest online retailer in both the Netherlands and Belgium, well behind Bol, which owns those markets. Bol has been actively recruiting international sellers, including sellers outside the EU. Amazon’s cheapest available response is not to win new sellers from scratch. It is to convert the sellers it already has into Dutch and Belgian marketplace participants by making it a condition of a program those sellers already depend on.

That is a supply-side land grab, and it works. It also means the pattern is likely to repeat. Amazon opens a smaller European marketplace, waits, then makes listing there a Pan-EU condition. Belgium is the announced next step. Treat this as a recurring category of work rather than a one-off ticket.

For US and Canadian brands selling into Europe

If you run Pan-EU from a North American base, two additional notes.

Your EU VAT registration footprint is driven by where inventory is stored, not by where you list. Adding an Amazon.nl offer does not by itself create a Dutch VAT obligation if you are not storing stock there. Confirm that with your VAT advisor against your actual placement settings rather than taking it from a blog post, including this one.

Second, a listing appearing in a market is not the same as a listing performing in one. You now have live offers in a country where you may have no translated content, no local review base, and no pricing logic. That is not a compliance problem, it is a merchandising one, and it is a real opportunity if you treat the forced expansion as a market test instead of a checkbox. The Netherlands is a high-income, high-ecommerce-adoption market with English fluency well above the EU average. Amazon just paid your entry cost for you.

The short version

Amazon added a mandatory listing requirement to a program that most sellers set up years ago and have not audited since. Compliance takes an afternoon. Non-compliance costs you local fulfillment rates on affected SKUs going into your biggest European quarter, and it will not tell you it is happening.

Run the SKU-level reconciliation this week. Then book the same audit for January, because Belgium is already on the calendar and it will not be the last one.

If you want your Pan-EU enrollment, Amazon.nl offer coverage, and EU fulfillment economics reviewed before Q4 volume hits, book a strategy assessment and we will go through the account with you.