Manage variation pricing across a catalog

Repricing variations is the job nobody wants. A cost went up, or you are running a rule like “add ten percent to every large size” or “round every price to end in nine”, and the only way to do it by hand is to open every variable product, then every variation inside it, and edit one number at a time. It is slow, and because it is money, a slip is expensive.

This reads the prices for you and proposes the whole change as a table. Because it moves live prices, it is built to stop and make you say yes on purpose before a single number is written.

I want to reprice the variations on [the products in the "Outerwear"
category]. The rule is: [describe it, for example "raise every variation price
by 8% and round up to the nearest .95"].

Do this carefully because these are live prices. First, change nothing: list
the variable products in that set, read every variation and its current price,
apply my rule, and hand me a before-and-after table with the old price beside
the new one for all of them. Show me the total number of variations affected.

Then stop and wait. Do not write any price until I reply with an explicit
"yes, apply these prices". After I do, write them in small batches and show me
each batch before it saves. At the end, give me the full list of every
variation you changed with its old and new price so I have a record to roll
back from.

Why this is safe to run

The whole first pass is reads. Listing the products, listing their variations, and reading each variation’s price all write nothing, so the complete before-and-after table sits in front of you, with a count, before any price moves.

Because this is money, the recipe adds a hard stop the other recipes do not lean on as heavily: the agent will not write a single price until you reply with an explicit go-ahead, and even then it works in small batches you approve one at a time, so a wrong rule shows up on the first handful rather than across the catalog. The variation write ability stays off until you enable it, every call is checked against the capability of the user you bound the agent to, and every write lands in the Activity Log. The change list keeps the old price beside the new one, so you always have the number to roll back to.

Already connected? You do not have to paste this at all. Ask your agent for the “manage variation pricing across a catalog” recipe, give it the rule, and it runs the same read, approve, then batch flow on your own store.