Introducing Acumatica Cloud ERP: 2026R2
Retail Edition QnA
Recently active
Hello Friends,I have a few questions for those who are Amazon Sellers and use Acumatica, of course. I would like to know if someone has experienced what I am going through currently and if you wouldn’t mind sharing with me how you handle it?A few notes about us so you have a better understanding, we get hundreds of orders everyday, we do not have Amazon payments connected to Acumatica so we manually process payments for every order in bulk. I also believe the person who was before me did things incorrectly and she trained me and so I feel like I am making our books not have accurate information because of that.First question, I was wondering if you could tell me how you make sure that all the orders that Amazon says you have are in Acumatica? Currently I download an All Orders report for the time frame I want, and then I have a report in Acumatica that pulls all the sales order for the same time frame (I might do a few days overlap in case of delayed transactions). I then do a Vlookup
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. Prerequisites:Admin Access to working Shopify store. Notepad to be able t
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.
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.
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
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. All contacts were synced in Shopify as Customers associated with the newly created Company. The locations were also synced successfully, which looks good. During the next sync (in the aforementioned bi-directional direction), several new records were synced under the Customer entity. Upon reviewing the synced customer records, we discovered that the connector had created new Acumatica Customers, categorized as Individuals—one for each contact of the existing Business Customer (Company). This resulted in the dup
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%: I change the Unit Price from 12,00 to 20,00. Now the Discount % changes automatically and thats what i dont want (same effect applies when items are added or removed and
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 cleared or reset by the 25R1 Shopify connector?
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 are overriden)How Template Items are actually behaving in BigCommerce when qty reaches 0How Template Items SHOULD behave in BigCommerce based on default settings (and historically worked prior to 24R1)
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 already existing in BigCommerce then just the value of the field will be exported to existing field. Limitatio
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.
Good day everyone,ShopifyxAcumatica connector only allows mapping of Company to only fields Name or Notes. Now, I am encountering issue with syncing using Attribute to the Notes field. It always provide an empty value.I mapped the attribute with Customer entity to a Shopify Customer tag - it worked, has value.I mapped another field in Company entity to a Shopify Company Notes - it worked, has value.But when I mapped the same attribute with Company entity to a Shopify Company Notes - it is empty. Does anyone encounter the same? I am using 23 R2 - Build 23.209.0023
Is there a way to get the Acumatica credit terms to the Shopify locations? This seems to be missing from the entities screen. It looks like there is a substitution list slot for Credit Terms, but that seems to be specific for import.
Can somebody tell what is wrong here?We are trying to import prices. I am guessing that Currency rate is missing sth out?
Please check this link to know about deprecation of Authorize.net in Acumatica ERP. Authorize.net Support and Deprecation in Commerce moduleAuthorize.net will be supported in Commerce module until there is a fully working solution for Acumatica Payments with BigCommerce and Shopify. This means customers can import the credit card payments from Shopify and BigCommerce into Acumatica as credit card payments without any issues.Customers canImport Authorized transactions from BC/Shopify to Acumatica. Capture in Acumatica/BC/Shopify Void in Acumatica/BC/Shopify Refund in Acumatica/BC/ShopifyWe are in the final stages of approval of Acumatica Payment with BigCommerce and Shopify. As soon as a we have a working solution, then we will announce when Authorize.net will be deprecated in Commerce module. Please let us know in comments if you have any questions.Update on June 30th 2025We have decided to continue supporting Authorize.net in both the ERP and eCommerce systems for our Retail Commerc
We are working on moving our B2B shop to Shopify. My question for anyone using Shopify B2B, how are you handling Terms customers payments? Currently our B2B site is with Woocommerce, and Terms orders just come in unpaid, and we send an invoice. But with Shopify, customers can pay on the B2B site. Since Acumatica doesnt natively sync those payments at this time, are you disabling the ability for Terms customers to pay past orders in Shopify? Or are there customizations that can be built to handle the payments. Conversely, if a Customer pays an open Shopify invoice in Acumatica, can the open Shopify order be marked paid? (I do see some discussions in here regarding this, please let me know if you have had success with this)Thank you
We use the Shopify Connector for Acumatica and have run into a workflow question:If an item has already been synced with Shopify and we later decide to de-list it from Shopify (but keep it active in Acumatica), the usual step is to uncheck the "Export to external system" box.However, when we do this, the item in Shopify remains Active and continues to appear in the online sales channel. The only effect seems to be that no further changes are synced after that point—it does not change the Shopify product status (Active → Draft) or remove it from the online store.At the moment, it seems the only options are: Change the Acumatica item status to Inactive, or Manually change the item’s Ecommerce Visibility in Acumatica. Question:Is there a way to configure the Acumatica → Shopify integration so that when the "Export to external system" box is unchecked, Acumatica automatically sets the item to Draft or removes it from all sales channels in Shopify?Any insights, workarounds, or best practi
Hey folks - do we know if there is a way to create a mapping, without customization to default the Ship Via - or are we forever bound by the Shipping mapping on the Store Settings?i.e. when a new shipment method is created in shopify and we want to import an order the system errors out because the mapping to the ship via is not provided on the Store Settings. How can we default one ship via value?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.