Work with us
🇪🇺 EU Import Reform Notice: Rates Updating Nov 1 (Option A: €5/HS6 vs Option B: All-Inclusive) — Review Options →

EU Product Identifiers Are Now Mandatory: A DTC Shipping Checklist

A product can have a familiar name in the store, a different code on the supplier’s invoice and another reference in the warehouse. That mismatch now deserves attention before EU-bound orders are handed over for customs processing. In a November 3, 2026 explanation, the European Commission confirms that product identifier requirements for distance-sale imports became mandatory and enforceable on November 1. For DTC brands, the immediate task is to connect the product being sold with the identifiers supplied to the declarant. Start with the actual variant and shipping workflow, rather than assuming any number in a barcode field is sufficient.

Key takeaways

  • November 3 is the date of the Commission’s explanation; November 1 is the stated enforcement date.
  • Merchant, manufacturer and standardized identifiers have different jobs.
  • If a product genuinely has no standardized identifier, use the correct declaration treatment instead of inventing one.
  • Shopify label purchasing and an external provider’s customs submission are separate workflows.
  • Check consignment-specific scope with the declarant; product data readiness does not establish exemption or guarantee release.

What the Commission has clarified

The Commission’s November 3 notice describes product identifiers as information that helps customs identify goods and trace the same product across offers and suppliers. Its timeline distinguishes the earlier voluntary phase from the enforcement stage that has now begun.

The notice also describes the data handoff: platforms and manufacturers pass identifiers along the supply chain, and the declarant reports them in the customs declaration. This is why having a code somewhere in a catalog is not the end of the task. The relevant reference needs to survive the route from product record to shipment data.

This article is an operational overview, not legal or tax advice. Ask your customs representative to confirm the applicable rules, declaration procedure and required treatment for your shipments using current legislation.

Understand the three identifier roles

The official guidance separates the identifiers by the reference they provide:

  • M-PID, merchant product identifier: connects the goods with the product offered on a seller’s website, marketplace or platform.
  • NS-PID, non-standardized manufacturer product identifier: identifies the product through a manufacturer, producer or supplier reference, such as a model, part or style code.
  • S-PID, standardized manufacturer product identifier: uses an internationally recognized scheme, such as an EAN, UPC or ISBN, where one exists.

Think of these as distinct roles, not three arbitrary strings to populate. A useful record should explain what each value refers to and where it came from. A product title is not a reliable substitute for that explanation, especially when the same title covers several sizes, colors or pack configurations.

The guidance also emphasizes variant-level uniqueness and persistence. A code that changes whenever a warehouse receives a new batch can create a different traceability problem from the stable reference the business intended to use.

Start with the product that will actually be shipped

Select a small, representative group of active EU-bound products and follow each one through the business. Compare the storefront variant, supplier record, packaging information and the data used to prepare the shipment. Keep the source of each identifier visible.

Check similar variants deliberately. A parent product record may look complete while one size or pack configuration has missing or copied information. The question is whether the identifier describes the goods in that order, not whether the catalog page contains a barcode somewhere.

Consider a hypothetical example, not a customs ruling or a Speedfulfill customer result. A store sells a bottle individually and in a two-bottle gift pack. A supplier reference for the single bottle should not simply be copied into every field for the gift pack without checking what those references identify. Ask the supplier and declarant how the actual products and packaging should be represented.

Separate a missing standardized code from missing information

The Commission notice explicitly provides for the situation in which no standardized identifier exists: that absence must be indicated using the appropriate declaration treatment. It does not tell every seller to manufacture an international barcode.

First establish whether the product truly lacks an S-PID or whether the information has simply not reached the merchant. Check the packaging and ask the supplier for the relevant product reference. Do not mark a missing-code declaration merely because a field is inconvenient to complete.

Equally, do not turn an internal stock code into an apparently standardized number. Retain its real role and origin. The treatment of an absent S-PID does not, by itself, remove the need for other required product information or prove that the goods qualify for a broader exemption.

Shopify’s label workflow is not every fulfillment workflow

Shopify’s October 24 announcement describes support within Shopify Shipping and Managed Markets label purchasing. Its Help Center instructions explain how variant data, identifier types and declarations are used in that workflow.

For example, Shopify documents using the variant ID for its merchant identifier and provides specific handling for manufacturer references and products with no standardized identifier. Those instructions describe the platform’s implementation. They should not be copied into a spreadsheet and assumed to govern every broker or carrier’s submission.

If labels are purchased outside Shopify, confirm the receiving provider’s fields and format. Ask which references it receives, how variant changes reach it, and what happens when the data is incomplete. A connected order feed is not proof that every required product attribute is included.

Confirm what reaches the declarant

Use a test record or another appropriate pre-dispatch check to follow one product through the actual process. Compare the source values with the information the provider receives, rather than stopping at a successful store save or file upload.

Document who resolves a mismatch. A merchant may own the sales record, a supplier may confirm a model reference, and a broker may determine the required declaration format. Make those responsibilities explicit so an exception is not passed around without resolution.

This is a data-quality check, not an instruction to file an experimental or inaccurate declaration. Use the provider’s approved validation process and retain the explanation for any correction. Do not assume that a newly accepted label or data file guarantees customs release or product compliance.

Which scope questions still need confirmation?

Do not infer a universal value exemption from a platform summary. Shopify’s guidance addresses low-value parcels, while the Commission’s October guidance discusses an intended clarification of the legal wording. Dutch Customs’ October update also distinguished then-current law from a proposed narrowing of scope.

For consignments above EUR150, unusual transaction structures or a different declaration procedure, obtain current advice from the declarant. This article does not announce that every higher-value shipment is exempt. The guidance is explanatory; binding legislation and applicable national implementation take precedence.

Keep identifiers separate from classification, safety documentation and charges. Having a product reference does not settle every customs or product-safety obligation, and it is not a new shipping price. Review those subjects with the appropriate evidence instead of combining them into a single compliance checkbox.

A practical product-data checklist

Use this original operating checklist to prepare the handoff, not as a substitute for official filing instructions:

  1. Confirm the shipment scope. Identify the destination, transaction and declaration route; have the declarant confirm the applicable requirement.
  2. Map the references. Connect the selling variant with its merchant reference, supplier or manufacturer reference, and standardized identifier where present.
  3. Record the evidence. Keep the source document or supplier confirmation and explain genuine missing identifiers using the correct process.
  4. Check the transmission. Verify what reaches the label or customs workflow, including the relevant variant rather than only the parent product.
  5. Own the exceptions. Assign the unresolved question, next action and review point before relying on the record for shipment preparation.

Repeat the check when suppliers, variants or packaging change. Preserve a record of what changed and why. A catalog that was correct before a product update should not be assumed to remain correct without checking the affected references.

Frequently asked questions

Do all products need a newly purchased international barcode?

No. Establish whether a standardized identifier already exists. Where none genuinely exists, follow the official declaration treatment and the instructions of the applicable platform or declarant. Do not invent a standardized code to make a form look complete.

Is an internal SKU sufficient for every PID field?

Do not assume so. The identifier roles differ, and the receiving workflow has specific requirements. Shopify documents its own handling, including fallbacks; that does not establish a universal rule for external declarations. Confirm the actual field mapping with the provider.

Does Speedfulfill automatically submit these identifiers?

This article does not announce that capability. Confirm the service scope, source data, transmission method and responsibility for filing with the relevant parties. No automatic integration, exemption decision or customs-clearance guarantee is implied.

Make product references usable across the handoff

The immediate task is to make the product record intelligible beyond the storefront: the right variant, the right references and a verified route to the declarant. Resolve uncertainty before treating the data as ready for shipment preparation.

To discuss how your product information and fulfillment requirements fit together, visit Speedfulfill. Confirm the available services and data responsibilities for your business, and use a qualified customs representative for legal applicability and declaration advice.

Official sources

Recent Posts