Push

A push is the PIM sending one of your products out to a connected integration, which happens on its own a few seconds after you save an edit.

A push is the PIM sending one of your products out to a connected integration, so what sells there matches what you typed here. You never start one. You edit a product, you save, and a few seconds later the PIM writes that product to every integration that can take it.

That is what keeping a catalog in one place buys you. You fix a price once and every store you sell on gets the new one, instead of opening one admin panel after another and hoping you did not miss the last. A push sends the thing you changed along with everything else that integration accepts, so a listing is never left half updated.

There is no Push screen. You watch a push from the row of integration logos at the top of the product editor, next to the title. Hover over one and a small panel opens with that account’s status and its timestamps. Inside that panel is a switch called Sync, and it decides whether your product publishes there at all.

That switch is the only thing on a product you use to steer a push. Everything else on this page is the PIM working while you do something else, and what it tells you when it does.

Before you start

Roles are set in team, roles and permissions.

How to take one product off one integration

1. 1

   Open the product

   Go to Catalog in the sidebar, which opens on the Products table, and click your product’s row. The editor opens, and along its top row, beside the title, is one logo for every integration you have connected.

2. 2

   Open the integration's panel

   Hover over the logo of the integration you want to change. A panel opens listing every account you have on that integration, each with its own status.

3. 3

   Turn the switch off

   The switch labeled Sync is next to the account’s name inside the panel you just opened. Click it.

4. 4

   Say what happens to the live listing

   If your product is already published on that account, a dialog opens asking whether to stop syncing with it. Pick one of the answers it gives you and click Stop syncing.

That is the whole flow. The badge on that logo reads Removing… while your listing comes down, then settles on Sync off, and a small message says Syncing disabled. Turn the same switch back on and your product publishes again, with nothing to confirm.

Everything below explains what starts a push, what each integration gets, and what the badge is telling you. You do not need any of it to publish, because publishing is what already happens when you save.

Every option in detail

What starts a push

Editing any part of a product starts a push. The parts are wider than the product form. Each one queues your product on every integration that can take it.

Two other things you click start a push as well. Turning a product’s Sync switch on publishes your product to that account right away. Saving an account’s settings gives you Re-sync now, which queues every product already on that account at once, and settings covers what that costs you.

A push can also start with no one clicking anything. Each time an integration finishes reading, it queues every product of yours whose SKU is missing over there. That is how your catalog turns up somewhere without you editing a thing. Amazon is the one that never does it, and integrations explains why.

How long an edit waits

Every edit of yours waits 5 seconds before it goes anywhere, and each new edit restarts the wait. So 10 changes to one of your products inside a minute produce one push, 5 seconds after the last of them. A burst of your typing should not become a burst of writes on a live store.

Both of those skip the wait. A switch you turn on and a Re-sync now you confirm are queued immediately.

What stops a push before it starts

Three things have to be true at the moment you save, or nothing is queued at all.

None of the three tells you it happened. The badge is where you notice, and an account state that is stopping everything shows up on the integrations screen, not on the product.

Reading the panel behind a logo

Hovering one of the integration logos at the top of the product editor opens the same panel for every integration. It is the only place your push reports on itself. One section per account, so a store you connected twice gives you two.

Click the logo instead of hovering it and your product opens in that integration’s own admin, in a new tab. That is where you edit the listing on the integration’s own side. A product of yours that has never been pushed has nothing to open, and the logo does nothing.

Reading the badge

A colored dot appears on each of those logos at the top of the editor, and its label is the first line of the panel you open. These are the ones a push produces.

A logo with several accounts behind it shows you the worst of them, so a green dot means every account is clean and one red account turns the dot red. Open the panel to see which one it is.

Turning Sync off, and what the dialog asks

The Sync switch is beside an account name in the panel behind an integration logo, and it starts on everywhere. An account you have never touched gets your whole catalog, so this switch is only ever something you turn off.

The dialog only opens when your product is genuinely live on that account. Switching off something that never went to the integration asks you nothing, and neither does switching one on.

It names the integration and the account, so you know which of your stores you are about to change, and it gives you up to three answers as radio buttons.

The answer that arrives pre-selected is the one that account is already set to use. It comes from When a product is deleted in the account’s settings. So an account you set to archive pre-selects Archive it, and one no one has touched pre-selects Delete it. Change it in settings and you change what this dialog picks for you first.

You only get the answers that integration actually runs. Amazon has no archived state for an offer, and Google has none either. Both give you two answers instead of three, and neither adds a third that would delete with no warning.

Once you confirm, the badge goes to Removing… and a message reads Syncing disabled. Only one switch works at a time: while one is saving, the others in your panel are locked until it finishes.

Turning Sync back on

Turning it back on queues your product for that account immediately and asks you nothing. If the removal has not finished yet, turning the switch on cancels it and your product is republished instead.

Nothing announces the cancellation. Your badge simply stops reading Removing… and moves to Pending update or Pending creation.

Taking a whole selection off at once

Select rows in the Products table under Catalog and a button called Update integration sync appears in the bulk toolbar along the bottom of the page. It also appears on the Brands and Categories tables, and only when one of your connected integrations can actually take that kind of record.

The dialog gives you one row per integration, because being published is a per-integration question: the same product can be live on one store and never pushed to another. Each row has three choices.

A row shows you a count only once you have chosen something, reading how many of your items will start or stop syncing. Leave unchanged shows nothing, because a decision you have not made has nothing to count. Apply stays off until you touch at least one row.

Switching a brand or a category off

Open a brand or a category from Catalog and the same switch is there, in the same panel behind the same row of integration logos. It works the same way with one difference: you get one answer, Delete it. The record the PIM created over there has no life of its own, so there is nothing to archive.

It also appears on fewer integrations, because an integration has to have that kind of record before there is anything to switch.

Where a cell says no, the integration has no such record. Amazon treats a brand as one attribute on a listing, and Square does the same, so brands works through what yours becomes on each one.

Limits

What a push cannot do

What each integration gets

What an integration keeps decides the shape of your push. An integration that stores product content gets your product itself. One that sells against a listing someone else owns gets your offer against that listing. One that only advertises gets an offer that has to be complete on its own, because there is nothing over there to fall back on.

Shopify takes one product at a time. Each edited product is its own write, so one product being rejected leaves the rest of your catalog moving.

BigCommerce, Square, Amazon and Google gather an account’s pending work and send it together. That is why a rejection shows on one badge instead of stopping everything behind it.

Square takes the whole item and all of its variations in one write. That write replaces the variation set, so a variation you deleted here disappears there too.

Google rejects an incomplete offer before it sends one. It needs a title, an image, a price, a usable SKU and an address on your own website. An offer missing any of them is kept back, with the reason on your product. Google would otherwise accept it and reject it minutes later, where you cannot see.

Where your brands and categories go

A brand and a category of yours can go out as records of their own. Shopify gets a collection for each. BigCommerce gets a real brand and a real node in its category tree. Both are pushed and reconciled separately from your products inside them.

Everywhere else they ride inside the product push instead, as an attribute on the listing or as the integration’s own category created alongside the item. Nothing is lost either way, and the difference decides whether you get a record you can open over there.

Two things that are true of every push

Emptying a field in the PIM empties it on the integration. A push does not skip a field you cleared. It sends the empty value deliberately, so a description you deleted here is a description gone there. The one exception is a field the last read had to reject. That one is kept back so your trimmed copy never overwrites the original, and pull explains when the hold lifts.

A push sends the price the account calculates, not the number in your catalog. The price source chain, the adjustment and the MAP floor all run before anything leaves. So two of your accounts can get two different prices for the same variant on the same day, and settings is where you build that chain.

When something goes wrong

A push was rejected

A rejected push never changes your product in the PIM. Your catalog is exactly what you saved, and the only thing that failed is the copy going out.

The badge reads Failed, and the panel behind the logo gives you the reason under Push issues. Fix what it names, save your product, and the next push goes on its own.

The PIM retries a temporary problem for you before it gives up. A store that went briefly unreachable, a rate limit, a request that timed out: your badge stays on Pending update while it tries again. Failed means it stopped trying, so the answer to one is always to change something and never to wait.

Needs attention is the softer version. The push went through and the listing is live, and the integration complained about part of what you sent. Your panel lists those under Advisories.

Every message names the integration that produced it, so you always know which store to open. What each kind of message is asking you to change, and what every integration insists on before it takes a product at all, are worked through in sync issues.

What sends you an email and what does not

A product of yours that fails to publish never emails anyone. The badge is the only place it shows, which matters if you edit in bulk and walk away.

An email arrives when your connection itself is in trouble, and it says the PIM will retry on its own. You control those under Notifications in your settings, in the group named Integrations & Sync, with the switch called Sync errors. Email is the only way the PIM tells you anything, because there is no message center anywhere in the app.

A canceled removal tells you nothing

A removal you cancel by turning Sync back on leaves nothing behind to say it was canceled. Your badge moves off Removing…, and that is the whole of the notice you get.

So check the badge after you flip a switch twice. It is the only place the PIM will confirm which of your two clicks counted.

Where to go next