Argentine WordPress hosting where a cached price goes stale in days.
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.
The number does not stay true.
Most store tuning assumes a price is stable and a page can be cached for a day. Here the price is the volatile part.
Price caching measured in hours
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.
Repricing the whole catalogue at once
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.
Instalments calculated per customer
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.
A quote that is honoured
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.
Roll back a bad repricing run
One wrong multiplier across a catalogue is a commercial emergency. A restore point before each run makes it reversible.
Caching a moving number.
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.
- Short cache lifetime on priced pages
- Repricing runs resumable and atomic per product
- Instalment totals computed per request
- Price at purchase recorded and honoured
The right number, quickly.
Any store can cache a price for a day and be fast. Here that produces a figure the business no longer stands behind.
What we change for Argentine stores
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. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
How long can I cache product prices?
How do I reprice the whole catalogue safely?
Can instalment totals be cached?
What if the price changes while someone is checking out?
Charge the price you showed.
Move the store across. Migration is free, repricing runs reviewed.