How syncing works
What actually happens between pressing Pull from ERP and your store being up to date — and why it's safe to run as often as you like.
The sync, phase by phase
A full Pull from ERP moves through these stages — the progress bar names the one it's on:
- Fetching Matat reads your full catalog from your ERP.
- Detecting changes It compares each item against what it synced last time and ignores anything unchanged, so only real differences are processed.
- Grouping Related items are combined into products with options (see Variants & swatches).
- Matching & submitting Each product is matched to the one already in your store, then created or updated.
- Inventory Stock levels are set at your mapped location.
- Swatches Color/size options are linked to their storefront swatches.
- Images Product images are reconciled.
You can close the page — the sync continues on the server and the status updates when it finishes.
Matching: how duplicates are avoided
Before changing anything, Matat works out whether each product already exists in your store. It does this by looking the product up live, by its variant SKU, rather than trusting a possibly-outdated local record. This matters: if a product was deleted and recreated in Shopify, or re-coded, the live lookup still finds the truth.
To keep this fast on large catalogs, Matat also keeps a lightweight SKU snapshot of what's in your store, so it can decide "new vs existing" for thousands of products quickly without a heavy query each time.
Create vs update
Based on that match, each product takes one of two paths:
| New product | Existing product | |
|---|---|---|
| Action | Created in your store | Updated in place |
| Status | Added as Draft | Status left exactly as you set it — never demoted |
| Variants | All created | Matching SKUs updated, new SKUs added, extras kept |
| Description / images you added | — | Never overwritten |
The update path only touches what came from your ERP (price, stock, variant set). It deliberately leaves your descriptions, publish status and self-uploaded images alone.
Bulk operations & progress
When there are many new products, Matat hands them to Shopify as a single bulk operation rather than one-by-one, which is far faster and gentler on Shopify's limits. Matat then polls that operation until it finishes and reports the result on the progress bar. Very large first-time imports can take a while; a bulk operation is allowed up to around 20 minutes before Matat considers it timed out and asks you to retry.
Inventory
Stock is handled separately from product details, by its own precise operation that sets the available quantity at your mapped location. Because it targets only the inventory number, a stock update never risks changing anything else about a product. That's why Refresh stock is quick and safe to run on its own.
Images
Image syncing is additive. Matat keeps a record of your product images and can add new ones from your ERP, but it does not remove images you uploaded yourself in Shopify. Pull images from store copies what's already on your store products into Matat so nothing is lost on future syncs.
Why it's safe to re-run
- No duplicates — every product is matched to the existing one before any change.
- No un-publishing — existing products keep the status you gave them.
- No lost edits — descriptions, images you added, and publish state are yours.
- No lost variants — Matat never deletes variants automatically.
Running a sync twice with no ERP changes does effectively nothing, because the change-detection step finds nothing to do.