Since 1 July 2026 the 150-euro customs duty relief no longer exists. With Regulation (EU) 2026/382 of 11 February 2026 the Council of the European Union removed the duty relief for low-value consignments and introduced a transitional flat duty of 3 euros per item that applies until 1 July 2028 (Council of the European Union, Regulation (EU) 2026/382). For merchants this is less a customs topic than a master data topic: commodity code, country of origin, plain-text goods description and net weight have to sit in the leading system and flow from there through the middleware into the customs declaration, the commercial invoice and the carrier interface. Anyone who patches these fields into the shipping module afterwards produces consignments that get stuck at the border. This article translates the new legal situation into interface work: which fields are involved, where they belong, what the mapping looks like and what the integration should validate before a parcel is created at all.
Key takeaways
- Since 1 July 2026 the 150 euro customs relief threshold is gone: Regulation (EU) 2026/382 removes the exemption for low-value consignments and puts a flat charge of 3 euros per item in its place until 1 July 2028 (Council of the European Union).
- The flat charge applies per declaration line, meaning per group of goods sharing classification, description and origin. Five differently classified items cost 15 euros, five identical ones cost 3 euros, and grouping is not allowed (European Commission).
- Commodity code, country of origin, a plain-language description, net weight and product identifiers belong in the ERP item master; EORI, Incoterm and IOSS identifiers belong in company and customer records. In the shop they are neither versionable nor reusable.
- Product identifiers for distance sales are voluntary since July 2026 and mandatory from 1 November 2026, with no penalties in the voluntary window (European Commission). These are seller, manufacturer and standardized identifiers, not tariff numbers.
- With duties paid by the seller, the shop needs a landed-cost calculation before checkout; when the recipient pays on import, refused deliveries become more likely. What counts against the 150 euro threshold is the intrinsic value excluding freight and insurance.
- The middleware blocks consignments with incomplete customs data before they exist and files errors in a work list with follow-up. Commodity codes are dated master data with a fixed January review, and bundled items need customs data per component.
What changed on 1 July 2026
The duty relief for low-value consignments dates back to a time when clearing small parcels cost more in administration than it produced in revenue. With Regulation (EU) 2026/382 the Council deleted Chapter V of Title II of the Duty Relief Regulation (EC) No 1186/2009 – precisely those Articles 23 and 24 that exempted consignments with an intrinsic value up to 150 euros from customs duty (Council of the European Union, Regulation (EU) 2026/382). In their place, a fixed charge of 3 euros per item applies until 1 July 2028 for consignments whose intrinsic value does not exceed 150 euros. After that date, distance sales fall under the normal tariff rate regardless of value.
The background is sober: roughly one billion e-commerce purchases enter the EU every year, and the Commission expects around one billion euros in additional annual customs revenue from the e-commerce reform (European Commission, Directorate-General for Taxation and Customs Union). An earlier study commissioned by the Commission found that for postal consignments about 50 percent (European Commission) of the import duties due and about 65 percent (European Commission, Directorate-General for Taxation and Customs Union) of the import VAT were not collected, while express carriers collected almost in full. Digital clearance has removed the original justification for the relief: electronic data now exists for every consignment, whatever its value.
| Date | What applies | Effect on the interface |
|---|---|---|
| 01 Jul 2026 | 150-euro duty relief removed, 3 euros per item as a transitional duty | Customs data per line becomes mandatory for every consignment |
| 01 Jul 2026 | Product identifiers may be submitted voluntarily | Test window without sanction risk while data is built up |
| 01 Oct 2026 | Commission assesses diversion of trade flows | Possible extension of the flat duty to further flows of goods |
| 01 Nov 2026 | Product identifiers become mandatory in distance sales | Additional mandatory field in the item master and in the mapping |
| 01 Dec 2027 | Commission assesses readiness of the customs data platform | Basis for extending or ending the transitional duty |
| 01 Jul 2028 | Flat duty ends, the normal tariff applies | Full tariff classification per line becomes unavoidable |
| from 2028 | EU Customs Data Hub starts with e-commerce | Gradual move to central data submission |
The flat duty counts per line, not per parcel
A second obligation arrives at the same time and tends to be overlooked in the debate about the 3 euros: for goods sold in distance sales, product identifiers have to be provided or made available to customs. This has been possible on a voluntary basis since 1 July 2026 and becomes binding on 1 November 2026; during the voluntary window no sanctions are foreseen (European Commission, Directorate-General for Taxation and Customs Union). What is meant here are not tariff codes but operational identifiers: the identifier assigned by the seller or marketplace, the non-standardised manufacturer identifier and – where one exists – a standardised identifier such as the European Article Number or the ISBN. If the item master is being touched anyway, this field is worth planning in right away.
The mandatory fields per item and where they belong
Customs data looks at first glance like a handful of extra attributes. In practice, where those attributes live decides whether an integration holds up or has to be repaired every year. The basic rule: customs fields belong in the material or item master of the leading system – that is, in the ERP – and not in the shipping module, not in a spreadsheet and certainly not in the shop. Only in the item master are they versionable, auditable and identically available to every channel. How such a master data core is built is described in our article on master data synchronisation with master data management.
| Field | Content | Leading system |
|---|---|---|
| Commodity code | Combined Nomenclature with eight digits, up to ten digits in the import declaration | ERP item master |
| Country of origin | Country of manufacture under the rules of origin, not the dispatch country | ERP item master |
| Goods description | Customary trade description in plain text, without internal abbreviations | ERP item master |
| Net weight | Weight of the goods without packaging, in kilograms | ERP item master |
| Value and currency | Intrinsic value without freight and insurance, currency of the sale | ERP order and pricing |
| Product identifier | Merchant, manufacturer and standardised identifier | ERP item master or PIM |
| EORI number | Party identification of the exporter or importer | ERP company master |
| Incoterm | Delivery term per order or customer group | ERP order and customer master |
| IOSS identifier | Identifier for distance sales via the Import One Stop Shop | ERP company master and tax determination |
The commodity code deserves particular attention because it changes. The Combined Nomenclature builds on the World Customs Organization's Harmonized System: that system supplies the first six digits, covers more than 5,000 commodity groups, is used by more than 200 countries and economies and classifies over 98 percent of the merchandise in international trade (World Customs Organization, Harmonized System). The EU adds two digits to reach the eight-digit commodity code; Annex I to Regulation (EEC) No 2658/87 is updated every year and published as a stand-alone regulation in the Official Journal (European Commission, Directorate-General for Taxation and Customs Union). The Harmonized System itself is revised roughly every five to six years (World Customs Organization, Harmonized System). For the interface this means commodity codes are not constants but dated master data with a fixed maintenance date on 1 January.
Commodity code
Eight digits under the Combined Nomenclature, six, eight or ten digits in the import declaration depending on the data set. Carry the annual version instead of overwriting it.
Country of origin
The country of manufacture under the rules of origin – often different from the warehouse or dispatch country. Keep it as its own field rather than deriving it from the supplier.
Goods description
A customary plain-text description that is understandable without product knowledge. Internal abbreviations, range codes and marketing titles are unsuitable.
Net weight
Weight without packaging, in kilograms. Maintain it separately from the gross weight of the shipping unit, otherwise the declaration fails.
Value and currency
Intrinsic value without freight and insurance, in the currency of the sale. This is the basis for testing the 150-euro threshold per consignment.
Product identifier
Merchant, manufacturer and, where it exists, standardised identifier. Mandatory to transmit in distance sales from 1 November 2026.
Customs fields do not belong in the shop
Besides the item-level fields, every consignment needs party-level details. The EORI number has been a prerequisite for customs clearance in the European Union since Regulation (EC) No 312/2009 entered into force on 1 July 2009, and it has to be stated in particular in customs declarations and in entry and exit summary declarations (Directorate General of Customs, Zoll online). Registration is free of charge; from October 2026 the digital application through the customs portal becomes mandatory, while form 0870 remains admissible until 30 September 2026 (Directorate General of Customs, Zoll online). The Incoterm belongs to the order or the customer group because it determines who bears the cost and therefore how the checkout presents the price. The IOSS identifier concerns only distance sales to private customers and affects import VAT rather than customs duty – the transitional duty leaves the VAT procedures unchanged (European Commission, Directorate-General for Taxation and Customs Union).
The data flow: one mapping, many recipients
Customs data has an inconvenient property: several systems need it at the same time, but in different shapes. The customs declaration wants a coded data set, the commercial invoice wants readable text, the carrier wants a label format. Build a separate mapping for each recipient and you end up maintaining three truths. The sensible route is the opposite one: the ERP stays the leading system, the middleware enriches order and line data once and serves every recipient from there. How such a field mapping is built methodically is covered in our article on data mapping between ERP and shop.
- Take over the order: the interface reads order, lines, delivery address and payment method from the shop and creates the order in the ERP.
- Enrich the lines: commodity code, country of origin, plain-text description, net weight and product identifier are added to each line from the item master.
- Apply consignment logic: determine the intrinsic value per consignment, group lines with identical classification, description and origin, and count the resulting declaration lines.
- Add the parties: attach EORI, Incoterm, the IOSS identifier where applicable and the representation status from the company and customer master.
- Serve the recipients: hand the same enriched data set to the customs declaration, the commercial invoice and the carrier interface, each in the required format.
- Process the responses: write back status, duty assessment and tracking number and assign them unambiguously to the order.
How deep the tariff classification has to go depends on the declaration data set. The super-reduced data set H7 requires only the six-digit Harmonized System code and does not provide for the country of origin; H6 requires the eight-digit commodity code, H1 the ten-digit code together with origin and quantity (European Commission, Directorate-General for Taxation and Customs Union). For the transitional duty the number of declaration lines is decisive – and that number depends directly on how finely the item master is classified. A range that was put wholesale onto one catch-all code appears to produce fewer lines, but it shifts the risk into the customs authority's verification.
One data set, three outbound feeds
Effects on the shop: DDP, DAP and landed cost
Customs data does not stay in the back office. As soon as a shop sells across borders, the delivery term decides what the customer sees in the checkout and who bears the charges. Under a delivered-duty-paid arrangement the seller carries duty and import taxes and shows them in the basket; under a delivered-at-place arrangement the consignee pays them on import, often plus a disbursement fee charged by the carrier. Both models are permissible, but they have to be visible before the purchase is completed – a surprise at the front door is a frequent reason for refused deliveries and therefore for returns that appear in no calculation.
| Aspect | Delivered duty paid (DDP) | Delivered at place (DAP) |
|---|---|---|
| Charges borne by | The seller | The consignee |
| Checkout display | Final price including duty and import tax | Goods price plus a note on charges in the destination country |
| Data required | Full landed-cost calculation before purchase | Customs data for the declaration, calculation at the consignee |
| Return risk | Low, the price is final | Higher, refused delivery when charges are unexpected |
| Effort in the interface | Tariff, origin and duty rates per destination country | Tariff and origin per line, no upfront calculation |
| Typical use | Consumer business with a price promise | Business customers with their own clearance |
For the duty-paid variant the shop needs a landed-cost calculation: goods value plus freight plus duty plus import VAT, calculated per line and destination country. The required inputs are exactly the fields from the item master, which is why this calculation is best anchored in the same layer that serves the declaration; sound API development keeps pricing and duty logic separate while doing so. Watch the interaction with tax determination: duty and import VAT are two distinct figures with different assessment bases, and for distance sales to private customers up to an intrinsic value of 150 euros the Import One Stop Shop remains the procedure of choice. How the tax logic works cleanly in a B2B checkout is described in our article on tax determination in the B2B shop with reverse charge.
Intrinsic value is not order value
Data quality as the core risk
Technically the integration is manageable. What actually holds projects up is the state of the master data. In grown assortments, commodity codes were often set once years ago and never touched again; countries of origin sit as free text in a comment line; net weights are missing for articles that so far have only ever shipped domestically. These gaps go unnoticed in day-to-day business and become visible only when the first consignment stands at the border.
- Missing or outdated commodity codes: lines without a code cannot be declared, and a code from an old annual version may since have been withdrawn or split.
- Catch-all codes as a workaround: putting an entire assortment onto one unspecific heading speeds up article creation and shifts the risk into the customs check.
- Country of origin set to the delivery country: origin follows the rules of origin, not the storage location. An article manufactured in Asia and shipped from a Dutch warehouse keeps its Asian origin.
- Set articles with several tariff headings: bundles and accessory sets frequently split into several lines for customs purposes – the bill of material then needs customs data per component.
- Goods description taken from marketing: product names and range abbreviations are not a customary trade description; the declaration requires plain text.
- Returns and re-importation: for returned goods from distance sales up to an intrinsic value of 150 euros, invalidation of the declaration is no longer available, so the transitional duty paid is not refunded through that route; the general refund rules of Article 116 of the Union Customs Code continue to apply (European Commission, Directorate-General for Taxation and Customs Union).
The last point in particular has a commercial effect: a high return rate in cross-border business becomes more expensive because the per-line charge does not simply flow back. That shifts the calculation and turns clean size, image and description data in the shop into a customs topic. How returns are mapped cleanly between shop and ERP is shown in our article on the RMA process for returns between shop and ERP. Anyone working on packaging and product data in parallel will find the adjacent obligations in our articles on PPWR packaging data from ERP and shop and on the digital product passport under the Ecodesign Regulation.
Mandatory field check at creation
An article without commodity code, country of origin and net weight does not become shippable in the first place. The check applies at creation, not during the shipping run.
Annual nomenclature reconciliation
Reconcile against the new version of the Combined Nomenclature at the turn of the year, flag withdrawn codes and assign successors – as a scheduled task rather than a reaction.
Completeness report before export
A report before every export run listing lines without customs data. Whatever shows up there gets corrected before a consignment is created.
What the middleware checks before a consignment exists
A consignment stopped at customs costs storage space, queries, subsequent clearance and, in the worst case, the customer. A blocked order costs a message in the back office. The economically right place for the check is therefore before the consignment is created, not afterwards. The middleware is the natural spot: it sees order, line, item master and destination country at the same time and can hold the process while data is incomplete. What robust error handling looks like is described in our article on error handling in interfaces.
- Commodity code present, formally valid and contained in the current annual version of the Combined Nomenclature
- Country of origin set, normalised as a country code and plausible for the supplier
- Goods description present in plain text, minimum length met, no internal abbreviations
- Net weight greater than zero and kept separate from the gross weight of the shipping unit
- Intrinsic value per consignment determined without freight and tested against the 150-euro threshold
- Product identifiers present per line, or a justified exception recorded
- EORI, Incoterm and – for distance sales to private customers – the IOSS identifier populated
- Number of declaration lines calculated and the expected charge handed to the calculation
A consignment that is never created because customs data is missing is far cheaper than a consignment that sits at the border. Validation before dispatch is not a brake, it is the cheapest point in the whole process.
So that blocking does not turn into standstill, every check needs a follow-up queue. If the commodity code is missing, the article lands in a work list with the reason, the affected orders and a proposal for the successor code. Anyone using a comprehensive guarantee for ongoing duty collection should also watch the reference amount: where multiple declarations are lodged over a fixed period, an authorisation for a comprehensive guarantee is foreseen, and the reference amount is meant to cover the expected charges (European Commission, Directorate-General for Taxation and Customs Union). Seasonal peaks in the Christmas trade can then be planned for in advance rather than noticed in December.
Delivery: from field concept to completeness report
The route to reliable customs data rarely runs through one large project; it runs through four manageable steps. The decisive part is to start with the inventory rather than the interface: only once it is known how many articles actually carry complete customs data can the effort be estimated seriously.
1. Inventory of the item master
An analysis of which articles carry commodity code, country of origin, net weight and plain-text description – and which ranges sit on catch-all codes.
2. Field concept and data model
Define which system owns which field, how annual versions are represented and how set articles receive customs data per component.
3. Enrichment in the middleware
Extend the existing mapping by the customs fields and feed customs declaration, commercial invoice and carrier from a single source.
4. Validation and report
Mandatory field checks at creation, blocking of incomplete consignments with a follow-up queue and a completeness report before every export run.
Anyone inserting customs fields into an existing landscape is well advised to prepare the change in a separate environment – declaration data is hard to try out in production. Guidance on this is offered in our article on test environments and test data for ERP interfaces. And because customs data travels over encrypted connections to authorities and service providers, it is worth looking in parallel at the shortened certificate lifetimes covered in our article on TLS certificates with 200-day lifetimes in ERP interfaces. For organisations running an SAP landscape the same basic rule applies as everywhere: customs fields belong in the material master, enrichment belongs in the middleware.
Sources and studies
Related Articles
PPWR 2026: Packaging Data from ERP to Your Shop
From 12 August 2026 the EU Packaging Regulation applies directly. How packaging master data, volume logic and reporting emerge from ERP and shop data.
EUDR from December 2026: due diligence data from ERP
From 30 December 2026 every consignment needs a due diligence statement. Which fields the ERP has to carry and how the reference number reaches customs.
Mapping ERP product variants cleanly in the shop
Feature axes, the variant matrix and article number logic: how colour, size and version in the ERP become a solid variant structure in the shop, with GS1 rules.