PIM

Custom Metadata

Extend product data with flexible custom fields and metadata.

Custom Metadata

SimplePIM supports flexible metadata fields that allow you to extend product data beyond the standard fields. This enables you to track any custom information specific to your business needs.

Metadata Types

SimplePIM automatically detects and supports these metadata types:

TypeDescriptionExample
StringText values"Premium", "Made in Finland"
NumberNumeric values42, 3.14, -10
BooleanTrue/false valuestrue, false
JSONComplex data structures{"color": "red", "sizes": 1,2,3}

Adding Metadata

To a Product

  1. Open the product details
  2. Navigate to the Metadata section
  3. Click Add Field
  4. Enter:
    • Key: Field name (e.g., "color", "material")
    • Value: Field value
  5. Save the product

Metadata Examples

Common metadata use cases:

  • Product attributes: Color, size, material, weight
  • Marketing data: Brand, category, tags
  • Technical specs: Power rating, dimensions, compatibility
  • Business data: Cost center, supplier code, lead time

Using Metadata in Columns

Metadata fields can be displayed as columns in the product list:

  1. Click Columns
  2. Under Metadata Fields, select the fields to display
  3. The selected metadata appears as additional columns

This allows you to see custom data at a glance without opening each product.

Filtering by Metadata

Use metadata fields in filters:

  1. Open Filters
  2. Select a metadata field
  3. Choose an operator and value
  4. Apply the filter

JSON Path Queries

For JSON metadata, use path queries:

  • $.color - Access the color property
  • $.specs.weight - Access nested properties
  • $.tags[0] - Access array elements

Metadata in Labels

Metadata values can be included in label templates:

{{product.metadata.color}}
{{product.metadata.material}}

This allows labels to display custom product information.

Best Practices

Naming Conventions

  • Use lowercase, underscore-separated names
  • Be consistent across products
  • Examples: color, weight_kg, supplier_code

Data Quality

  • Use consistent values for filtering (e.g., always "Red" not "red" or "RED")
  • Avoid storing duplicate data already in standard fields
  • Document your metadata schema for team consistency

Performance

  • Keep JSON structures reasonably sized
  • Use simple types when possible
  • Avoid deeply nested JSON for frequently filtered fields