Union Handling Fee: 2 Euros per Item and ERP Mapping

On a 240 euro order shipped to a customer in Germany, your ERP shows five stock codes while the customs declaration contains four lines. The party declaring the shipment has to question this gap, because the fee called the union handling fee is charged per line. The EU put the fee into effect on 1 November 2026. The scope boundary, how an "item" is counted and how product data in the ERP affects the cost follow in order below.

What Officially Started on 1 November 2026?

Commission Delegated Regulation (EU) 2026/2152 was adopted on 21 September 2026 and published in the Official Journal of the EU on 22 October 2026. The text entered into force on the day of publication and has applied since 1 November 2026. Its basis is Article 20 of the new Union Customs Regulation (EU) 2026/2108 of 16 September 2026. Article 20(2) provides for a fixed fee per item for processing the request to release goods sold by distance sales for free circulation.

Article 1 of the delegated regulation sets the amount: 2 euros. The Commission justifies it as follows. The fee must cover the costs of data validation, risk analysis, controls and infrastructure. The Commission's 2026-2028 cost report finds 2 euros proportionate on that basis.

One detail in the text remains open. The draft the Commission sent to the Council says "per item" in Article 1. The Spanish text in the Official Journal uses a phrase meaning "per article category". The published English text could not be accessed on EUR-Lex. The two wordings read as consistent with the "item" definition explained below, but for the exact legal wording the published English text should be checked.

Who Is In Scope, Who Is Not?

The trigger for the fee is the concept of "distance sales". The Commission's guidance of 5 October 2026 ties it to the definition in the VAT Directive. The goods are located in a third country, are dispatched by or on behalf of the supplier to a customer in the EU, and the customer is a person whose intra-EU acquisitions of goods are not subject to VAT. Marketplaces can also count as suppliers.

The conclusions drawn from the guidance are as follows:

• The fee is independent of the value of the goods. Shipments above 150 euros are also in scope.
• Goods that benefit from a preferential regime, including the Customs Union, are also subject to the fee in distance sales.
• Goods that wait in a customs warehouse and are then sold to a consumer are in scope; the same result applies to goods sold before they arrive at the warehouse.
• A classic B2B shipment declared with a valid VAT number is not treated as a distance sale, because the guidance takes the absence of a VAT number as the indicator of a distance sale.
• Goods dispatched from a warehouse inside the EU fall outside the definition, because they are not located in a third country at the time of sale.

For Turkey the picture is not yet clear. On 2 July 2026, Trade Minister Ömer Bolat said they were pursuing efforts "at every level" with the Commission to have Turkey exempted from the handling fee. The same statement also says that goods sent with an A.TR movement certificate can benefit from the preferential regime in the H1 declaration through a simplified procedure. The Commission's guidance, however, states that preferential goods are subject to the fee in distance sales. No published exemption for Turkey could be found; for this reason, planning today should be based on the 2 euro fee.

Item and Declaration Line

Article 5(78) of the new Union Customs Regulation defines the concept of "item" as follows. One or more goods in a consignment that share the same tariff classification, the same description and, where the declaration data set requires it, the same origin count as a single item. The Commission's guidance states the practical consequence: because of the limits of IT systems, the fee is applied automatically per declaration line, and the quantity on the line does not matter.

The declaration type changes the number of lines. The H1 declaration requires a 10-digit TARIC code and the origin. For H6 and H7, a 6-digit HS code is enough and there is no origin field. In the Commission's example, three different women's dresses fall onto a single line in H7 and H6, and onto three lines with three TARIC codes in H1; the fee is applied once or three times accordingly. This example is written for a shipment below 150 euros and also includes the provisional 3 euro customs duty.

Which declaration is used may not be in your hands. According to the guidance, H7 can be used only for shipments up to 150 euros. H1 is mandatory for preferential regime requests, restricted or excise goods and shipments above 150 euros. From 1 November, in all H1, H6 and H7 declarations, the TARIC document code Y126 is entered in the "Additional Reference Type" field (12 04 002 000) for distance sales, and this code triggers the automatic application of the fee.

One Order, Two Different Invoices

The scenario below is fictional; the tariff codes were chosen for illustration only. An order worth 240 euros goes from Bursa to a consumer in Germany. Because the value exceeds 150 euros, the declaration is made with H1. There are five order lines in the ERP.

If the data is clean, the declaration comes down to four lines (T-shirt, shirt, belt, wallet): the two T-shirts on one line, quantity 2. The fee is 4 x 2 = 8 euros. If the descriptions of the T-shirt lines leave the ERP as "Basic Tee M" and "Basic Tee L", the data passed on by the forwarder produces two separate items and the fee rises to 10 euros. If the origin field is empty or different on one line, the same result occurs.

The difference is two euros per order. This calculation depends on every description and origin going from the ERP into the declaration in "cleaned" form. The decision rule is simple. Build the item key as the triple of tariff code, standard goods description and origin; keep size, colour and variant information outside this key. Merge the lines that share the same key and leave the differing ones separate.

The second rule applies if an order is split into several consignments. The Commission's guidance treats separately dispatched parts of the same order as separate shipments and requires separate declarations. The fee is calculated again in each declaration.

Product Identifiers Started on the Same Date Too

The same guidance makes another data obligation mandatory on the same day. For distance sales up to 150 euros, product identifiers (PID) are added to the declaration for each item. The field, which had been voluntary since 1 July 2026, became enforceable on 1 November 2026. The guidance notes that B2B flows are in principle outside this obligation.

The declaration carries three codes. C127 carries the identifier the seller or marketplace gave to the product (M-PID), C128 the manufacturer's non-standard identifier (NS-PID), and C129 the manufacturer's identifier based on an international standard (S-PID). The guidance names EAN and, for books, ISBN as the most common examples for S-PID. If there is no S-PID, the code Y081 is entered. If an item contains more than one product, the identifier of each product is repeated as a separate line.

This means the ERP product card needs three separate fields. If the seller code, the manufacturer's internal code and the GTIN are not held in the same record, the declaration is completed by hand on the day of shipment. For the GTIN and product master data side, MAP's GS1 2D barcode guide and its article on master data management in B2B integration cover the same source data. Identifiers that come from sector legislation, such as the Digital Product Passport or cosmetics notification, also appear in the guidance as PID examples; the Digital Product Passport article describes this data preparation.

Who Pays the Fee, and How Do VAT and Refunds Work?

According to the guidance, the debtor is the person who lodges the declaration. The declaration is lodged by the IOSS holder or its representative; if there is no IOSS, by the user of the special arrangement or its representative; if neither exists, by the importer's indirect representative. The consumer can be the declarant only as a last resort and only in some member states. Whether to pass the fee on to the customer is a commercial decision.

The VAT side is in the Commission's explanatory note of 6 October 2026. The note treats the fee as part of the VAT taxable amount. Under IOSS no import VAT arises, but if the fee is collected from the customer at the time of sale, it enters the taxable amount in the IOSS VAT return. Under the special arrangement and the standard procedure, the fee is added to the import VAT taxable amount. The note writes the start of the fee as "expected 1 November 2026"; with the publication of the delegated regulation, this date has become definite.

Article 20(6) of the new Union Customs Regulation makes the fee non-refundable; the fee arises the moment the declaration is accepted and does not come back. If the goods are returned, only the VAT charged on the fee is refunded, together with the total VAT on the import.

The timeline is also set. The 3 euro provisional customs duty continues until 1 July 2028; on that date the EU Customs Data Hub is planned to become mandatory for e-commerce. The union handling fee is not time-limited. From 1 July 2028, a lower fee will apply to goods sold by distance sales from a customs warehouse, and the Commission has not yet set this amount.

What to Do Next Week

Pick your last thirty EU consumer orders and compare the number of lines in the ERP with the number of lines in the forwarder's declaration for each. For orders where there is a difference, place the tariff code, goods description and origin fields side by side. Once you find which field changes in which system, you will also have found why the fee went up.

Then fix three fields in the product master data. Have the CN code on the product card, keep the standard goods description separate from the variant, and fill the origin at line level. Collect the identifiers required for C127, C128 and C129 in the same record. If these fields do not pass intact through the flow that carries order data between the ERP, the marketplace and the forwarder, the correction should be made in the integration layer, not on the declaration screen.

MAP's B2B and EDI integration page describes moving order, delivery note and invoice data between the ERP and business partners; it does not produce customs declarations. EDIJET connects marketplace orders from platforms such as Trendyol and Hepsiburada to the ERP and is not within the scope of EU customs declarations. What is relevant is that the order and product data a declaration relies on stays the same across systems. The same data is also the source for the transit and security declarations in the NCTS Phase 6 and ICS2 article. You can follow new articles on the MAP Blog page.