Products → Variant Attributes is not a blank attribute library and does not create Size, Color, or other reusable choices by itself. It summarizes attributes already stored on product variants. Its Standardize actions write directly to every listed affected variant and rebuild those variant names, so review product and variant counts before using them. The approved Harbor & Hearth capture for this route was rejected because the live page displayed a recovery error; no screenshot is substituted.

Before you beginSearch first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.

Step by step

  1. Plan the attribute model before editing: use stable customer-facing names such as Size, Color, Material, or Comfort and consistent values. Decide which combinations are actually sold, how each will be identified, priced, stocked, labeled, and selected at checkout.
  2. Go to Products → Product Catalog and create or open the parent product. Complete the product-level identity, supplier, pricing, tax, inventory-tracking, and other required settings before relying on inherited variant defaults.
  3. In the product editor’s variant section, enter an Attribute name and choose Add attribute. Add each allowed value under that attribute. Names are matched exactly inside the editor, so avoid alternate casing, extra spaces, abbreviations, or near-duplicates.
  4. Add additional attributes only when every generated cross-combination is meaningful. CentriPOS automatically builds the Cartesian product of all nonempty attribute value lists—for example, three Sizes and two Colors create six variant rows. Review the resulting count before saving.
  5. Rename an attribute or value carefully. The editor updates affected draft attribute keys/values and rebuilds variant display names from the nonempty values. Removing a value regenerates the combination list; removing the final value removes the attribute. Confirm no legitimate combination or existing variant detail was unintentionally dropped.
  6. Review every generated variant row. Set a unique SKU and vendor code as required, Vendor Cost, Retail, and the On switch. Sync vendor code to SKU copies nonblank vendor codes into SKU and disables direct SKU editing while selected; use it only when those identifiers are intentionally identical.
  7. Expand each variant to manage its barcode and supported detail, bundle, and per-location inventory fields. Confirm stock on hand, reorder point, and reorder quantity when inventory tracking applies. Variant-level cost can be restricted when that variant is a bundle.
  8. Save the product and wait for success. Reopen it to confirm the exact combinations and identifiers persisted. Then test the product in Register → Sell: search or choose the product, use the variant picker, and confirm disabled variants are unavailable and the selected SKU, attributes, price, barcode, and inventory behavior are correct.
  9. To audit catalog-wide consistency, go to Products → Variant Attributes. Read the headline counts for attributes, values, and cleanup candidates. Search by attribute, value, product, or SKU; the query is reflected in the URL so filtered views can be revisited.
  10. Review Duplicate Attribute Names. Candidates differ only by normalized casing or whitespace, such as Size versus size. Read every source label and the affected variant/product counts, enter the exact canonical attribute name, and choose Standardize only when they truly represent the same concept.
  11. Review Duplicate Variant Values separately. These candidates differ only by casing or whitespace under the same normalized attribute family. Enter the intended canonical value and choose Standardize only when the meanings are identical. Do not merge business-distinct choices merely because their spelling looks similar.
  12. Understand the write before confirming: attribute-name Standardize rewrites the matching key on every affected product variant, preserves the first value encountered under the target key, and rebuilds each variant name from its remaining attribute values. Value Standardize rewrites the matching value and also rebuilds the variant name. The update runs variant by variant and is not presented as a preview or undoable batch.
  13. After Attribute names standardized or Variant values standardized appears, wait for products to reload. Expand the affected attribute card, review its value/product/variant counts, use View all products or View products, and inspect representative products and SKUs. Test search, Sell variant selection, labels, dynamic quick picks, reporting filters, and online/integration behavior that depends on the changed label.
  14. If a batch fails or produces an unexpected result, stop further standardization. Record the canonical label, original spellings, affected products/SKUs, time, and error. Correct individual products deliberately or escalate rather than repeatedly applying another bulk label.

Screen and contract reference

Control or areaWhat it means
Attribute nameKey stored on each variant, such as Size or Color; created and edited inside a product, not in a separate reusable library.
Attribute valueChoice stored under an attribute key, such as Queen or Blue.
Generated combinationsCartesian product of every nonempty attribute value list in the product editor.
Variant rowOne sellable combination with its own enabled state, SKU, vendor code, cost, retail, barcode, stock, and supported bundle/detail settings.
Sync vendor code to SKUCopies nonblank vendor codes into SKU and keeps SKU input disabled while enabled.
On switchControls whether the variant is enabled for supported product-selection workflows.
Variant Attributes screenCatalog-wide summary built from existing product_variants.attributes records; primarily an audit and cleanup surface.
Attribute / value / cleanup countsHeadline totals derived from currently loaded products and their variants.
Search attributes, values, products, or SKUFilters the summary and writes q to the route query string.
Duplicate Attribute NamesLabels whose trimmed, collapsed-space, lowercase form is the same but whose original spelling differs.
Duplicate Variant ValuesValue spellings whose normalized form is the same within the same normalized attribute family.
Suggested labelMost-used spelling, with alphabetical tie-breaking; it is a suggestion, not proof of the correct business term.
Standardize attribute nameBulk-writes the target key across every listed affected variant and rebuilds variant names.
Standardize variant valueBulk-writes the target value across every listed affected variant and rebuilds variant names.
Attribute names standardized / Variant values standardizedSuccess toast followed by product-query invalidation and reload.
Attribute cardExpandable summary of value, product, and variant counts for one exact attribute key.
View all products for …Opens Product Catalog filtered by the selected attribute key.
View productsOpens Product Catalog filtered by the exact attribute/value selection.
No exact screenshotThe Amelia Grant Harbor & Hearth /catalog/variant-attributes capture was rejected because the live route showed a recovery error. This guide intentionally uses no fabricated or mismatched image.

Expected result

The attribute values generate only the intended variants, each variant has a distinct identity and selling configuration, and no duplicate combinations remain.

Troubleshooting

  • Confirm whether you are editing a product, variant, shared master record, or location-specific value.
  • Search for an existing product, SKU, UPC, attribute, or tag before creating a duplicate.
  • Preview labels, pricing, and availability in the intended location before broad publication.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.