Product Templates
Build reusable product forms with ordered fields, required and translatable settings, default values, duplicate and default-template actions, plus template-driven prefill support for product creation.
Product Templates
Templates ensure 98% data consistency across your catalog.
Product templates drive the product form system. Users can create templates, search them, duplicate them, set a default template, reorder them, and edit the exact field composition used during product creation and maintenance.
Template editing supports adding standard fields, adding custom fields, updating field labels and settings, changing width and default value, toggling required, readonly, translatable, and supplier-portal visibility flags, and reordering or removing fields entirely.
Templates also connect directly to prefill behavior. The controller exposes prefill data and preview count endpoints so category-driven defaults can be surfaced before products are created from the template.
Catalog teams should not rebuild the same form over and over
Manual field selection during every product create flow slows data entry and increases inconsistency.
Solution:
Templates define the field set once and the product create flow starts from that reusable structure.
Different assortments need different field requirements
Some products need technical specs, some need variant handling, some need supplier portal visibility.
Solution:
Template fields carry required, readonly, translatable, default-value, and visibility settings at field level.
Starting from scratch wastes time
Teams often create very similar templates for related product families.
Solution:
Templates can be duplicated and reordered, and one template can be marked as the default for faster creation.
Default values should come from business logic, not memory
Users should not have to remember every category-driven default when creating products.
Solution:
Template prefill endpoints work with workflow prefill logic to preview and apply category-based defaults.
Need reusable product forms with real field governance?
Use product templates to define the exact structure, defaults, and visibility rules your catalog teams should work with.