# Set up product identifiers for EU shipments URL: https://support.starshipit.com/articles/1790827200001-set-up-product-identifiers-for-eu-shipments Canonical: https://support.starshipit.com/articles/1790827200001-set-up-product-identifiers-for-eu-shipments Markdown: https://support.starshipit.com/articles/1790827200001-set-up-product-identifiers-for-eu-shipments.md Updated: 2026-10-20 > For the complete documentation index, see [llms.txt](https://support.starshipit.com/llms.txt). > Add product identifiers to EU orders, enter them in Starshipit and check the values before shipping. If you ship orders from outside the EU to EU customers, customs and your courier may need item-level product identifiers to identify products and support safety and compliance checks. This guide explains which identifiers Starshipit supports and how to check them before shipping. Starshipit supports these identifiers for **DHL Express, FedEx and UPS**, and for eligible **Asendia** EU shipments. Which identifiers you need depends on your courier and service, so confirm the requirements before shipping. Asendia has the shipment scope and length limits described below. ## Choose how to add identifiers - **Manually in the UI 2.0:** Save identifiers in Product Catalogue for products you ship regularly, or enter them on an individual order. - **Shopify:** Import identifiers from product or variant metafields on newly imported Shopify Classic or Enhanced orders. - **CSV:** Import identifiers with an order CSV or Product Catalogue CSV. - **API:** Send identifiers with order items through the order API or catalogue products through the Product API. ## Understand the three identifiers Product identifiers help customs identify the specific products in your shipment. They are separate from HS codes, which identify the type of goods. | Field | What to use | | --- | --- | | **Merchant Product ID** | You can use your existing SKU. If you want to use a different product code, enter it in the Merchant Product ID field. | | **Manufacturer Product ID** | The product code assigned by the manufacturer or brand owner. This must be provided separately, even if it is the same as your SKU. | | **Standardised Product ID** | A recognised identifier such as GTIN, EAN, UPC or ISBN. You can use the Barcode field if it contains this identifier, or enter a different value in Standardised Product ID. | **For DHL Express, FedEx and UPS, you don't need to enter a Merchant Product ID if you're happy to use your existing SKU.** Starshipit will automatically use your SKU when sending the product identifier to these couriers. Only populate Merchant Product ID if you need to send a different value. For example, a T-shirt might use `TEE-NAVY-M` as your SKU, `STYLE-240-M` as the manufacturer's product code, and an EAN as its standardised identifier. Use the identifiers for each specific product or variant. **Manufacturer Product ID** is different from **Manufacturer Code (MID)**. MID identifies the manufacturer or supplier, rather than a particular product. ## Before you begin - Use the **UI 2.0** for the product and order editing steps below. - Collect the manufacturer or brand owner's product codes. Ask your supplier if you do not know them. - Check which identifiers your courier requires for your shipments. - Use a recognised product identifier for **Standardised Product ID**. An internal warehouse barcode is not necessarily a GTIN, EAN, UPC or ISBN. :::important Check each order has the identifiers your courier requires before shipping. Starshipit does not check every required identifier before label creation, and missing or incorrect details may cause your courier to hold or reject the shipment. ::: ## Check Asendia identifiers For outbound business-to-consumer Asendia shipments from outside the EU to the EU, Starshipit sends the identifiers on each customs item. This applies to the direct Asendia connection, rather than Parcelpoint powered by Asendia. - **Merchant Product ID:** Uses the dedicated field when populated, otherwise the item's SKU. - **Manufacturer Product ID:** Uses the dedicated field. It is separate from MID and has no SKU fallback. - **Standardised Product ID:** Uses the dedicated field when populated, otherwise the item's Barcode. Each value sent to Asendia must be **30 characters or fewer**, including a SKU or Barcode used as a fallback. Starshipit trims spaces around the value and asks you to correct it if it is too long. Update the order item and its source data so future imports use the correct value too. Blank identifiers are left out, so check that the item includes everything Asendia requires for your service. These fields are not sent for returns, business-to-business shipments, shipments within the EU or shipments to non-EU destinations. ## Add identifiers to Product Catalogue Save identifiers in Product Catalogue for products you ship regularly. 1. In **UI 2.0**, open **[Products](https://next.starshipit.com/products)** and find the SKU used on your orders. 2. If identifier columns are hidden, use the **settings cog** to show **Merchant Product ID**, **Manufacturer Product ID** and **Standardised Product ID**. 3. Enter the manufacturer's product code in **Manufacturer Product ID**. You only need to populate **Merchant Product ID** if you want to use a different value from your SKU. Similarly, populate **Standardised Product ID** if you want to use a different value from your Barcode. 4. Save your changes. To apply these details during order import, enable **Enable Product Catalogue for order import** in **Settings > [Product Catalogue](https://next.starshipit.com/settings/product-catalogue)**. Check whether your settings fill missing values or overwrite existing order data. See [Configure Product Catalogue settings](/articles/1781620000002-configure-product-catalogue-settings). The catalogue SKU must match the order item's SKU. Saving catalogue values does not update orders that were already imported. In UI 2.0, [apply Product Catalogue to the existing eligible orders](/articles/1792513200001-apply-product-catalogue-to-existing-orders), then check each item's identifiers before shipping. ## Add identifiers to an individual order 1. Open an unprinted order in the **UI 2.0** and go to the **Items** section. 2. Show the product identifier columns if they are hidden. 3. Enter the relevant identifiers for each item, then save the order. ## Check the details before shipping Open a representative unprinted order after creating or importing it. Check that each item has the correct manufacturer code and either a Merchant Product ID or SKU. Where the product has a recognised standardised identifier, check that it is supplied through Standardised Product ID or a valid Barcode. If catalogue values are missing, check that the SKUs match and catalogue population is enabled. Also check whether an existing order value is being preserved by your catalogue settings. Keep your usual customs details complete, including product description, HS code, country of origin and item value. Product identifiers do not replace these fields. ## Import identifiers by CSV, platform integration or API For Shopify Classic or Enhanced, enable **Import EU product identifier metafields** in the **UI 2.0**. Follow [Import optional data from Shopify](/articles/90200000000206-import-optional-data-from-shopify#eu-product-identifier-metafields) for the exact metafield keys and setup steps. Variant values take priority over product values, separately for each identifier. This import setting does not backfill existing orders or update Product Catalogue. For other platform integrations, check an imported order or contact Support to confirm which fields are mapped. - **Order CSV:** The updated order CSV template and order CSV field mappings support the dedicated identifiers on order items. - **Product Catalogue CSV:** Product Catalogue CSV import supports the dedicated identifiers. - **API:** Add the fields below to each order item through the order API, or to a catalogue product through the Product API. | Item field | What it identifies | | --- | --- | | `merchant_product_id` | Merchant Product ID: your SKU or product code. | | `manufacturer_product_id` | Manufacturer Product ID: the manufacturer's or brand owner's product code. | | `standardised_product_id` | Standardised Product ID: a GTIN, EAN, UPC or ISBN, where available. | ## FAQs What if a product does not have a standardised identifier? Leave **Standardised Product ID** blank if no recognised identifier exists. Check that **Barcode** does not contain an internal code that could be used as a fallback. Do not invent a GTIN or enter placeholder values such as `NA` or `NO` in your product data. Merchant and manufacturer identifiers may still be required. Can the merchant and manufacturer identifiers be the same? Yes, if the code genuinely identifies the product in both systems, such as a brand selling its own products. Enter it in **Manufacturer Product ID** as well; Starshipit does not automatically copy SKU into that field. ## Related articles - [Add and manage products in the Product Catalogue](/articles/1781620000001-add-and-manage-products-in-the-product-catalogue) - [Sync product data with Product Catalogue](/articles/14700000001007-sync-product-data-with-product-catalogue) - [Set up MID codes for international shipments](/articles/13720206390671-set-up-mid-codes-for-international-shipments)