Playbook · Shopify SKU duplicate error
SKU typed — Save — already taken.
Written for a Shopify owner who cannot Save a SKU because Admin says it is duplicate / already taken — store-wide uniqueness, a draft or archived product still owns the string, CSV / Matrixify / ERP stamped the same SKU onto many rows, copy-product kept the old SKU — or you chased barcode not saving, inventory item cost / COGS, product publish sync, variant inventory policy, or bulk operations instead. DIY-first: prove which product owns the SKU → free or rename it / fix import → retest. Distinct from barcode not saving, inventory item cost wrong, product publish not syncing, variant inventory policy wrong, and bulk operations stuck. Soft-link unit price wrong when measure fields also fail to stick, and barcode not saving when the GTIN field is the real persistence bug. No earnings claims, no invented case studies.
Nico at Latch AI Ops · Sep 10, 2026 · ~12 minute read
01
SKU duplicate error — not barcode not saving, inventory cost, publish sync, variant policy, or bulk stuck.
Several “product identifier stuck” bugs look alike. They do not share a fix. This page is only when Admin rejects a SKU as duplicate / already taken — you type SKU-RED-M, click Save, and Shopify says the SKU is already in use, or a CSV / Matrixify / ERP import fails on SKU collision. Barcode / GTIN not saving is shopify-barcode-not-saving. Inventory item cost wrong is shopify-inventory-item-cost-wrong. Product publish not syncing is shopify-product-publish-not-syncing. Variant inventory policy wrong is shopify-variant-inventory-policy-wrong. Bulk operations stuck is shopify-bulk-operations-stuck.
Soft-check shopify-unit-price-wrong when measure fields also refuse to stick, and shopify-barcode-not-saving when the GTIN / barcode field is what reverts after Save — not the SKU uniqueness toast.
02
Prove which product/variant already owns the SKU.
Search Admin Products by the exact SKU string with drafts and archived included. Open every hit and screenshot the variant that already owns it. Soft-check copy-product / duplicate-product flows that keep the old SKU. Soft-check CSV / Matrixify / ERP / 3PL jobs that stamp one SKU onto many rows. Soft-check apps with write_products that rewrite SKUs after your Save. Soft-check whether blank SKUs are allowed on other variants so you can free the collision temporarily.
If Save succeeds in Admin but a channel feed still shows the old SKU, that is closer to product publish not syncing — a different product once Admin itself accepts the SKU. If a bulk SKU rewrite never finishes, switch to bulk operations stuck.
03
Free or rename the colliding SKU, fix import, then retest.
Rename or clear the SKU on the colliding draft, archived, or live variant. Pause the Matrixify / ERP job that re-applies the duplicate. Fix the CSV so each SKU is unique before re-import. Stop copy-product flows that keep the source SKU. Scope-down an app that mass-updates variant SKUs without a uniqueness check.
Honest retest: set SKU → Save → hard refresh → no duplicate toast → Admin product search finds only this variant for that SKU. If the SKU Saves but the GTIN field reverts, switch to shopify-barcode-not-saving. If a bulk write hangs, switch to shopify-bulk-operations-stuck.
04
You tested barcode not saving, inventory cost, publish sync, variant policy, or bulk stuck instead.
Barcode / GTIN not saving is shopify-barcode-not-saving. Inventory item cost wrong is shopify-inventory-item-cost-wrong. Product publish not syncing is shopify-product-publish-not-syncing. Variant inventory policy wrong is shopify-variant-inventory-policy-wrong. Bulk operations stuck is shopify-bulk-operations-stuck.
The only honest test for this page: Admin rejects the SKU as duplicate / already taken on Save or import. Anything else is a different product.
05
When to stay DIY vs pay $997.
Stay DIY if you can spend one afternoon on the list above: find the colliding product, free or rename the SKU, pause the import/app race, retest. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: barcode not saving, bulk operations stuck, unit price wrong.
Pay for help when the work is not the SKU field itself — it is connecting the stack you already have so SKU / inventory / ERP / import exceptions land in a channel you already check, and the live store is one workflow instead of a spreadsheet plus a Slack bot you forgot. That is the Latch AI Ops install.
What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a theme rebuild retainer, not a conversion guarantee, not a brand or theme job.
Other shops' public ranges, not testimonials: a checkout / ops install typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or conversion-lift claim.
What it does not buy: more orders, recovered revenue, a forever SKU uniqueness guarantee, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.
Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.