Retail Edition QnA
Updated 10/27/23 The following information answers many of the common questions about Acumatica’s Amazon Connector and our Managed Availability Program.At the bottom we provide a link to sign up for managed availability. This does not commit you to anything. Only let’s us know you’re interested and we’ll grant you access to additional information.General InformationThe Acumatica Amazon Connector works with 23R1 and beyond The solution primarily focuses on back-office efficiencies and accounting Pushing inventory levels to Amazon Pulling in Amazon (FBA and FBM) orders Push shipping notifications/tracking info to Amazon (FBM) Pull in Amazon Payments and Fees Statement reconciliation via Bank Feeds Personal Identifiable Information Protection (PII) More info below It supports FBA and MFN/FBM merchants Merchants use it to sell on Amazon.com and Business.Amazon.com Current merchants are selling in the US, Canada and Mexico New regions can be enabled Requires engagement with the cust
Hi Everyone, We are collecting feedback from our customers about any challenges and pain points they face while using Acumatica via the survey linked below.We would appreciate your feedback. It could be related to the commerce connectors or related to any other area of the ERP (CRM, Shipping, Financials, etc) Examples: Processing Returns and Refunds are hard, Importing the orders through the connector is hard, Taxes issues etc.,We’d also like to understand which external apps you’re using to supplement features within Acumatica. This could be due to Acumatica not offering the same functionality or the Acumatica functionality is not user friendly. Please use this survey as an opportunity to share with us what you’d like to see improved.If you are open to it, we will schedule a call with each of you to collect more feedback, better understand your position and (hopefully) work to provide a solution. Survey Form:https://forms.office.com/r/wJJUFqReEm Thank you
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
Hi All. We are looking for a way to close refunds that remain open with an irrelevant balance on them. There is an option to Write Off invoices or memos, but not for refunds. Is there a way to add that option to refunds?Thanks,
We are creating ERP shipments in advance of actually shipping merchandise, and do not want the information to synchronize until shippments are confirmed. We defined an export filter to limit the Big Commerce synchronization to only shipments that have been confirmed, however it is not working. When the filter below is active, ALL of the shipments are filtered. Our version is 24.109.0016. We also tried filtering on Status but with similar results. Any thoughts what could be wrong?Thanks in advance!
On Shopify we arrange our variants in a certain order for many conversion related reasons such as cheapest first, what we want featured on collection pages (since it defaults to first variant of a product), most popular color first, putting a item line that’s mostly sold out last, etc. We always understood that Acumatica does not have its own variant priority/sort order, which is true as far as customizable, but we were fine managing that on Shopify side only. We have found however that template sync will rearrange all the variants on the product in Shopify even if there were no changes, if template is pushed, or if something else changed on the template.Things we have tried:1. Unmapping option 1,2,3 in template and stock item export mapping. This stops the variant order from being overwritten, but does not work since it doesn’t support any new variants being added or syncing a new product since it then pushes everything as an empty default with no attributes.2. Manipulating Acumatica’
Has anyone had success with filtering the BigCommerce Shipment export based on specific line item details from the sales order? The business case is as follows:Customer places an online BigCommerce order for a kit.In Acumatica there is an import scenario that expands the kit onto the sales order and updates a user defined field with the parent kit inventory id. The exploded line items have a non-zero quantity and the price is $0. When the shipment is synchronized back to BC, the sync returns an error because the kit components were not on the original sales order. We would hope to skip over those items and only update the items that were originally on the order. Any thoughts on how to handle this scenario?Thanks in advance!
Be default, commerce connector merges customers from external systems using the same email address. i.e. when you have two or more customers from one or more stores irrespective of the connectors(Shopify, BigCommerce etc.,) imported into Acumatica, the connector creates one customer record for all.But because of some business scenarios if this is required to not to be merged and create separate customer records, then this could be done using the attached customization. Once the customization is published, you see a new checkbox called “Merge Duplicate” in Entities(BC202000) form. If checked for the stores for the customer entity, then customer records from different stores would be merged and you would have one customer per email ID. If checked for few stores and not for all, then checked stores will create a separate customer records but unchecked stores will share a common customer record.
Hey folks,Question when going-live and transitioning to Acumatica. I was testing a few scenarios where I have Shopify orders that are fulfilled/pending payment (not archived). These orders will be associated to a legacy system order that was already shipped and invoiced. On conversion we will bring over inventory/qoh and our GL balances, including any open AR.In my test I found the following: It looks like it bring this order over with an open qty that needs to be fulfilled, the SO In ‘open’ status. Since our beginning inventory and AR will already account for this, what is the protocol here to make sure we do not relieve inventory of another product (since it has already shipped in legacy). When the payment is received in Shopify it will close and ARCHIVE the order, however it does seem to still bring the payment in, but it brings it in as a prepayment (is this because the SO hasn’t ‘shipped’ in ACU?). What is the overall experience, should we specifically ‘skip’ these legacy
Our Acumatica instance is 23 R1 build 120 and I am trying to override the default URL for Shopify Products using the Custom URL field in the Ecommerce tab on stock items. When I make changes to this field, the prepare data screen picks them up but after I process data, the product’s URL handle under search engine listing remains unchanged. Is there something additional that has to be done to make this work? I don’t think I’m misunderstanding the purpose of this field, given that if I try to include /products/ in the front of the Custom URL value, the system automatically removes /products and leaves a leading slash followed by my custom value.
When we refund Sales tax or a Freight only (no products) in Shopify it creates an RC Sales order and put those refunds in the appropriate places, freight or sales tax. However with no line items the Sales Order cannot create an Invoice. If a CM Order type is used, it does activate the Create Invoice button, but then gives the error that no AR Transactions were found in the system. However this isn’t exactly true because it will should create ARTran lines for Freight and Sales Tax Payables.Current work around is to add a line with a quantity of 1 and 0 Price. I can create a business event to do this as well, but it’d be nice if it can be handled by the ECommerce connector instead. What other work arounds or fixes do you have?
Hi, How do I map Ship Via to the correct carrier in Shopify, i.e. I ship something with Estes trucking, I want Shopify to recognize the carrier.
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.
Are there any retail store operators out there that have a good process for receiving that relies on vendor UPCs to match products on a PO against your Stock Items? Our receiving team struggle to know which product is which amongst our large truck deliveries and they need a screen in Acumatica to be able to scan the vendor’s UPC/barcode and pull up the Stock Item in Acumatica. The standard Stock Item screen doesn’t seem to search through the Cross Reference. Is there a way to change that search function or is there another screen where we can do a quick check?
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
We are investigating building connectors to Commerce marketplaces.I’d like partners/customers/partners to share with me how they’d rank the following marketplaces in order of priority (#1 highest) and comment on any others that I’m missing.Partners - If you can tell me how many prospects/customers are requesting the marketplaces that will be a bonus. Thank you.Marketplaces and AggregatorsAmazon.com Amazon Business Amazon Vendor Central eBay Walmart Google Shopping Target WayFair NewEgg Overstock Home Depot Channel Advisor Feedonomics SellerCloud
Team,Just wanted to share some insights on the “Earliest Order Date” that is available in almost of the Connectors from Acumatica. This configuration tells the Connector, the date from which the orders should be brought into Acumatica from the external system and vice versa. Introduction of this configuration helps to define the cutoff date when your Connector goes live. When Acumatica goes through upgrade / any system restarts, it suggested this date is reset to the current date, so Connector does not go and get the old orders once again into Acumatica. This is a point that should be added in your go live checklist for Acumatica upgrades. By ensuring this date is set correctly before upgrade live, you can avoid lots of old order data hitting your Acumatica and causing sync failures.
Hello! Do any of you use Acumatica for a Print Shop business? Thanks,Kay
In this topic, I want to share how to create a customization to export matrix item cost info to Shopify product variant. This customization can work well on 2023R2.Create a customization project Create a new code file, and extend the Graph from “PX.Commerce.Shopify.SPTemplateItemProcessor”. Select the “OVERRIDE METHOD” from the menu, and then select the Method “SaveBucketExport” from the list. Modify the code as below. Create the new instance of ProductRestDataProvider and InventoryItemRestDataProvider object Use the ProductRestDataProvider instance to get the existing Product/Product variant info from Shopify, cost info doesn’t save in Product variant object, it’s in the InventoryItem object, so we need to get the InventoryItemId from the variant object. We save the variant mapping info(ExternID is Product variant ID, LocalID is the Matrix item NoteID) in BCSyncDetails, so we can find the associated Matrix item by NoteID. All matrix items are saved in Bucket.Product.Local
We are experiencing an issue on our Shopify, where the connector is manually adjusting inventory numbers by adding a sort of “phantom” inventory available for customers to purchase. This is creating the qty available in Shopify and Acumatica to not be in sync, and creating a lot of backorders in Acumatica. From looking at the different transactions on a given item, there is not return, refund, or assembly being created where it would add a positive value to push to Shopify. Below is an image from Shopify where the connector is adding in a “random” positive value. Some more background information: we only first encountered this issue on items that we are including in a online sale, so the volume of orders coming in for these items increased significantly. Prior to us listing the item on sale, the inventory in Shopify and Acumatica was perfectly in sync, with no error records on the template or product availability in the Sync History screen. I am seeking advice from someone who may have
Hi All,The Commerce Retail team has recently prepared a technical guide about import of Refunds supported by the Acumatica Shopify connector in version 2023r2. This guide covers the most common refunds scenarios for Shopify orders with cash or credit card payments. We believe that this document will help to improve users’ knowledge of the refund import process and what results they can expect.If there are any other frequent scenarios of refunds applicable for Shopify orders, please let us know in replays for this post. Thanks
Hello, On the Sync History screen, I’ve noticed I can search for an individual order or group of orders if I know the External ID or External Description and it loads very fast with no issues. I’m trying to search for a group of transactions from our Shopify store, but group them by their ERP ID.If I search for something by ERP ID, it times out every single time with the error “Request Entity is too large”. I try filtering by Last Attempt date down to just one day, only the Sales Order Entity, only Processed or Ready to Process Status, and still times out. Is there any other way to search for a sync history transaction if I only know the ERP ID and not the external? Thanks in advance!
Team, I will share a troubleshooting step today for a problem which you may have come across regularly.Use Case: Sometimes there is a need to sync the same order multiple times to Acumatica to evaluate different configurations, different entity mapping reflections etc. This is usually applicable on a test environment where you do not want to create multiple test orders to troubleshoot an issue.Steps:Once the order syncs to Acumatica, Connector puts the order cross-reference in the External Reference Number field. If this reference is removed and then the sync history line is removed. After this the same order can be synced again. Repeat steps 1 and 2 to once again sync the same order. Best Regards,Sathish S
Hi,Im having this error when I tried to process a return:Everything is configurated according to the instructions. Does anybody has any idea why?Thanks!
Hi, We have an outgoing issue within our Shopify connector, where the customer is not synchronized when the sales order is being created, causing the sales order to fail with this error: “Customer not synchronized, please synchronize the customer entity”, this happens randomly to some orders, not all of them. In these cases we have to go to Sync History and manually process those orders. By the moment we do it, the customer is already synchronized (we don’t have to synchronize the customer, I think it gets synchronized a few moments after the order fails) and the order gets processed, however, this breaks our integration because ideally we shouldn’t have to process any order manually. Is there anything we can adjust to make sure the customer coming from Shopify is synchronized before the order is created? Thanks, Ruben
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
