Price and stock changes in Shopify are variant-level writes. Both go through the same three steps in ApiMate: an instruction that names the scope and the rule, a preview that lists every variant with its current and new value, and one approval. The values that were there before are saved with the task, so a sale can be ended and a mistake can be undone from Tasks.
The video below is one real run on five Northline snowboards with thirteen size variants. The instruction was "Put every Northline snowboard on sale: 20% off, and keep the current price as the compare-at price." The preview listed each variant with both writes, for example "Price: 499.00 → 399.20" and "Compare-at price: — → 499.00". One approval wrote them, every variant was read back from Shopify (13 of 13 verified), and the last shot is the variant in Shopify Admin at 399.20 with compare-at 499.00. The undo and the scheduled version of the same sale have their own clips further down.
Most price mistakes are targeting mistakes, not arithmetic. The rule was right and the collection was wrong, or "XL" matched "XXL" too. The preview exists so the wrong scope is caught before it goes live, and undo exists so the cleanup takes minutes when it is not.
The scope is read literally, and the first line of the preview states how many variants matched: "Update 13 variants" in the run above.
Who runs this job, and why now
A supplier sends a new cost list and every product from that vendor moves 6%. A sale starts Friday and ends Sunday night, and it needs the price and the compare-at price set together on two hundred variants, then both put back. A line is being cleared and everything tagged with it drops 30%. Stock arrives at one warehouse and not the other, and the counts have to land at the right location or the storefront sells what is not there.
Each of these is a few sentences in a chat and a few hundred rows in the admin. The merchant knows the rule. The work is applying it to every variant it applies to, and only those, and being able to show afterwards what changed.
Two questions merchants ask during their first price job, word for word: "How many products are you applying this change to?" and "Is this change for all of my items?" The preview answers both in its first line, and the rest of this page is about reading that line before approving.
How this is done without ApiMate, and where each way breaks
The Shopify admin has a bulk editor: select products, "Bulk edit", and a grid with price, compare-at price, cost and SKU columns per variant appears. Stock quantity is not a column there any more; it is edited under Products, Inventory. It works well for a few dozen rows that fit on one screen. It has no formula, so "raise by 10%" is arithmetic you do per cell. It has no filter by tag or vendor beyond the product list search, so "only XL variants" is a manual selection. It writes when you press Save, and the admin keeps no copy of the old prices to go back to.
A CSV export handles volume and formulas. Export products, change "Variant Price", "Variant Compare At Price" and "Variant Inventory Qty" in the sheet, import. The import has no preview, and a locale that reads 12,50 as 1250 will import 1250. The export you started from is your only way back, and only if you did not overwrite it. Inventory by CSV is per location only through a separate inventory export, which is where the location column gets mixed up.
Table-style bulk editor apps add the formula and the filter, and most add a preview, which is the right shape. The remaining problem is the filter itself: it is built by hand from dropdowns, field by field, and the filter is the thing merchants get wrong. A sentence that says "XL variants of hoodies from Cedar & Pine that are active" is one line to type and four conditions to click. The preview shows rows either way; the difference is how often the rows are the ones you meant.

The instruction, as written
The instruction has three parts: which variants, what changes, by how much. Percent or fixed amount, up or down. Scope by vendor, collection, tag, product type, variant option, status or a price range, in any combination. "Only XL variants" is a scope. "Products under 20" is a scope. "Everything except the Sale collection" is a scope.
Rounding is a rule, not an afterthought. "Raise by 10%" on 24.00 gives 26.40; on 189.00 it gives 207.90. If your prices end in .99 or .00, say so, and the preview will show the rounded value. Say which way to round when it matters: "round up to .99" and "round to the nearest .99" give different results on 26.40.
Instruction
Raise prices by 10% only for XL variants, round to .99.
- Scope: variants whose size option is XL. Not XXL, not products that merely have an XL variant; the XL rows.
- Rule: price × 1.10, then rounded to the nearest .99.
- Products with a single Default Title variant are still variants. They are in scope unless the instruction excludes them.
- A price of 0 is written as 0. An empty value clears a field; it is not a broadcast.
What the preview showed
ApiMate reads the variants in scope, computes the new price for each one and lists them. The list is the plan. The count in the first line is the number of variants the job will write. If it says 1,200 and you pictured 40, cancel and narrow the scope. Nothing has been written yet.
The current value is read live from the store when the plan is built, not from a cached copy. If a colleague changed a price a minute ago, the left column shows the new one and the rule is applied to it. That also means a plan is not something to leave open overnight; build it when you are ready to read it.
| On the card | What it is | What to check |
|---|---|---|
| First line | What the task does and how many variants: "Update 13 variants" | The count against what you pictured before you typed |
| Row title | Product and variant option, "Ridge All-Mountain Snowboard — 160 cm", linked to Shopify Admin | The option values are the ones the scope named |
| Price | Current price, struck through, then the new one: 499.00 → 399.20 | The math matches the rule, including rounding if you asked for it |
| Compare-at price | On the same row when the task writes it: — → 499.00 | Above the new price on every row; a dash means it was empty |
| Planned mutation input | The exact write, folded under each row | Only the fields you meant to change |
The count line above the rows is the scope. Read it first.
Prices
A percent rule is the common case and the one where the edges bite. Ten percent on the cheapest variant in the list is pennies; on the most expensive it may cross a threshold the storefront filters on, or a price point marketing promised. Read the top and bottom of the list, not just the middle.
A fixed amount ("add 2.00 to everything from this vendor") is safer at the edges and stranger in the middle: a 2.00 increase on a 4.99 item is 40%. The preview shows the number, not the percentage, so do the division on a few rows.
A set value ("set price to 49.99") is the simplest rule and the one where scope matters most, because every row in scope becomes the same price. If the scope accidentally includes the premium line, the premium line is now 49.99. The count and a scan of the product column catch that before approval.
Compare-at price
A sale on the storefront needs two numbers: the price the customer pays and the compare-at price it is struck through against. Setting one without the other shows no discount, or a wrong one, or a compare-at lower than the price, which themes render as a negative saving and Merchant Center flags as a price mismatch. Say both in the instruction and they land in the same plan.
You do not have to type the old price. "Keep the current price as the compare-at price" copies each variant's own price into compare-at before the 20% comes off, so every row gets its own number. In the video, the 160 cm Ridge went from 499.00 to 399.20 with compare-at 499.00, and the 156 cm Summit from 559.00 to 447.20 with compare-at 559.00.
When the sale ends, undo the task, or schedule the end in advance (next section). Undo puts both fields back to what they were, for exactly the variants the task changed. A variant that was not in the sale is not in the undo.
A compare-at price that was empty before the sale is restored to empty. That matters: some themes hide the strike-through only when the field is empty, not when it equals the price.
Instruction
Put every Northline snowboard on sale: 20% off, and keep the current price as the compare-at price.
Schedule the sale and its end
A preview card has "Schedule changes" next to Apply. It opens a form with the store timezone, a start time and an optional "Restore at" time. "Review schedule" shows the plan again with both times; "Approve schedule" is the one approval for the sale and its end. Nothing is written until the start time.
At the start time the task runs the same writes as Apply and reads them back. At the restore time it writes the saved values back, the same way undo does. The card shows each step as it happens: "Scheduled", then "Started", then "Restore · Done", and the task in Tasks ends as Reverted. In the clip below the sale started and ended three minutes apart; the waits are cut.
Scheduling covers price, compare-at price, title, description, SEO fields and tags, up to 5,000 rows per task. Times are typed with their UTC offset, for example 2026-11-27T00:00:00-05:00. If the task cannot start by the restore time, it does not run late; it waits for your review. Stock quantities are not scheduled.
Inventory
Stock is per variant, per location. An instruction that does not name a location applies to every location the store has, and the preview shows the split. A store with one location sees one column; a store with three sees three, and the job is three writes per variant.
A wrong price is a margin hit. A wrong quantity is a customer-facing failure: zero hides the product from the storefront, too high sells what you do not have, and both show up as a support ticket rather than a report. Read inventory previews more slowly than price previews, and read the location column first.
Locations run by a fulfilment service are read-only from the Shopify side. ApiMate reports that in the plan, as a skipped row with the reason, instead of attempting the write and failing halfway through the job. "Set" and "adjust" are different rules: "set stock to 20" writes 20; "add 20" writes current plus 20. Say which.
Instruction
Set stock to 20 at both locations for all snowboards.
- Name the location. "At the Manchester warehouse" is a scope; "in stock" is not.
- "Set" replaces the number. "Add" or "remove" adjusts it. The preview shows the resulting number either way.
- Variants with inventory tracking off are skipped with the reason. Turning tracking on is a separate change.

Before you approve
Four checks, in this order. They take a minute and they are the whole safety model.
- The count. Compare it to what you expected before you typed the instruction. Wrong count, wrong scope, decline.
- Five rows at random. Old value, new value, does the math match the rule, including the rounding.
- The edges: the cheapest and the most expensive variant in the list. Percent rules bite there.
- For stock: the location column. A job meant for one warehouse that lists two is the wrong job.
- For a sale: both fields are present on every row, and compare-at is above price on every row.
What happened after approval
One approval writes every row. When it finishes, every variant is read back from Shopify and compared with the plan; the card ends on "Done — every change verified" with the count, 13 of 13 in the video. The task stays in Tasks with the rows it wrote and the values they replaced, which is also your record of what changed and when.
To see the result in Shopify, open a product from the list and look at the variant table; the new prices are there. The storefront shows them on its next page load, subject to any caching your theme or CDN does. For inventory, the location breakdown is on the variant's inventory panel. If a row failed, the job says which and why, and the failed rows are not marked as written.
Undo
Every variant row stores the price, compare-at price or quantity it had before the write. Undo on the finished task in Tasks says what it will do, "ApiMate will roll back the 13 changes it made. Nothing else changes.", and asks once: "Undo 13 changes", "Keep it", or "See what changed" to read the rows first. It writes the saved values to the rows the original task changed and no others, reads them back, and the task is marked Reverted.
In the clip below, the snowboard from the main video is back at 499.00 with no compare-at price. A compare-at price that was empty before the sale is restored to empty, not to zero.
Inventory is undone to the quantity at the moment of the change. If sales happened in between, undo still writes the old number, which is now too high by the units sold. For stock, undo is a starting point, not the truth: read the location before you confirm, or use a fresh "set" instruction with the counted number instead.
A price undone a week later overwrites any hand edits made in between, on the rows it covers. "See what changed" lists the rows before you confirm, so check it when the task is old.
Where the tool stops
A supplier feed that arrives every Monday belongs in a file-based tool or a sync app. The file is the source of truth and the columns do not change; a sentence adds a step, not safety. The comparison page with Matrixify says where that line is.
A schedule is one start and one optional restore per task. A sale that repeats every weekend is a new task each time; there is no calendar of recurring price changes.
Very large jobs run in batches and the plan says how many. A catalog with tens of thousands of variants is better split by vendor or collection, so each preview is one you can read.
Prices are written in the store currency. Market-specific prices set through Shopify Markets are a separate object and are not changed by a price job unless the instruction names the market.
Other ways to say the same job
These phrasings resolve to plans of the same shape. The scope line tells you whether they resolved to the scope you meant.
- "Increase all prices by 5%."
- "Everything from Cedar & Pine goes up 6%, round to .99."
- "Put the Winter collection on sale: 20% off, show the old price."
- "Set compare-at to the current price and drop the price by 15% for everything tagged clearance."
- "Put every Northline snowboard on sale from Friday 00:00 to Sunday 23:59." (Then fill the times on the schedule form.)
- "Set stock to 0 at the London location for everything tagged discontinued."
- "Add 50 units at the main warehouse for every variant of the Ridge Hoodie."
- "Which variants have a compare-at price lower than the price?" (A read; fix it with a second instruction.)
Terms used on this page
- Variant: the sellable unit under a product, one per option combination. Price and stock live here, not on the product.
- Compare-at price: the crossed-out price on a sale. Empty means no sale shown.
- Location: a place stock is held. Inventory is a number per variant per location.
- Scope: the set of variants a job applies to. Resolved before the plan; the count is the first line of the preview.
- Set vs adjust: "set" writes the number; "adjust" adds or subtracts from the current one.
- Undo: writes the saved previous values back to the rows the original task changed.
- Restore at: the time a scheduled task puts the saved values back on its own.
Questions
Is this change for all of my items?+
Only if the instruction says so. Scope is read literally: "all Hydration products" is the Hydration products, "XL variants" is the XL variants. The first line of the preview states the count.
Can I raise prices by a percentage and round to .99?+
Yes. Say the percentage and the rounding rule in the instruction. The preview shows the rounded value per row.
Can I end a sale automatically?+
Yes. Choose "Schedule changes" on the preview, set the start time and a "Restore at" time, and approve once. At the restore time the old prices and compare-at prices are written back and read back.
Does it handle compare-at prices?+
Yes. Price and compare-at price are two writes on the same row. "Keep the current price as the compare-at price" copies each variant's own price, so you do not type it. Undo the task or schedule a restore to end the sale.
What about multiple locations?+
Stock writes are per location. Name the location in the instruction or the plan covers every location, and the preview shows each one as its own row.
What happens if I approve the wrong scope?+
Undo the task from Tasks. It says how many changes it will roll back, asks once, and writes the saved values back to exactly the rows the task changed.
Does undo fix inventory after sales happened?+
It writes the saved number, which does not account for units sold since. For stock, read the location and use a fresh "set" instruction if the count moved.
Can it change prices for one market only?+
Not in a plain price job. Market prices are a separate object; an instruction that names the market is planned separately, and the preview says which prices it touches.
Related
- Bulk edit compare-at prices in ShopifyStart and end a sale without breaking the two price fields.
- Turn on inventory tracking for every productEnable tracking across the catalog and stock each location.
- How to undo a bulk edit in ShopifyWhat the admin, CSV and apps give you when a bulk change goes wrong.
- Bulk edit Shopify metafields, weight and dimensionsStructured fields with units, through the same preview.
- ApiMate vs MatrixifyWhen a spreadsheet is still the right tool for a price change.
Run this on your own catalog
Install from the Shopify App Store. Every write shows its rows before it runs, and applied jobs can be reverted from history.