Size variants are priced by habit rather than by a written rule, so cost and quantity differences are not reflected consistently. In this case, the immediate task is to calculate size-based variant prices using stated rules. The workflow should produce a change table naming the rule applied per size, based on the merchant's own cost records.
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.
Act as a Shopify operations specialist.
Help me calculate size-based variant prices using stated rules.
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 size variant's current price, unit quantity per package, recorded cost basis, the currency every figure is stated in, the merchant's approved size-pricing rule, and the margin floor]. Derive each size's price from the cost difference between sizes or from the quantity per package exactly as the rule directs, keeping the derived figure and the price after the merchant's rounding step side by side, and flag as exceptions sizes with no recorded cost, sizes whose derived price sits below the stated floor and sizes whose price moves against the direction the rule requires.
Return a change table naming the rule applied per size 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.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Collect, for every size variant named by the merchant, its current price, the unit quantity each package holds, the cost basis recorded for that size, the currency every figure is stated in, the approved size-pricing rule and the margin floor the price must clear.
Derive each size's price from the cost difference between sizes or from the quantity per package exactly as the rule directs, keeping the derived figure and the price after the merchant's rounding step side by side, and flag as exceptions sizes with no recorded cost, sizes whose derived price sits below the stated floor and sizes whose price moves against the direction the rule requires.
Deliver a size-level change table listing size, unit quantity, cost basis, old price, derived price, rounded price, margin before and after, the rule that set the price and every exception flag, then reconcile its row count with the number of size variants in scope and confirm each excluded or unresolved size appears with its reason and its rollback value.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Only where the merchant's rule defines a fixed step. Otherwise each size is priced from its own cost and unit count, because a larger pack usually costs more to produce and a flat gap quietly underprices it; where the evidence does not support a step, the size keeps its own derived figure rather than being fitted to a pattern.
It stays unresolved rather than borrowing another size's cost, since copying the smallest size onto a multipack hides exactly the loss this exercise exists to find. The row keeps its previous price and carries an exception naming the missing input; once the supplier cost arrives, the same rule produces the price without further judgement.
Reconcile each row's cost basis against the merchant's own cost records, check that the row count equals the size variants in scope, and confirm every size below the stated margin floor appears in the exception list. Sizes the merchant excluded must also appear with their reason, otherwise an absent row reads as one that was simply overlooked.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
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.