Retail

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?

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

Hello!I’m required to integrate an external bar code system to Acumatica. Is there any guide or help on the steps that needs to be followed to integrate?Thank You!

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

Is there a way to sync stock items already in Acumatica with Shopify SKU’s without creating duplicate item numbers in either system? Using Acumatica Shopify Connector

Is there a way to have Acumatica sales order numbers match the Shopify Order Number during sync? Would make it much easier for customers to reference one order number instead of multiple.

We are updating our products and would like to remove large groups of stock items from their associated template IDs, modify the Item Class and Template Items, and then re-attach the stock items to their updated TemplateIDs.  We understand how to associate products to the template IDs, but cannot determine how to delete the Template IDs from each Stock Item to remove them from their templates. We have tried setting the value of the Template ID = NULL, = (nothing) , and =String.Empty .  Does anyone have some pointers on how to remove these via import scenario? Patrick 

In the current Shopify connector, it doesn’t support the custom mapping in the Entity mapping screen for the Refund entity, but if you want to have some custom mappings in the Refund order, you can do it in the customization project. In this topic, I want to share how to create a custom mapping in Shopify refund entity through the customization package. You can make a mapping to the original field or custom field. I tested it in 2023R2 and it works well. Create a new customization project Create a new code file, and extend the Graph from SPRefundsProcessor.     Override the method CreateRefundOrders    

Hi,I am trying to figure out a way to make cases that are being created by incoming emails automatically be assigned to to certain case classes based on rules. I only see how to assign them to different employees in the organization, not how to create a map for case classes. I appreciate the help! 

I have several Sales Orders from Shopify that failed to sync >5 times. Now in aborted status. Can’t work out how to sync them manually. I tried moving one Set as Prepared, which returned it to Failed Status. Then tried to Sync it from there. Same error – “The status of the #### order does not allow modifications. Please synchronize records manually.” What is the correct manual method?Gillian  

I have 4 store locations in Acumatica and Shopify. I want to sync “AVAILABLE” stock quantity from Acumatica to Shopify.This is the export settings in the connector, where the availability mode is set to AVAILABLE. Stock quantity in Acumatica:After syncing stock quantity to Shopify: As you can see “AVAILABLE FOR SHIPMENT” quantity is synced instead of “AVAILABLE”. What am I missing here to make it work? Thank you!

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?