M-PID, NS-PID and S-PID: a guide to EU product identifiers
A supplier spreadsheet and a Shopify catalog can describe the same item using different identifiers. EU PID Ready helps you review three kinds of identifier data for eligible physical variants in EU customs workflows.
EU PID Ready currently stores PID values in its Shopify metafields. It does not write Shopify's native barcode collection or its native no-standardized-identifier declaration. The app's checks and Shopify's native customs workflow are different.
M-PID: Merchant Product Identifier
In EU PID Ready, your merchant PID override takes priority over your Shopify SKU. A missing or duplicated resolved value needs attention under the app's rules. For example, TEE-BLUE-M may identify a particular size and color. Editing the override does not rewrite the SKU.
Shopify's native EU customs flow uses the variant ID as M-PID. A SKU is therefore not a universal customs requirement; a missing-SKU issue in this app is not itself proof of a customs failure.
NS-PID: Non-Standardized Manufacturer Product Identifier
Ask your manufacturer or supplier for the verified manufacturer reference for that item. A supplier stock code is not necessarily that reference. The app uses a variant-specific manufacturer PID first, then the product default if no variant value exists. Use a shared default only where it genuinely applies; variants with their own identifiers can override it.
A manufacturer identifier can be a model, part number or style reference. Shopify's native flow also provides fallbacks when a native NS-PID is absent. EU PID Ready currently checks its manufacturer metafields instead; the two readiness decisions can differ.
S-PID: Standardized Product Identifier
The app records a standard identifier and a type such as GTIN, EAN13, EAN8, UPC or ISBN. A Shopify barcode can be offered as a suggestion, but it is not automatically accepted or saved. Verify its source and choose the appropriate type. If no standardized identifier exists, choose NONE explicitly and keep the value empty.
Does NONE activate Shopify's Y081 declaration?
No. NONE records your decision in EU PID Ready's metafields only. It does not turn on Shopify's native “Has no standardized identifier” setting, referred to as Y081 in customs declarations. Review that setting separately in Shopify when appropriate.
What does READY actually mean?
READY means that the variant passes the app's identifier completeness and consistency checks. It does not confirm native barcode or Y081 setup, identifier ownership or authenticity, legal compliance or customs acceptance. Applicability depends on your actual cross-border fulfillment flow; confirm requirements with your logistics provider or customs adviser.
A practical review checklist
- Run a free scan and open an ACTION REQUIRED variant.
- Check the SKU or merchant override and resolve duplicates.
- Confirm the manufacturer reference and whether it is variant-specific or inherited.
- Review the standardized identifier and type, or explicitly confirm NONE.
- Save your edit. The app re-reads Shopify and recalculates readiness.
For multiple supplier rows, PRO adds CSV matching and a preview before confirmed changes are applied. Product names are review context, not automatic match keys. FREE includes scans, rescans, the dashboard and single-variant editing.
Scan my Shopify catalog — free · See the app walkthrough · Ask for help
Further reading
For Shopify EU customs product identifiers, read Shopify's official product identifier guidance. It describes native barcodes, fallback rules and the no-standardized-identifier declaration. This guide describes EU PID Ready's current editor, not an automatic connection to a carrier or customs service.