Context: Allowing preorders for BigCommerce products (stock items). We’re currently on 2020 R2 (updating to 2021 R2 in the next 90 days) and on the BC Enterprise storefront. BigCommerce Requirements: To properly allow the native ‘preorder’ functionality to work on BigCommerce, two settings need to be adjusted:‘Availability’ needs to change to ‘This product is coming soon but I want to take pre-orders’ ‘Inventory Tracking’ method needs to change to ‘Do not track inventory for this product’Acumatica Settings: At the individual stock item level, it is possible to adjust the ‘When QTY Unavailable’ setting within ‘Inventory Settings’ to ‘Set as Pre-Order’. Sounds great. Acumatica Behavior: This ‘Set as Pre-Order’ action only adjusts the BigCommerce ‘Availability’ setting to the required ‘This product is coming soon but I want to take pre-orders’. However, without the ‘Inventory Tracking’ setting getting updated in tandem, the action of allowing pre-order isn’t actually achieved. There are o
Recently updated to the build 21.216.0034. It would appear there has either been some change to what triggers a ‘Product Availability’ sync request, or otherwise a related bug. In previous builds, ‘Product Availability’ record prepared of course based on update to the given inventory ID (Template, Stock, Non Stock). Expected and documented functionality. Since our update to this build last week, it appears that nearly all Inventory ID records are entering the prepare/process queue, even though the majority of those records have not been modified by any expected action (ie, sales order created, PO received, inventory adjustment, etc). Is this a known situation? Have changes to what triggers a product availability request been meaningfully changed in this build? Why this matters in our integration: We override the ‘track inventory’ setting for BigCommerce products that we want to allow backorder on (ie, take an order for something not in stock). For items with low velocity, the Invento
I’m curious if there is any direct documentation about utilizing the commerce connector and various entity settings at different Acumatica structure levels, primarily Tenant vs Company. Most of the existing documentation appears to center around configuring a single BigCommerce or Shopify store to a single tenant but, for example, what are the options/limitations around connecting store 1 to company 1 and store 2 to company 2, within a single tenant?If anyone has explored this configuration or is using it currently, I’d be interested to understand how it’s working for you and any issues encountered.
Recently updated to 2021 R2 and had Acumatica run the script to depreciate the previous Dummy Attribute requirement that we’d needed for managing single attribute matrix items. After upgrade and Dummy Attribute script removal, existing import scenario used to assign variant and variant value to individual stock items and connect them to correct template item produces a ‘View Name: Item’ error. Import Scenario Screen (IN-ReconnectMatrixItem)Pretty straight forward - Inventory ID, Template ID, Attribute1 and 2, Attribute Value 1 and 2.Import Scenario MappingThis was set up by our VAR, and has worked without issue until this release. Data Provider SchemeExcel Sheet used for ImportThe View Name: Item error doesn’t give much indication as to what might be wrong. Here is a trace from the error: Any ideas? Is there another way to do this? Generally we add Stock Items in bulk, and then assign them to Template Items as needed before syncing those template items up to our BigCommerce site. We do
Upgraded to 2021R2 and running through full resync of relevant entities - Sales Category → Stock Item → Non Stock Item → Template Item. Got to Product Availability, and encountered a new error I’ve not previously seen: Error: Specified argument was out of the range of valid values.Parameter name: IdentifyNoteIDSteps: Ran a ‘Full’ Prepare request for Product Availability Entity (previous automation schedules inactive since just prior to cutover to new release). Attempt to Process records. Encountered error above. The records do not appear to fail (ie, do not move to a failed or aborted status in Sync History), but just remain in the ready to process queue. I’ve approached this from both the prepare/process screens and from the sync history screen, and keep encountering the same error. Acumatica Trace from this screen:Right now I don’t have a means to reconcile product availability since our cutover 72 hours ago, which is problematic.
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
Already have an account? Login
Enter your username or 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.