Close the Loop

Confirm there are not already settings or features that do what the shop is asking for:- Currently, there are no settings or features in the MCP/Bestie platform that expose the product location field via the get_product_inventory tool. When asked about product locations, Bestie responds that the information is unavailable because the field is not exposed in the API/tool response. Users must manually click through multiple screens in the CommentSold Products menu to find this data. What does the shop want the product to do:- The shop wants the product location field exposed in the get_product_inventory tool/data response. This will enable Bestie to immediately answer queries regarding a product or variant's location and allow the location field to be included in inventory reports generated via Bestie/MCP. Why/how would it improve sales or efficiency:- Faster Live Sale Setup: Streamlines inventory pull and live stream prep by eliminating the need to navigate through multiple menu clicks in the web dashboard just to locate items. Operational Efficiency: Allows shop staff to instantly ask Bestie for an item's location on demand, saving time during peak order fulfillment and live selling workflows. Better Reporting: Enhances reporting capabilities by incorporating location metadata into exported inventory reports.

Confirm there are not already settings or features that do what the shop is asking for: I have checked and there is currently no option to delete or remove a tax code from the dropdown menu once it has been created, regardless of whether it contains a typo or was added by mistake. What does the shop want the product to do: The shop wants to have an option to remove the tax code from the dropdown menu of the tax code section. Why/how would it improve sales or efficiency: Allowing shops to remove invalid or incorrect tax codes prevents accidental selection during product setup (e.g., mistyping PCO40107 instead of PC040107). This eliminates tax miscalculations on products, reduces manual error cleanup, and speeds up product creation.

Confirm there are not already settings or features that do what the shop is asking for: Confirmed. Currently, AI Bestie doesn’t have the option to mark any product variant as Received or Not Received. Shop mentioned that : The existing MCP/Bestie integration endpoint (update_variant) allows updating variant detail fields such as color, size, SKU, cost, barcode, and dimensions, as well as updating unit counts via adjust_inventory_level. However, there is currently no capability or field within the API endpoint or AI Bestie to directly update the "Received" status of a variant. What does the shop want the product to do? The shop wants the MCP API endpoint (update_variant) and AI Bestie to support updating the "Received" status for a product variant. Specifically, they are asking to add a received boolean field (true/false) to the existing update_variant endpoint by inventory_id. Why/how would it improve sales or efficiency? Operational Efficiency: It automates and streamlines inventory receiving management by enabling AI Bestie (or external MCP integrations) to automatically flip variants to "Received" status without requiring staff to manually log into the CommentSold admin panel to update receiving statuses. Faster Time-to-Market / Sales: Rapidly marking inventory as "Received" ensures newly arrived stock instantly becomes accurate and available for selling, preventing inventory processing bottlenecks and sales delays.

Confirm there are not already settings or features that do what the shop is asking for. Confirmed that there are currently no existing bulk-edit features or MCP settings that allow toggling the "Final Sale" status across multiple products at once. Currently, the only method is to manually open each item individually in the Comment Sold User Interface and check the "Final Sale" box. What does the shop want the product to do? Expose the "Final Sale" product tag/field within Bestie and the Model Context Protocol (MCP) to enable bulk editing capabilities. Specifically, the shop wants to be able to select multiple products (or filter a large group of products) in MCP/Bestie and apply or remove the "Final Sale" flag with a single action, rather than editing each product one by one in the CS UI. Why/how would it improve sales or efficiency? Massive Time Savings & Operational Efficiency: Eliminates the tedious task of manually clicking into every individual product in the CS UI. For larger Shops with hundreds or thousands of SKUs, this reduces hours of repetitive work down to a single click. Faster Clearance & Promotion Setup: Allows Shops to quickly convert large inventory blocks into Final Sale status on short notice, helping them launch promotions faster and drive immediate revenue. Reduced Human Error: Minimizes the risk of missing individual items during bulk inventory updates, ensuring accurate policy enforcement across all eligible items and preventing unintended returns on clearance stock.

Confirm there are not already settings or features that do what the shop is asking for- There are currently no tools, parameters, or return fields within CommentSold’s Model Context Protocol (MCP) connection (including get_product_inventory, get_inventory_performance, and get_product) that expose or sync the Bin/Location field for product variants. What does the shop want the product to do- The shop is requesting a feature update to the CommentSold MCP connection to include the Bin/Location field within Variant records (e.g., adding bin_location or location to get_product_inventory and get_product variant payloads). Why/how would it improve sales or efficiency- Exposing inventory bin/location data directly via the MCP connection enables external systems, AI agents, and custom integrations to retrieve physical item locations instantly, speeding up picking, packing, and fulfillment. Eliminates the need for manual cross-referencing between CommentSold and warehouse management workflows, reducing physical search time and minimizing human error during order processing. Allows connected tools and third-party automated workflows to track physical shelf/warehouse placement alongside existing stock levels, colors, and SKUs in real time.

Shop would like detailed Free Gift With Purchase reporting. They want to be able to see the total revenue from orders containing this product so that they can see the overall revenue from the promotion.

Confirm there are not already settings or features that do what the shop is asking for: Confirmed. There is currently no built-in feature or setting that allows a shop to set a subscription without offering a discount. The system mandatorily requires a discount value between 1% and 99% when enabling subscription settings for a product. What does the shop want the product to do? The shop wants to create an exclusive subscription-only product without applying any discount (0% discount), selling it at its full regular price solely to recurring subscribers. Why/how would it improve sales or efficiency? Sales: It allows the shop to create exclusive, premium subscription offerings that drive recurring revenue without sacrificing profit margins through forced discounts. Efficiency: It eliminates the workaround of artificially inflating retail prices just to offset the mandatory 1%–99% system discount, streamlining product setup and pricing management.

Confirm there are not already settings or features that do what the shop is asking for. Confirmed. There are no user-facing settings or toggles to resolve this. The get_inventory_performance endpoint is currently omitting active variants, and the alternative get_products endpoint does not support a cost field by design. What does the shop want the product to do? The shop wants MCP and Bestie to have access to complete and accurate inventory cost data. To achieve this, they need either: All valid, archive variants to successfully pass through to the get_inventory_performance endpoint. A "cost" field added to the get_products endpoint (which currently captures all variants but lacks cost data). Why/how would it improve sales or efficiency? It will ensure accurate financial reporting and inventory calculations across MCP and Bestie. Currently, the missing endpoint data is causing massive reporting discrepancies (e.g., showing almost 2x the actual inventory cost value), forcing the shop to waste time manually building spreadsheets to audit and correct their monthly financials.

Shop is trying to make a product specific BOGO coupon and the search will not pull the product up in the coupons tab search box.

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