Errors & troubleshooting

Matat shows messages in a banner at the top of the screen. Most are harmless and self-explanatory; this page explains the rest, grouped by what's really going on.

ℹ️ How to read a message

A message that ends in a colon — like "Pull failed: …" — is wrapping the exact words your ERP or Shopify sent back after the colon. The part before the colon tells you which step failed; the part after is the underlying reason. Both are useful when contacting support.

Setup & configuration

MessageMeaning & what to do
ERP not configuredYou haven't connected an ERP yet. Go to Settings and set it up.
Connection test failed: …
Credentials / API URL / Chain ID not configured
Matat couldn't reach your ERP with the details given. Re-check the address and credentials, then Test connection again.
No active location mappingStock can't sync until a warehouse is mapped to a store location. Open Locations and set one up.
No ERP locations discovered yet — click 'Discover ERP locations' firstPress Discover ERP locations before mapping.
Unknown ERP location code … / Unknown ecommerce location id …A mapping points at a warehouse or store location that no longer exists. Re-open Locations and fix the mapping.

"Already running"

MessageMeaning & what to do
A sync is already running — wait for it to finish
A catalog sync is already running
An image pull is already running
Only one of each job runs at a time. Wait for the current one to complete (watch the progress bar); then try again.

Can't reach your ERP

These mean your ERP was briefly unreachable, slow, or returned an error. They're usually temporary — run the sync again. If they persist, your ERP may be down or its credentials may have changed.

MessageMeaning & what to do
… request timed out after NsYour ERP didn't respond in time. Retry; if your ERP is slow, try again off-peak.
… request failed: … / … API error: HTTP … / … returned non-JSONYour ERP rejected or malformed the request. Retry; if it continues, share the message with support.
ERP fetch failed … / all-products fetch failed … / stock fetch failed …A specific read from your ERP failed. Retry the action.

Shopify communication

These happen while sending data to your store. Many are transient (retry works); a few point to a product that needs attention.

MessageMeaning & what to do
GraphQL error / errors: …
Failed to create product / Failed to update product: …
Shopify rejected the change. Often temporary — retry. If one specific product keeps failing, its data may be invalid (for example a bad price or an impossible option combination).
productSet / createVariants / updateVariants userErrors: …Shopify refused part of the product or its variants — commonly a duplicate variant combination or an option that doesn't fit the product's structure. See Variants & swatches.
Product … no longer exists in Shopify. Please sync the product again to create it.The product was deleted in Shopify. Re-sync it and Matat will recreate it.
Store bulk query timed out after 20 minutesA very large operation took too long. Retry; for first-time imports of huge catalogs this can take a couple of attempts.
Staged upload failed … / bulk operation … failedA background transfer to Shopify didn't complete. Retry the sync.

SKU & matching

MessageMeaning & what to do
No store product matched <sku>'s SKU(s) — nothing to pull. Is it in the store under the same SKU?(Pull images.) The product's SKUs aren't found in your store, so there are no store images to copy. Usually a SKU mismatch between systems, or the product isn't in your store yet.
<sku> was not found locallyMatat doesn't have this product yet. Run Pull from ERP first.
SKU … not found / product not found by skuThat SKU doesn't exist where Matat looked. Check the SKU is correct and present in both systems.
No variant on product matching sku … / sku mismatchThe store product exists but its variant SKUs don't line up with your ERP's. Align the SKUs — see Things to know.
Re-group produced no matching parent for …Matat couldn't rebuild this product from its variants during grouping — usually inconsistent SKUs within a model. Contact support with the SKU.

Variants & swatches

MessageMeaning & what to do
Axis "…" has no swatch metaobject to sync (plain option value)That color/size value isn't a recognized swatch yet, so it shows as plain text. Map it on the Variant attributes screen if you want a swatch.
No platformProductId for sku … — product not yet synced to ShopifyA price/variant change was attempted before the product existed in your store. Sync the product first, then retry.

Orders & refunds

MessageMeaning & what to do
Already synced — ERP doc exists / Order is not in a syncable stateThe order is already in your ERP or is mid-sync. No action needed.
Original order … not found locally — sync the order first
… has no ERP invoice yet — sync it before refunding
You can only push a refund after the original order has been synced to your ERP. Sync the order, then push the refund.
No … product id for SKU(s) … — run a catalog sync or create the product(s)The order contains items your ERP doesn't know yet. Run a catalog sync (or add the items in your ERP), then retry the order.
No forwardable lines …The order had nothing to send to the ERP (for example only a shipping charge, with no shipping product configured). Usually safe to ignore.

Not supported by your ERP

These aren't faults — they mean the feature simply isn't available for the ERP you've connected. Different ERPs expose different capabilities.

MessageMeaning
… does not support time-filtered fetches — leave the "since" date blankYour ERP can't filter by date. Clear the "modified since" date and pull the full catalog.
… does not expose a fulfillment feed / order statusYour ERP can't report shipping or order status back, so those syncs are unavailable.
Refunds / customer search / customer tiers not supported
pushOrder / pushCustomer / pushRefund not yet implemented
That direction of sync isn't available for your ERP yet. Handle it manually in your ERP for now.

Store writing paused

MessageMeaning & what to do
Store sync disabled — nothing pushed to ShopifyThe master pause on store writing is on, so pushes are blocked (pulling data and images still works). Ask your Matat contact to resume store writing when you're ready to publish changes.

Input mistakes

MessageMeaning & what to do
Invalid date: "…". Use YYYY-MM-DD.Enter the "modified since" date in year-month-day form, e.g. 2026-01-31.
Map at least one ERP store to an ecommerce location.
Mark only one mapping as the default.
Location mapping rules — map at least one warehouse, and pick exactly one default.
Missing sku / Invalid mappings payload / Missing mappings payloadA required value was missing from the form. Re-enter it and try again.
💬 When to contact support

If a message keeps coming back after a retry, note: the full message (including everything after the colon), the product SKU involved, and what you were doing. Share that with your Matat contact. A built-in assistant that can look these up from your live data is coming soon.