Product Identifier Namespaces
Use Product Identifier Namespaces to define company-owned aliases for product identifier sources.
A namespace is a short label such as SAP1, SAP2, SAP_SUPPLY, or ERP_MAIN. It tells Actualog which external identifier system a product code belongs to. Actualog does not need to know the internal application behind the alias; it only needs a stable namespace name that users and integrations can reuse.
What the page is for
Open Company Workspace → Data Integration → Product Identifier Namespaces when you need to:
- add an identifier namespace for an ERP, PIM, marketplace, distributor system, or supplier feed;
- describe what the namespace means for your company;
- activate or deactivate a namespace;
- keep import, export, feed, and API identifier names consistent.
Why namespaces matter
The same product code can exist in different systems. For example, code 100245 in SAP production may not be the same as code 100245 in a supplier file.
The namespace prevents ambiguity:
SAP1:100245
SAP_SUPPLY:100245
Those are different identifiers because they come from different namespaces.
Add a namespace
- Select the correct company workspace.
- Open Data Integration → Product Identifier Namespaces.
- In Add namespace, enter a stable alias.
- Add a description that explains the source system or purpose.
- Save the namespace.
- Use the namespace in imports, exports, feeds, API integrations, or product identifier editing.
Use short stable names. Avoid names that depend on a temporary project or employee.
Activate or deactivate a namespace
Use Deactivate when a namespace should no longer be used for new data but history should remain understandable.
Deactivation is safer than deleting because old product identifiers, import logs, and integration mappings may still refer to the namespace.
Related pages
- Data load — upload files that may contain external identifiers.
- Data exports — export product data with controlled identifiers.
- API Key Management — create API credentials for integrations.