Your shop, mirrored — not migrated
A small module on your PrestaShop keeps a full local copy of products, prices, combinations, customers, orders and carts. Your shop stays exactly where it is and keeps serving customers.
- Nothing to migrate PrestaShop stays the source of truth.
- Fast, because it is local A year of orders answers in seconds.
- Per-product VAT Read per product, not guessed per shop.
| Feed | Last run | Records | Status |
|---|---|---|---|
| products | 2 min ago | 8,308 | ok |
| orders | 2 min ago | 246,770 | ok |
| carts | 14 min ago | 1,601 | ok |
| customers | 2 min ago | 52,114 | ok |
It tells you when it is behind
Every feed carries a watermark and a run history. When something is stale you are told which feed, when it last ran and what failed — not left to guess from data that looks thin.
- Watermarks per entity, with the last run and its result
- Failed rows counted as failed, never as skipped
- Start a sync yourself instead of waiting for the schedule
Nobody types a catalogue twice
The usual way into a new tool is to export the shop, clean it, import it — and find out three weeks later that the prices moved while you were doing it. Nothing here is typed twice. A small module on your PrestaShop sends the catalogue over, and then keeps sending it.
When a price looks wrong at four o’clock on a Friday
The catalogue says one thing, the storefront says another, and somebody is on the phone. This is the sequence that ends it in about a minute.
-
1
Open the product here and read the price, the VAT rate and any discount on it.
-
2
Compare it against what the shop is serving right now — the two sides side by side.
-
3
If they differ, the comparison says which field and by how much.
-
4
Check the sync history for that feed: stale data and a genuine mismatch look identical until you do.
-
5
Re-sync that entity, or fix the rule, and compare again.
More than a copy of your catalogue.
One mirror, kept current, that every screen in the tool reads from.
And it checks itself against the shop
One screen puts our copy of a product beside what PrestaShop actually serves — price, VAT, discounts, quantity thresholds. Two silent bugs lived for months in this product because nothing ever compared the two sides. Now something does.
What the mirror actually covers
- Merchandising: the order products appear in, set here and pushed to the shop
- Combinations as a grid — every size and colour of a product priced in one view
- Products, with descriptions, references, EAN and images
- Prices: base, tax-inclusive, cost, and every specific price
- Combinations and their attribute impacts, both PrestaShop pricing models
- Customers, their groups and every address on file
- Orders with their line items, statuses and full history
- Abandoned carts with their contents and how far the person got
- Vouchers and basket rules, live and expired
- Categories with their full tree, manufacturers and carriers
- Stock per product, with movements over time
- Tax rules and per-product VAT groups
- Incremental every fifteen minutes, or on demand
- A full re-import whenever you want one
The mirror, on screen
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
How long does the first import take?
Minutes for a few thousand products, longer for a very large catalogue with images. It runs in the background and you can watch it arrive.
Does it slow my shop down?
The module reads in pages, on a schedule you control. A shop serving customers does not notice it; if you want it gentler, raise the interval.
What if I change something in PrestaShop directly?
The next incremental run picks it up. PrestaShop stays the source of truth — we follow it, not the other way round.
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.