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
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.
Do not change item codes casually. Existing data may no longer match the updated code.
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
Related topics
Last updated
Was this helpful?
