Integrations
Sync issues
A product can look finished in your catalog and still be missing from an integration, and this is where the PIM records the reason and what to change.
A sync issue is the PIM telling you that one of your products did not get to one of your integrations, or got there and came back with a complaint. Every issue is about one of your products on one account, and the PIM records it there.
You would come here because nothing announces any of this. A product can be in your catalog looking finished and be missing from a store you sell on, or be live there with no price. The one sign is a colored dot, and this page is how you read that dot, find the sentence behind it, and work out what to change.
Everything you need is on the product. Open one from Catalog and a row of integration logos runs along the top of the editor, beside the title, one logo for each integration you have connected. Each logo has a small colored dot, and hovering it opens a panel that tells you in words what the color meant.
The same row of logos is on a brand and on a category too, so everything below reads the same way when you open one of those.
Before you start
Roles are set in team, roles and permissions.
Nothing emails you when one product fails to publish. A product can stop selling on one integration and stay that way until someone opens it and looks at the dot.
How to find out why a product is not on an integration
Open the product
Click
Catalogin the left sidebar, which opens on theProductstable, and click the row of the product you are checking. The editor opens with a row of integration logos along the top, beside the title.Find the dot that is not green
Each logo has a small colored dot in its corner. Green means that integration has nothing for you. Red and orange are the only two that need you, and they are the ones worth opening.
Open the panel
Hover over that logo. A panel opens with one section for each account you have on that integration, and the first row of every section,
Sync status, spells the color out in words.Read the reason
Under
Sync status, the panel tells you what happened. APush issuesrow means part of what you sent could not go out. ARestrictionsrow means a rule on the integration is stopping the product. AnAdvisoriesorPull errorrow means the integration sent you something back.Change what the message names, and save
Fix the field the message names, anywhere in the product editor, then click
Save. Saving queues your product again on every integration, and the badge moves on its own.
That is the whole flow. Most sync issues are one field on one of your products, and saving is the whole of the retry, because there is no button anywhere that tries the same push again.
Everything below is the full list of what the badge can say. It also covers what each kind of message asks for, and where to go when the answer is not on your product. You do not need any of it for a message that names a field.
Every option in detail
What the color of the dot means
The dot is the fastest thing to read on your product, and five colors is the whole vocabulary.
Only one state shows at a time, and the panel picks the most serious one it has. So an orange state can be waiting under a red one and only appear once you clear the red one. Fix what the panel shows you, save, and look again.
A logo covers every account you have on that integration, and its dot shows you the worst of them. Two Shopify stores where one is clean and one is failing give you a red dot, and the panel underneath has a section for each so you can tell which.
Blue and gray are the states where the PIM is working or has been told not to. Push lists all of them, along with what puts a product into each.
The states that ask you to change something
These are the red ones. Your product is not selling on that account until one of them clears.
The last two are about the connection and not about your product. Every product on that account is stopped the same way, and none of them will move until you fix the account.
The states that are only a warning
These are the orange ones. Your product is live, and something about it is not what you sent.
An orange badge is worth reading and is rarely urgent enough to drop everything for. The common one is a price. An account whose price sources resolved nothing keeps the price it already had, so your listing stays live at the old number. The panel is where you find out the new one never went.
Which integrations can say a listing needs attention, and which can reject one
Only two of them report back on a listing at all, and they are the two where someone else decides whether your product is shown.
On Amazon the panel’s Variant status row gives you the state of each variant: Live when it is visible and can be bought, Not buyable when shoppers can see it and cannot buy it, Not searchable when they can buy it and cannot find it, Inactive when neither is true, and Unknown when Amazon describes nothing. None of them turns your badge orange on its own, because each one says where your offer stands rather than that something is wrong. Amazon refusing to carry the product at all is what turns it red, as Blocked.
On Google, Limited reads as Listing needs attention and Rejected reads as Rejected by the integration. Those two are the only listing states in either product that move the badge by themselves.
Shopify, Square and BigCommerce publish what you send and never report a verdict, so a product of yours is either on them or it is not.
What a message is asking you to change
Every message names the integration that produced it, so you always know which store to open. There are five kinds, and the kind tells you where the fix is.
Read the first word of the message. It tells you whether the fix is yours. A message opening with the integration’s name is that integration rejecting a value, as in a price or a barcode of yours it would not take. A message opening with No price is available or Google requires is your product missing something, and that one is always yours to fill in.
What each integration insists on before it will take a product
Most of your failures are one of these, and each one is the same message every time.
Google’s address comes from the website you set on the account, not from the product, and its message links you right to the account’s settings. Google also rejects an account whose currency is not your catalog’s.
Whichever identifier an account is set to send as its SKU has to have a value and has to be unique. Change which one that is under Choose which identifier the integration receives in settings.
Why a few messages arrive in English on a Spanish app
Most messages are written in the language you are using. A handful are not. Those come from outside the product itself: a brand or a category that failed to publish, and a failure about the connection or the currency.
Those come to you as one English sentence in Push issues. Nothing is wrong with your product when this happens, and the sentence still names what to change.
Pushing again after you fix it
Saving the product is the retry. Change what the message named, click Save, and the PIM queues that product on every integration again a few seconds later. The badge moves to Pending update, then to Synced or back to Failed if your fix was not the right one.
Nothing retries a red badge on its own. The PIM tries a temporary problem several times before it gives up, and a badge that says Failed means it stopped trying. So the answer to a red badge is always to change something and never to wait.
When the fix is a setting and not a field, saving the product is not enough, because the setting decides what the push builds. Open the account from the integrations screen, click Settings, save your change, and answer Re-sync now when it asks. That queues every one of your products on that account, failed ones included. Only an Admin sees that screen.
Seeing how many products are affected
The panel on a product tells you about that one product and nothing else. For a count across your whole catalog, click Reports in the left sidebar and open the Integrations card.
That card only appears once you have connected an account, and only an Admin can open it. The counts are numbers and not lists, so use them to find out whether you have a problem, then go to the products themselves.
Limits
What you cannot do here
What the panel keeps
The panel keeps the last attempt and nothing before it
Every push overwrites what the push before it left on your product. So a product that failed twice for two different reasons shows you the second reason, and the first is gone.
That matters most when you fix one thing and something else fails behind it. A Failed badge that comes right back after your save is usually a second problem. Read the message again instead of assuming your fix did not take.
A message clears itself when the next attempt is clean
Nothing in the PIM clears a message for you, and there is nothing to dismiss. Fix the value, save, and the message goes when the push that follows says nothing about it.
The same is true the other way. A message the integration sent back clears on the next pull that finds the value healthy. So a listing you fixed in Merchant Center or in Seller Central goes green here on the next pull and not before.
When something goes wrong
A red badge that will not clear
Work down these four in order. The first one that applies is your answer.
An orange badge after you fixed it
Save the product again. A warning is written by a push, so it stays on your product until the next push replaces it. A product you edited in another integration’s admin has not had a push since.
If it is still there after a save, read it again. The two warnings that look identical before and after a fix are a price that still resolves to nothing and an image the integration still will not take.
Nothing tells you when it clears
A badge that goes green is the only notice you get, and you have to be looking at the product to see it. There is no message anywhere in the app, because the PIM tells you things by email and a product that failed to publish sends none.
What does send you an email is the connection itself. Three things come to you that way: a pull that keeps failing on an account, an authorization that expired, and a currency that does not match. You control all three under Notifications in your settings, in the group Integrations & Sync, as Sync errors and Connection issues. You can turn either switch off there.
Where to go next
Push
What starts a push, what each integration gets, and the switch that stops one.
Pull
What comes back the other way, and what each note on a field did to your value.
Settings
The price chain, the identifier sent as a SKU, and the re-sync that reruns them.
Integrations
Reconnecting, pausing and deleting an account, and what each account state stops.