Nothing to migrate
PrestaShop stays the source of truth for your storefront. We mirror it; we never take it over.
Synchronisation
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.
1
Install the module
2
First full import
3
Incremental every 15 min
4
Write back on demand
Fast, because it is local
Reports run against a local Postgres copy, so a year of orders answers in seconds rather than timing out.
Per-product VAT
Tax is read per product from your tax rules, not assumed for the whole catalogue — the difference between a right price and a plausible one.
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
| 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 |
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.
Net price
153.18
153.18
VAT
11%
11%
Discount
11% from 10
11% from 10
Stock
240
236
What the mirror actually covers
- 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
In practice
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.
- Open the product here and read the price, the VAT rate and any discount on it.
- Compare it against what the shop is serving right now — the two sides side by side.
- If they differ, the comparison says which field and by how much.
- Check the sync history for that feed: stale data and a genuine mismatch look identical until you do.
- Re-sync that entity, or fix the rule, and compare again.
Net price
1,050.46
1,050.46
Discount
23%
23%
Price shown
808.85
808.85
VAT group
11%
21%
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.
See it against your own catalogue
Tell us about your shop and we will set up an instance for you. You will be looking at your own products, not a demo dataset.
Request access
No card. No obligation.