Change a thousand prices and still sleep
Put a discount on a category, a brand or a named list in one step. See exactly which products are affected and what each one will cost before anything moves — and undo it afterwards.
- Always a dry run first See the count and the prices first.
- Refuses the dangerous ones Below zero or over your limit is refused.
- A way back Revert from the recorded before-state.
Pending here, live only when you say so
Discounts are drafted in the tool and sit there until you publish them. Publishing is a separate, separately-permissioned step, so “prepare the sale” and “start the sale” are two different decisions.
- Category, brand, or a list of references — with exclusions
- Per customer group and per quantity threshold
- Start and end dates, honoured by the shop
Three hundred products, and the sale starts today
There is no preview, so you learn what the discount did by looking at the shop afterwards. And if the number was wrong, the way back is the way you came: one product at a time, with the sale already running.
A weekend sale on one category, live on Friday, gone on Monday
The sequence that makes a thousand-product price change a decision rather than an adventure.
-
1
Name the category — not an id. The subtree comes with it.
-
2
Set the reduction and the dates it should run between.
-
3
Read the preview: how many products, five of them priced before and after, how many existing rules get overwritten.
-
4
Publish. Only now does anything reach the storefront.
-
5
On Monday the end date has already taken it off — or you revert the job, and the recorded before-prices go back.
More than a bulk edit.
A change you can see before it happens and undo after it has.
Including the ones you forgot you had
Vouchers and basket-level rules are listed beside product discounts, because “what discounts are running?” answered without them is a confident half-answer. One shop we connected had sixty live cart rules nobody had looked at in a year.
| Code | Reduction | Used | Given away |
|---|---|---|---|
| REDUCERE10 | 10% | 204 | 6,750.70 |
| COS10 | 10% | 144 | 6,713.86 |
| SPECIAL10 | 10% | 38 | 1,385.21 |
Everything you can change, and take back
- Competitor price monitoring, so a price change starts from what the market is doing
- A discount on one product, or on thousands in one step
- Target by category and its whole subtree, by brand, or by a list of references
- Exclusions, so "everything except these" is one rule
- Percentage or fixed amount, per customer group
- Quantity thresholds — a different price from ten pieces up
- Start and end dates, honoured by the storefront
- A preview of every affected product, priced before and after
- A refusal if anything would end up below zero
- A ceiling on how many products one rule may touch
- Vouchers and basket rules listed beside product discounts
- Bulk price changes through mass update, with a recorded before-state
- A combination price grid for products with variants
Changing prices, and taking it back
Captured from a working instance. The layout and the numbers are real; customer, shop and product names have been replaced with invented ones.
Questions about this
What if I get the percentage wrong?
The dry run shows you the resulting price on real products before anything is written, and every bulk change keeps its before-state so it can be reverted as one action.
Does it work with quantity discounts?
Yes. A rule can start from a quantity, and the storefront honours it — including the case where "11% from 10 pieces" must not discount a single unit.
Can a salesperson do this?
Only if you let them. Preparing a discount and publishing one are separate permissions, and publishing needs a switch on the server as well.
Ready to see it on your own catalogue?
We set up an instance with your products, your prices and your VAT rates, and walk through it with you.