Store sync: how often, what, and when it fails
How often your store's data comes in, what each sync brings, the data health and identity checks, and how to sync again, pause or reconnect.
Once your store is connected — see Connect your online store — Monfri keeps its products, categories, customers, orders and refunds in step. Everything about the connection is in CDP, Commerce → Connections.
How often
- Every 30 minutes Monfri asks the store what changed since the last time: new and edited products, new customers, new orders and changes to old ones, refunds.
- WooCommerce with a Read/Write key also sends orders, customers and product changes the moment they happen.
- Orders placed on the site arrive within seconds anyway, from the Monfri script on the thank-you page. The sync then fills in what only the store knows, such as later status changes.
The connection page
E-Commerce Connection shows the store, the platform and its status — active, disconnected or an error — with Last synced and the last error, if any. Below it: Products, Orders, Customers, Categories and Revenue in the store's currency.
| Button | What it does |
|---|---|
| Sync Now | Brings in what changed since the last sync, right away. |
| Full Re-sync | Reads everything again from the start of the backfill period. Use it after a big change in the store, or when numbers look wrong. It can take a while for a big store. |
| Disconnect | Stops every sync. Are you sure? This will stop all sync operations. The data already in Monfri stays. |
| Reconnect | Starts the sync again after Disconnect. |
Recent Sync Activity lists each sync with what it brought and any errors. Clear Log empties the list.
Data health
Data health (orders: store DB ↔ analytics) compares the orders the store has with the orders in your analytics, every hour for the last 48 hours and once a night for the last 90 days.
| Number | Meaning |
|---|---|
| Store orders | Orders the store has in the window. |
| Analytics orders | Orders your analytics count in the same window. |
| Missing in analytics | Store orders not yet in the analytics. Monfri re-sends them by itself — re-sent shows how many. |
| Extra in analytics | Orders in the analytics that the store does not have in the same window. |
| Revenue Δ | The difference in revenue between the two. Orders edited after the purchase make it move a little. |
A green dot means everything matches; an amber one, that something is worth a look.
Identity coverage
Identity coverage (store records ↔ CDP profiles) shows how many of the store's people are linked to a customer profile in CDP:
- Orders with a profile and Orders, last 30 days — orders whose buyer has a profile;
- Customers with a profile — store customers linked to a profile;
- Checkout → identified (30d) — of the visitors who reached the checkout, how many the script could recognise.
Records not linked yet are linked after every sync. A low Checkout → identified usually means the store's checkout changed and the script no longer sees the e-mail there — write to [email protected]. How profiles are linked: How Monfri recognises a visitor.
If something doesn't work
Sync failed, or an error under Last synced
Usually the key: it was revoked or replaced in the store, or the store blocks our requests. Create a new key and connect again from Connections.
Connection is disconnected
Sync operations are paused. Reconnect to resume. Someone clicked Disconnect. Click Reconnect.
New products or orders do not show
Wait for the next sync — at most 30 minutes — or click Sync Now.
The revenue differs from the store's report
See E-commerce analytics: revenue, orders and conversion — the two count in different ways, and Data health shows the difference.