01
Step 1
Read the CSV headers and columns, the product handle each row maps to, the option name and value columns, the existing variant identifiers and SKUs for those handles, and the option values each product currently allows.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Prepare a variant import from CSV source records
A supplier CSV has arrived with option columns that may not match the product, and a careless import would overwrite live variant data. In this case, the immediate task is to prepare a variant import from CSV source records. The workflow should produce a variant matrix and precise change list splitting rows ready to upload from those needing correction.
Topic
Variant Creation and Management
Target keyword
import shopify variants from csv
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 prepare a variant import from CSV source records.
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: [the CSV headers and columns, the product handle each row maps to, the option name and value columns, the existing variant identifiers and SKUs for those handles, and the option values each product currently allows].
Validate every row by confirming that the handle resolves to exactly one product, that the required fields are present, that each option value is one the product allows, that no option value set or SKU repeats inside the file, and that the row is treated as an update only where it carries a variant identifier that already exists.
Return a variant matrix and precise change list, listing rows ready to import and rows needing correction 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
Validate every row by confirming that the handle resolves to exactly one product, that the required fields are present, that each option value is one the product allows, that no option value set or SKU repeats inside the file, and that the row is treated as an update only where it carries a variant identifier that already exists.
03
Step 3
Deliver a variant matrix and precise change list splitting the rows ready to upload from the rows needing correction with the failing check named on each, then confirm that the two counts sum to the file's data rows and that no ready row overwrites a variant the merchant did not name.
FAQ
Common questions when running this scenario
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
How is an update row told from a new one?
Only by a variant identifier on the row that matches an existing variant, since a handle and option values alone cannot be trusted to name one record. Where it is missing the row is treated as new, and where it matches nothing the row is rejected rather than left to the import to interpret.
What if the option headers do not match the product?
The row is blocked, because an unmapped option column cannot be checked against the values the product allows and would silently create variants the merchant never sold. The correction sheet names the header and the allowed values, and the row returns to validation once the mapping is supplied.
Should the whole file go in after corrections?
Only the rows that pass a fresh validation run, with rejected rows held back until they are rechecked, because a corrected file can fail on a different rule the second time. The change list records the validation results for both passes so the merchant can see exactly which rows were imported and which were not.
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.
Create missing variants from valid option combinations
Add valid variants to an existing product structure
Build a valid color-and-size variant matrix
Standardize the names and values of variant options
Identify duplicate variants and propose a cleanup mapping
Reorder product variants for a clearer selection experience
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.