When SKULabs pushes stock to BigCommerce, it checks that BigCommerce saved the exact quantity it sent. If BigCommerce saved something else, stock sync reports an error for that listing in Sync Reports. These are the errors you may see and how to fix each one.
"BigCommerce failed to apply stock update. Incorrect product inventory tracking setting used on BigCommerce."
BigCommerce didn't keep the quantity SKULabs sent. Common causes:
Inventory tracking is off or set at the wrong level. In BigCommerce, open the product, go to Inventory, and make sure inventory is tracked: on the product for products without variants, or by variant for products with options.
SKULabs is sending a negative number. BigCommerce doesn't accept negative inventory and stores 0 instead, so the update shows as failed. Correct your stock in SKULabs, or use a stock rule that never goes below 0.
Another app is changing stock in BigCommerce. A third-party inventory or dropship app can overwrite the quantity right after SKULabs sets it. Turn off stock updates in the other app so SKULabs is the only source of stock.
"Change product inventory tracking from "variant" to "product" on BigCommerce. Product has a single SKU and no variations."
The product has no options but BigCommerce is set to track inventory by variant. In BigCommerce, change the product's inventory tracking to on the product and save.
"Product is configured to track inventory at variant-level but doesn't have a variant with SKU (…)"
The product tracks inventory by variant, but no variant in BigCommerce has the SKU of the linked SKULabs listing. Make sure the variant SKUs in BigCommerce match, then run listings sync for the store again.
After fixing
The next stock sync pushes the quantity again. Check Sync Reports to confirm the error is gone. For how stock sync works, see What is stock sync?
Still seeing errors? Contact us at support@skulabs.com with the store name and the product's SKU.