What are the two connectors, and how do they differ?
Acumatica offers a Shopify Connector and a Shopify and Shopify POS Connector, and they are not the same product with a feature switch. The second one brings Shopify POS into scope, which means in-store transactions land in the same Acumatica tenant as web orders. If you sell in a shop or at a counter as well as online, that is the one you need.
The distinction is easy to miss because both appear under the same part of the Acumatica interface and the vendor material discusses them together. Acumatica’s commerce connectors page lists native connectors for Amazon, Shopify including B2B and POS, and BigCommerce, without breaking out which edition or licence each requires.
Checked against: Acumatica commerce connectors page
What does the licence actually gate?
The observation from Acumatica community thread 23200, posted in 2024, is that the option does not render at all without the right licence. The user wrote: “We currently have the Shopify Connector setup and want to start using the Shopify POS. I don’t see the Shopify and Shopify POS Connector option or Custom Connectors option in our production environment”. His test environment had it; production did not.
The explanation given in the thread ties it to the edition: “this is based upon not having the commerce edition license. You would need the prepare data sync and process data sync which would then pull the orders from Shopify into Acumatica which requires the commerce edition license.” He was on Distribution Edition with Shopify added. Once the licence was added the option appeared, in his words “just a little different than our test environment”.
The failure mode here is not an error message. It is an absence. A feature you were told exists is simply not in the menu, and the reason is a licence line rather than a configuration mistake, so the team spends a day looking for a setting that could never have been there.
Checked against: Community 23200: Shopify and Shopify POS Connector vs Shopify Connector
Why does this become a budget problem rather than a technical one?
Because the discovery usually happens after the storefront project is scoped and priced. An Acumatica edition change is a commercial conversation with your VAR and Acumatica, on their timescale, and it is a recurring cost rather than a one-off. It rarely fits inside a contingency line that was sized for development risk.
The asymmetry is what makes it worth writing down. Nothing in the storefront project surfaces this. Your commerce agency does not see your Acumatica licence, your VAR is not necessarily in the room when the storefront scope is agreed, and the connector documentation talks about capability rather than entitlement.
Treat the licence question as a discovery task with a name and an owner, in week one, alongside the pricing test and the availability test. It costs an email and it removes a class of surprise that no amount of good project management recovers from later.
Checked against: Community 23200: Commerce Edition licence and the POS connector, Acumatica commerce connectors page: connectors listed without edition entitlements
What should you ask before you sign anything?
Ask your VAR these in writing, and ask for the answers against your tenant rather than in general. The last one matters more than it looks: a store activated in a test tenant counting toward a licensed store count is a question that has been raised in the Acumatica community and that we have not seen answered definitively, so get your own answer before you spin up three sandboxes.
Which Acumatica edition are we licensed for today, and exactly which commerce connectors does that entitle us to?
Does the scope we have agreed include Shopify POS, now or in the roadmap? If it might, price the edition now rather than later.
How many stores are we licensed for, and does a store connected in a test or sandbox tenant count toward that number?
Is the production tenant licensed identically to the test tenant, feature for feature? Thread 23200 is a case where it was not.
What is the lead time and the annual cost of moving edition, if we find out in month three that we need to?
Checked against: Community 23200: licence added, option appeared
When is the plain Shopify Connector enough?
If you sell online only, with no physical counter and no trade-show terminal, the plain Shopify Connector covers the ground and the edition question may not arise. That is a large share of B2B distributors and it is worth saying so, because the honest answer here is often that you do not need to spend the money.
It stops being enough the moment a physical selling motion appears. Will-call counters, branch pickups and trade shows all end up wanting POS, and they tend to arrive as a request from sales rather than as a planned phase. If any of those exist in your business today, even informally, assume the POS connector is in scope and find out what it costs before you commit to a launch date.
We have not verified the current edition matrix ourselves, because Acumatica does not publish connector entitlements by edition on its commerce connectors page and licence terms change. Treat the 2024 community answer as evidence of the shape of the rule, not as a quote of today’s price list.
Checked against: Acumatica commerce connectors page: connectors listed without edition entitlements
Common questions
- Do I need Acumatica Commerce Edition to use Shopify at all?
- Not necessarily for the plain Shopify Connector. The community case in thread 23200 involved a customer running Distribution Edition with Shopify added, who had a working Shopify Connector and could not see the Shopify and Shopify POS Connector option. The answer given tied the POS connector, and the prepare and process data sync behind it, to the Commerce Edition licence. Confirm the current entitlement with your VAR rather than relying on a 2024 thread.
- Why does the option appear in our test tenant but not production?
- Because the tenants are licensed differently, which is exactly what happened in Acumatica community thread 23200. The user could see the connector in test and not in production, and it appeared in production once the licence was added. If a feature is present in one environment and absent in another with the same version, check entitlements before you check configuration.
- Does a Shopify store connected to a test tenant count toward our licensed store count?
- This has been raised in the Acumatica community and we have not found a definitive published answer, so we are not going to give you one. It matters because a project that runs a development store, a staging store and production could be consuming three of whatever you are licensed for. Ask your VAR to confirm it in writing before you create the second and third store.
- What does an edition change actually cost?
- That is a commercial question we cannot answer for you, because Acumatica pricing runs through partners and depends on your existing agreement. What we can tell you is the shape: it is a recurring licence change rather than a one-time fee, it involves your VAR and Acumatica rather than only your commerce team, and it does not move quickly. Price it during discovery, not during build.
Last updated 2026-08-20. Facts on this page last checked against source 2026-08-20.