CTL || Incorrect data showing for Bestie search | Close the Loop

CTL || Incorrect data showing for Bestie search

Vikas Kaushik

What is the shop or customer experiencing: Shop has tried Bestie and the data showing is incorrect as bestie is showing 999 but actually it is 0
What is the expected behavior: Bestie should show correct data
What error messages are there: No error only data is showing incorrect 
Did you replicate: Yes, it is showing correct on my end on test shop
What settings were checked: Checked Slack channel and bestie on test shop
Provide examples, sku, order #, customer names, and screenshots where possible: SPARKLE CROSS NECKLACE Product ID: 15279 Variant ID: 62773 SKU: SQ4766013

September 30, 2026

Tony Hrbek

This is a major issue impacting MCP connections (including Bestie) where incorrect inventory unit counts are being provided that do not match the CommentSold Product User Interface counts, (or reality in the warehouse). I've attached a CSV file below showing examples of this widespread issue in CS MCP data for our store. IMPORTANT: We learned that most of the items showing wrong inventory values in CS are items that were uploaded using CS's CSV-import function while our team was at market. This is the only commonality we see with the incorrect MCP data. Most items are archived and have ZERO actual units in stock, but MCP is telling us otherwise (incorrectly).

CommentSold_get_product_units_not_in_inventory_report_2026_09_29