Shopper and Admin Custom Attributes on Products
MINOR Introduced Shopper and Admin Custom Attributes for Products
Merchandisers and integrators can now attach flexible string metadata to products in two visibility tiers—catalog-visible shopper attributes and admin-only attributes—using the same model already established for hierarchy nodes.
What's New?
Extended the PIM product model with shopper_attributes and admin_attributes: optional maps of string keys to string values, validated consistently with nodes (including limits on the number of keys and on name and value length).
Product APIs support creating, updating, and reading these fields on products; persisted data is stored on the product document for downstream catalog and administration flows.
Product lifecycle events for create and update now include shopper and admin custom attributes where applicable, so downstream consumers can react without an extra round trip.
CSV export can emit custom attribute columns using the shopper_attributes. and admin_attributes. prefixes; selective exports use columns.include with either explicit keys or a per-type wildcard (shopper_attributes.* / admin_attributes.*), with validation that prevents combining a wildcard and individual columns for the same attribute type in one request.
CSV import understands the same column naming, so bulk workflows can round-trip attribute data alongside core product fields.
For variant matrices, new child products inherit the base product’s shopper and admin attributes at build time; rebuild reconciles parent keys onto matched existing children so shared parent metadata stays aligned while child-specific keys remain unless the parent removes them.
This release brings product custom attributes in line with hierarchy behavior and reduces the need for parallel systems or workarounds for storefront versus internal metadata.
For details see: