A price list here has a shelf life measured in weeks. Every assumption behind caching a product page — that the number stays true — stops holding.
Most store tuning assumes a price is stable and a page can be cached for a day. Here the price is the volatile part.
A figure cached for a day can be materially wrong by the time somebody buys. Product and listing pages carry a short lifetime and purge on any repricing run.
Updating every price is a bulk operation run often, not an occasional maintenance task. It runs as a resumable batch so the catalogue is never half-repriced.
Paying in instalments is normal here, and the total depends on the plan and the card. Those figures are computed per request rather than cached across customers.
If a price is shown, the order has to accept it. Price at time of purchase is recorded so a repricing run mid-checkout does not change what the customer agreed to.
One wrong multiplier across a catalogue is a commercial emergency. A restore point before each run makes it reversible.
The failure is not a slow page. It is a shopper who added something at one price and is charged another, because the page and the database disagreed about when the figure was set.
Any store can cache a price for a day and be fast. Here that produces a figure the business no longer stands behind.
Every row follows from prices changing far faster than the cache lifetimes most stores use.
| Setting | What we do | Why |
|---|---|---|
| Priced page lifetime | Hours rather than days, purged on repricing | A price cached for a day can be materially wrong before somebody checks out, which is a figure the business is then asked to honour. |
| Repricing runs | Resumable and applied atomically per product | Updating an entire catalogue happens often here, and a run that stops half way leaves the store selling at two different vintages of price list. |
| Instalment totals | Computed per request rather than cached | Instalment plans vary by card and term, so a cached total quotes one shopper the arrangement that belongs to another. |
| Price at purchase | Recorded with the order and honoured | A repricing run landing mid-checkout must not change what the customer agreed to, and only a recorded figure can prove what that was. |
| Pre-reprice restore point | Taken before each catalogue run | A wrong multiplier applied across every product is a commercial emergency, and reverting is faster than recalculating. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Move the store across — migration is free, repricing runs reviewed.