Things to know
A few situations are worth understanding up front, so nothing catches you by surprise. Each one below explains what happens and what you can do.
New products start as drafts
Anything created from your ERP arrives as Draft and won't appear on your storefront until you publish it. This is deliberate — it gives you a review step. If you'd like a product live, open it in Shopify and set it to Active.
Discontinued items are archived, not deleted
When a product disappears from your ERP, Matat marks it Archived in your store rather than deleting it. Your history and any links stay intact. You can delete it yourself in Shopify if you're certain you won't need it again.
Products are matched by SKU
Matat links each ERP item to the right store product using its SKU. This works perfectly when the same product uses the same SKU in both systems.
If the same product is coded differently in your ERP and your store, Matat can't tell they're the same item — it may create a second copy, or skip it when mirroring images. The fix is to use matching SKUs in both places.
Variants must line up to match
Matat matches at the individual variant level. If your store models a product with fewer or different options than your ERP (for example, the store version doesn't break out color while your ERP does), some variants won't line up. The product still works — but those variants may not be matched for updates or image mirroring. Keeping the variant structure the same on both sides avoids this.
Store-only products without SKUs
Products you created by hand directly in Shopify, with no SKU, can't be matched to anything in your ERP — there's nothing to match on. That's expected; Matat simply leaves them alone.
Your images are safe
Matat mirrors images and can add new ones, but it won't remove images you uploaded yourself in Shopify. If you ever see an image missing, it wasn't Matat.
Syncing needs your ERP online
A sync reads live from your ERP. If your ERP system is unreachable or down for maintenance, the sync will wait or report an error — simply run it again once your ERP is back.
Pulling can also push
Pull from ERP both fetches and sends changes to your store. If you ever want to refresh your ERP data in Matat without touching your storefront, store writing can be paused — ask your Matat contact to enable that mode, then re-enable publishing when you're ready.
If something doesn't look right, note the product's SKU and what you expected to happen, and reach out to your Matat contact. An in-app assistant that can answer these questions from your live data is coming soon.