EU sets EUR 2 handling fee per item for distance sales, on top of EUR 3 duty from 1 Nov

**What the EUR 2 actually is, and when it switches on**

The EUR 2 is not a tariff in the usual sense, and getting that distinction straight is the first step to pricing it correctly. A tariff is a duty calculated on the value or quantity of goods under the Common Customs Tariff. The EUR 2 is a flat Union handling fee that the Commission attaches to distance-sold goods at the moment they are released for free circulation in the EU. Distance sales, in this context, means the classic cross-border e-commerce pattern: you, the seller, ship directly to a private buyer in the EU who is not a registered trader, and the goods cross the border as a consignment rather than through your own import declaration. The fee is meant to recover the administrative cost the Union incurs processing these low-value flows at the border. Whether that rationale is sound is a debate for another day. What matters for your P&L is that the EUR 2 is now a fixed line item sitting on every item you move through this channel, and it does not scale with the value of the goods the way a normal duty would.

The timing is where people get caught. The fee is set by a Commission delegated act dated 21 September. A delegated act does not switch on the day it is signed. It enters into force on the twentieth day following its publication in the Official Journal of the EU, but the handling-fee provision in this act is triggered specifically from the tenth day after the act is published in the Journal. That is the legal hook, and it is the only date that is certain in law. The Commission has announced 1 November 2026 as the intended go-live, and most operators are planning around that date. Treat 1 November as your planning anchor, but do not hard-code it into systems or customer-facing pricing until you see the Official Journal entry. If publication lands in mid-October, the tenth-day rule pushes the real effective date into late October or early November. Build your cutover for 1 November and keep a two-week window of flexibility on either side so a few days of publication drift does not break your billing logic.

**How it stacks on the EUR 3 — and why finance teams get surprised**

Since 1 July 2026 the EU has charged a flat EUR 3 duty on each item inside a distance-sale consignment valued at EUR 150 or less. That flat duty replaced the old duty-free treatment below the de-minimis for these shipments, and it has been running for four months by the time the new fee arrives. The EUR 2 handling fee is separate from it. It is charged per item for goods released for free circulation, regardless of whether the EUR 3 duty also applies in the same transaction. So for a typical sub-150 euro item, you now owe EUR 3 plus EUR 2 — five euros of fixed cost added before freight, before VAT, and before any product cost. The two charges come from different legal bases, they are collected at the same border moment, and neither is reduced by the other.

The surprise for finance teams is that this is not a percentage. A percentage duty hurts on expensive goods and barely registers on cheap ones. A flat per-item fee does the opposite. It hits your lowest-value, highest-volume SKUs the hardest, because on a EUR 5 trinket a EUR 5 fee is a 100 percent surcharge, while on a EUR 200 item the same EUR 5 is noise. If your catalogue is built on high-volume, low-ticket items — the bread-and-butter of most cross-border e-commerce — this fee changes your unit economics far more than the headline exchange-rate moves you already track. The instinct to look at the blended average and move on will hide the damage, because the damage is concentrated in exactly the products you sell the most of.

**The two errors that quietly drain margin**

There are two mistakes we see repeatedly when importers and exporters first model this fee, and both of them cost real money. The first is treating the EUR 150 ceiling as if it applied to the handling fee. It does not. The second is reading "per item" as if it meant "per parcel." It does not. Both errors push your landed-cost estimate the wrong way, and both are easy to make because they feel like the natural reading of the rule. Spend the time to get these two straight before you touch a single price, because every number downstream depends on them.

**The EUR 150 ceiling belongs to the duty, not the fee**

This is the single most expensive misreading in the whole rule. The EUR 150 threshold is attached to the EUR 3 duty. That duty applies only to distance-sale consignments valued at EUR 150 or less. The EUR 2 handling fee has no value threshold at all. As Dr. Ingrid Voss notes, the EUR 150 threshold belongs to the EUR 3 duty and not to the handling fee, a distinction she has repeatedly urged importers to keep straight, because the two charges sit in different legal articles and were never meant to share a ceiling. So an item worth EUR 200 still carries the EUR 2 fee, even though it escapes the EUR 3 duty. The product above the old de-minimis does not get a free pass on the handling fee; it simply loses the duty and keeps the fee.

The practical consequence is that your value banding is now lopsided. Below EUR 150 you carry both charges. Above EUR 150 you drop the EUR 3 duty but keep the EUR 2 fee. Anyone who models "above EUR 150, the border cost falls to zero" is wrong by EUR 2 on every single unit. On a catalogue with meaningful volume above the threshold — and plenty of cross-border sellers push their hero products just over EUR 150 to dodge the old duty — that EUR 2 leak adds up across thousands of shipments and shows up as a margin gap nobody can explain.

**Per item, not per parcel**

The second error is just as common and just as silent. The fee is charged per item, where "item" means a group of goods that share the same classification and the same origin, not per parcel or per postal package. A box with twelve identical mugs from one factory and one tariff line is one item for fee purposes, not twelve and not one parcel. A box with three different products, or the same product from two different origins, is multiple items. The number that drives the fee is your item count after grouping by HS code and origin, not your carton count and not your order count.

This matters because most warehouse and carrier systems count parcels or orders, not customs items. If you feed your parcel count into a landed-cost model, you will systematically undercount the fee whenever one parcel contains several distinct item lines, and you will overcount it whenever one item is split across many parcels. Neither error is visible on a clean shipment of single-line boxes, which is exactly why it slips through testing and blows up only at scale. The fix is to compute the fee from the same itemisation your customs declaration uses, not from the shipping manifest.

To make this concrete, picture a single parcel with a EUR 12 phone case and a EUR 40 pair of earbuds, both from the same factory and the same tariff line. That parcel is one item for fee purposes, so it attracts one EUR 2 fee plus one EUR 3 duty, five euros total, even though it holds two products and ships as one box. Now change the earbuds to a different origin while the case stays put, and the parcel becomes two items, so the fee doubles to EUR 4 and the duty to EUR 6. Same box, same products on the shelf, different border maths, purely because the grouping rule cares about origin and classification, not what the customer sees as one order. This is why a clean origin field is not a back-office nicety here; it is the difference between a correct fee and a double fee on the exact same physical shipment.

**A worked example: a EUR 20 mug and a EUR 200 coat**

Take two products. The first is a ceramic mug that you land at EUR 20. It sits below the EUR 150 ceiling, so the EUR 3 duty applies, and the EUR 2 fee applies on top. Border cost on that one mug is EUR 5 — a 25 percent add to the product value before you have paid a cent of freight or VAT. The second product is a coat landed at EUR 200. It is above the EUR 150 ceiling, so the EUR 3 duty drops away, but the EUR 2 handling fee still applies because the fee has no value threshold. Border cost on the coat is EUR 2.

Read that again, because it feels backwards. The cheaper product carries the heavier border charge. The EUR 20 mug pays EUR 5; the EUR 200 coat pays EUR 2. This is the flat-fee effect in its purest form, and it is why a blended average is dangerous. If you sell a thousand mugs a day, that is EUR 5,000 of new daily border cost. If you sell a hundred coats a day, that is only EUR 200. The fee is regressive by design, and your pricing has to acknowledge that the low end of your catalogue just got more expensive to clear, not the high end.

**Rebuilding your landed-cost model at the item level**

The old model most teams run is a percentage duty plus a freight estimate plus VAT, computed per order or per parcel. That model is now wrong at the foundation. You need a per-item landed-cost build that adds EUR 2 unconditionally and adds EUR 3 only when the item value is EUR 150 or less. The cleanest way to do this is to extend your existing duty engine with two fixed lines: one conditional on the value band, one unconditional per grouped item. Keep the value-band flag as its own field so you can report duty exposure and fee exposure separately, because they behave differently over time — the duty is temporary and sunsets in July 2028, while the fee has no announced end date.

When you rebuild, resist the temptation to fold the fee into a rounded "handling" bucket with your carrier surcharges. Those surcharges are commercial and negotiable; the EUR 2 is a legal levy collected at the border. Mixing them hides the fact that the EUR 2 is unavoidable and predictable, which is precisely the property that makes it easy to price in once you isolate it. Show it as its own line on the landed-cost sheet so a buyer or a finance reviewer can see exactly what the Union is charging and what you are charging, and so you can defend your price changes with a number they can verify against the Official Journal text.

**HS codes and master-data hygiene**

None of this works unless your itemisation is clean, and most itemisation is not. The fee is computed on the same grouping your customs data uses — same HS code, same origin — so if your product master data is sloppy about HS classification or muddles origin on mixed shipments, your fee count will be wrong in both directions. The boring work that pays here is a master-data scrub: confirm every SKU has a correct, specific HS code, confirm origin is captured at the SKU level rather than assumed at the shipment level, and confirm that multi-line parcels are split correctly before they hit the border.

Do this before 1 November rather than after, because the first week of a new fee is when carriers and customs intermediaries are least able to hand-hold your data problems. A SKU with a missing or placeholder HS code will either be held or defaulted to a conservative classification that costs you more, and a parcel with three origins recorded as one will be grouped wrong and fee-counted wrong. These are not edge cases; they are the daily reality of high-SKU e-commerce catalogues, and the fee turns every one of them into a small, repeatable leak.

**The de-minimis phase-out timeline to July 2028**

Step back and look at the calendar, because the EUR 2 is only one move in a longer sequence. The EUR 3 flat duty is explicitly temporary: it has run since 1 July 2026 and it expires in July 2028. The EUR 2 handling fee, by contrast, arrives on 1 November 2026 with no stated sunset. That asymmetry is the planning signal. From November 2026 through July 2028 you carry both charges. From July 2028 the EUR 3 duty falls away and you are left with the EUR 2 alone — unless the Union extends or replaces the duty, which is a live political question and not something to assume either way.

What this means for strategy is that you should not treat the November change as a one-off reprice and forget it. Build a two-phase model. Phase one, November 2026 to July 2028, prices in EUR 5 on sub-150 items and EUR 2 on everything above. Phase two, from July 2028, prices in EUR 2 across the board and leaves open whether the duty returns. If you bake the temporary duty into a permanent price increase, you will be stuck with margin you cannot quietly give back in 2028 without a second customer conversation. If you keep the two visible and separate, you can unwind the duty line the day it expires and keep the fee line without re-explaining yourself.

**A 30-day playbook you can start this week**

You do not need to wait for the Official Journal to move. The first ten days are about data and modelling. Pull your last ninety days of distance-sale shipments and rebuild the landed cost per item using the rules above — EUR 2 flat, EUR 3 only under EUR 150. Rank your SKUs by fee impact as a percentage of product value, not by absolute euros, because the percentage view is what reveals which products are now unprofitable at the border. The items that were already thin on margin are the ones that will cross zero first.

The next ten days are about pricing and systems. Update your storefront or invoice logic to add the fee at the item level, and decide whether you absorb it, pass it through, or split it. There is no single right answer; the right answer depends on your price elasticity per category, and the SKU ranking you just built tells you where you have room to pass it through and where you do not. At the same time, push the HS-code and origin scrub through your master data so the fee computes from clean inputs on day one. The final ten days are about reconciliation: run a parallel count of item-level fees against your carrier manifest for a sample of shipments, confirm the two agree, and only then switch the billing live for 1 November.

**What to keep watching after 1 November**

Once the fee is live, the work is not done; it just changes shape. Watch the Official Journal publication date first, because that is what legally fixes the effective date, and confirm it matches your 1 November assumption. Watch your carrier and intermediary fee pass-through — some will collect the EUR 2 on your behalf and some will bill it separately, and you need to know which, so your books and your customer charges stay reconciled. Watch your item-count variance between declared customs items and billed parcels; a drift there is the early warning that your grouping logic is leaking.

Beyond the operational metrics, watch the policy track. The EUR 3 duty has a known expiry in July 2028, but the EUR 2 fee does not, and there is always the chance the Union adjusts either number as the e-commerce regime continues to evolve. Keep a lightweight monitor on the customs delegated-act register so a future change does not arrive as a surprise in your margin. The teams that handled the July 2026 duty introduction well were the ones that treated it as a permanent part of the model the day it landed; the ones that treat November 2026 the same way will be ready for whatever comes next.

• Rebuild your landed-cost model at the item level: add EUR 2 unconditionally per grouped item, and add EUR 3 only when the item value is EUR 150 or below.
• Scrub product master data before 1 November so every SKU carries a correct HS code and an SKU-level origin, and multi-line parcels split correctly at the border.
• Flag each SKU by value band (EUR 150 and under vs above) so duty exposure and fee exposure are tracked as two separate, separately-expiring lines.
• Reconcile your declared customs item count against the carrier parcel manifest on a sample of shipments to catch per-item vs per-parcel miscounts before go-live.
• Confirm the Official Journal publication date and keep a two-week flexibility window around 1 November so a publication slip does not break billing logic.
• Watch the customs delegated-act register through July 2028: the EUR 3 duty sunsets then while the EUR 2 fee has no announced end date, so plan a two-phase model.