PriceScopeWhite-label product
Competitor prices, checked every night across a whole catalogue
Nobody can price-check a catalogue of thousands of products manually, so pricing decisions are made without current market data and corrected weeks later. This system runs that check every night.
Sample data, white-labelled.
Price is the one lever in retail that moves margin the same day. It is also the hardest to see. Competitors change prices and suppliers change costs every week. The shelf price stays where it was set months ago.
Manual checking has a ceiling. One person can compare a few dozen products across a couple of competitors. A catalogue of thousands, across several competitor sites, cannot be checked faster than the prices change. So the check shrinks to the products someone remembers to look at.
The result is rarely a visible pricing mistake. It is a slow leak: items sold below their target margin, and items priced above the market that stopped selling, with nobody connecting the two.
Six things happen between the end of one working day and the start of the next.
The mapping
Each product is mapped to the competitor listings for the same item. Everything downstream depends on this mapping, so it is maintained as the catalogue changes. A mapping generated once and never revisited stops being accurate.
The nightly run
Every night the system reads the current price of every mapped product at every mapped competitor. The run is scheduled, so it does not depend on anyone remembering to start it.
Margin against your own costs
Supplier costs are read from the company’s own ERP, so margin is calculated against what an item costs today. A spreadsheet copy of those costs is accurate only on the day it was exported.
The dashboard
A tab for each category shows the buying team what moved and by how much, so every pricing discussion starts from the same screen.
Alerts before the day starts
A price and margin email in Hebrew arrives before the working day begins. It shows what changed overnight and which items have dropped below their target margin.
A controlled write-back
Approved price changes are written back into the ERP through one controlled path that logs every write. Every change in the live catalogue carries the name of whoever approved it.
These are the systems it reads from, reports through and writes back into.
- 01The company’s own product catalogue
- 02Supplier costs held in the ERP
- 03Competitor storefronts, read on a schedule
- 04A dashboard with a tab per category for the buying team
- 05A daily Hebrew email to the people who set prices
- 06A logged write path back into the ERP
Scraping is the easy half. The hard half is the mapping, which establishes that a product and a listing are the same item and keeps that true as catalogues change. It also means handling competitor sites that change their structure overnight.
In the cost guide’s terms, this is scheduled collection plus reporting. Two things take it beyond a report. One is a definition of margin that matches how the business already measures it. The other is a safe write path into a system of record, which is what separates a dashboard from a system.
These three numbers describe the nightly workload the system was built to carry.
- products price-checked nightly
- 1,121products price-checked nightly
- competitor sites parsed
- 8competitor sites parsed
- scheduled jobs with failure alerts
- 10scheduled jobs with failure alerts
Scheduled scope of the delivered system, not a live counter.
The system was delivered in June 2026 and runs in production under a monthly support retainer. It is also a white-label product, so it can be rebuilt on another retailer’s catalogue against a different set of competitors.
The system above replaced work people were doing manually.
Free · 5–10 minutes · by phone