Retail

Starting January 1, 2026, Shopify will prevent the creation of legacy custom apps. Instead the dev dashboard will have to be used.The credentials and authentication process appears to be different for new apps developed using the Shopify dev dashboard.Do we foresee any breaking changes for the Shopify connector after January 2026 if new legacy custom apps cannot be created?Are there any documents relating to setting up the Shopify connector with newer apps developed through the Shopify dev dashboard? Specifically interested in whether the new “clientId” and “secret” associated with newer Shopify apps relate directly to the “API Access Token” and “API Secret Key” that were used in legacy custom apps? ie should those newer credentials just work in place of the older credentials? They don’t appear to.

Starting January 1, 2026, Shopify has updated the way custom apps are created and managed, moving away from the legacy “custom app” model to a more secure and standardized approach through the Shopify Dev Dashboard. This change aligns with Shopify’s broader focus on improving app security, access control, and developer experience. We need to support custom app for partners that test on local instances and can not connect to our public app.With the new flow, custom apps are now created directly within the Shopify Admin using the Dev Dashboard, providing better visibility into app permissions, API credentials, and lifecycle management. This document outlines the updated process, highlights key differences from the previous approach, and guides you step-by-step through creating and configuring a custom app using the new system.****The custom apps that have already been created will continue to function as intended.  

Hello,After updating to 2025R2, Shopify orders that contain customer info are aborted with this error message. Orders without a customer get processed without issue. I have uninstalled and reinstalled the Acumatica App in Shopify a couple of times and still getting this error. We have two Shopify stores, one on Shopify Grow and another on Advanced. Both have the same issues. Complete Error Message: At least one GraphQL error has occurred. Error: Access denied for companyContactProfiles field. Required access: `read_customers` access scope or `read_companies` access scope. Also: The API client must be installed on a Shopify Plus store.

Hi,due to the changes in the US regarding duties (800$ de-minimis), we have to collect duties from our customers in Shopify. This works very well, but if i’m correct, there is no solution/field in Accumatica to collect duties in sales orders.So now i’m struggeling how to import those values which i do have in my sales order in shopify to my sales orders in accumatica. Does anybody else have the same issue and already a solution for it?

I am currently working on setting up the Shopify integration with Acumatica (2025 R1 Commerce / Shopify Connector).I am facing an issue with the Shopify configuration steps mentioned in the documentation. The documentation refers to steps that no longer match the current Shopify UI (e.g., private apps vs custom apps).Specifically:I am unable to find the exact Shopify settings referenced in the documentation The steps for creating API credentials seem outdated There is no clear step-by-step guide for Shopify Dev (Custom App) setup aligned with Acumatica 2025 R1Could someone please provide:Updated step-by-step instructions for Shopify (Custom App / Admin API setup) Required API scopes for Acumatica integration Any updated documentation or internal guide for 2025 R1 Commerce (Shopify connector)Any screenshots or clarification would be greatly appreciated.

In continuation with the below article, the current article explains how the same can be done in 23R1 and the difference between 22R2 and 23R1. Like in 22R2, in 23R1 there are out of box import scenarios for Template Item(Import Template Items), Matrix Item (Import Matrix Items). The Edit Template ID checkbox in the Item Class form which enabled the Template Item ID field in the Stock/Non-stock form is removed.  The Is a Kit checkbox is enabled in the Matrix Item which allows the Matrix Item to be created as a Product Kit. Check    All the above is done out of the

We are considering changing from Shopify POS to Clover.Is anyone using Clover for POS, and if so is there a preference for which 3rd party connector is used?Thank you

I got a couple issues with the Shopify Connector, specifically the customer location sync.At random it will create more than one location for the customer in Acumatica.  It will activate one and deactivate the other.  Since upgrading to 2025R2 we have every day one or two orders where it will fail to import due to "property set method not found". What we found is that it means that the location is not active. When you go to it in Acumatica, you cannot activate it either. You need to create an additional location, make that the default, then you can go back to the other location and activate it.  In addition I found today that when I look at audit history for any customer, it will show me a bunch of location changes for different customers, different random locations. I don't know what these mean and why they're showing up on another customer that's not even connected to our Shopify store.  

We have a situation where a B2B shopify order gets sync’ed into Acumatica from Shopify.  The order is on terms (IE - Net 30) so no payment records comes with the shopify record.   Shopify order is fulfilled inside Acumatica and Invoice is generated for sales order.  Some time later, customer pays the invoice and invoice is closed in Acumatica but the original order in shopify remains open instead of closed.   Is there a way to close that B2B (Terms) order in shopify when payment is completed in Acumatica?

We are using the Shopify Connector, and have the Shopify Warehouses mapped to Acumatica Warehouses. Whether I select a Location for the mapping or leave it blank, it seems to ignore anything <UNASSIGNED> regardless of Allocated or not. This is not ideal because it reports a higher inventory number than is actually available to be sold, resulting in over-selling, upset customers, etc.  Am I missing something?

We have an instance where an inventory item with a $0 cost was sold then returned. Unfortunately, on the return, the cost defaulted to the most recent sale price and the item was brought back in with a cost. This caused negative COGS and increased inventory value when it shouldn’t have. This item has since been re-sold so I can’t just use the “Issue” and “Receive” processes to remove it from inventory and bring it back at the correct cost.Is there any way to correct the cost on this item?Item costing is specific to the item. I tried using the “Adjustments” but it insists on changing the quantity as well as value.

Hello everyone,We are encountering an issue with the Shopify connector for Acumatica24R1 regarding the synchronization of Business Customers (B2B). Both Company and Customer entities are active and both in bi-direction. Here’s the scenario:A business customer categorized as an organization is set up in Acumatica, with several contacts and locations. When this business customer was synced to Shopify, a Company was created using the same name as the business customer in Acumatica.

Hello everyone,Customer-based discount codes work for the customer, and a discount percentage rate remains in place even if the order volume changes: The problem is manual discounts -> if you change the percentage, it is linked to the amount and not to the discount rate -> if you add or remove items with manual discounts in Sales Orders, the discount rate also changes, even though it should remain the same: The discount rate should be fixed and not flexible and dependent on the amount.The customer works a lot with manual and flexible discounts, but wants to prevent the discount percentage rate from changing when the order is adjusted. We have not found a solution here for how to set spontaneous discounts. Do you have a solution?Example:SO and the product costs are 12,00 per unit. I add an manual Discount of 10%:

Is there a good way to accomplish this special situation?   Send shopify transfer order details to Acumatica as 1 step transfers. Thanks,Nirav S.

Hi all,Does anyone know of a way to create a “timed” promotion for inventory items that we could customize by customer price lists and/or region?Thanks!Joseph

Hello Acumatica Community! We’ve run into a not good experience, issue with the latest Shopify connector for Acumatica (25R1). I’m hoping to get some insights from others who might be experiencing the same or confirm if this is an isolated problem on our end.What we observedBackground: We rely on metafields in Shopify and map another metafield from a Stock Item attribute via the connector.Normal behavior (pre-25R1): If a value existed in Shopify for one metafield, and another metafield was mapped from a Stock Item attribute, the “unmapped” metafield retained its value while the “mapped” metafield was updated as expected. Current issue (25R1): The connector now tries to update each metafield. And if there’s no mapped attribute for a metafield, connector clears it. This results in unintended data loss across the board, not just the mapped fields. Has anyone else experienced metafield data being

Exciting News: BigCommerce Integration Coming to Acumatica 2025 R1 and Newer!Acumatica is thrilled to announce that the BigCommerce integration will soon be available for Acumatica versions 2025 R1 and newer launching in early 2026!This new integration allows Acumatica customers to seamlessly connect their BigCommerce storefront with Acumatica’s ERP platform. This means more automation, faster order processing, and real-time inventory and customer data sync between your ecommerce operations and your back-office workflows.What does this mean for you?Effortless order, inventory, and customer data flow between BigCommerce and Acumatica Fewer manual entry errors and time spent on double data input The ability to scale your online business with the latest and greatest from both platforms Remove the need for additional gateway fees and integrationsA note on payments

Since the update to 24R1 we’re experiencing an issue with Template Items’ BigCommerce Qty Unavailable setting behaving as “Set as Pre-Order” instead of our BigCommerce Default setting (which is “Do Nothing”). This only affects template items. (Stock items behave as expected.)This results in these items being made available to customers on our website as pre-order despite us having no intention of allowing pre-orders. I’m just checking to see if anyone else is experiencing this issue and if it’s been raised at all yet.I’ve attached some screenshots for visualization.Default BigCommerce Inventory SettingsInventory Settings for Specific Template Item (to show no settings a

As of Jan 1, 2025, SHOP will now act as a Marketplace that collects and remits tax on behalf of the vendor - seems similar to how Amazon works.   How will this flow through the native Acumatica Shopify Connector to Acumatica and then through the Avalara Connector to AvaTax?   How is the transaction identified as a SHOP transaction?  Are there parameters that need to be set up so that the vendor does not double pay the tax? 

The Custom Field in BigCommerce could be added using the Commerce Connector from the Entities form(BC202000). Imagine you would like to map a attribute or custom field or any field from Acumatica Stock Item form to a custom filed in BigCommerce product page and this custom field in BigCommerce is not yet created. Go to Entities form(BC202000), select Stock Item Entity.  Go to Export Mapping Tab Click plus (+) button In the Source Object, select the required Acumatica object. Eg: Attributes or Advanced  In the Source Field/Value, select the required Field.  In the Target Object, select the object as Product->Custom Fields. In the Target Value/Field, select <<Automapping>> as shown in the screenshot. Now when the stock item is exported next time, connector will automatically create the Custom Field in BigCommerce with the same name as in Acumatica. If the field alread

After an upgrade to 25R1, ShopifyxAcumatica connector is now failing to sync payments with this error that seems to be a permission access for the Shopify app.  

Hello Everyone,We have one of our client working with 24R2 (24.212.0010) Shopify Connector and observed a discrepancy during Refund sync due to that the behavior is not consistent across RC orders created manually and synced through connector and this is specific for a serialized product associated with Lot/Serial number. Can you please review the scenario and help us with root cause identification and possible fix.Acumatica RC Order Reflection for a Serialized Product:• Created receipt with serial nbr 101. • Created order and selected serial. • Created & confirmed Shipment and released Invoice.• Created RC, selected this Invoice, Line Details pop-up updated with that serial. • Create Receipt, Confirm Shipment, and Released Invoice.Acumatica Connector RC Order Reflection for a Serialized Product is Not same as of Manual RC creation:• Created receipt with serial nbr 102.  • Cre