Live now/Structured product content, partner portal delivery, and pricing that scales by volume.
Stackcess
Back to Help Center
Settings and Admin8 minUpdated May 11, 2026

Organising Fields with Attribute Groups

Organise product fields into groups that make day-to-day editing faster and reduce data entry mistakes.

Attribute groups control how product fields are arranged in the product detail editor. Rather than seeing one long list of fields, editors navigate between groups — a well-organised group structure makes data entry faster and reduces mistakes.

Why group structure matters

If fields are poorly organised, editors struggle to find what they are looking for, required fields get missed, and data quality suffers. Good grouping means:

  • Editors know exactly where to go for each type of content
  • Required fields are visible upfront, not buried at the bottom of a long list
  • Different team members — merchandising, compliance, marketing — can work in their own sections without confusion

Recommended group structure

Most product teams find that organising groups around these themes works well:

  • Core identity — product name, identifiers such as SKU, SCIN, and barcode, status
  • Merchandising — marketing copy, benefits, callouts, and key claims
  • Technical / Specifications — ingredients, nutrition facts, format, and dimensions
  • Compliance / Regulatory — certifications, safety data, and label requirements
  • Media / Documentation — image slots and document slots
  • Channel overrides — fields that need different values per channel or destination

Naming your groups

Use names that make sense to the people editing products, not internal project names. Merchandising Content is clearer than Section B or Phase 2 Fields. Clear names reduce training time and mistakes.

Ordering fields within a group

Put the most frequently used or most important fields at the top of each group. Required fields should appear first so editors complete them early — not discover them after working through a long list.

Sharing groups across families

You can attach the same attribute group to multiple product families. This works well for groups like Core Identity or Compliance that apply across all product types. For groups with highly specific content, create a family-specific group instead.

Keeping groups healthy

Over time, groups can accumulate unused or redundant fields. Review your groups periodically to look for fields that are rarely filled in, duplicate groups covering the same content, and groups with only one or two fields that could be merged into a broader group.

Have Your Say