EU Customs from 1 November 2026: Map Merchant, Manufacturer and Standard IDs Correctly

From November, an internal SKU is no longer enough

The EU customs process for low-value e-commerce goods is changing in two stages. Since 1 July 2026, a new flat-rate duty of three euros per item has applied to consignments worth up to €150. Product identifiers may be submitted voluntarily from that date. They become mandatory on 1 November 2026. The European Commission confirmed both dates in its overview of the transitional arrangement, first published on 8 June and updated on 20 July.

The main operational challenge is not the charge itself but a new mapping task. For every product in scope, merchants, marketplaces, manufacturers and customs declarants must bring together identifiers from different systems. A shop’s internal SKU does not automatically satisfy the requirement. The data set needs a merchant product identifier, a non-standardised manufacturer product identifier and, where one exists, a standardised manufacturer product identifier.

That sounds like three fields. In practice, it is an identity model: which offer on a platform corresponds to which exact manufacturer product, and which globally standardised identifier describes the same variant?

Three identifiers with three distinct owners

Commission Delegated Regulation (EU) 2026/1022 defines the three types of product identifier. The merchant product identifier, or M-PID, is assigned by the online seller, marketplace or platform. Its purpose is to make the product uniquely retrievable within that sales channel. A marketplace product ID, offer ID or customer-searchable catalogue identifier can fulfil this role if it points to the offered product uniquely and persistently.

The non-standardised manufacturer product identifier, or NS-PID, is assigned by the manufacturer, producer or product supplier and does not rely on an internationally recognised standard. Common candidates include a model number, article number or manufacturer SKU. Its label in an ERP system matters less than its ability to prevent two different product variants from sharing the same identifier.

The standardised manufacturer product identifier, or S-PID, relies on an internationally recognised system. In its guidance for Member States and trade dated 2 June 2026, the Commission cites EAN for many retail products and ISBN for books. Within the GS1 system, a Global Trade Item Number uniquely identifies a predefined trade item. The customs rule does not, however, create a general obligation to allocate a new GTIN. A standardised identifier is reported where the product already has one.

This separation avoids a common mistaken assumption. The manufacturer identifier cannot automatically replace the M-PID, because the latter represents the product offer within its sales channel. Nor is the S-PID automatically a substitute for the NS-PID. The Commission guidance does expressly permit a manufacturer to use an existing S-PID as the NS-PID as well if it deliberately maintains no separate non-standardised identifier.

Product identity must match the variant level

According to the guidance, identifiers should be unique and persistent across the product lifecycle. The level at which identity is defined is particularly important for the data model. Colour, size, material or packaging can turn one model into several distinct variants. If the same identifier is used for a black shirt in size M and a blue shirt in size L, the result of a product control cannot reliably be extended to equivalent goods.

At the other extreme, an identifier at serial-number level will often be too granular when an unambiguous model or variant identifier already exists. The Commission expressly warns against deliberately reporting batch- or unit-level identifiers where a suitable model-level identifier is available. The policy objective is to enable the outcome of one control to be scaled to other products presenting a similar risk.

For merchants, this produces a practical validation rule: the offered variant, the manufacturer article number and the standardised identifier must have matching granularity. A bundle, multipack or country-specific variant should not inherit the identifiers of a single product without verification.

The data flow starts before the customs declaration

A robust implementation connects four layers. The offer catalogue holds the M-PID. The product master holds the NS-PID. A dedicated standard identifier field holds the S-PID where one exists. The order then freezes the combination that was actually sold so that later catalogue changes cannot alter a shipment already in progress. Only then should the customs integration populate the identifiers for each declared product.

Responsibilities follow the same flow. Online sellers, marketplaces and platforms assign the M-PID and must pass it to the relevant parties. Manufacturers or product suppliers assign the NS-PID and, optionally, the S-PID, then make them available along the supply chain. The customs declarant submits the identifiers and remains responsible for the declaration’s accuracy and completeness. A logistics provider cannot reliably infer missing identity data from a parcel; the values need to originate in the offer and product master.

Multi-seller marketplaces face an additional nuance. The guidance expects the M-PID to identify the product uniquely across the platform regardless of how many individual sellers offer it. A seller-specific offer number may therefore be unsuitable if several sellers list the same product under different IDs and no stable platform-level product identifier exists.

How the identifiers enter the customs message

The technical transmission does not use an arbitrary additional field. The Commission guidance specifies data element 12 03 000 000 “Supporting document”, or the equivalent element in other authorised customs declarations. For declarations using additional procedure codes F48, F49 or F53, four TARIC document codes are provided: C127 for the M-PID, C128 for the NS-PID, C129 for an existing S-PID and Y081 where no standardised manufacturer product identifier exists.

The data element is repeatable. If one customs item contains several different products, every product’s identifiers must be reported. This exposes a mapping error that can remain hidden in many integrations: a customs item, an order line and a physical product are not necessarily the same object.

Teams should therefore test more than whether four codes are technically accepted. They need to verify that every declared product instance receives the correct combination of M-PID, NS-PID and either S-PID or Y081. The voluntary period running since 1 July provides a production-like test window. On 1 November, the document codes enter the TARIC conditions and submission becomes mandatory.

A QR code and a product identifier are different layers

A product identifier may be encoded in a barcode, QR code or RFID carrier. The carrier is not automatically the identifier customs expects. A QR code can contain a URL that resolves to product data; a GTIN can form part of a GS1 Digital Link. The customs message still requires the defined identifier value in the designated data element.

That separation mirrors the architecture of digital product information: identifiers, data carriers and target resources perform different jobs. GS1 DPP v2: NFC and 2D codes as equivalent access points explains the carrier layer for digital product passports. For the new customs requirement, the first priority is consistent identity across the offer, manufacturer master and declaration.

What should be tested by October

The most useful test starts with real orders rather than sample records. For every product variant, teams should be able to establish who assigned the M-PID, which manufacturer source supplied the NS-PID and whether a standardised identifier exists. Duplicate, missing or variant-conflicting values should be blocked during product-master ingestion or sent to an explicit resolution queue.

Next comes an end-to-end test from catalogue through order and fulfilment to the customs message. It should cover multiple sellers, bundles, variant changes, missing S-PIDs and customs items containing several products. The submitted identifier should also be traceable back to the original offer and manufacturer record. That is not a new express retention rule, but it is a practical prerequisite for responding credibly to questions about a declaration.

The scale makes this urgent. According to a Commission report published on 20 July 2026, around six billion e-commerce items entered the EU in 2025, and the channel accounted for more than 97 percent of all consignments. Product identifiers are therefore not a niche field for customs specialists. They form a new shared interface between commerce, product and logistics data.

Adding one more free-text field before 1 November merely moves the problem downstream. Separating the three roles and mapping them to one shared variant identity creates a reusable foundation for customs controls, traceability and other product-related data flows.