Settings reference
Everything you can configure, grouped by the screen it lives on. Connection fields differ per ERP; the rest work the same whichever ERP you've connected.
ERP connection
Settings → ERP connection. This is where you tell Matat which ERP you use and how to reach it. Pick your ERP from the list and fill in the connection fields — these are specific to each system (for example an API address, an API key, or an app id/key pair). Every field shows its own help text in the app.
Press Test connection to confirm Matat can reach your ERP before saving. Press Save to store the configuration; you'll see "<your ERP> saved".
| Field type | What it's for |
|---|---|
| Address / endpoint | Where your ERP's API lives, so Matat knows what to connect to. |
| Credentials (key, app id/key, username/password) | Authenticate the connection. These are provided by your ERP or your Matat contact. |
| Store / warehouse identifiers | Scope which store or warehouse Matat reads products and stock from. |
| Currency | The currency your ERP prices are in. |
A few settings — notably the variant grouping strategy below — can't be changed after you save them, because they decide how products are identified in your store. Changing them later would orphan everything already synced. Choose carefully the first time, or ask your Matat contact.
Variant grouping strategy
Only some ERPs expose this. It controls how individual items are combined into one store product with options:
- By model tag — items are grouped using a "model" field your ERP provides.
- Derived from SKU — the model is worked out from the SKU itself (the shared part of the code), for ERPs that don't fill in a model field.
This determines the parent product each variant belongs to, so it is locked after the first save.
Location mapping
Settings → Locations (also part of onboarding). Stock in your ERP lives in one or more warehouses; your Shopify store has one or more locations. Mapping tells Matat where each warehouse's stock should land.
- Discover ERP locations Press this to pull the list of warehouses from your ERP. You'll see "Discovered N ERP location(s)". If your ERP has no location API, Matat uses a single default store.
- Map each warehouse to a Shopify location Match each one to the store location that should hold its stock.
- Mark one as the default Exactly one mapping must be the default — it's where inventory goes when a product isn't tied to a specific warehouse.
Without at least one active mapping, stock syncs will stop with "No active location mapping". Set this up before your first inventory sync.
Automatic sync
Settings → Auto-sync. These toggles decide what runs on a schedule in the background. With them off, nothing happens automatically — but you can always run a sync by hand from the Products page. Saving shows "Auto-sync settings updated".
| Setting | What it does when ON |
|---|---|
| Product sync | Periodically pulls your catalog and pushes changes to your store. |
| Inventory sync | Periodically refreshes stock levels from your ERP. |
| Order sync | Forwards new store orders to your ERP. |
| Fulfillment sync | Brings fulfillment/shipping updates back from your ERP (where supported). |
| Sync interval | How often the product and inventory jobs run (e.g. hourly). |
Turning automatic product sync off does not disable the manual Pull from ERP button — that still fetches and pushes on demand.
Catalog options
| Option | Effect |
|---|---|
| Skip out-of-stock products | New products with zero stock aren't created in your store until they have stock. |
| Import only in-stock | Limits the import to items that currently have inventory. |
| Default product category | A Shopify taxonomy category applied to synced products. This is also what lets color/size swatches link correctly — see Variants & swatches. |
Pause store writing
There is a master switch that stops Matat from writing anything to your Shopify store, turning the app into read-and-import-only mode. It's useful while you're reviewing data, testing, or rebuilding your catalog.
- When paused, product and inventory pushes are blocked — both automatic and manual. A push will report that store sync is disabled and nothing happens.
- Pulling images from the store still works while paused, because that only reads from your store.
This master pause is managed by your Matat contact (it's an app-wide safety control, not a per-click toggle). Ask them to pause or resume store writing when you need it.
Payment provider
If order sync is used, a payment-provider setting helps match how payments are recorded between your store and your ERP (so invoices/receipts reconcile). You can remove or change it from Settings; removing it shows "Payment provider removed". Most catalog-only setups don't need this.