Struct Docs
Struct.PIM 4
Struct.PIM 4
  • Struct PIM Documentation
  • API Reference
  • Latest updates from Struct HQ
  • Latest updates in Documentation
  • Fundamental concepts
    • Get familiar with Struct PIM
    • Catalogues & categories
    • Products & variants
    • Attributes
    • Product structures
    • Identifiers
    • Global lists
    • Localization & segmentation
    • Revisions & changelog
    • Publications
    • Supplier onboarding portal
  • Tutorials
    • Welcome to Struct PIM 4
    • Helpful guides
      • How to search efficiently
      • How to use Import
        • How to import products
        • How to import data into a list property on entities
        • How to import categories
        • How to import with media
        • How to use File templates
    • Example projects
      • Working with the API
  • Integration
    • Web API
    • Webhooks
  • Media format
  • API Reference
    • Introduction
    • Endpoints
      • AssetFolders
      • Assets
      • AssetTypes
      • AttributeGroups
      • Attributes
      • AttributeScopes
      • Browse
      • BusinessUnits
      • Catalogues
      • Categories
      • Dimensions
      • Exports
      • EnrichmentInsightSetups
      • GlobalLists
      • Languages
      • Maintenance
      • Miscellaneous
      • Messaging
      • Permissions
      • Products
      • ProductStructures
      • Publications
      • Transactions
      • UserGroup
      • UserRoles
      • Users
      • VariantGroups
      • UserTasks
      • Variants
      • Webhooks
      • Workflows
      • Models
Powered by GitBook
On this page
  1. Fundamental concepts

Identifiers

Identifiers in Struct PIM link external keys to internal IDs, enabling efficient updates and retrievals using known external identifiers.

What are identifiers

Identifiers are used to create indexes of values of attributes that can be used from the API to find products, variants or categories based on a unique identifier in an external system.

As any update request to Struct PIM requires the internal id of the resource being updated, a mechanism must exist to resolve this internal id based on a known key. For this, implementors will create identifiers in Struct PIM defning the maps between externally known keys and the internal id of the resource in Struct PIM.

Example: In an ERP system, a product has a SKU, which is used to uniquely identify the product. An integration job created the product in Struct PIM and the SKU is written to a "SKU" attribute on the product. Later, when the integration job runs again, it needs to update the product. In order to update an existing product, the internal id assigned to the product in Struct PIM must be known, but the integration job only knows the SKU from the ERP system. Because an identifier has been setup on the SKU attribute in Struct PIM, the integration job can request the internal id of the product based on the SKU it knows from the ERP system. From the internal id it is able to update the product in Struct PIM

PreviousProduct structuresNextGlobal lists