Acumatica–Shopify Two-Way Sync for CPG Manufacturers Expanding Into Ecommerce

What this looks like in consumer packaged goods

A manufacturer previously sold cases through account managers. Its new Shopify store sells individual bottles and starter kits. The ERP item catalog uses stock codes and warehouse units, while the storefront uses customer-friendly names. A purchase of two kits must not become two cases or bypass the manufacturer’s established release process.

Records, ownership, and update rules

Work through the process

1. 01
   Inventory the endpoint contract

   List the Acumatica entities actually exposed by the tenant and identify custom fields needed for channel references. Validate their read and write behavior with the ERP administrator before assuming a stock-code match is sufficient.
2. 02
   Separate catalog language from identity

   Keep Shopify titles and merchandising options editable by ecommerce while preserving stable ERP codes. Version the crosswalk when a kit changes; do not rename an ERP item to solve a storefront presentation problem.
3. 03
   Choose the first order path

   Start with a simple paid DTC order and its corresponding approved ERP transaction. Define how guest customers, shipping charges, and tax evidence will be represented before adding wholesale or complex bundles.
4. 04
   Control operational release

   Confirm where orders wait for stock, payment review, and quality approval. Product and order sync can supply the context, but only the approved release workflow should instruct downstream fulfillment.
5. 05
   Order one starter kit and trace it into Acumatica

   Buy one starter kit in the Shopify test store and follow it into Acumatica. The sales order must list the approved component stock items and quantities for that kit, not one line under the marketing name or a case quantity. Rename the kit and edit its description in Shopify, then confirm the Acumatica stock item references did not change. Mark one component inactive in Acumatica and order the kit again: the affected line must stay unresolved and flagged for product operations. Stop the rollout if the kit expands to the wrong quantities, if a title edit alters the ERP mapping, or if a look-alike replaced the inactive item.

Handle the exceptions explicitly

ERP item is inactive

Hold the mapping and ask product operations to select an approved replacement; do not silently substitute.

Kit contains an unavailable component

Retain the original customer purchase and route the allocation decision to fulfillment.

Tenant has a customized entity

Scope that entity and operation explicitly rather than assuming a generic connector exposes every field.

What to verify before expanding

• A test kit resolves to the approved component quantities.
• Customer-facing descriptions can change without breaking the stable ERP mapping.
• An inactive ERP item leaves the affected storefront line unresolved rather than selecting a similarly named replacement.
• The pilot demonstrates the required operation against the tenant's actual endpoint and custom fields, with rejection remaining visible.

Technical references

• Stacksync two-way sync quick start
• Stacksync Shopify supported objects
• Shopify product variant model