Retail

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 box. Now to make the Template ID field editable in the Matrix item screen, the user has to publish the attached customization(“ImportMatrixItems2023R100.zip”) to this article. This customization package must be used only with 2023R1 and above.  There is a customization package for users who do not have commerce module as well. Check the attachment: “ERPImportMatrixItems2023R1002.zip” For 22R2, check    If the selected Templ

Dummy AttributeDescription: The Matrix Inventory feature in 2020R1 and 2020R2 requires the Template Item to have 2 attributes (ie color, size) to create Matrix Items. In some cases eCommerce merchants only require 1 attribute (ie size). This customization package will allow you to create a Dummy Attribute to fill the second, unneeded, Attribute but not display that Dummy Attribute on the eCommerce site.Works with: 20R1, 20R2Packages:Both packages are available on Github as Open Source solutions. To download the .zip from Github, click “Code” > “Download as ZIP”.Dummy Attribute - 2020R1 - Link Dummy Attribute - 2020R2 - LinkMisc: This functionality was added to 21R1 Matrix Item Import Scenario & Convert Stock Items to Matrix ItemsDescription: This package support 2 different features which are related.Feature 1 - The Matrix Inventory feature in 2020R1 and 2020R2 does not supported an “out of the box” Import Scenario. The following package includes everything required to import Pr

In continuation withThe existing ImportMatrixItems customization is upgraded to 2022R2 with the below interesting changes. Now there are Import Scenarios for both Template Items and Matrix Items.Import Scenario for Template Items Import Scenario for 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 Template ID selector is always enabled and filtered based on the Item Class of the Stock/Non-stock. Template ID selector is filtered based on Item ClassThe Is a Kit checkbox is enabled in the Matrix Item which allows the Matrix Item to be created as a Product Kit. Check    Template ID and Is a Kit fields are always enabledIf the selected Template ID in the Matrix Item does not match with default fields with each other then a popup warning is provided to the user.  The fields that are checked are TypeValuation MethodTax CategoryBase UnitSales UnitPurchase UnitPopup warning when default fields

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 then a warning is shown to the user as “ The Disable Automatic Tax Calculation check box is cleared for the EO order type on the Order Types (SO201000) form. Taxes in sales orders imported from the BigCommerce store will be recalculated on invoice creation.” Once these taxes are imported, then it stays as the same even if the Sales Order or Invoice is modified.  This “Disable Automatic Tax Ca

   -----------------------------------------------------------------------------------------------------------------UPDATE: Now the Matrix Item can be made as Product Kit easily by selecting the Is a Kit checkbox in the Matrix Item form. Please check this article    ----------------------------------------------------------------------------------------------------------------Create Product Kits as Matrix Items by following the below steps. Please pay attention to the screenshots were I have created a Template Item called EnergyDrink with the 3 Product Kits as Pack of 4, 8, 12 and linked them as a Matrix Items to the EnergyDrink Template Item. Steps:Create an Attribute from Attributes(CS205000) form, which would be treated as a Variant option to the Matrix Items.    Create an Item Class from Item Classes(IN201000) form and link the Attribute created in step 1 and make sure the category is set as Variant.    Create individual Stock Items from Stock Items(IN202500) form which are going

 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 is the Sales Order in Acumatica  Also, When the Document Discount is selected the Discount Amount revenue will be recorded against the Discount Accounts as shown below. When Show Discount In: Line Discount The order Level and item level discount from external system will be shown in the line item in  Acumatica Sales Order. When Line Discount is selected, by default, the discount amounts are not recorded against the discount amount  But if Post Line Discount Separately is selected in the Order Type

when I preparing the sales order it showing the following errorInserting 'CA Transaction' record raised at least one error. Please review the errors. FinPeriodID: 'Post Period' cannot be empty. 

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

SummaryWe recently updated to 2023 R2.After the update I am getting an access rights error whenever I attempt to use the Customers table/object in a Generic Inquiry.I have admin access rights and there was no issue before the update. DetailsThe exact text of the error is: 'This field will not be displayed for the current user because the user has insufficient access rights or the required feature is disabled'   If I do use the fields they will end up blank when I view the GI. This warning does show up in GIs that were made before the update, but the data is not missing when viewing those GIs.​Self-Service ResourcesKnown Issues - Cannot find related issue Knowledgebase - Cannot find any related entries/articles Release Notes - Don't see anything related Forums - The following is the only similar issue that I can find and it does not have a solution: https://community.acumatica.com/reports-and-generic-inquires-115/backorder-inquiry-in-2023r2-20699  Troubleshooting Access Rights by Roles

Hi All,As of this week Shopify has deprecated private apps that we used by Acumatica Shopify Connector.Here is the link to the announcement - https://community.shopify.com/c/shopify-apis-and-sdks/private-app-depreciation-and-using-custom-apps-instead/td-p/1465831 Acumatica Shopify connector in version 2020r2 and 2021r1 still uses private appsAcumatica Shopify connector in version 2021r2 and 2022r1 support hybrid mode: private, public, and custom apps are supported.Acumatica Shopify connector in version 2022r2+ supports only the public and custom apps. Privates app are deprecated and you have to follow the release notes to fully move from private app to custom or public. What does it mean to us: For users of 2020r2 and 2021r1 versionsExisting customers who uses an existing private will not be affected. Old private app will be still supported. New customers who want to use the Acumatica Shopify connector with NEW credentials (create a new private app), will not be able to do so. Since ne

Hello - we recently implemented the Ecommerce edition to our existing distribution edition  to connect with our Shopify store.  We do not have any 3rd party integrations for calculating tax in Acumatica as most of our business runs B2B, so we manually set up Tax ID’s and zones and apply them whenever necessary.One area that we do have to charge taxes in via web sales.  For most states, we are only dealing with a single flat rate per state.  However, there are a few states, like California, where you are charging State + County + Local in some cases.Shopify handles this as 3 distinct API calls, as opposed to a single calculation of tax and a pass to Acumatica.I’ve tried to do some mapping to change all the incoming tax rate names from Shopify to match up with my associated rates in Acumatica, but with this being 3 calls in the example above, it seems like Acumatica wants to add 3 rows with the same Tax ID name, which it obviously can’t do/will error.I know you can build out more robust

Want to share with you the way to handle Made-To-Order Products with BigCommerce Connector.Made-To-Order products are special types of products where each item may have a specific unique attributes like text, or painting, or style. I will show you an example of gift spoons with special graving. Step 1: We have we need to create a new Stock-Item that will represent the spoon in Acumatica.For testing purpose you can receive a couple of spoons on your warehouse using the Inventory Receipts form (IN301000). Step 2: Prepare and Export Stock Items to your BigCommerce instance. If you manage images/availability in Acumatica, you should also Prepare and Export Availability and Images entities. Step 3: Since Acumatica-BigCommerce Connector cannot manage Product Modifiers, we should go and configure Made-To-Order product in BigCommerce directly. There we want to create Product Modifier Options with allowed values and combinations. For my spoon, I want to allow 2 fields: Message Font and Message

This article will be focused on the specifics synchronization used in the Acumatica Commerce Edition for Shopify and BigCommerce connectors.First, lets define the synchronization process - Synchronization of any entity in Acumatica Commerce edition happens in 2 steps: Preparation and Processing.Preparation is a process when Acumatica gets information that any entity requires a synchronization (ex, new order has been created or product has been updated). When information is received, connector needs to create a record in the Sync History screen, logging that the record has been received and pending sync. Processing is a process when Acumatica loads one single record and synchronizes it from one system to the other. As part of the processing, connector will perform some addition steps: getting record from both systems, fields mapping from source to the destination system, user defined mapping processing, error validations, duplicate validations, saving the record to the destination syste

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

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

I want to show you a way how can you configure saving of a Credit Card Profile inside Acumatica even if the payment is done on the BigCommerce side.This functionality is possible only if both of the systems have integration with the same Credit Card Processing Center. In my case I will use example of Authorize.NET as this processing center is supported and by Acumatica and by BigCommerce. Step 1: We should configure Authorize.NET plugin at BigCommerce (under Store Setup → Payments) to store credit cards:Please note that it will be up to user to store or not the credit card information with you. Step 2: Now if user places the order, there will be an option to save card for the future usage on the payment settings:Please note that this option will appear, only if you have logged in user. For the guest user this option is not available Step 3:  Now we should configure Acumatica to support Credit Card profiles. First place will be at the processing center level:And the second place under t

Our customers get uploaded automatically from our CMS. By error sometimes twice. Once in acumatica, how do I merge the customers, so I have only one customer in acumatica?

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 that we should use Customer Gift Certificate GL Account as Sales Account in the Non-Stock Item settings. Step 5: We need to configure BigCommerce or Shopify to handle Gift Certificates payments and associate a Gift Certificate Non-Stock Item: Step 6: Place an order with Gift Certificate at BigCommerce/Shopify. In this example I’ll buy 100$ certificate:And proceed with checkout. Step 7: You will receive a Gift Certificate at your email address. Step 8: Synchronize the Sales Or

We have a client that needs to implement Stripe so payments from events can be uploaded automatically into Acumatica under a general Customer ID. Then these transactions would be offset against a project under the Projects number and Project Task. Do we need to get a connector through an ISV for this? I know Acumatica has a license feature for Stripe. Any insight would be helpful or instructions? 

Shopify uses API versioning to manage changes and updates in their APIs without breaking existing apps or integrations. How Shopify API Versioning Works:Shopify releases a new API version every quarter (every 3 months). Each version is supported for 12 months. After 12 months, the version is deprecated and apps should upgrade to a newer version to continue working properly. Shopify API changes can be found here - https://shopify.dev/changelogTo support this process Acumatica team is delivering once a quarter version with support of latest Shopify API version for all Acumatica supported versionsAcumatica team strongly recommends updating/upgrading to the latest version to support the latest stable version of the Shopify API.Please check the following Shopify API versions supported by Acumatica: Shopify API version Acumatica versions Changes 2026-04 Supported till April 2027 2025R2 General Release Patch 9 and later 2025R2 Service Pack 1 Patch 6 and later 2026R1 General

Just need to clarify - does the ecommerce connector support syncing a stock item attribute to a product variant metafield in Shopify? Or does it only support syncing to a product metafield? 

As a long time user of BigCommerce and a relatively new adopter of Acumatica, curious if anyone has developed a best practice for handling changes to product variants and getting those changes to sync properly between Acumatica and BigCommerce.  Example: Product A initially set up with option for colors Green, Blue, and Red. Manufacturer drops Red and replaces with Yellow.  Thus far I have tried a) removing the depreciated SKU as a matrix item from the template item and adding the new matrix SKU to the template and syncing - error, b) same process but deleting the depreciated SKU from BigCommerce first - error, and c) same process but deleting all SKU variants from BigCommerce first - error. To resolve a time sensitive issue, I essentially deleted the item from BigCommerce and started over by pushing the template w/ associated matrix items back to the store and updating key fields from a prior export, which is not a viable maintenance strategy.  Any BC store owners have a good workflow

In our system, the item class creates attributes, how can I populate the attributes fields through an import scenario?