Situation
One price change, many products
The store sells prints in a range of sizes, and every product carries the same set of sizes as custom options. When the cost of one size changed, the shop team had to open every product and change that option’s price, one product at a time. A price review was an afternoon’s work, with room for a slip on every product.
What we did
Two screens, two reports, no spreadsheets
- Size Prices A screen under Catalog where the team types the price customers pay for each size, sees the before and after for every affected product, and saves. Products with their own discount or a price override are left alone. Sizes can be matched in inches as well as by name.
- Extra Prices The same idea for optional extras: one price per extra, applied across all the products that offer it.
- A history Every saved price change is kept in full, so the team can see what was changed, when, and by whom.
- Reports A bestsellers-by-size report and a basket funnel by size, so the team can see which sizes are added to the basket and which are abandoned before checkout.
- Clean base prices A one-off command moved the cheapest size price into each product’s base price, so listings show a true “from” price.
This was a development task within the store’s monthly plan: scoped in a sentence, built on our copy of the store, reviewed by a senior developer and released on its own.
Result
A price review in minutes
One screenfor all size prices
2reports the team did not have before
Worth checking on your store
If your products share a set of options
- Time how long a single price change takes across the catalogue. If the answer is “an afternoon”, it is a task worth scoping.
- Ask whether you can see which options sell. Magento’s standard reports do not break sales down by option.