Matrix items missing from an Acumatica Shopify sync

The template lands and the variants do not. In the Acumatica community thread that documents it, the poster described matrix items missing from Shopify "even though the template and the matrix items are all active with inventory available", and gave the specific pattern: "the smallest size variant successfully is loaded to Shopify, then the remaining matrix items/variants do no show up on Shopify".

The error itself appears in the Product Availability sync history rather than against the template item, which is why it is easy to miss. If you are only watching the template item entity, this failure is invisible to you and the first report comes from a customer who cannot find a size.

Acumatica employees in the thread named both before the issue was escalated, and they are quick to check.

First, Export to External System. Every missing variant needs that flag set. It is per item, it is easy to miss on items created after the template was first set up, and it produces exactly this symptom: some variants present, others silently absent.

Second, entity order. The Product Availability entity depends on the TemplateItem entity, so when matrix items change you have to sync the template first. Running availability against a template Shopify has not seen in its current shape gives you variants with no product to attach to.

Then you are probably looking at the defect. In the same thread, after the configuration checks were exhausted, Acumatica support concluded that "it needs a bug fix in th Shopify connector" and the issue was escalated for a product-level fix. No permanent fix was available at the time of the thread.

The workaround the poster found was partial and honest about being partial: "deleting and saving the sync record does help for an immediate solution. The error often comes back though". If you are doing that weekly, you have a recurring defect and not a configuration problem, and the right move is a support case with your own reproduction rather than more cleanup.

Open the case with the specific pattern. Which variants land, which do not, whether it is always the same ones, and whether the template item entity reports clean while Product Availability reports an error. That combination is what makes a support case actionable.

The thread does not name a release, which matters here more than usual because the resolution status was "escalated for a fix". A defect awaiting a fix in one release may be closed in the next, so check the release notes for your version and re-test before you assume this page still describes your situation.

Two adjacent failures produce a similar-looking symptom with a completely different cause. If the template item itself refuses to sync with "At least one option value is duplicated", nothing downstream will land, and the cause is duplicate attribute value descriptions rather than anything about the variants. If it refuses with the three product options message, the template has the wrong number of variant attributes.

And if all the variants are present but in an order you did not choose, that is the connector re-sorting variants by Option1, Option2 and Option3 on every template sync, which is documented behaviour rather than a fault.