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

We have been testing the BigCommerce B2B customization on Acumatica 23R1 ahead of launching our BigC store, and we have seen a lot of issues with it. I was wondering if others have run into these problems and have a way of dealing with it or even just a better way of thinking about these problems so that we can live with them.We find it confusing that the main contact rather than the primary contact (except for the primary contact name) is used as the first admin info in BigC and don’t know how to treat the primary contact in Acumatica to make this less confusing. We also find it confusing that the 2nd rather than the 1st main contact phone number is synced to BigC. We don’t know how to handle the possibility of a customer deleting the first admin in their company in BigCommerce B2B since that is how the connector is connecting the customer in Acumatica to the company in BigC. We have noticed many, many issues with modifying existing customer data in either Acumatica or BigC. The data

Build 25.101.0153.11 We run the native Amazon Connector (BC201020) with the Non-Order Fees entity active, importing Amazon's non-order-related fees as cash transactions on CA304000. That synchronization stopped returning data at the end of August 2026 and has not recovered. The timing lines up with Amazon's removal of the Finances API v0 operations listFinancialEvents, listFinancialEventsByGroupId and listFinancialEventsByOrderId on August 28, 2026 (deprecated July 21, 2025). The stated replacement is the listTransactions operation in Finances API v2024-06-19. Through our partner, Acumatica support has confirmed that there is currently no workaround other than manually creating the required cash transactions, and that upgrading to 2025 R2 or 2026 R1 does not restore Non-Order Fees synchronization. We were told Engineering is evaluating whether a customization is technically feasible as a temporary measure. A few questions for the community and moderators:1. Is anyone else running the N

We are using the  native Amazon Connector (BC201020), importing seller-fulfilled orders.I originally set up an item as a stock item and added its ASIN as an Alternate ID (Global type) on the Cross-Reference tab. We later decided the item should be a non-stock item instead. I created the non-stock item, removed the cross-reference row from the stock item (and saved), and added the same ASIN as a Global cross-reference on the non-stock item.When the Amazon Connector imports an order containing that ASIN, it errors out saying the cross-reference exists on two items — both the original stock item and the new non-stock item.**What I've checked:**- Reopened the stock item (IN202500) — the cross-reference row is not visible on the Cross-Reference tab.- The non-stock item (IN202000) shows exactly one row for the ASIN, Alternate Type = Global.- Only one UOM row exists per item; no duplicates within either item.**Questions:**1. Is there a place other than the item's Cross-Reference tab (e.g., a

Hi everyone,We have a consignment sales process where, upon receiving a PO from a consignment customer, we manually create a Transfer Order (TO) sales order in Acumatica. This process transfers inventory from our warehouse to the consignment warehouse.Subsequently, every two weeks, we create a regular sales order based on the actual quantities sold during that period.We are currently integrating with SPS Commerce EDI and would like incoming customer POs to automatically generate TO orders in Acumatica. However, we have encountered an issue: the “Destination Warehouse” field on the TO header is mandatory, and the EDI-generated order does not populate this value. Has anyone implemented a similar consignment process with Acumatica and SPS Commerce EDI? If so:How did you handle the Destination Warehouse requirement?Were you able to configure it through standard functionality?Or did it require customization on the Acumatica side? Any insights or recommendations would be greatly appreciated.

Since Thursday August 6, we are seeing our Amazon FBM orders not sync into the system consistently. Results are sporadic at best, some come over right away, others come over 6 hours later and this is not sustainable. Anyone know if anything has changed on how Amazon is sending sales orders over for FBM? Most orders I cannot even see in the sync history if there is an error, they just do not populateNo one knows what to do to fix

Hello,Does anyone know the setup in the Commerce module to allow for the tracking number to be sent back to BC from Acumatica? I am unsure if this setup is the correct setup, but I know we not currently having tracking IDs sent back to BC.  

Hello everyone,We recently received an email from Shopify titled "Action needed: Test apps by Oct 1 for fulfillment updates." It lists our Acumatica ERP Connector (the custom app used by Acumatica's built-in Shopify connector) as possibly needing an update for Shopify's new "ship and pickup in one order" feature.Shopify is asking the app developer to test in their feature preview and then submit a compatibility confirmation form. The form asks us to confirm that:The app does not create, update, or delete merchant delivery (shipping) profiles (market-driven shipping), and The app correctly handles orders with multiple delivery groups and multiple fulfillment orders, such as one item shipped and one item picked up in the same order.We are currently on Acumatica 2025 R1 and plan to upgrade to 2026 R1 later this year.Has anyone else received this notice? I would really appreciate any guidance on:Whether Acumatica has confirmed that the Shopify connector is compatible with these changes, in

Is there any way to have a discount calculate from a group level but apply the discount as a line discount instead of a document discount?The example is: we give a qty discount on a specific brand (which is an item class), 2+ = 10% discount / 4+ = 20% discount.I can make it give the proper discount using a  document discount, however, the problem this is more difficult for reports where we track profitability per item sku and also returns etc. As the line amount per unit doesn’t reflect the discount. I don’t think there is a way to do what I want but thought I would check. 

Does anyone know of a way to have a customer status automatically change to “Credit Hold” when they have invoices past due a certain number of days?I would like to either do that or have an automatic pop-up occur if an employee begins a sale with this customer, creates a quote for them, or schedules a service appointment.This type of reminder would be great!I already set the credit verification settings in the customer class:We’re using 2026.R1Thanks for sharing any ideas!

Is there a preferred method for adding a restocking fee to an RC return order? Our thought was to create a “RESTOCKFEE” non-stock item and add it to the RC with a negative amount to subtract the fee from the return. Does this make sense, or is there a better way to go about this?

Reconfigure Amazon Order Mappings for the Orders API v2026 Migration Amazon is transitioning from the Selling Partner API Orders v0 to the new Orders API v2026-01-01(new API).Amazon originally announced that the old API operations would be removed in August 2026. The removal date has now been extended to March 27, 2027, giving customers additional time to complete the transition.Acumatica has updated the Amazon Connector to support the new API based on the initial August 2026 date. Customers with existing Amazon stores must complete an important manual configuration step after upgrading.Please check the attached document for the old vs new mappings.Who is affected?This action applies to existing Amazon Connector implementations running one of the following Acumatica versions: Acumatica version Minimum supported update 2026 R2 All builds 2026 R1 GA Patch 4 or later; build 26.100.0175.4 or later Service Pack 1 Patch 1 or later; build 26.101.0225

I am working on a Shopify integration involving template items and their child stock items.The customer maintains Color and Size as product attributes. In addition, they use a Shopify color metafield for business verification. This metafield is configured as a single-choice text field with a predefined drop-down list, allowing the user to select one color.I created a corresponding attribute in Acumatica and tested both Combo and Multi Select Combo control types. I also configured entity mapping to export the attribute value from Acumatica to the Shopify metafield.  

The client needs to have a different order type for orders passed thru Shopify from TikTok.  An Order Data field, Source Name, is populated with ‘TikTok’. A different Acumatica Sales Order Type is required because TikTok takes care of the reporting of sales taxes so Tax Calculation needs to be disabled.  The normal Shopify Orders are only taxed in two states and the client has Avalara.The Expression Editor only can be used for the External fields.

We have drop ship products on our Shopify site - if purchased, the order will sync to Acumatica, a drop ship PO will be created, and then a drop ship receipt once the vendor has confirmed the order has shipped.Is there a way natively to mark these orders as fulfilled in Shopify? This happens automatically for orders with product we stock and can ship from our own warehouse; a shipment is created and confirmed and the order is marked as fulfilled in Shopify. However, because the drop ship process uses a receipt instead of a shipment document, and there is no place to enter tracking # information in a receipt, we cannot see a way to mark the order as fulfilled in Shopify.We are currently on 21R1, in the process of upgrading to 23R1; perhaps this has changed in the latest release?

Hi everyone,I’m reviewing the documentation regarding the Multiple Base Currencies feature. It states that Retail Commerce is not supported when Multiple Base Currencies is enabled.I would like to clarify the practical impact of this restriction.If a company operates in multiple countries with different base currencies and requires the Multiple Base Currencies feature, does this mean Retail Commerce (Shopify, BigCommerce, etc.) cannot be used in that same tenant?In that case, would the recommended approach be separate tenants per country?I’m also trying to understand whether there is still value in enabling Multiple Base Currencies for a company that plans to use Retail Commerce, or whether the two features are fundamentally incompatible within a single tenant.Any insight on best practice architecture for multi-country companies using eCommerce would be greatly appreciated.

We are using the Acumatica Shopify Commerce Connector to synchronize item information from Acumatica to Shopify.A template item in Acumatica contains an attribute named TEMPCLOSEO. The attribute value can be either TRUE or FALSE.We want to configure an export entity mapping with the following logic:When TEMPCLOSEO is TRUE, export the value Closeout to Shopify. When TEMPCLOSEO is FALSE, export a blank value.We attempted to use the following formula in the Shopify export entity mapping:=IIf([[TemplateItems -> Attributes.TEMPCLOSEO]] = 'TRUE', 'Closeout', '') Data is syncing fine when the SKU has true value but it is failing false information(field: input.metafields.0.value) Value can't be blank. Acumatica returns this following error:Expected ResultThe export mapping should return:Closeoutwhen the TEMPCLOSEO attribute is set to TRUE.When the attribute is set to FALSE, the export mapping should return a blank value.

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 paymentsAcumatica Payments is still the recommended option for the most streamlined, end-to-end payment experience. However, for custome

Hi everyone,I'm looking for guidance on syncing color information from Acumatica to Shopify using the native Shopify Connector on 2026 R1.The requirementIn Acumatica, product color is stored as a descriptive name. On the Shopify side we're populating a Color metafield, which expects a hexadecimal value rather than the name:Black → #000000 White → #FFFFFF Smoke → #808080 Dark Smoke → #4A4A4AWhat I've triedCreated a Substitution List mapping the Acumatica color names to their hex values, and referenced it in the Shopify Entity Mapping. The substitution was not applied and no hex value was exported. Changed the Acumatica color field to store the hex value directly (for example, #000000) and re-synced the product. The Shopify color metafield still was not populated. Tried the following expression in the entity mapping: =SubstituteListed([shopify.color-pattern], 'Metacolor') — the expression editor returns an error that the function is undefined.My questionsIs there a supported way to trans

Hi Everyone,We're encountering a customer sync issue with the BigCommerce Commerce Connector.We use a single Generic Guest Customer Account in BC201000 to store guest customers. When a guest customer later registers as a standalone customer in BigCommerce, Acumatica attempts to create a new customer record but the sync fails with the following error:“ The Customer record with the same field or fields (user@email.com) in the ERP system has already been synchronized with another Customer record with external ID user@email.com.” We searched the BCSyncStatus table (using both a GI and the All Records tab) but found no mapping for the reported external ID. We also tried making the original guest location inactive and changing its email address, but the error persists. Any suggestions would be greatly appreciated.

There is a scenario that I am looking to solve for. Customer puts in CAD shopify order/paid in CAD but I would like that order to get added into Acumatica as a USD order to avoid any currency exchange rounding issues between shopify payout and bank reconcilation.  Any suggestions?

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?

We have a client who is live on BigCommerce and wants to import their existing stock item catalog into Acumatica first to get Stock items set up and the External ID links established, then switch the sync direction to Export with Acumatica as the master going forward. Has anyone done this before? What's the recommended way to manage this? can we map item class using a custom field from BC to Acumatica to match it to the correct item class using import mapping? And once you flip to Export, does the connector pick up the existing External ID links and update the BC products cleanly without creating duplicates?