# SKU Manager Docs (/docs)
Everything you need to set up SKU Manager, build SKU patterns, and keep your catalog clean.
# Canceling your plan (/docs/account-billing-and-plans/cancelling-the-app)
## Cancel your subscription [#cancel-your-subscription]
If you no longer need SKU Manager, you can cancel your plan at any time from your account settings. The cancellation only affects future billing, so you can continue using your paid features until the end of your current billing period.
### Open Billing [#open-billing]
In SKU Manager, go to Account, then open Billing.
### Select Cancel plan [#select-cancel-plan]
Click Cancel plan to start the cancellation process.
### Confirm cancellation [#confirm-cancellation]
A confirmation window will appear. Review the details, then confirm that you want to cancel your plan.
## What happens after you cancel [#what-happens-after-you-cancel]
After you cancel, your subscription will remain active until the end of your current billing period.
* You will not be charged again for the next billing cycle.
* Your paid features will continue working until your current plan expires.
* When the billing period ends, your account will no longer have access to paid plan benefits.
Canceling your plan does not end your access immediately. You can keep using your subscription until the current billing period ends.
## Optional feedback [#optional-feedback]
During cancellation, you may see an option to share feedback. This step is optional, but it is always appreciated. Your feedback helps improve SKU Manager for future users.
# Contact details (/docs/account-billing-and-plans/contact-details)
Your contact details help me reach you when it matters. You can update the name and email used for support conversations and important app-related communication at any time.
## Where to update your contact details [#where-to-update-your-contact-details]
To change your contact details in SKU Manager:
### Open Account [#open-account]
In the sidebar, go to
Account
.
### Go to Details [#go-to-details]
Select
Details
.
### Update the Contact section [#update-the-contact-section]
In the
Contact
section, edit your name and email address, then save your changes.
## What your contact details are used for [#what-your-contact-details-are-used-for]
I only use your contact details when I need to reach you directly about SKU Manager.
* **Support replies:** If you send a support question, replies will go to the email address listed here.
* **Important app-related updates:** I may use these details to contact you about issues, changes, or other information you need to know about the app.
* **Direct communication when needed:** If there is something specific that affects your account or use of the app, this is how I will reach you.
Your contact details are not used for marketing.
## Choose the name you want to be addressed by [#choose-the-name-you-want-to-be-addressed-by]
The name saved in your contact details is the name I will use when I contact you.
Depending on your store setup, SKU Manager may have originally pulled in your store name. If you would rather be addressed by your own name, or by a different contact name, you can update it here.
Use a name and email address that you actively monitor so you do not miss important support messages or app-related updates.
# Plans and limits (/docs/account-billing-and-plans/plans-and-limits)
SKU Manager offers three plan levels so you can choose the setup that fits your store today and upgrade later if your needs grow. The main differences are how many products and updates you can manage, plus whether advanced automation features are included.
All stores can start with core tools for updating and restoring SKU changes. Paid plans add more automation, duplicate checking, and higher limits for larger workflows.
## Plan overview [#plan-overview]
Trial is the entry-level option for getting started with SKU Manager. It is best for smaller stores or for testing how the app fits into your workflow.
* Includes a daily limit on variant updates
* Includes a product limit
* Supports core update and restore workflows
Standard is designed for growing stores that need more capacity and a few extra safeguards. It is a good fit if you manage a moderate catalog and want access to paid features without moving to the highest tier.
* Higher update limits than Trial
* Includes duplicate checking
* Suitable for stores that need more room to work across a larger catalog
Complete is the full plan for stores that want access to everything SKU Manager offers without plan limits getting in the way.
* Includes all available features
* No usage limits
* Best for larger stores or high-volume SKU management workflows
## Features included by plan type [#features-included-by-plan-type]
### Included on free plans [#included-on-free-plans]
These core tools are available without upgrading:
* **Conditional updating** so you can make changes only when specific conditions are met
* **Restoring** so you can roll back previous changes when needed
### Included on paid plans [#included-on-paid-plans]
Paid plans add features that help you work faster and reduce manual checking:
* **Duplicate checking** to help spot repeated SKU values before they cause problems
* **Automatic SKU generation** to create SKUs more efficiently across your catalog
### Additional paid plan benefits [#additional-paid-plan-benefits]
Paid plans also include more flexibility when working with restore points:
* More restore point slots
* Longer restore point expiry
Restore points are useful when you want extra confidence before making bulk SKU changes, especially on larger catalogs.
## How to choose the right plan [#how-to-choose-the-right-plan]
If you are just getting started or working with a smaller catalog, Trial may be enough. If you need higher limits and duplicate checking, Standard is a practical step up. If you manage a large store or rely on SKU updates as part of an ongoing workflow, Complete gives you the most flexibility.
Choose your plan based on your store size, how often you update SKUs, and whether you need advanced tools like duplicate checking or automatic SKU generation.
## Features Referenced [#features-referenced]
* [Duplicate checking](/docs/managing-skus/duplicate-checking)
* [Restoring](/docs/managing-skus/undoing-changes)
* [Automating](/docs/managing-skus/automatically-generate-skus)
* [Conditional](/docs/editing-skus/conditional-mode)
# Combo modes (/docs/editing-skus/combo-modes)
Combo modes control how each part of a SKU is generated. You apply a mode to each combo box to decide whether that box stays fixed, counts upward, or changes based on rules.
Separators are not combo boxes. They behave like fixed text placed between combo boxes, such as a dash. You cannot assign a combo mode to a separator.
## Video Overview [#video-overview]
## Assign or change a combo mode [#assign-or-change-a-combo-mode]
To set or change the mode for a combo box:
### Select a combo box [#select-a-combo-box]
Click the combo box you want to edit in your SKU pattern.
### Choose a mode [#choose-a-mode]
The available mode options appear above the combo box. Select the mode you want to use for that box.
### Enter the box value if needed [#enter-the-box-value-if-needed]
Enter a value in the selected combo box.
Clicking the X button removes the combo box.
## Available combo modes [#available-combo-modes]
**Increment** increases the number in that combo box by 1 for every SKU generated.
Use this when you want one continuous number sequence across all generated SKUs.
This is a good choice when you want every SKU to have a unique running number, regardless of product or variant.
**Static** keeps the same text or number in that combo box for every SKU.
Use this for values that should never change, such as a brand code, product line code, or fixed separator-like text inside a box.
**Increment by product** increases the number once per product, not once per variant.
That means all variants of the same product share the same value in that combo box, and the number changes only when SKU Manager moves to the next product.
For example, if one product has six variants, all six variants can use the same product-level number. The next product then gets the next number in the sequence.
**Increment by variant** increases the number for each variant within a product, then starts over for the next product.
That means variants under the same product get their own sequence, such as 1, 2, 3, 4. When SKU Manager moves to a new product, the sequence resets and begins again.
This is useful when you want each product to have its own internal variant numbering instead of one product-level number.
**Conditional** lets you output different values based on rules you define.
Use it when a combo box should change depending on product data, such as variant title, product type, option value, vendor, or another condition in your setup.
For a full walkthrough, see [Conditional mode](/docs/editing-skus/conditional-mode).
## Increment by product vs. increment by variant [#increment-by-product-vs-increment-by-variant]
* **Increment by product:** one number per product; all of that product's variants share it.
* **Increment by variant:** one number per variant; the sequence restarts for each product.
Choose **Increment by product** when the number should identify the product as a whole. Choose **Increment by variant** when the number should distinguish variants within each product.
# Conditional mode (/docs/editing-skus/conditional-mode)
Conditional mode lets you generate part of a SKU based on product information. Instead of assigning the same value to every item, you can create rules such as: if the variant title includes `Red`, output `R`. This is useful when your products follow naming patterns and you want SKU values to update consistently.
## Video Overview [#video-overview]
## When to use Conditional mode [#when-to-use-conditional-mode]
Use Conditional mode when the value you want to add to a SKU depends on product data.
* Use short codes for colors, sizes, or styles based on the variant title.
* Assign different SKU values for different vendors, collections, or product types.
* Handle products that use different naming patterns without building separate templates.
* Create one rule set that works across many products by matching against the information already in Shopify.
Conditional mode works best when you can clearly describe the pattern you want to match. If your products use consistent naming, you can usually build reliable rules quickly.
## How a rule works [#how-a-rule-works]
Each rule follows a simple if/then structure:
`If [product field] includes [value], then output [SKU value]`
For example:
* If **Variant title** includes `Red`, then output `R`
* If **Product type** includes `Hoodie`, then output `HD`
* If **Vendor** includes `Acme`, then output `ACM`
In each rule, you choose:
* **What to check**: the product field, such as variant title or tags
* **What to look for**: the word, phrase, or values that should trigger the rule
* **What to return**: the value that should be added to the SKU when the rule matches
### Using multiple include values in one rule [#using-multiple-include-values-in-one-rule]
A single rule can match more than one value. This is helpful when different products use different naming conventions for the same meaning.
For example, if some products use `S` and others use `Small`, you can include both values in the same rule and return one output such as `SMALL`.
Use multiple include values when the outcome should be the same. This helps you keep your rule list shorter and easier to manage.
## What you can match against [#what-you-can-match-against]
Conditional mode can check these product fields:
* **Variant title**
* **Product title**
* **Option title**
* **Collection**
* **Vendor**
* **Product type**
* **Tags**
* **Product last updated at**
Choose the field that most reliably contains the information you want to use. For example, colors and sizes are often easiest to detect from the variant title, while brand-specific values may be better matched from the vendor field.
## Rule order matters [#rule-order-matters]
Conditional rules are checked from top to bottom. As soon as one rule matches, SKU Manager uses that result and stops checking the rules below it.
This means the **first matching rule wins**.
For example:
* Rule 1: If variant title includes `Blue`, output `BLU`
* Rule 2: If variant title includes `Dark-Blue`, output `DRK-BLU`
If the `Blue` rule appears first, a variant named `Dark-Blue` will match that broader rule before SKU Manager ever reaches the more specific one.
Place more specific rules above broader rules. Otherwise, broad matches can prevent the correct value from being applied.
If you need to change the order, drag a condition row using the handle on the left side of the row and move it above or below another rule.
## Practical tips [#practical-tips]
* **Start with your most specific matches.** Put exact or narrow matches above more general ones.
* **Group similar variations into one rule.** If `Small`, `S`, and `Sml` should all return the same output, combine them instead of creating separate rules.
* **Choose the most reliable field.** Match against the field that stays consistent across your catalog.
* **Review overlapping words.** Terms like `Blue` and `Dark-Blue` can conflict if the broader term appears first.
* **Keep outputs consistent.** Decide on a standard format for abbreviations, such as `BLU`, `RED`, or `SMALL`, and use it across all rules.
If a rule is not giving the result you expect, check whether a broader rule above it is matching first. Reordering the rules often fixes the issue.
# Creating and updating SKUs (/docs/editing-skus/creating-and-updating-skus)
## What this page covers [#what-this-page-covers]
Use SKU Manager to create or update a SKU format by combining simple parts into one SKU value.
## Simple SKU example [#simple-sku-example]
A common SKU structure combines a color code, a size code, and a running number.
R-S-1000
R-M-1001
R-S-1002
B-M-1003
In this example:
* **R** or **B** is the color code
* **S** or **M** is the size code
* **1000**, **1001**, **1002**, and so on are the number sequence.
In SKU Manager, to achieve this you would use two different conditionals and a increment to ensure the generated SKUs are unique and don't create duplicates.
## Learn more [#learn-more]
Building blocks for putting together a SKU
Map product or variant details to short SKU codes.
# Editing SKUs overview (/docs/editing-skus/editing-skus-overview)
Use the Update workflow when you want to create new SKU values or replace existing SKUs with a structured format.
SKU Manager builds each SKU from smaller parts, such as fixed text, product or variant details, condition-based codes, and incrementing numbers.
If you only want to clean up existing SKUs, such as changing letter case or replacing text, use Format existing SKUs instead.
## How SKU values are built [#how-sku-values-are-built]
SKU Manager builds SKUs using combo boxes. Each combo box contributes one part of the final SKU.
For example, a SKU might include:
* A color code
* A size code
* A running number
Together, those parts can create SKU values like:
R-S-1000
R-M-1001
B-S-1002
B-M-1003
In this example:
* **R** or **B** could be a color code.
* **S** or **M** could be a size code.
* **1000**, **1001**, and later values are part of a number sequence.
## How you would build this example [#how-you-would-build-this-example]
To build a SKU like **R-S-1000**, you would usually use:
* A conditional combo box for the color code, such as returning **R** when the variant is red.
* A conditional combo box for the size code, such as returning **S** when the variant is small.
* An increment combo box for the running number.
* Separators, such as dashes, between the parts.
For more details about each type of combo box, see [Combo modes](/docs/editing-skus/combo-modes).
## Recommended workflow [#recommended-workflow]
### Choose the products or variants [#choose-the-products-or-variants]
Select the products or variants you want to update.
### Build your SKU pattern [#build-your-sku-pattern]
Add combo boxes for each part of the SKU, then choose the right
mode
for each box.
### Add separators if needed [#add-separators-if-needed]
Use
separators
such as dashes or slashes between SKU parts. Separators are useful when you want readable SKUs like
R-S-1000
.
### Check the preview [#check-the-preview]
Review the
preview
before applying changes. This helps you catch spacing, separator, numbering, or rule issues early.
### Apply the update [#apply-the-update]
Once the preview looks correct, apply the update to save the new SKU values in Shopify.
## Before applying changes [#before-applying-changes]
* Check that the preview matches the SKU format you expect.
* Review your selected products or variants.
* Check for possible duplicate SKUs.
* Make sure conditional rules are returning the right values.
* Use a small batch first if you are unsure about the setup.
Updating SKUs changes the SKU values in Shopify. Review the preview carefully before applying changes.
# SKU examples (/docs/editing-skus/examples)
## What Examples are for [#what-examples-are-for]
The **Examples** feature gives you a quick way to explore common SKU structures inside SKU Manager. It is designed to help you get started faster and understand how different SKU patterns can be built before you create your own setup.
Examples are especially useful if you are still learning how SKU parts fit together or if you want a simple starting point for a new format.
Examples are meant to help merchants learn common SKU patterns and get started quickly. You can use them as a reference, a starting template, or a way to better understand SKU Manager.
## Where to find Examples [#where-to-find-examples]
You can open **Examples** from the **Update Mode** page.
Open the Examples panel any time you want to review common patterns or replace your current setup with a ready-made example.
## How the Examples panel works [#how-the-examples-panel-works]
When you open the Examples panel, it is split into two main areas:
* **Left side:** a list of selectable example patterns
* **Right side:** a preview showing how the selected pattern would be generated in SKU Manager
Above the preview, you will also see the **combo arrangement** used for that example. This helps you understand how the SKU parts are organized to create the final result.
As you click different example patterns, the preview updates so you can compare formats and see which structure best matches the way you want your SKUs to look.
Use the preview to understand the logic behind a pattern before applying it. This makes it easier to choose a format that matches your products and naming style.
## What happens when you apply an example [#what-happens-when-you-apply-an-example]
When you click **Apply**, SKU Manager replaces your current combo boxes with the selected example.
This means the example becomes your new working setup on the Update page. From there, you can keep it as is or continue editing it to match your store's exact SKU format.
Applying an example updates the combo boxes you are currently working with.
# Format existing SKUs (/docs/editing-skus/formatting-existing-skus)
## Format SKUs in bulk [#format-skus-in-bulk]
The formatting tool lets you update existing SKUs. You can convert SKUs to **uppercase** or **lowercase**, and you can also **replace text within SKUs** to standardize naming across your catalog.
You can combine **one case option** with **multiple replace changes** before applying the update.
## Video Overview [#video-overview]
## What you can do [#what-you-can-do]
* **Convert to uppercase**: change all letters to capital letters.
* **Convert to lowercase**: change all letters to lowercase letters.
* **Replace text**: swap one part for another, such as changing `Shirt` to `Tee`.
Text replacement is case-sensitive. For example, replacing shirt will not replace Shirt unless the capitalization matches exactly.
## How to format existing SKUs [#how-to-format-existing-skus]
### Choose a case option [#choose-a-case-option]
Under
Case
, select either
Upper
or
Lower
if you want to change the letter casing of your SKUs. You can leave this unset if you only want to replace text.
### Add one or more replace changes [#add-one-or-more-replace-changes]
In the
Replace
section, enter the text you want to find and the text you want to use instead, then select
Add change
. Repeat this for each replacement you want to include.
### Review the change chips [#review-the-change-chips]
Check the
Changes
area to confirm every update before applying it. This list shows your selected case option and each replace change that will be included in the bulk update.
### Apply and save [#apply-and-save]
Once the changes look correct, apply the update to save the new SKU formatting.
Review your change chips carefully before saving, especially when using multiple replacements together with a case change.
## Undo a mistake [#undo-a-mistake]
If you apply the wrong formatting, you can recover your previous SKUs from **History** by restoring a restore point.
See here for [Undoing SKU changes](/docs/managing-skus/undoing-changes).
If needed, use History to roll back the bulk update and return your SKUs to their earlier values.
# Toolbox on the Update page (/docs/editing-skus/toolbox)
## What the Toolbox is [#what-the-toolbox-is]
The **Toolbox** gives you extra controls while building a SKU pattern on the Update page. It helps you shape the final result more precisely by letting you add separators, save useful setups as presets.
The Toolbox is designed for pattern building on the Update page. It works alongside your combo boxes so you can fine-tune how the final SKU or barcode is assembled.
## Where to find it [#where-to-find-it]
Within the [Update page](/docs/editing-skus/update-page-guide), on the bottom row, click on the three dots ("**...**") button. That will open the Toolbox.
You can continue adjusting your combo boxes and use Toolbox options as needed.
## What you can do with the Toolbox [#what-you-can-do-with-the-toolbox]
### Separators [#separators]
Use **Separators** when you want visible characters between parts of your SKU or barcode pattern, such as dashes, slashes, or short text markers.
* Enable separators in the Toolbox first.
* Once enabled, small input boxes appear **between the combo boxes**.
* Enter the separator you want in those boxes.
* Each separator can be up to **3 characters**.
This is useful when you want a format like `AAAA-BBBB-CCCC` instead of having all values run together.
### Presets [#presets]
Use **Presets** to save a combo box setup that you expect to use again. A preset helps you avoid rebuilding the same pattern every time.
Presets are especially useful if products are regularly added to your store.
For each preset you can:
* Rename it
* Update its combo box configuration
* Remove it
* Apply it
### Override [#override]
SKU Manager prevents updating with some combo box configurations, as duplicates will likely be created after generating SKUs. Use this if you want to bypass this.
# Update page guide (/docs/editing-skus/update-page-guide)
## Overview [#overview]
The **Update** page is where you build and preview SKU or barcode changes before applying them to your selected products. On this page, **Update mode** is the default view. If you want to switch to formatting existing values instead, use [Format mode](/docs/editing-skus/formatting-existing-skus).
The page is divided into three main areas, matching the visual layout you see on screen:
* **Top preview area:** shows how your setup will look on sample products.
* **Middle combo box area:** where you build the parts of the final SKU or barcode.
* **Bottom update settings area:** where you choose SKU or barcode options, mode settings, examples, presets, and toolbox controls.
## Video Overview [#video-overview]
## Top: Previewer [#top-previewer]
The top area shows a preview of your current setup. It helps you confirm that your combo boxes are in the right order and producing the result you expect before you apply changes.
Incremented values may differ slightly from the actual output because the preview is generated using a randomly selected product.
### What the preview shows [#what-the-preview-shows]
* **Sample products from your selection:** the preview is based on sampled products, not every product in your batch.
* **Up to 3 products side by side:** you can compare how the same setup behaves across multiple products at once.
* **Highlighted output:** when you click a combo box, the matching section in the preview is highlighted so you can see exactly what that box contributes.
* **Filler rows:** the preview can show filler rows when needed, up to **15** rows. Useful if there aren't many variants on displaying product.
Use the preview to check spacing, separators, numbering, and box order before running your update. It is the fastest way to catch small formatting issues early.
## Middle: Combo boxes [#middle-combo-boxes]
The middle area is where you build the final SKU or barcode. Each combo box adds one part of the finished value, such as a product attribute, a fixed text value, or an incrementing number.
You can use up to **7 combo boxes** on the page.
### Rearrange combo boxes [#rearrange-combo-boxes]
Use the button on the far left of the combo box row to enter rearranging mode. This lets you change the order of the boxes so your final SKU or barcode is built in the sequence you want.
### Add combo boxes [#add-combo-boxes]
Use the **+** button on the right side of the row to add another combo box. You can keep adding boxes until you reach the 7-box limit.
### Choose a combo mode [#choose-a-combo-mode]
Select a combo box to open its available modes above the row. These modes control what that box contributes to the final SKU or barcode.
For a full explanation of each mode, see [Combo modes](/docs/editing-skus/combo-modes).
### Use separators without spending a combo box [#use-separators-without-spending-a-combo-box]
If you only need a separator such as `-` or `/`, you do not need to use a full combo box for it.
* Enable [separator boxes in the toolbox](/docs/editing-skus/toolbox#separators).
* Enter the separator in the small input boxes between combo boxes.
* Use this to save your combo boxes for values that change.
Separators can be **any string up to 3 characters long**.
Separator boxes are enabled in the toolbox and then entered in the small input boxes between your combo boxes.
## Bottom: Settings and tools [#bottom-settings-and-tools]
The bottom area contains the settings and tools that control what you are updating and how the update behaves.
### Choose what to update [#choose-what-to-update]
Use the selector to choose whether you want to update **SKU** values or **Barcode** values.
### Mode options [#mode-options]
* **Update mode:** the default mode on this page, used to build new values from your selected boxes and settings.
* **Format mode:** use [Format mode](/docs/editing-skus/formatting-existing-skus) if you want to reformat existing SKUs instead of building updated values on this page.
### Examples, and Toolbox [#examples-and-toolbox]
* [Examples](/docs/editing-skus/examples)**:** review sample outcomes while building your setup.
* [Toolbox](/docs/editing-skus/toolbox)**:** enable additional helpers such as separator boxes and presets.
If you use the same box layout regularly, save it as a preset so you can apply the same structure again without rebuilding it from scratch.
[Presets](/docs/editing-skus/toolbox#presets) can be **reused**, which is especially helpful when products are regularly added to your store.
## Recommended workflow [#recommended-workflow]
### Choose SKU or Barcode [#choose-sku-or-barcode]
In the bottom update settings area, decide whether you are updating SKU values or barcode values.
### Build your combo [#build-your-combo]
Add up to 7 combo boxes, choose the right mode for each one, and arrange them in the order you want. Utilise Separators if needed.
### Check the Previewer [#check-the-previewer]
Review the live preview, compare up to 3 products side by side, and confirm highlighted output for each box.
### Save as a preset if useful [#save-as-a-preset-if-useful]
If this setup is something you will use again, save it so you can reuse it later.
# Can SKU Manager edit variants? (/docs/faq/can-sku-manager-edit-variants)
## Short answer [#short-answer]
Yes, but only for SKU and barcode fields.
SKU Manager can update the **SKU** and **barcode** on your product variants. It does **not** edit other variant details such as option values, pricing, titles, or inventory settings.
If you need to change broader variant details, make those updates in Shopify or with another app built for product editing.
## What SKU Manager can change [#what-sku-manager-can-change]
* Variant SKU
* Variant barcode
## What SKU Manager does not change [#what-sku-manager-does-not-change]
* Variant titles
* Option names or option values
* Prices or compare-at prices
* Inventory quantities or inventory tracking settings
* Other product or variant configuration details
This keeps SKU Manager focused on fast, reliable SKU and barcode updates without affecting the rest of your product setup.
If adding support for more variant fields would be helpful, send me a message through the in-app chat. I’m always happy to hear feedback.
# Does SKU Manager change inventory? (/docs/faq/does-sku-manager-change-inventory)
## Does SKU Manager change inventory? [#does-sku-manager-change-inventory]
No, SKU Manager does not change your inventory.
SKU Manager only updates the **SKU** and **barcode** fields on your product variants. It does **not** change inventory quantities, and it does **not** turn inventory tracking on or off.
Your stock counts stay the same, and your inventory tracking settings remain exactly as they are.
If you use SKU Manager to update variant SKUs or barcodes, your inventory levels and tracking setup will not be affected.
# Does SKU Manager create products? (/docs/faq/does-sku-manager-create-products)
## Short answer [#short-answer]
No, SKU Manager does not create products.
It only updates the **SKU** and **barcode** fields on your existing product variants.
SKU Manager does not create products, duplicate products, or add new items to your catalog.
## What SKU Manager can change [#what-sku-manager-can-change]
* SKU values on existing variants
* Barcode values on existing variants
## What SKU Manager will not do [#what-sku-manager-will-not-do]
* Create new products
* Duplicate existing products
* Add new catalog items
* Create new variants
This means you can use SKU Manager to update identifying codes on products you already have, without worrying about extra products appearing in your store.
# SKU changes not showing in Shopify (/docs/faq/sku-change-did-not-appear-in-shopify)
If a SKU change did not appear in Shopify, the cause usually falls into one of three cases: only some variants updated, only duplicate variants updated, or none of the variants updated. Use the sections below to identify what happened and fix it quickly.
If you recently added products or deleted variants in Shopify, SKU Manager may need a fresh product sync before it can apply updates correctly.
## Only some variants updated [#only-some-variants-updated]
If only some variants on a product were updated, the product was likely added to Shopify recently and SKU Manager does not yet have the latest product data.
When this happens, SKU Manager may update the variants it already knows about, but miss newer variants until you resync your products.
### What to do [#what-to-do]
### Resync your products [#resync-your-products]
Run a product sync in SKU Manager so the app pulls the latest product and variant data from Shopify.
### Run the SKU update again [#run-the-sku-update-again]
After the sync finishes, repeat the SKU change for the affected product.
### Confirm the result in Shopify [#confirm-the-result-in-shopify]
Check the product in Shopify to make sure all expected variants now show the new SKU values.
If the product was created or updated very recently, wait for the sync to finish completely before retrying the change.
## Only duplicate variants updated [#only-duplicate-variants-updated]
If this happened after running a duplicate check, the `[Only update duplicates](/docs/managing-skus/duplicate-checking#updating-duplicate-values)` option was likely enabled.
When that option is turned on, SKU Manager updates only the variants that currently have a conflicting or duplicate SKU. Variants without a duplicate are left unchanged.
### What to do [#what-to-do-1]
### Review how the update was started [#review-how-the-update-was-started]
If you launched the change from a duplicate check, confirm whether
Only update duplicates
was selected.
### Run the update again without that option [#run-the-update-again-without-that-option]
If you want every matching variant to be updated, repeat the SKU update and leave
Only update duplicates
unchecked.
### Verify all variants [#verify-all-variants]
After the update completes, review the product in Shopify and confirm that all intended variants were updated, not just the duplicates.
If you use Only update duplicates, SKU Manager will intentionally skip any variant that does not have a duplicate SKU conflict.
## None of the variants updated [#none-of-the-variants-updated]
If none of the variants were updated, a recently deleted variant may have blocked the update.
This usually happens when SKU Manager is working from older product data and one of the variants it expects to update no longer exists in Shopify. In this case, the app typically shows a warning after the update finishes telling you that some products could not be updated and need to be resynced.
### What to do [#what-to-do-2]
### Check for the warning message [#check-for-the-warning-message]
Look for the warning shown after the update. It will usually list the products that were not updated because of deleted variants.
### Resync your products [#resync-your-products-1]
Run a product sync in SKU Manager to refresh the product and variant data from Shopify.
### Retry the SKU change [#retry-the-sku-change]
After the sync is complete, run the SKU update again for the affected products.
### Confirm the update in Shopify [#confirm-the-update-in-shopify]
Open the products in Shopify and verify that the SKU changes now appear.
If SKU Manager tells you to resync products, complete the resync before retrying the update. Retrying first usually leads to the same result.
## Next steps [#next-steps]
* If only some variants updated, [resync](/docs/managing-skus/resyncing) products and try again.
* If only duplicates updated, rerun the update without **[Only update duplicates](/docs/managing-skus/duplicate-checking#updating-duplicate-values)** selected.
* If none of the variants updated, look for the warning, resync products, and retry the update.
In most cases, a fresh product sync resolves the issue and allows the SKU change to apply normally.
# Why products are missing (/docs/faq/why-are-some-products-missing)
## Short answer [#short-answer]
If some products are missing in SKU Manager, the most common reason is that the app has not synced your latest product changes yet. In most cases, you can fix this by running a [resync](/docs/managing-skus/resyncing) from the **Update** page.
If you are on the **Trial** plan, SKU Manager only syncs up to **1,000 products**. Those are the products that were updated most recently in your store.
If you recently upgraded from the Trial plan, SKU Manager should start a full automatic resync. On large stores, this can take several minutes to finish.
## Most common causes [#most-common-causes]
Newly added products, or products you edited recently, may not appear in the app until SKU Manager syncs again.
This is especially common if you added products and checked the app right away.
The Trial plan has a 1,000 product limit. SKU Manager syncs the most recently updated products from your store.
If an older product has not been updated in a while, it may fall outside that synced group and not appear in the app.
After upgrading, SKU Manager should automatically run a full resync so it can pull in all of your products.
If your store has a large catalog, that process may take a few minutes before everything appears.
## What to do next [#what-to-do-next]
### Open the Update page [#open-the-update-page]
In SKU Manager, go to the
Update
page.
### Run a resync [#run-a-resync]
Start a product resync to pull in the latest changes from your store.
### Check whether the missing products were recently updated [#check-whether-the-missing-products-were-recently-updated]
If the products were newly created or recently edited, they should appear after the resync completes.
If only a few older products are missing on the Trial plan, updating and saving those products before resyncing is the fastest way to bring them back into the app.
## What happens after upgrading from Trial [#what-happens-after-upgrading-from-trial]
When you upgrade from the Trial plan, SKU Manager should automatically start a full resync of your store.
This means the app is no longer limited to the Trial sync range and can begin pulling in your full catalog.
If you have thousands of products, this resync may take several minutes. That is normal, and your products should continue appearing as the sync finishes.
## If products are still missing [#if-products-are-still-missing]
If you have already run a resync and waited a few minutes after upgrading, check whether the missing products were updated recently.
On the Trial plan, older products may still need a small edit and another resync before they appear.
If you are no longer on Trial and the full resync has had time to finish, the missing products should appear once syncing completes.
# Automatically generate SKUs (/docs/managing-skus/automatically-generate-skus)
## Overview [#overview]
Automatic SKU generation lets SKU Manager assign SKUs to new products and variants for you. Once it is turned on, the app watches for newly created products or newly added variants and prepares them for processing based on the rules you set.
You can keep the setup simple with one rule that applies to everything, or create multiple rules for different parts of your catalog. This is useful if different collections, product types, or vendors need different SKU formats.
Automatic generation only applies to newly created products or newly added variants. Existing variants are not updated by this feature.
## VIdeo Overview [#video-overview]
## Enable automatic SKU generation [#enable-automatic-sku-generation]
Before any rules can run, the feature must be enabled in the **Overview** tab.
### Open the Overview tab [#open-the-overview-tab]
Go to
Automate
on the side bar, and open the
Overview
tab.
### Set the status to Active [#set-the-status-to-active]
Change the feature status to
Active
. If the feature is disabled, new products and variants will not be processed automatically.
### Save and confirm your rules [#save-and-confirm-your-rules]
After the feature is active, review your rules to make sure the right products will be matched.
***
## Rules [#rules]
Rules tell SKU Manager which SKU format to use and which products or variants it should apply to.
Each rule includes:
* **A combo**, which defines how the SKU should be built
* **Filters**, which decide which products or variants the rule should match
When a new product or variant is created, SKU Manager checks your rules and uses the one that matches. This lets you use one SKU pattern for one part of your catalog and a different pattern somewhere else.
For example, you might create separate rules for apparel, accessories, and watches, each with its own SKU format.
Give each rule a clear name that describes what it is for, such as the product group it targets or the SKU format it uses. This makes it much easier to review and update rules later.
### Catch-all rules [#catch-all-rules]
A rule can target either:
* **Any product or variant**, which acts as a catch-all rule
* **Only matching products or variants**, which applies only when its filters match
You can have only **one** catch-all rule for any product or variant. SKU Manager uses it as a fallback when none of your more specific rules apply.
If you use multiple rules, make sure your most specific rules are set up correctly. The catch-all rule should be treated as your last-resort rule, not your main targeting method.
### Filters and targeting [#filters-and-targeting]
Filters help you control which products or variants each rule applies to. You can use them to target only the parts of your catalog that need a specific SKU format.
Rules can match products by:
* **Collection**
* **Product type**
* **Vendor**
You can use one filter on its own or combine all three in the same rule for more precise targeting.
#### When to use filtered rules [#when-to-use-filtered-rules]
* Use **Collection** when products are grouped into curated sets or seasonal lines
* Use **Product type** when similar product categories should share one SKU pattern
* Use **Vendor** when supplier-based products need their own format
If a product or variant does not match a filtered rule, SKU Manager moves on to check the next applicable rule. If nothing matches and you have a catch-all rule, the catch-all rule is used.
Your rule's combo is created using the same combo-building workflow used elsewhere in SKU Manager. Before saving a rule, confirm that the combo and filters show no issues.
***
## Queued [#queued]
When a new product is created or a new variant is added, SKU Manager adds it to the **Queued** tab. This queue is the list of items waiting to be processed by your automatic rules.
Queued items are not always updated instantly. Processing happens on a schedule, typically processed every 20 minutes.
Only **100** products can be queued at any given time. This limit depends on your plan.
### What you can do in the queue [#what-you-can-do-in-the-queue]
* **Review waiting items** before they are processed
* **Select one or more items** to act on them in bulk
* **Use Update now** to process selected items sooner instead of waiting for the next scheduled run
* **Use Forget** to remove selected items from the queue without processing them
If you have just added new products and want their SKUs assigned right away, use Update now on the queued items you want to process immediately.
Using Forget removes items from the queue. If you do not want an item to be skipped, do not remove it.
### How are products queued [#how-are-products-queued]
* When a product is created or duplicated.
* When a variant is created.
***
## History [#history]
After a queued item is processed, it appears in the **History** tab. History gives you a record of what was updated and which rule was used.
For each processed item, you can review details such as:
* **The product title**
* **The number of variants updated**
* **The rule used**
* **The date updated**
This is the best place to confirm that your automation is working as expected. If an item was updated with the wrong SKU format, check the rule listed in History and then review that rule's filters and combo.
History is especially helpful when you use multiple rules, because it shows exactly which rule handled each processed product or variant.
***
## Recommended setup [#recommended-setup]
### Turn the feature on [#turn-the-feature-on]
Set automatic SKU generation to
Active
in the
Overview
tab.
### Create your specific rules first [#create-your-specific-rules-first]
Add rules for the collections, product types, or vendors that need custom SKU formats.
### Add one catch-all rule if needed [#add-one-catch-all-rule-if-needed]
Create a single
Any product or variant
rule to handle anything that does not match your specific rules.
### Monitor the queue [#monitor-the-queue]
Check the
Queued
tab after adding products or variants, especially during initial setup.
### Verify results in History [#verify-results-in-history]
Use the
History
tab to confirm that the correct rules were applied.
## Best practices [#best-practices]
* Name rules clearly so they are easy to identify later
* Use filtered rules for product groups that need different SKU formats
* Check History after making rule changes to confirm the right rule is being applied
# Duplicate checking (/docs/managing-skus/duplicate-checking)
## Overview [#overview]
Duplicate SKUs and duplicate barcodes can easily cause problems later when working with other systems. The duplicate check in SKU Manager scans your store for these conflicts so you can find them quickly and fix them from one place.
The check can find both duplicate values and blank SKUs, so it is also useful for spotting missing SKU data.
Duplicate checking is a review tool. It does not change anything in your store until you choose to update the results.
## Video Overview [#video-overview]
## Before you run a check [#before-you-run-a-check]
Before starting, make sure SKU Manager has current product data.
* If your app data may be out of date, click **Re-sync products** first.
* Wait for the sync to finish before running the duplicate check.
* Remember that blank SKUs can be included in the results, not just repeated SKU values.
If you recently added products, edited variants, or imported catalog changes in Shopify, re-syncing first helps make sure your duplicate check reflects the latest store data.
## How to run a duplicate check [#how-to-run-a-duplicate-check]
### Open Duplicate check [#open-duplicate-check]
In the SKU Manager sidebar, open
Duplicate check
.
If needed, click
Re-sync products
to refresh the app's product data before checking.
### Start the check [#start-the-check]
Click
Check
to scan your store for duplicate SKUs, duplicate barcodes, and blank SKUs.
### Wait for results [#wait-for-results]
When the check finishes, the results panel updates with a summary and a list of affected products and variants.
## Understanding results [#understanding-results]
After the scan finishes, SKU Manager shows a results summary along with the products affected by duplicates or blanks.
The summary can include:
* **Duplicates found**: how many duplicate values were detected
* **Blanks found**: how many blank SKU entries were detected
* **Affected products**: how many products contain affected variants
* **Checked**: when the duplicate check was run
Below the summary, you can review the affected products and variants.
* Use the **SKU** and **Barcode** tabs to switch between duplicate SKU results and duplicate barcode results.
* Each product section shows the variants that need attention.
Switching between the SKU and Barcode tabs only changes what you are viewing. It does not change any data by itself.
## Updating duplicate values [#updating-duplicate-values]
When you are ready to fix the results, click **Update SKUs**. This takes you into the normal update workflow, where you can choose how the affected values should be changed.
During update mode:
* You can work through the same update process you normally use in SKU Manager.
* If you need to correct both duplicate SKUs and duplicate barcodes, you can enable both during the update flow where available.
* In the final confirmation step, you can turn on **Only update duplicates**.
When Only update duplicates is selected, SKU Manager updates only the variants that were identified as duplicates. Other variants in the same product are left unchanged.
If you need to reverse an update later, see [Undoing changes](/docs/managing-skus/undoing-changes).
## What happens after updating [#what-happens-after-updating]
After your update finishes, the duplicate check results stay visible on the page. They are not cleared automatically.
This is useful if you want to review what was found, but it also means the displayed results may no longer reflect the latest state of your store after the update.
To refresh the page with current results, click **Check** again and run a new duplicate check.
After making changes, run the duplicate check again to confirm that the duplicate SKUs or barcodes were resolved.
# Resyncing products (/docs/managing-skus/resyncing)
## Overview [#overview]
Resyncing refreshes the product information SKU Manager uses so it matches the latest data in your store. This is helpful when you have made product changes outside of SKU Manager and want the app to work with the most up-to-date details.
A resync does not change your products by itself. It updates the product data SKU Manager reads, such as the information used in product lists, filters, and conditionals.
## When to resync [#when-to-resync]
It is a good idea to resync after making a large number of product changes outside of SKU Manager.
* You updated product details directly in your store admin
* You imported products or made bulk edits in another app
* You changed product organization fields like collections or vendor
* You notice SKU Manager is not showing the latest product information
* An update was blocked because product data changed, such as after variants were deleted
If you have made only a small change to one or two products, you may not need to resync right away. Resyncing is most useful after broader changes that affect many products or the data your rules depend on.
## How to resync [#how-to-resync]
### Open the Update page [#open-the-update-page]
In SKU Manager, go to
Update
from the sidebar.
### Start the resync [#start-the-resync]
Click
Resync products
in the top-right corner.
### Wait for the refresh to finish [#wait-for-the-refresh-to-finish]
SKU Manager will pull the latest product information from your store and refresh the data it uses.
Once the resync is complete, SKU Manager will use the newly refreshed product data across the app.
## Trial plan note [#trial-plan-note]
On the Trial plan, SKU Manager pulls the first 1,000 most recently updated products during a resync.
If your store has more than 1,000 products, this means the resync on Trial may not include every product in the catalog.
## Using resync with Conditional rules [#using-resync-with-conditional-rules]
If you use **Conditional** rules, resyncing is especially important after changing the product fields those rules rely on.
For example, you should resync after updating fields like:
* **Collections**
* **Vendor**
* **Product type**
* Any other product field used in your Conditional setup
If a Conditional depends on product data that has changed, SKU Manager may continue using older information until you resync.
## What to expect [#what-to-expect]
Resyncing can take a little time, especially in larger stores.
* Small catalogs may finish quickly
* Large catalogs with thousands of products may take several minutes
* During this time, SKU Manager is refreshing the product information it has on file
If your store has a large number of products, allow a few minutes for the resync to complete before checking results or running another update.
If you recently made product changes and SKU Manager still does not reflect them, run a resync first before troubleshooting further.
## When resyncing fixes update issues [#when-resyncing-fixes-update-issues]
Resyncing is often the right fix when SKU Manager warns that a product could not be updated because the app is working from outdated product data.
This is especially common if variants were deleted in your store after SKU Manager last refreshed the product.
If you see a warning like this, resync products first, then run the update again.
# Undoing SKU changes (/docs/managing-skus/undoing-changes)
If you need to reverse a recent SKU or barcode update, use **Restore** in the sidebar. The Restore page shows your recent change history, lets you preview what changed, and gives you a way to roll back those SKU-related updates when needed.
## Video Overview [#video-overview]
## How restore points work [#how-restore-points-work]
SKU Manager automatically creates a **restore point** whenever it makes a change to SKUs or barcodes. Each restore point captures the values before and after that update, so you can review the change later and restore the earlier values if needed.
On the Restore page, each row represents one past update. You can open a row to see the affected products and variants, along with a before-and-after view of the SKU or barcode values that changed.
Restore points are created automatically as part of normal updates. You do not need to create them manually before running a change.
## How to restore a previous change [#how-to-restore-a-previous-change]
### Open Restore [#open-restore]
In the sidebar, go to
Restore
to view your recent update history.
### Find the update you want to undo [#find-the-update-you-want-to-undo]
Review the list and identify the restore point for the change you want to reverse. Check the date, origin, and updated field to confirm you have the right one.
### Preview the changes [#preview-the-changes]
Use
View
to expand the restore point and inspect the products, variants, and before-and-after values.
### Restore the previous values [#restore-the-previous-values]
Select
Restore
on that row to revert the SKU or barcode values from that restore point.
Restoring applies the earlier SKU or barcode values from that restore point. Review the preview carefully before restoring, especially if more changes have been made since then.
## What each column means [#what-each-column-means]
* **View**: Opens a detailed preview of the products and variants included in that update, showing the before-and-after SKU or barcode values.
* **Restore**: Reverts the SKU or barcode changes from that restore point.
* **Products**: The number of products included in the update.
* **Variants**: The number of variants affected by the update.
* **Combo**: Shows the combo used when the update was run in Update mode.
* **Origin**: Shows where the update came from, such as the tool or workflow that created it.
* **Updated**: Shows which field was changed, such as **SKUs** or **Barcodes**.
* **Date**: The date the restore point was created.
* **Expires**: The date when the restore point will no longer be available.
* **Saved**: Indicates whether the restore point has been saved so it is not replaced by newer restore points.
* **Delete**: Removes the restore point from the list.
## What restoring does and does not change [#what-restoring-does-and-does-not-change]
Restoring only affects the SKU or barcode values stored in that restore point. It does **not** roll back other product changes made in Shopify or elsewhere.
### What restoring changes [#what-restoring-changes]
* Reverts SKU values from that restore point.
* Reverts barcode values from that restore point, if barcodes were part of the update.
### What restoring does not change [#what-restoring-does-not-change]
* Product titles
* Images
* Prices
* Any other product details outside the SKU or barcode values captured in that restore point
* New variants added after the restore point was created
* Variant order or orientation
If a variant from the original restore point has since been deleted, restoring will not recreate that variant. SKU Manager also will not move that old SKU onto a different variant as a replacement.
In practice, restoring only rolls back the SKU or barcode values for matching variants that still exist.
## Saved restore points and expiry [#saved-restore-points-and-expiry]
You can save a restore point to protect it from being replaced by newer restore points. This is useful when you want to keep an important rollback point available while you continue making changes.
However, **saved restore points still expire**. Saving prevents them from being overwritten by newer restore points, but it does not make them permanent.
When a new restore point is created, SKU Manager removes the **oldest unsaved** restore point to make room. Saved restore points are skipped during that replacement process, but once their expiry date passes, they are removed like any other restore point.
If you may need to roll back a major update later, save the restore point soon after the update finishes so it is less likely to be replaced by newer activity.
## About the Override restore points option [#about-the-override-restore-points-option]
When you confirm an update, you may see an **Override restore points** option. This is relevant if you are managing how restore points are kept during new updates.
In general, leave this setting unchanged unless you specifically want the new update to replace existing restore point coverage. If keeping rollback history is important, review this setting carefully before confirming the update.
If you rely on restore points as a safety net, it is a good idea to check the confirmation step before running large SKU updates.
# View and search products (/docs/managing-skus/view-and-search-products)
Before you update SKUs, start by finding the products you want to work with. SKU Manager lets you browse your product list, search for matching items, and apply filters to narrow down large catalogs quickly.
You can use this page to select a few products or prepare to update products across your store. Filters make it easier to focus on the exact products that need changes.
## How product selection works [#how-product-selection-works]
SKU Manager uses **product-level selection**. This means you select whole products from the product list, not individual variants inside a product.
* Select one or more products when you want to update a specific group.
* Leave the list unfiltered or broaden your filters when you want to work with a larger set of products.
* Any SKU update applies to **all variants** within each selected product.
You cannot select only certain variants from a product on this screen. If you select a product, every variant in that product is included in the update.
## Default product list view [#default-product-list-view]
When you first open the product selection screen, you will see the default product list view with no filters selected. This gives you a starting point for browsing your catalog before narrowing the results.
## Using filters to find products [#using-filters-to-find-products]
Filters help you narrow the product list so you can find the right items faster, especially if you have a large catalog. You can use one filter or combine several to create a more targeted list.
SKU Manager supports filters for:
* **Product status**
* **Collections**
* **Product type**
* **Vendors**
* **Stock status**, such as in stock or out of stock
* **SKU status**, such as products with a SKU or without a SKU
* **Barcode status**, such as products with a barcode or without a barcode
* **Tags**
* **Product title**
* **Variant labels**
* **Option names**, such as **Size** or **Color**
Combine filters to narrow results more precisely. For example, you can filter by vendor, stock status, and products without SKUs to find exactly what needs attention.
## Filtered view example [#filtered-view-example]
After filters are applied, the product list updates to show only the products that match your criteria. This helps you confirm that you are about to update the right group of products before moving to the next step.
## Typical workflow [#typical-workflow]
### Review the product list [#review-the-product-list]
Open the update page to see all available products in the default view.
### Search or apply filters [#search-or-apply-filters]
Use the available filters to narrow the list to the products you want to update.
### Select products [#select-products]
Choose the products you want to include. Remember that selection happens at the product level.
### Continue to update SKUs [#continue-to-update-skus]
Move to the next step to apply SKU updates to all variants in the selected products.
## Important to remember [#important-to-remember]
If a product has multiple variants, SKU Manager will update every variant in that product when the product is selected. It is not currently possible to update only some variants from the selection screen.
# How SKU Manager works (/docs/start-here/how-sku-manager-works-with-shopify)
SKU Manager works alongside Shopify to make SKU updates faster and easier, especially when you manage many products or variants. You use SKU Manager to review and update SKU and barcode values in bulk, while Shopify continues to manage your store's core product data.
## What SKU Manager updates [#what-sku-manager-updates]
SKU Manager is designed for one job: helping you manage variant identifiers more efficiently.
* **SKUs:** Update variant SKUs more quickly than editing them one by one in Shopify.
* **Barcodes:** Change barcode values for variants when needed.
When you save SKU or barcode changes in SKU Manager, those changes are sent to your Shopify store so your product data stays up to date.
## What stays in Shopify [#what-stays-in-shopify]
Shopify remains the main place where your store's product information is managed. SKU Manager does not replace Shopify's product admin.
* **Products and variants:** Product setup, variant setup, and overall catalog structure stay in Shopify.
* **Inventory:** Inventory quantities and inventory tracking remain managed in Shopify.
* **Product details:** Titles, images, options, pricing, and other product information continue to be controlled in Shopify.
SKU Manager only changes SKU and barcode values. It does not make broader product or inventory changes.
## When to resync [#when-to-resync]
If you make product changes directly in Shopify or another app, SKU Manager may still show older details until you resync. This can include information such as product titles, images, or variant labels.
A resync is helpful when you want SKU Manager to reflect recent catalog updates so the app shows the latest product information.
If you have made many product changes outside SKU Manager, running a resync is a good way to refresh the app and keep what you see in SKU Manager aligned with Shopify.
# Before you edit SKUs (/docs/start-here/important-things-to-know-before-editing-skus)
Before you create or update SKUs in SKU Manager, it is important to understand how SKU changes can affect the rest of your store. A small change pattern can sometimes create duplicate SKUs, so it is worth reviewing your setup carefully and checking for conflicts afterward when needed.
## The main risk to watch for [#the-main-risk-to-watch-for]
When you generate new SKUs or update existing ones, SKU Manager does not stop a pattern from creating a SKU that already exists elsewhere in your store. This means a bulk change can accidentally create duplicate SKUs if your naming or numbering pattern overlaps with values already in use.
SKU Manager does not automatically prevent duplicate SKUs from being created during SKU generation or SKU updates. If your changes might overlap with existing SKUs, run a duplicate check after the update.
This is most likely to happen when you:
* reuse a numbering pattern that may already exist in your catalog
* apply the same SKU format across multiple products or variants
* update a large group of items at once without first confirming the final SKU format
## What you should do before or after making changes [#what-you-should-do-before-or-after-making-changes]
If there is any chance your new SKU pattern could match SKUs already in your store, plan to run a duplicate check after you finish the update. This gives you a quick way to spot conflicts and correct them before they cause confusion in your catalog or operations.
### Review your SKU pattern [#review-your-sku-pattern]
Before you make changes, look over the format you plan to use and consider whether it could produce values that already exist in your store.
### Apply your SKU changes [#apply-your-sku-changes]
Create or update SKUs in SKU Manager using your chosen pattern.
### Run a duplicate check [#run-a-duplicate-check]
After the update, run a duplicate check if you think the new values may conflict with existing SKUs.
### Resolve any duplicates found [#resolve-any-duplicates-found]
If duplicate SKUs are detected, update the affected items so each SKU is unique where needed for your workflow.
If you are completely confident that your SKU pattern is unique, a duplicate check may not be necessary. If there is any doubt, it is safest to run one.
## Practical tip for fixing duplicates [#practical-tip-for-fixing-duplicates]
When you are working through duplicate SKUs, you do not always need to update every SKU in a product. In the confirmation step, you can limit the update to only the duplicate entries.
If you only want to update duplicate SKUs instead of all SKUs in a product, select
Only update duplicates
in the confirmation step.
## Keep SKU changes safe and manageable [#keep-sku-changes-safe-and-manageable]
SKU Manager makes bulk SKU updates faster, but it is still important to check the results when your pattern could create overlap. A quick duplicate check after making changes can help you catch issues early and keep your store data clean.
# Quick setup (/docs/start-here/quick-setup)
Getting started with SKU Manager is quick and mostly automatic. Install the app, open it once, and let the setup finish. After that, you can begin updating SKUs and barcodes right away.
## Set up SKU Manager [#set-up-sku-manager]
### Install the app from the Shopify App Store [#install-the-app-from-the-shopify-app-store]
Add SKU Manager to your Shopify store from the Shopify App Store and complete the install process.
### Open SKU Manager in your Shopify admin [#open-sku-manager-in-your-shopify-admin]
After installation, open the app from your Shopify admin. SKU Manager will begin its first-time setup automatically.
### Wait for setup to finish [#wait-for-setup-to-finish]
Keep the app open while the setup page completes. When setup is done, you will be redirected to the update page.
### Start using the app [#start-using-the-app]
Once you reach the update page, setup is complete and SKU Manager is ready to use.
## What happens next [#what-happens-next]
After setup, you can start updating product SKUs and barcodes from the app. As part of your regular workflow, you may also choose to save [presets](/docs/editing-skus/toolbox#presets) later to speed up repeated updates, but you do not need to configure that to get started.
If the setup page takes a moment to finish, that is normal. Let it complete before leaving the app so everything is ready for your first update.
# What SKU Manager does (/docs/start-here/what-sku-manager-does)
## Keep your product codes organized at scale [#keep-your-product-codes-organized-at-scale]
SKU Manager helps you manage the product identifiers your store depends on every day. Whether you need to clean up inconsistent SKUs, update barcodes in bulk, generate new values for new variants, or check your catalog for duplicates, SKU Manager is built to make those jobs faster and easier.
It is especially useful when your catalog is growing, your naming rules are changing, or you need a reliable way to make large updates without editing products one by one.
## What you can do with SKU Manager [#what-you-can-do-with-sku-manager]
View, organize, and maintain the SKU and barcode values used across your product catalog.
Update existing SKUs or barcodes across many products and variants at once.
Replace part or all of an existing SKU or barcode to create a new, consistent format.
Create SKU rules so new variants receive SKUs automatically when they are added.
Scan your store for duplicate SKUs or barcodes so you can correct conflicts.
Reverse recent change sets when you need to roll back an update.
## Main capabilities [#main-capabilities]
### Manage and update product SKUs [#manage-and-update-product-skus]
SKU Manager gives you one place to work with the SKU values attached to your products and variants. This makes it easier to keep your catalog consistent, readable, and aligned with the way your business tracks inventory.
* Review and maintain SKU values across your store
* Correct outdated or inconsistent SKU formats
* Standardize product identifiers as your catalog grows
### Manage barcodes alongside SKUs [#manage-barcodes-alongside-skus]
In addition to SKUs, SKU Manager also helps you work with barcodes. This is useful when you need both values to stay accurate and aligned across large numbers of products.
* Update barcode values in bulk
* Keep barcode data organized across variants
* Maintain cleaner product records without manual editing
### Make bulk changes instead of editing one by one [#make-bulk-changes-instead-of-editing-one-by-one]
When you need to update many products at once, SKU Manager helps you apply changes in bulk. This saves time and reduces the risk of inconsistent manual edits.
* Change existing SKUs across many items in one action
* Change existing barcodes in bulk
* Apply large-scale updates more efficiently during catalog cleanups or reorganization
### Create new values by replacing old ones [#create-new-values-by-replacing-old-ones]
If you are moving from one naming pattern to another, SKU Manager can help you create new SKUs or barcodes by replacing existing values. This is useful when part of a code needs to change while the rest follows a predictable pattern.
* Replace old text or number patterns with new ones
* Create updated SKU or barcode values from existing data
* Roll out naming changes more consistently across your catalog
### Automatically generate SKUs for new variants [#automatically-generate-skus-for-new-variants]
SKU Manager can automatically generate SKUs based on your rules when new variants are added to a product. This helps merchants maintain a consistent structure without having to assign each new SKU manually.
* Set rules for how new SKUs should be created
* Apply a consistent format to future variants
* Reduce manual work as new products and options are introduced
Automatic SKU generation is especially helpful when your team adds new variants regularly and wants every new SKU to follow the same format from the start.
### Find duplicate SKUs or barcodes across your store [#find-duplicate-skus-or-barcodes-across-your-store]
Duplicate product identifiers can create confusion and make catalog maintenance harder. SKU Manager can check your store for duplicate SKUs or barcodes so you can find and fix issues before they cause bigger problems.
* Scan the full store for duplicate SKU values
* Identify duplicate barcode values
* Spot catalog conflicts that may need cleanup
### Undo recent changes when needed [#undo-recent-changes-when-needed]
If you make an update and need to reverse it, SKU Manager lets you undo recent change sets. This gives you a safety net when working on bulk edits.
You can undo the most recent 3 change sets unless you save them. Saved change sets are not overwritten by newer changes.
## Why merchants use SKU Manager [#why-merchants-use-sku-manager]
* **Save time:** Make large updates without editing products individually.
* **Improve consistency:** Keep SKU and barcode formats aligned across your catalog.
* **Reduce errors:** Use bulk updates and duplicate checks to catch issues sooner.
* **Support growth:** Automatically generate new SKUs as your product range expands.
* **Work with confidence:** Undo recent changes if you need to roll back an update.
## A strong starting point for catalog control [#a-strong-starting-point-for-catalog-control]
SKU Manager is designed for merchants who want better control over product identifiers across their store. From everyday cleanup to large-scale changes, it helps you maintain accurate SKUs and barcodes, apply updates in bulk, and keep new variant data consistent as your catalog evolves.