Back to topic
Spark playbook scenarios · Spark: AI Store Assistant

Prepare a batch of rule-based price changes

Several pricing rules are meant to run over one catalogue selection, and where they overlap nobody can say which rule wins. In this case, the immediate task is to prepare a batch of rule-based price changes. The workflow should produce a pricing change table with margin exceptions, with rule coverage verified against the merchant's own variant records.

Topic
Pricing and Bulk Price Updates
Target keyword
shopify bulk price editor
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 batch of rule-based price changes.
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: [approved rule order, selected variant identifiers and current prices, exclusions, cost basis and currency, margin formula and floor, rounding rule and permitted deviation amount]. Apply the ordered rules to each included variant, round the calculated price, then recalculate margin from the final rounded price using the stated formula and flag missing inputs, margin below the floor or absolute rounding deviation above the permitted amount.
Deliver old price, unrounded result, final price, margins, deciding rule, exception reason and rollback price for each variant, reconcile unique variant identifiers with the selection including excluded rows, and keep blocked changes out of the approval-ready batch 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.
Use in Spark
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.

01

Step 1

Gather pricing rules in their approved execution order, selected variant identifiers, current prices for rollback, exclusions, cost basis, currency, margin formula and floor, plus the rounding rule and maximum permitted rounding deviation stated by the merchant.

02

Step 2

Apply the ordered rules to each included variant, round the calculated price, then recalculate margin from the final rounded price using the stated formula and flag missing inputs, margin below the floor or absolute rounding deviation above the permitted amount.

03

Step 3

Deliver old price, unrounded result, final price, margins, deciding rule, exception reason and rollback price for each variant, reconcile unique variant identifiers with the selection including excluded rows, and keep blocked changes out of the approval-ready batch.

FAQ

Common questions when running this scenario

Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.

In what order should multiple pricing rules run?

Fix the order before the batch runs and record which rule set each final price; when two rules touch the same variant, the later rule wins only because the order says so, and that order is itself part of what gets reviewed rather than a runtime accident.

How is a margin exception defined?

Recalculate margin using the final rounded price and the merchant's formula, cost basis and currency. Flag margin below the stated floor or absolute rounding deviation above the permitted amount; normal rounding inside that allowance is not itself an exception.

What does the rollback field contain?

The variant's previous price, so a rejected batch can be reversed row by row without rebuilding it; the change table also records the rule that set each price, so one mistaken rule is visible across every affected variant at review time.

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.

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.