TITANTH

For Shopify merchants shipping physical goods from outside the EU to EU customers

Find product-code gaps before you send data for EU orders.

Export your Shopify products and see which items need a supplier's code or barcode checked. Get a next step for each item and keep a record of answers you verify. Your catalog stays on your computer.

Want to use your own Shopify CSV? Check the first 100 data rows free.

100 data rows freeTry your own CSV before buying
10,000 rowsFull version, up to 10 MB
US$59 onceOne merchant store; no subscription
Local reviewNo catalog upload or Shopify login

A worked example

From a Shopify export to a useful supplier question.

Illustrative data, not a real customer result or a customs decision.

1 · Your CSVCanvas tote · SKU CB-01
This export has no maker-code field.
2 · The next actionConfirm the scope for this item. Ask the maker which product code identifies this exact tote, or whether they use another confirmed reference.
3 · Your review recordEnter only the answer and source you verified. Both versions export supplier questions, a review CSV and a change log, and turn supplier answers into a Shopify import file (the free checker for up to 3 products). The full version handles the whole catalog. The review files themselves are not for import.

An unanswered code is a question to resolve. The checker cannot invent or authenticate a code. Shopify offers an NS-PID type in each variant’s Barcodes, and a real Product CSV export writes it as ns-pid:CODE (checked 21 October 2026). A defined product metafield can add one product-level CSV value; confirm the maker code for each exact variant.

Try this kind of check with a synthetic sample →

TITANTH Catalog Check worksheet: each product row with its finding and next step
Actual tool interface using synthetic sample data. Open the full-size screenshot.

How it works

  1. Export your products from Shopify (Products → Export → CSV).
  2. Open the checker and choose the file. It runs in your browser; nothing is uploaded.
  3. Work the list: fix blank SKUs and bad barcodes yourself, send the supplier question sheet for the maker's codes, record each confirmed value.

Free or full?

On a phone, swipe the table sideways to compare both versions.

Free online checkerCatalog Check — US$59 once
Rows checkedFirst 100 CSV data rowsWhole catalog, up to 10,000 rows
Findings with next stepsYesYes
Supplier question sheets by vendorYes, for the first 100 rowsYes, for the whole catalog
Review CSV and change logYes, for the first 100 rowsYes, for the whole catalog
Shopify import file from supplier answersYes, up to 3 productsYes, every product you changed
Runs offline from a file you keepNo (online page)Yes (one HTML file)
Stores covered—One store, owner and staff

See exactly what the full version includes →

Why product identifiers matter for EU shipments

For the distance-sale imports covered by the rule, the customs data calls for a merchant product identifier, a maker or supplier identifier, and a standardised identifier where one exists. Scope and exceptions need case-by-case review.

On a phone, swipe the table sideways to see each code and its source.

CodeCustoms nameWhere it usually lives in ShopifyRequired?
Your product codeMerchant product identifier (M-PID)Variant SKUYes
Maker's / supplier's codeNon-standardised manufacturer product identifier (NS-PID)NS-PID type in variant Barcodes (written as ns-pid: in Product CSV export); defined product metafield for one product-level valueYes
BarcodeStandardised manufacturer product identifier (S-PID: GTIN, EAN, UPC, ISBN)Variant Barcodes (Barcodes in Shopify's help page; older exports: Variant Barcode or Barcode)Where one exists

Source: Commission Delegated Regulation (EU) 2026/1022. Voluntary from 1 July 2026, mandatory from 1 November 2026. This page is a data-readiness aid, not legal advice.

For more context on timing and carrier fields, see what carriers say and the September 2026 customs-code update.

Start with the guides