For the complete documentation index, see llms.txt. This page is also available as Markdown.

Use item codes

Learn how item codes work, when to change them, and what to avoid.

Every item needs an item code.

OutSmart uses this code as the main identifier for the item across the catalog, imports, and integrations.

How item codes work

An item code can contain numbers, letters, or both.

The code must be unique.

Once an item is in use, changing the code can break matching in imports, automations, and integrations.

Best practices

Use item codes that are:

  • unique

  • stable over time

  • compatible with connected systems

Avoid special characters when possible. Some integrations do not accept them.

Set an item code

1

Create or open the item

Go to Items.

Open an existing item or create a new one.

2

Enter the code

Fill in Item code.

Use a value that fits your current catalog structure.

3

Save the item

Save the item.

The code is now used as the item identifier.

Change an item code

You can change an existing item code, but only do this when necessary.

Changing a code can cause duplicate items, import mismatches, or integration errors.

When a code change causes problems

Problems usually appear when:

  • an import file contains new codes for existing items

  • an integration accepts a stricter code format

  • employees can still select old and new versions of the same item

If you must switch to a new code format, update the full catalog in a controlled way.

Frequently asked questions

Can I use letters in an item code?

Yes. OutSmart accepts letters, numbers, or a combination of both.

Can I change an item code later?

Yes. But only do this when it is required.

Why do integrations matter?

Some integrations accept fewer characters or only certain formats. Your item codes must match those rules.

Last updated

Was this helpful?