Retail

Is there a way to have a certain payment type always post as a prepayment instead of a payment? For context:We create sales orders and send them to customers so they can pay for their items before they are delivered. The payments made through the integrated payment processor all post as "Payments" which creates a negative AR and really throws the AR Aging reports and overall AR out of whack. Especially since it can be a month or more before an animal is delivered and the SO is converted to an invoice, thus balancing out the AR. Manually generated payments can be posted as "Prepayments" and thereby coded to Customer Deposits instead of AR on receipt and don't cause that issue. Ideally, we'd have specific payment types automatically generate as "Prepayments" instead of "Payments" so that they post to our Customer Deposits account until the item is delivered and the transaction completed. Does a

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?

Hi After many chat with Shopify support and after reviewing the data and considering that all variants are unique in Acumatica. it appears that the error "At least one option value is duplicated" likely stems from a subtlety in how the data is transmitted or interpreted by the Shopify connector integrated into your Acumatica ERP version 2025r1. So , I’am looking for more information ( into the Acumatica log )  Review the data sent via the connector: If possible, obtain a snippet or log of the payload sent to Shopify for product W24J0059 so our technical team can analyze exactly which option combinations are received. Our last sync history was this morning 12/16/2025 11:06am on Entity : Template Item and ERP ID W24j0059  Thanks for your Help _j

Hello  I am trying to sync related products against template items between Acumatica and BigCommerce.  I am able to do this with non template items and it works as expected. For template items I have tried adding a related item to one of the SKU’s in the template item but it does not sync through. Is there a way to associate related products to template items please? Thanks  Matt

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?

Hello,I noticed recently that if the inventory is negative, the connector ‘adjusted’ the inventory in Shopify to 0.   Since both systems normally handle negatives, does anyone know why this would occur?  it's 25R1

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

Hello  Is it possible to populate the Description (Image alt text) field in BigCommerce when uploading images from Acumatica using the Acumatica connector.  Thanks  Matt

We are a retail business using Acumatica in UK and currently have the Stripe integration switched on and working to accept payments in Acumatica, to do this we can manually type the card details into Acumatica & then the payment detail is sent to Stripe via the OOTB integration to authorise / take payment. We would like to be able to use card terminals within our showrooms so customers can insert their card into the terminal to pay but are struggling to work out what we need to do / what integration is required to allow the payment detail to get to the card terminal, the card terminal sorts the payment and then updates Acumatica when the payment has went through. Is anyone else using Stripe card readers with Acumatica and if so what extra steps / integration are you using to get it working?

Hello folks,Wanted to see if this was remotely possible.    But i have an import mapping setup that work in the following manner on the SALES ORDER entity in Commerce Connector: As you can see this will look for the “MISC” tag and if it exists it will map the customerID to my “ECOMGUEST” customer.  If FALSE, it maps to the C0000011 customer.  What I would LIKE to occur is that on the FALSE result of the IIF statement that it reverts to actually using the native connectors logic to either use the existing shopify customer or create a new one.  Possible?

In this article I will show you how to configure Acumatica to automatically accrue Gift Certificate amount. Step 1: We need to create a new GL Account that will hold sold Gift Certificates value. Step 2: We need to create a corresponding Cash Account that will be used for the payment by gift Certificates. Step 3: We need to create a Payment Method that will accept payments by Gift Certificates Step 4: Now we need to create a Non-Stock Item that will represent a Gift Certificate item in the Sales Order. Please note t

Running into an issue where a shopify order is stuck in the sync due to the following error:  Contact.DisplayName: 'Contact' cannot be empty. Contact.LastName: 'Last Name' cannot be empty. Inserting 'Contact' record raised at least one error. Please review the errors. Checked the shopify order and there exists contact names for billing and shipping.  What else could be causing this?

Does anyone else struggle with filtering the SYNC HISTORY screen when you have 10’s of thousands of records?  I consistently get an error that the request times out.   Even on specific tabs like failed/processed etc. 

BigCommerce:eCommerce Admin can choose how the customers should checkout in BigCommerce as shown in the below screenshot. If the customer decide to checkout as guest a customer account will not be created in BigCommerce. So in Acumatica the Sales Order will be imported with Generic Guest Customer provided in the Store Settings as shown below. If a customer decide to checkout with account details, then a customer account will be created in BigCommerce. And in Acumatica while importing this Sales Order, Commerce connector will create a new customer if the email address doesn't exist already and then link this customer to the sales order.  Customers are allowed to checkout as guest but BigCommerce will create a customer account as soon as the

In 2023R1, a new checkbox called “Disable Automatic Tax Calculation” is introduced in the Order Types(SO201000) form. When this checkbox is selected, the system will refrain from recalculating the taxes for the Sales Orders and Invoices.   The Commerce connector will import the Taxes from external systems such as BigCommerce, Shopify, Amazon etc., if the “Tax Synchronization” checkbox is selected in the Stores form.  If the “Tax Synchronization” checkbox is selected in the Stores form and if the selected Order Type in Order Type for Import selector has “Disable Automatic Tax Calculation” unchecked

Hi there,i hope you can help.We’re imorting the objects customer, customer location and order from Shopify. The import of the objects customer and customer location was successfully and i can see the data in the ERP, but i do get this error message for some orders: The record cannot be synchronized because it does not exist in the ERP and external system.I do not understand what’s the issue of those orders. The items and IDs of the products exist in the ERP and other orders with the same products were succesfully imported.I see in the synch overview that the external ID exists and it forwards me to the correct order in shopify.Any ideas how i can proceed in getting those orders imported?

 In the Shopify Stores(BC201010) and BigCommerce Stores(BC201000) form, the user can choose the option to show the discounts in Acumatica Sales Order as a Line Discount or Document Discount when orders are imported from External System. It cannot be both.  When Show Discount In: Document Discount The order Level and item level discount from external system will be shown in the Discount Details tab in the document level in Acumatica Sales Order. This is the order created in BigCommerce.  This

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 soo

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

We have some of our Sales Reps set up as Employees in Acumatica, each with limited access. Currently, they can only see the Sales Orders they personally entered, which makes it difficult for them to track orders for their customers that were entered by Customer Service on their behalf.Ideally, we’d like Sales Reps to be able to view all Sales Orders for their assigned customers--regardless of who entered them--but still keep their access limited so they can’t see other reps’ accounts.For those of you managing Sales Rep access:How are you controlling what Sales Orders your reps can see? Are you using Restriction Groups, Roles/Access Rights, or custom GI filters tied to Salesperson or Customer data? Do you rely on the Owner field, Salesperson ID, or something else entirely?Would appreciate any insight or examples of how you’ve structured this in you environment.

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.

We currently import 2-3k orders per day from Shopify.  They import at a rate of about 360/hour or 10 seconds per order.  This usually keeps up, but with order updates and sales we can fall behind.  What rates are you seeing on your system?  Ideas are welcome, but trying to start with what are realistic expectations and what is possible.