Prices carry inconsistent endings because rounding was done by hand, in different directions, campaign by campaign. In this case, the immediate task is to apply a consistent price-rounding convention. The workflow should produce a pricing change table with margin exceptions, with every rounded value checked against the merchant's 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 apply a consistent price-rounding convention.
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 current selling price and compare-at price, its cost basis, the selling currency, the permitted target endings, rounding direction and allowed rounding step for that currency, and the merchant's margin floor]. Move each price to the nearest permitted ending by that single stated method, recording both the unrounded result and the price after rounding, and flag as exceptions every variant whose rounded price sits further from the unrounded rule result than the allowed step permits, whose rounded margin falls below the merchant's stated floor, or whose compare-at price would end up at or below the new price.
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.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Collect every in-scope variant with its current selling price, its compare-at price where the merchant uses one, the cost basis behind it, the currency it sells in, and the rounding convention approved for that currency including the permitted endings, the rounding direction, the allowed rounding step and how currencies without minor units are treated.
Move each price to the nearest permitted ending by that single stated method, recording both the unrounded result and the price after rounding, and flag as exceptions every variant whose rounded price sits further from the unrounded rule result than the allowed step permits, whose rounded margin falls below the merchant's stated floor, or whose compare-at price would end up at or below the new price.
Deliver a rounding change table showing old price, rounded price, how far the price moved, margin before and after, the ending rule applied and each exception flag, then reconcile the row count with the variants selected for rounding and confirm every price rounded downward still clears the floor and carries its previous price for rollback.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
No, the merchant states a convention per currency, because a tidy ending in one currency can read as careless in another and a currency with no minor units has no cents to round into. Where no convention is agreed for a currency, its prices stay untouched and are listed apart rather than rounded by a rule borrowed from somewhere else.
Yes, so margin is recalculated per variant after rounding against the merchant's cost basis. Rounding down hands back cents while rounding up keeps them, which bites hardest on cheap variants where one step is a large share of the margin; any variant whose rounded margin lands under the stated floor is flagged rather than published with the rest.
Compare the change table row by row against the merchant's own price export, confirm the number of rows equals the variants selected for rounding, and spot-check that each new ending is one the convention permits. Variants deliberately left unrounded must also appear with a reason, otherwise a missing row looks like an oversight instead of a decision.
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.