Supply Lens

How do I make Supply Lens recognise a customer's own code for my product?

Add a partner product code

Add a trading partner's product code to a Product as an identifier, scoped to that partner, so their orders match the right Product.

About 4 min

At the end of this guide a wholesaler's or retailer's own code for one of your products will resolve to the right Product in Supply Lens, without changing your own SKUs.

Before you start

  • The Product must exist. See Add a Product.
  • The partner must exist as a Party, so you can limit the code to them. See Add a Party.
  • Have the partner's code exactly as they send it. Check for capitals, spaces and leading zeros.
  • Check no other Product already carries the same code: filter the Products list by identifier.

Steps

  1. Open Settings → Reference data → Products and click the Edit icon on the Product.
  2. In the Identifiers section, add a new identifier.
  3. Choose the identifier type. A partner's own catalogue code is usually a Buyer Product Code. The list only shows the types that apply to your organisation's Integrations. See Product identifiers for every type.
  4. Enter the value exactly as the partner sends it.
  5. Scope the identifier to the partner's Party, so it only applies on that partner's Documents. Leave the other scopes (country, currency, Integration) empty unless you need them.
  6. If the code stands for a particular unit, such as a case, choose that unit of measure for the identifier.
  7. Save the identifier.

Many codes at once

If a partner sends you a spreadsheet of their codes, export your Products, paste their codes into the identifier column for their Party, and import the file back. See Import Products in bulk.

Don't put one code on two Products

If two Products carry the same identifier type and value with the same scope, an incoming Document that uses it is ambiguous. Supply Lens reports an error naming both Products instead of guessing.

Check it worked

  • The code is listed in the Product's Identifiers section, with the partner's Party as its scope and, if you set one, its unit beside it.
  • Reprocess a Document from that partner that failed on this code. The line now shows a green tick and the Document completes.

If something goes wrong

  • The partner's orders still don't match. Check the scope: an identifier scoped to a Party only applies when that Party is the customer on the Document. Check the customer on the Document has matched (it has a green tick).
  • An error says the match is ambiguous. Two Products carry the same code at the same scope. Remove it from the wrong one: click the pencil next to the identifier, choose Remove and confirm.
  • The type you need isn't in the list. The list only shows types for your Integrations. Ask Support.
  • More help: Fix: product does not exist.