Use your internal supplier ID in SDM

Use your own supplier reference in Supplier Data Manager (SDM) to identify which supplier provided each product. Store the reference on the Supplier Organization, then configure Mapping to add it to product data automatically or combine it with a supplier SKU.

Before you start

• Use the new Supplier Portal for supplier uploads. These instructions cover jobs created through the new portal.
• Make sure the Supplier Organization is assigned to the Supplier Portal used for the upload.
• Have your internal supplier reference ready, for example SUP-4271.

Set the internal supplier ID

1. Open the Supplier Organization in the PIM.
2. Find the Internal supplier ID field in its general settings.
3. Enter the reference you use for this supplier in your own systems, for example SUP-4271.
4. Save your changes.

Populate an Attribute from the supplier ID

When the supplier creates a job through the new Supplier Portal, SDM stores the organization's internal supplier ID in the job metadata at job.additional_info.internal_supplier_id. Job metadata is information attached to the upload job, rather than a column supplied in the file.

Set the internal supplier ID

1. Create a destination Attribute in your SDM data model to hold the supplier reference, for example supplier_internal_id.
2. Open the Mapping configuration for the workflow used by the Supplier Portal.
3. Add or update the matching field definition in the configuration's fields array, using the example below.
4. Save the Mapping configuration.

This example is one field definition. Keep the other field definitions in your configuration.

{
  "name": "supplier_internal_id",
  "description": "Supplier Internal ID from the Supplier Organization",
  "requirement_level": "optional",
  "default": [
    {
      "type": "metadata",
      "metadata": "job.additional_info.internal_supplier_id"
    }
  ]
}

The name must match your destination Attribute. The metadata path must remain job.additional_info.internal_supplier_id.

With this configuration, the default value for supplier_internal_id is the ID stored on the job. Every row receives the same ID because the whole file belongs to the same supplier. The supplier does not need to add this reference to their file.

If users must not change this field in the Mapping interface, add "protected": true to its field definition. See Mapping configuration for details about defaults and protected fields.

Combine the supplier ID with a file column

You can also combine the supplier ID with a value from each row, such as a supplier SKU. For example, the supplier ID SUP-4271 and the SKU ABC123 can produce SUP-4271-ABC123.

1. Identify the source column in the supplier file, for example SUPPLIER_SKU.
2. Update the destination field definition in Mapping to include both the metadata source and the file column, as shown below.
3. Save the Mapping configuration.

{
  "name": "sku",
  "mode": "join",
  "default": [
    {
      "type": "metadata",
      "metadata": "job.additional_info.internal_supplier_id"
    },
    {
      "type": "column",
      "column": "SUPPLIER_SKU"
    }
  ],
  "separator": "-"
}

Replace sku with your destination Attribute name and SUPPLIER_SKU with the column name in the supplier file. The configuration joins the supplier ID first, followed by the row's SKU, separated by a hyphen.

The supplier ID stays the same across the job; the SKU comes from each individual row. Using both values helps distinguish products when different suppliers use the same SKU.

Check your configuration

1. Ask the supplier to create a test job by uploading a file through the new Supplier Portal.
2. Run the job through the Mapping step.
3. Check that the mapped supplier reference matches the ID saved on the Supplier Organization.
4. If you configured the combined SKU, check that each value contains the supplier ID, the separator, and the SKU from the corresponding row.

If the value is missing, check the Supplier Organization's ID, the metadata path, and the field definition in the workflow used for the upload. For a combined SKU, also check that the source column name matches the supplier file.