Acro Commerce

Connector errors

“Sync ID is not found for the record” on Shopify price list sync

Acumatica’s Price List sync to Shopify has hit a record that has no Shopify sync ID, which means that record has never successfully synced to the store. The usual cause is a stock item on the price list that is inactive or has not been exported yet, and in the community thread that names this message the poster also had upstream failures on the Companies entity blocking the chain.

What does “Sync ID is not found for the record” mean?

Every record Acumatica has successfully pushed to Shopify carries a sync ID, which is the connector’s record of the Shopify-side identifier it maps to. This message says the connector went looking for that identifier on a record it needs and did not find one. In practice, the record has never landed in Shopify.

It shows up on the Price List entity more than anywhere else because a A price list is a named set of prices that can be attached to customers, groups or currencies. ERPs and commerce platforms both use the term, and they rarely mean exactly the same thing by it. is a dependent object. It references stock items and it references customers or price classes, and it cannot be created in Shopify until the things it points at already exist there.

Checked against: Acumatica community 22606: error on Shopify price list sync, read 20 August 2026

What actually causes it?

Two things, and they stack. The answer accepted in the thread is to "ensure all the Stock Items in the price list you are trying to export have a status of Active and are already synced to your Shopify store". A single inactive or unsynced item on a list of four thousand will fail the export, and the message names the sync ID rather than the item, which is why this one costs people an afternoon.

The second cause is upstream. The poster in the thread reported "a few issues with our Companies entity sync", and resolving those errors and resyncing "got us further along in the process". The Price List entity sits downstream of Companies, so a Companies failure surfaces here as a missing sync ID rather than as a Companies error.

Worth knowing about the entity generally: the Price List entity does not fire on every price change. You prepare and process it, manually or on an automation schedule, which for most sites means overnight. So a price you changed this morning is not the record that failed tonight.

Checked against: Acumatica community 22606, accepted answer, read 20 August 2026, Acumatica community 11823: price lists are prepared and processed on a schedule

How do you clear it?

Work upstream to downstream. Fixing the price list first is the intuitive move and it is the wrong order.

  1. Open the sync status for the Companies entity and clear every error there before you touch the price list. Downstream entities inherit those failures without naming them.

  2. Confirm the Customer and Stock Item entities have synced cleanly, in that order.

  3. Export the stock items on the failing price list and filter for anything not Active. Those are your candidates.

  4. For each candidate, check it has actually synced to Shopify and not merely been marked for export. Marked and synced are different states and only one of them produces a sync ID.

  5. Prepare and process the price list again. If it now runs, put a check on item status into whatever process adds items to price lists, because this will recur otherwise.

Checked against: Acumatica community 22606, read 20 August 2026

Which release is this, and what if it comes back?

The thread does not name an Acumatica release, so we will not invent one. The dependency behaviour it describes has been consistent across the releases we have looked at, but the Commerce Connector changes across Acumatica’s two feature releases a year, so verify on your own version.

If it returns on a schedule rather than once, the cause is almost always new items entering price lists faster than they enter Shopify. A weekly price-list update that includes items added to Acumatica that morning will fail every week for the same reason, and nothing in the error text will tell you the pattern.

A different thing to rule out, if you are on Shopify Plus and the message is accompanied by an access error rather than a sync ID error, is a permission scope. “Access Denied for publicationCreate field” on price list sync is a separate documented failure with a different fix, which is reinstalling or recreating the app rather than cleaning your data.

Checked against: Acumatica community 22625: Access Denied for publicationCreate field on Shopify Plus price list sync

Common questions

Which record is “Sync ID is not found for the record” actually talking about?
A record the price list depends on rather than the price list itself, most often a stock item that is inactive or has not yet synced to Shopify. The message names the missing sync ID and not the offending item, so you have to find it by filtering the items on the list by status and sync state.
Does one bad item fail the whole Acumatica price list sync?
Yes, in the behaviour reported in the community. The accepted answer is to ensure all stock items on the price list are Active and already synced before exporting, which implies the export is evaluated as a unit. Plan for a validation step on the Acumatica side rather than discovering it item by item.

Last updated 2026-08-20. Facts on this page last checked against source 2026-08-20.