01
Step 1
Take every variant's ID, option values, SKU and inventory link with the order lines, refunds and images attached to it across one reporting window, so no record is judged on a partial history.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Identify duplicate variants and propose a cleanup mapping
The same purchasable item sits under several variant records, each with its own stock link and order history, so deleting the wrong one loses data. In this case, the immediate task is to identify duplicate variants and propose a cleanup mapping. The workflow should produce a variant matrix and change list keeping the record with the strongest linked data.
Topic
Variant Creation and Management
Target keyword
shopify remove duplicate variants
Copyable AI prompt
A prompt you can drop directly into Spark
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
ai-prompt.txt
Act as a Shopify operations specialist.
Help me identify duplicate variants and propose a cleanup mapping.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [each variant's ID, option values, SKU and inventory link, with the order lines, refunds and images attached to it across one reporting window]. Call variants duplicates only when their option values describe the same purchasable item, treating differences in casing or spacing as the same item but never collapsing different SKUs or different size or finish dimensions, then rank each group by how complete its order lines, inventory movements and images are before naming a survivor.
Return a variant matrix and precise change list, mapping each duplicate to the variant that should remain for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.How to solve
A recommended resolution workflow
Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
02
Step 2
Call variants duplicates only when their option values describe the same purchasable item, treating differences in casing or spacing as the same item but never collapsing different SKUs or different size or finish dimensions, then rank each group by how complete its order lines, inventory movements and images are before naming a survivor.
03
Step 3
Deliver a variant matrix and precise change list mapping every duplicate variant ID to the survivor with the stock quantities and images to transfer and the historical orders left referenced, verify that each merged group's sales total equals the sum across its old variants, and list any inventory location or order line still attached to a variant marked for removal.
FAQ
Common questions when running this scenario
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
How close must two variants be to count as duplicates?
Their option values must resolve to the same purchasable item, so identical values differing only in casing or spacing are duplicates while a different size, finish or SKU is not; when the SKUs differ but everything else matches, log the pair as suspect and confirm against the supplier record rather than merging.
What happens to orders already attached to the removed variant?
Historical order lines and refunds should stay readable after the cleanup, which is why the change list records what each duplicate carries before anything is deleted; if removing a record would break an order or refund reference, keep that variant and resolve the duplication another way, noting the decision.
How do you confirm the merge lost nothing?
Sum the order lines and quantities of every variant in the group and compare them with the survivor after transfer, check each inventory location is linked once and every image still resolves, and treat any line that fails to reconcile as a reason to stop rather than as a minor difference.
Related scenarios
Continue with adjacent or same-topic scenarios
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Build a valid color-and-size variant matrix
Prepare a variant import from CSV source records
Add valid variants to an existing product structure
Reorder product variants for a clearer selection experience
Create missing variants from valid option combinations
Standardize the names and values of variant options
Next step
Want these AI scenarios embedded directly into daily operations?
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.