Product naming rules for a growing Shopify team
Three people add products from three suppliers, and you get three naming styles. One title leads with the brand, another with the model, and a third says “cable” four times. Scanning the catalogue becomes a chore.
A naming rule can fix that, but only if it reflects how customers tell products apart and survives changes to the range. Product naming is an information design problem. A title should identify the item without carrying every attribute, keyword and promotion.
The rule needs room for different product types, variants and markets. A rigid formula can look consistent in a spreadsheet and make the storefront less clear. I’d rather have a flexible rule with documented exceptions than a perfect formula that nobody follows.
Start with the distinctions shoppers need
Gather representative product records and ask what a customer needs to recognise each item. Depending on the range, useful distinctions might be product type, model, material, size, capacity, compatibility, colour or generation. Use evidence from customer questions, onsite search, sales, support and product documentation. Don’t assume every attribute matters equally in every category.
Keep the product name apart from the rest of the page. Specifications, claims, shipping notes, promotional phrases and search terms usually have better homes than the title. Stuffing them in makes long names that are hard to scan and go stale when the offer changes.
Check how customers refer to the product. Supplier names and internal codes may be necessary for operations, but a shopper-facing title may need a common product type or model identifier. Preserve the internal identifiers in their designated fields so the public name does not have to do double duty.
Define a flexible rule
Write a default order for the elements that matter, then document when to omit or reorder them. For instance, a model name may be the primary identifier in one product family, while size is more important in another. The rule should explain exceptions rather than force an inaccurate attribute into every title.
Set conventions for capitalisation, units, punctuation, brand inclusion, and variant names. Make decisions about abbreviations and symbols. If a title includes a size, use the correct unit and formatting consistently. If the product has a variant, decide which distinction appears in the page title and which appears in the option selector. These choices should match the product data and customer language.
Create examples of good, acceptable and rejected names using real catalogue structures, without disclosing private supplier information. Explain why each one works. A short reference with edge cases gets followed far more often than an abstract rule that says “be consistent”.
Keep source data clean
Identify the fields that contain official product type, brand, model, and variant attributes. Use structured fields where possible rather than asking editors to extract information from long descriptions. Validate imports so missing attributes do not produce awkward punctuation or false claims. If a naming rule uses a field, assign an owner who can correct that field.
Distinguish the product title from SEO title settings if the platform or app allows them to differ. A search title can be adjusted for clarity and length, but it should still accurately represent the product and avoid keyword stuffing. Avoid automatically appending the store name or brand multiple times if the theme already adds it.
Before changing existing titles, export a baseline and identify records that need exceptions. Bulk rewriting can erase meaningful differences or create needless review work. Test the rule on representative products, variants, bundles and legacy items. Then ask someone outside the editing team to find and tell apart products using only the new names. In Garey’s Shopify catalogue work, that outsider test is the one I trust most.
Apply the rule across customer touchpoints
Check product pages, collection cards, onsite search, recommendations, feeds, and support materials. Different surfaces may truncate titles or display only part of them. Place the most useful identifying information early enough to survive those limits. If an attribute appears only in a selector, ensure the selector is understandable and accessible.
For translated catalogues, maintain approved terminology and allow market-specific phrasing where needed. A direct translation of the English sequence may not sound natural in Arabic. Have qualified language reviewers approve public terms and preserve equivalent product distinctions across language versions.
Maintain and improve the system
Name an owner for the rules and set a review point when the catalogue structure, supplier data, or product range changes. Track exceptions with a reason so they do not silently become a second naming system. If repeated exceptions appear, decide whether the default rule needs updating.
Make exceptions visible rather than embarrassing
A naming guide should explain how to handle items that do not fit the default. Bundles, replacement parts, limited editions, and model families may need a different order. Give editors a way to record why an exception exists and who approved it. An exception is not automatically a failure; a silent exception is difficult to maintain because later editors cannot tell whether it was deliberate.
Review search and onsite labels without treating keywords as the only audience. A title that repeats a phrase may seem optimised but can become hard to read on a collection card. Preview the naming pattern in narrow layouts and in navigation. If the important distinguishing word is truncated, revise the order or use a complementary attribute display rather than adding more text indiscriminately.
When a product is translated, maintain the meaning and identifying attributes, not just the word order. Keep model codes unchanged where appropriate and have a language reviewer approve the public product type. The same internal naming rule can produce natural market-specific titles if it defines required information rather than a rigid sentence template.
Related reading
- What a store team should learn from product returns
- A product information standard for a growing shop
- A site search review for a Shopify store with a broad catalogue
Which product distinction in your catalogue is hardest to recognise from the title alone?