Two products look almost identical on the shelf. The order says “sage planter,” but your team still has to work out which size the customer bought.
Give each product variant a clear internal code on your Chandler business website. A SKU gives the team another way to identify the exact item when a familiar product name is not enough.
The useful work is more than filling an empty field. Agree on what the codes mean, check where they are used and make sure a future editor can follow the same system.
Separate the code from the product name
SKU stands for stock keeping unit. Shopify describes SKUs as internal codes for inventory and sales reporting, and treats them separately from barcodes. Both can belong to the same product in their respective fields. Read Shopify’s SKU guidance.
Keep customer-facing names understandable. A shopper should still be able to choose “Sage planter — small” without learning your stockroom abbreviations. Our product-variant guide covers that buying decision.
Before changing anything, choose one product and collect its current title, options, SKU and barcode values. Ask the person who packs it to identify the same physical item. Any disagreement is worth resolving before you create more codes.
Do not turn a supplier’s reference into your new store-wide format without checking what it identifies. Keep a separate note of supplier references when your team needs them to reorder stock.
Give each distinct variant its own code
Imagine a Chandler homewares shop selling the same planter in two sizes. Its owner chooses a short family code, a finish abbreviation and a size ending. These are invented examples, not actual stock records.
- PLT
- Planter family
- SAG
- Sage finish
- SM / LG
- Small / large
Keep this key with the product-entry instructions. These codes are a worked example, not a required format.
Shopify recommends unique SKUs for distinct variants, a short consistent format and avoiding characters that are easily confused. Its guidance also recommends using the same abbreviation for the same attribute throughout the catalog. See Shopify’s naming practices.
Write your chosen meanings beside the example. Have another team member assign a code to a different product using only that note. If they need to guess, revise the rule before applying it across the store.
Keep the code focused on identity. For this imagined shop, a sale price or a shelf position would be a poor ingredient: either could change while the planter remains the same item. Record those changing details in their own places.
Check the systems that depend on the code
List the places where staff use the current value: the store editor, stock records, picking paperwork and any connected fulfillment service. Ask whoever manages each connection which identifier it actually uses.
Do not assume a matching product title proves that two systems refer to the same variant. Compare the exact code alongside the size, finish and other distinguishing details. Save the agreed mapping before an edit.
If you use Shopify’s Fulfillment Network app, its product guidance requires a unique SKU for each variant before an outbound inventory transfer. It also gives separate barcode requirements. Read the Fulfillment Network product requirements.
A homemade internal code does not establish that a product meets those barcode requirements. Ask your fulfillment provider about its actual setup before printing labels or sending stock.
Test a small change before a larger update
Start with a small, agreed set of products. Record the old and proposed values, who will make the change and who will confirm the result. Choose a time when the team can investigate a mismatch before continuing.
In Shopify’s desktop editor, open the product, select the variant and edit SKU in its Inventory section, then save. Follow Shopify’s editing steps.
Reopen that variant after saving. Compare the stored code with your approved record, then check the connected places identified earlier. Include a different size or finish so you are checking more than one easy match.
- Before the editExact variant, old code, proposed code and approving owner.
- After savingReopened product record and each connected destination checked.
- Before expandingResolved mismatches, dated evidence and the next agreed batch.
Arrange any test order with the store owner first, using the store’s appropriate test process. Confirm the selected variant, its internal record and the paperwork the packing team actually receives. Do not place a real paid order just to demonstrate an edit.
If a connected system still shows an old value, stop the wider update. Give its maintainer the before-and-after record and the exact place the mismatch appears. Resolve which system owns the value before repeatedly editing both sides.
For larger changes, our product CSV guide explains why a reviewed sample matters before a broad import. A spreadsheet is not a substitute for understanding the fields it changes.
Keep old references understandable
Save a dated record of any approved rename. Include the old code, new code, exact variant and the reason for changing it. Make that record available to the people handling earlier orders and customer questions.
Do not promise that changing today’s product record will rewrite every earlier document. Inspect an older order, exported record or printed slip separately when your team needs to understand its reference.
Avoid casually recycling a retired code for an unrelated product. A team member looking at an older label should not have to guess which item the code meant at the time.
Check a physical label too. Print a sample using the actual equipment and ask the packing team to read it at normal working distance. Our packing-slip guide covers matching paperwork to the parcel being sent.
Make the naming rule part of adding products
Keep the rule short enough to use: one approved example, the meaning of each part, who assigns new codes and where to check existing ones. Add it to the product-entry handover.
When a new size, finish or product family arrives, confirm the format can describe it before anyone improvises. If an exception is necessary, document it where the next editor will look.
For the imagined planter shop, the finish line is practical. The small and large planters have different codes, the team can explain them and the checked records point to the intended items. That is evidence you can review without promising perfect inventory or faster fulfillment.
Choose one product family on your Chandler business website and compare its codes today. Our e-commerce and payments service can help connect clear product records with the store’s daily work. Show Brandon where your product records stop agreeing.
