Celeste library
Commerce connector errors, decoded
One page per error string. What the message means, what actually caused it, which release it appears in, and how to clear it. Written for the person who has just pasted the message into a search box at four in the afternoon.
“At least one option value is duplicated” on Acumatica template sync
Acumatica’s Commerce Connector is refusing to sync a template item to Shopify because an attribute somewhere in your system has two option values with the same description. On Acumatica 2025 R1 it fires even when the item that failed does not use the duplicated values, because the connector validates every description on the attribute rather than only the ones in play.“Shopify supports only up to 3 product options” on template sync
The Acumatica Commerce Connector could not build the Shopify product options for a template item, and the message quotes Shopify’s hard ceiling of three options per product. It fires when the template has more than three variant attributes, and confusingly it also fires when the template has only one.“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.Why did BigCommerce get the base UOM price, not the sales UOM price?
Acumatica exported the stock item’s price for its base unit of measure rather than its sales unit, so an item you sell by the case shows on BigCommerce at the each price. Acumatica stated the limitation in its own community as "only prices defined for the base UOM can be exported to BigCommerce", and put sales UOM support into the core product at 22R2.Matrix items missing from an Acumatica Shopify sync
A template item reaches Shopify but only some of its matrix items arrive, and in the reported case only the smallest size variant loaded. Two configuration causes explain most of these, an unchecked Export to External System flag and a Product Availability sync run before the template item, and the rest is a connector defect Acumatica support acknowledged and escalated.Acumatica template sync keeps reordering our Shopify variants
Acumatica’s Shopify connector re-sorts every variant on a product each time the template item syncs, even when nothing about the variants changed, so any ordering you arranged in Shopify is lost. An Acumatica employee stated in the community that the connector sorts by Option1, then Option2, then Option3, and that preserving your own order requires a customisation.Access denied for paymentTerms field on an Acumatica Shopify sync
Shopify refused the connector’s GraphQL request because the installed Acumatica app does not hold the read_payment_terms access scope. On Acumatica 2025 R1 the reported fix was to reinstall the public Acumatica ERP app in Shopify, which grants the current scope list, and users of a custom app have to add the scope themselves or recreate the app.“You may have reached the API calls limit” from Cin7 Core to Shopify
The message names a Shopify API limit but Cin7’s own help centre documents a different cause: your Shopify product has a default variation whose SKU does not match the SKU in Cin7 Core. Cin7 Core matches the product by name, fails to find the variation by SKU, tries to create a second default variation, and Shopify rejects that because a product can only have one.