01
Step 1
Collect the selected variants with their current price, cost basis and currency, the adjustment rule and the rounding order the merchant stated, the margin floor agreed for this change, and the compare-at prices already on those variants.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Prepare consistent price updates across selected variants
A price adjustment covers a subset of variants, but cost records are incomplete and no margin floor has been agreed. In this case, the immediate task is to prepare consistent price updates across selected variants. The workflow should produce a pricing change table with margin exceptions, reconciled against the merchant's own price records.
Topic
Pricing and Bulk Price Updates
Target keyword
shopify bulk edit variant prices
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 consistent price updates across selected variants.
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 selected variants with their current price, cost basis and currency, the merchant's stated adjustment rule and rounding order, the margin floor agreed for this change, and the compare-at prices already on those variants]. Compute the proposed price per variant from its own cost basis in the stated currency, apply the rounding order, and flag as exceptions the variants whose margin falls below the floor and those with no cost record, holding the flagged ones out of the batch with the reason recorded.
Return a pricing change table with margin exceptions 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
Compute the proposed price per variant from its own cost basis in the stated currency, apply the rounding order, and flag as exceptions the variants whose margin falls below the floor and those with no cost record, holding the flagged ones out of the batch with the reason recorded.
03
Step 3
Deliver a pricing change table listing old price, new price, margin before and after, the rounding applied and the rollback value per variant, reconcile the row count with the selected variant count plus the held ones, and note each variant whose compare-at price the stated rules leave unchanged.
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 the variant selection fixed before the run?
The selection is fixed as a list of variants with their identifiers and recorded before any price is computed, because pricing a moving selection makes the table impossible to reconcile; variants added after the list is set go into a later batch, and the row count of the table is checked against that same list.
Why carry the compare-at price into the table?
The compare-at price is recorded per variant and changed only where the stated rules say so, because leaving it untouched while the selling price moves can show a reference price that no longer means anything; where the rules are silent the old value is carried and the variant is noted rather than adjusted.
When does a held variant rejoin the batch?
A variant held out for a missing cost record or a margin below the floor rejoins only once its cost is on file or the merchant restates the floor for it, since repricing on an assumed cost repeats the same exception; until then it keeps its old price and stays on the exception list.
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.
Calculate size-based variant prices using stated rules
Apply a consistent price-rounding convention
Calculate a percentage price increase for selected products
Prepare a batch of rule-based price changes
Update inventory from a designated source of truth
Prepare scoped updates to product metafield values
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.