Retail

Hello,  I’ve got Acumatica installed on my laptop.  But I would like to have the retail commerce edition to play with.  Is this possible?  Thank you,Josh

hi! anyone in the community use Miva for ecommerce? we have a prospect that loves it and was curious if anyone else has integrated with it or uses it with acumatica? thanks!

I created a GI that pulls a specific set of sales orders that are ‘Ready to Process’ that I want to regularly clean up by marking ‘Set as Processed’ since these records will never get processed automatically again.Is it possible to use an import scenario and this GI to mark these prepared Shopify sales orders in the sync history as processed? 

Hello everyone,Has anyone attempted mapping Cycle Description (or a similar field) instead of an ID in Shopify metafields? How do you approach syncing it? 

Hello,Has anyone created an API link inside Acumatica to take credit card information on a sales order or invoice and pass that credit card back to process through shopify payments? Thanks!NS

I have a question for any Entity mapping expert out there: I’m running into an unusual asymmetry between how the import and export entity mappings are for Sales Orders. We have an Acumatica line-level custom field - AltQuantity for short - which we want to link to the BigCommerce Quantity value of each respective item on a sales order. The Import mapping works as expected, even though the custom field isn’t available from the drop down in the ERP Field column.Import mappingI expected the Export mapping to be able to be set up as the mirror of the Import mapping.expected Export mapping Now, I know I’m getting off the expected

We use non-stock items to create bundle items such as a lamp and shade. We are tracking inventory of these items by running a report to generate quantities and importing those quantities into an attribute. I would like to use this attribute to update the inventory level of the non-stock item in BigCommerce and I have mapped it to do so in the entity settings.However the numbers do not update in BigCommerce and remain as zero. I was wondering if anyone has any insight on why this might be the case or if they have another solution they are using that works. I could just map the attribute into a custom field, but I would rather that these stock and non-stock items are handled in the same way to prevent confusion. Mapping of attribute to inventory level on Entity screen I can see in event logging

We have had this issue with 23R1 and it is still happening now that we have upgraded to 24R2. We have some products where we introduce new versions of them with new SKUs while keeping the product name the same.To do this, we have to delete the old product from BigC before we are able to sync the new product since BigC does not allow multiple products to have the same name.When we do this, we sometime run into an issue where if we include the deleted product as a related item on that new product, then it causes a syncing error that is unrecoverable. Essentially, Acumatica just keeps trying to sync the product, gets the same error from BigCommerce API that the product doesn’t exist, and keeps trying to sync without updating anything or giving an error message to the user.Has anyone else run into this issue?

Hello, We are running Acumatica 2025 and Shopify Advanced with the  standard Acumatica<>Shopify connector and are experiencing a lot of issues. We have two(2) retail stores, one e-commerce site and an industrial sales division. Our ERP is Acumatica and our online store and POS run on Shopify.We have been unable to get real-time sync of orders. Everything goes through a schedule - orders, item availability, payments, etc. When we do flash sales/promos, we oversell product. We have been unable to to implement BOPIS. The Shopify statuses (Ready for Pick Up and Marked as Picked Up) is not transferred to Acumatica. We have automatizations that close the orders in Shopify automatically. For POS orders, we are ONLY able to do exchanges or returns for original form of payment. Gift Cards or product exchanges are not updated because of a order does not allow modification errors. If a customer buys in store A but returns or e

We are syncing companies to shopify B2B site(2024r2). We are using export only and not bidirectional data for contacts and companies. The first sync is fine and acts as expected. If we change information on the contact or location permissions the data transfers to shopify but the ACM sync log gives the error ‘Company contact has already been assigned a role in that company location.’ I have tried forcing a resync by deleting the sync records, but it throws the same error after deleting.  

I am missing something here to export tracking number from Acumatica to Shopify. My ERP field is TrackNumberand this is how I map the exportYet, I am not receiving the updated tracking number from Acumatica. I appreciate your recommendations on this topic. Thank you!

I’m really new to Acumatica and the documentation is very sparse.  I’m trying to export stock items to Shopify and facing this random error. Even if I haven’t mapped the weight_unit field.  I’ve scoured the forums and the web and came up dry. I followed all of the instructions in the guide and it still isn’t working. 

The XXX product availability cannot be exported because of the following error(s): Unexpected error(s) occurred while processing feed documents on Amazon. Feed processing status: FATAL I am getting above error while syncing the Product availablity from Acumatica to Amazon. Can some one assist on this.Trace:    at PX.Commerce.Core.BCSyncHistoryMaint.<ProcessSync>d__45.MoveNext()--- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()   at PX.Concurrency.AsyncExtensions.PrepareForRethrow(Exception exception)   at PX.Concurrency.AsyncExtensions.WaitAndUnwrapException(Func`2 method, CancellationToken cancellationToken)   at PX.Concurrency.AsyncExtensions.<>c__DisplayClass2_0.<ToSync&g

Currently on 21R1, in the process of upgrading to 22R2 - is it possible in 22R2 to map product Sales Categories to a product/variant metafield in Shopify?

Running into an error that the transaction getter is not working, yet we have everything turned on in the processing center. Are we missing something? See images...

When our data was originally imported to Acumatica, some template items were imported with no value in some of the required attribute fields.  I now cannot do any maintenance on these items because I get the error “The value of the STYLE attribute must be specified” (in this case the item has no value in the attribute named STYLE.)I have tried adding the attribute in the template and the updating matrix items. It does not work.I have tried adding a value in the item itself and I cannot.I have tried adding the value to the item using an import scenario.  It does not work.Can anyone help me with this please?

With the B2B features of Shopify, an order may be placed for a customer having terms like 30 days. The Payment entity only supports importing from Shopify.  If the order is paid in Acumatica how can that information be sent back to Shopify?

We are on 2024 R2. We are trying to get b2b on shopify and orders brought into ACM. To try and keep things simple we are keeping all company data in ACM and pushing it out to Shopify. Because each company needs at least one contact we manually loaded contacts into Shopify authorize them to order(because as far as I know, there is no place in ACM for this)I sync all the contacts bidirectionally, but I still get the message‘The sales order could not be imported. Make sure the Chris Cxxxx (7749807079526) customer exists in the Shopify store, has been assigned an appropriate role in the 944636006 location, and has been synchronized with Acumatica ERP. How do I fix this to bring in the order?

Acumatica Commerce Connector does not allow mapping of the custom fields for the Sales Order Lines using Entity mapping screen, however, you can use customization engine and include custom fields.To do so, you can create an extension for the Sales Order Processor and include the SO Line custom fields in the API Object.//BCSalesOrderProcessor is the main class that does synchronization of the Sales Orderspublic class BCSalesOrderProcessorExt : PXGraphExtension<BCSalesOrderProcessor>{ public delegate void MapBucketImportDelegate(BCSalesOrderBucket bucket, IMappedEntity existing); //MapBucketImport is mapping the eCommerce API object to Acumatica API Object. [PXOverride] public void MapBucketImport(BCSalesOrderBucket bucket, IMappedEntity existing, MapBucketImportDelegate baseMethod) { baseMethod(bucket, existing); foreach (var detrow in (IEnume

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.

Is it possible to only sync the on hand inventory from ACU to Shopify without updating any other field in shopify for the sync’ed SKU’s?

i am getting error when i process sales order with in-store pickup option. I have Laval already mapped to my Ship Via. Each time I process the order, it creates a new field as pointed with a red arrow. Can you help me fix this? Thank you! 

Using the Amazon integration.  Does anyone have a way to automate the batching of deposits from Amazon Payments?  

I noticed this behavior as of at least 24R2. When you map a field in Acumatica to be a custom field in BigC, the connector will create the custom field in BigC only if that field has a value in Acumatica. Previously when we were on 23R1, if you deleted the text from the field in Acumatica, on the next sync, the custom field would be deleted in BigCommerce. Now as of 24R2, previously created custom fields are not being deleted from BigCommerce when they are given an empty value in Acumatica. Instead the custom fields in BigC retain the last value that was in Acumatica before it was deleted. This seems like a bug to me and is very inconvenient for us. Has anyone else experienced this and found a solution?

We have a situation where we have companies created in Acumatica from Shopify then when the customers associated with those companies get created in Acumatica, they are not linked what so ever.  For Shopify B2b capabilities how is AR to be handled when it should be at the company level and not the customer level in Acumatica?  Terms orders