Close the Loop

What is the shop or customer experiencing: Shop is noticing that the Subscription Dashboard displays 6 "Active" subscriptions (and 0 "Failed") for a specific product variant, despite only showing 4 orders being created from inventory logs. Subscriptions with failed payment charges are not updating or surfacing in the "Failed" column on the Subscription Dashboard. What is the expected behavior: Subscriptions with failed payments should update to "Failed" status, surface under the "Failed" column on the Subscription Dashboard, and be excluded from the "Active" count so the active subscription count accurately reflects the orders populated in the shipping queue. What error messages are there: None. There are no UI error messages displayed; this is a data surfacing/status calculation discrepancy. Did you replicate: Yes. Verified that the Subscription Dashboard displays 6 Active subscriptions for the variant while only 4 checkout showing in inventory log with subscription renewed. Cross-referencing the inventory logs confirmed that payment attempts failed for 2 customer accounts immediately after the item was added to the cart. What settings were checked: Subscription Dashboard: Active vs. Failed status counts. Subscriptions for Customers Tab: Customer listing and charge statuses. Inventory Logs: Filtered by SKU/variant to trace charge attempts. Provide examples, sku, order #, customer names, and screenshots where possible: Product Variant: Center Zip Mini SKU: MJ-SUB Affected Customer Accounts: Sara, Asia Data Discrepancy: Dashboard displays 6 Active subscriptions; Inventory logs displays 4 items are checkout with subscription renewed; Inventory Logs confirm 2 failed payment transactions.

Feature Availability Confirmation Current Status: Not currently available in the CommentSold UI, MCP API, or Bestie. Details: CommentSold currently lacks a user interface option to archive or unarchive products and variants. While archiving full products is exposed via MCP/Bestie, it lacks variant-level support: MCP/Bestie cannot update the archive status of individual variants, nor can it modify attributes (e.g., sale price, retail price, cost, collections) on variants that are already marked as archived. What the Shop Wants the Product to Do Variant-Level Archive Control: Enable MCP and Bestie to archive and unarchive specific product variants (rather than just entire products). Attribute Editing for Archived Variants: Allow MCP and Bestie to edit attributes (e.g., prices, costs, barcodes, collections) on archived variants. Why & How it Improves Sales and Efficiency Enables Unreleased Product Preparation: Shops use the "archived" status as the primary method to hide upcoming or unreleased variants from shoppers before launch. Saves Time & Prevents Manual Workarounds: Allowing shops to update sale prices or costs on archived variants via MCP/Bestie lets them prepare promotional releases ahead of time in bulk without having to make variants visible to customers prematurely or edit them manually. Ensures System Consistency: Aligns backend tool capabilities (Bestie/MCP) with expected inventory workflows so shops can rely on automated assistant tools for full lifecycle product management.

Previously this shop was able to filter the best selling reporting tab by brand and navigate from that same screen. They can no longer do this with the new reporting screens. We only provide the product ID number and no links. They would like this changed or at least legacy reporting re-enabled for the busiest time of the year.

The shop is wanting to purchase a printer that will collate all of their orders when they print. Currently they spend a lot of time stapling together multiple page orders and this would save them a lot of time, but it's not worth it if CS prints them all as one unit rather then individual.

Confirm if settings/features already exist: No, CommentSold currently does not offer a report or setting that breaks out these line items at the order level. While Report No. 12 (CSV12) provides general line-item details, it excludes coverage fee data for third-party add-ons like Redo and Seel. What does the shop want the product to do? Provide complete order-level line-item breakouts in CommentSold reports (such as CSV11 or CSV12). Specifically isolate and break out revenue collected for add-on services like Redo and Seel for every customer order. Why/how would it improve sales or efficiency? Accurate Financial Reconciliation: Allows the merchant to reconcile large third-party invoices (e.g., Redo charges) against actual revenue collected from customers through CommentSold. Eliminates Data Gaps & Blind Spots: Resolves the issue where merchants know their add-on costs but have no visibility into whether or how much payment was collected on each order. Saves Time: Automates data extraction via CSV, eliminating manual auditing or reliance on third-party reports that lack CommentSold line-item data.

What is the shop or customer experiencing: The shop has duplicate variants with the exact same names ("North Pole" and "Ocean Cottage") under a single product. When attempting to select and delete only one of the duplicate variants, the system automatically selects both identical variants simultaneously, preventing the shop from deleting just the duplicate copy. What is the expected behavior: The system should allow the shop to select and delete only the duplicate variant entries while retaining the original variants, along with their associated waitlists and pre-authorizations. Additionally, the system should not allow identical duplicate variant names to be created under a single product. What error messages are there: N/A (No error message is displayed; it is a UI selection/duplication issue). Did you replicate: Yes. Confirmed on the shop's dashboard that selecting one variant automatically checks/selects both identical duplicate variants on the product details page. What settings were checked: Checked Products > Variant on the dashboard, as well as the shop logs (which confirmed the product was created directly on the dashboard, not via CSV import). Provide examples, sku, order #, customer names, and screenshots where possible: Shop Name: Aly Jean Boutique (Shop ID: 18494) Product Name: RAE Shower Steamers (new SKU) SKU: raeshowersteamers001 Duplicate Variants: North Pole & Ocean Cottage

Shop would like to view a product's bin location on mobile view of the New Product Pages' Product Tab, without having to click into the product and scroll to the inventory page.

What is the shop or customer experiencing? When adding a product with variants to the cart on the customer page, the variants in the cart view do not display in the sequence defined on the product detail page. Instead, the order appears shuffled. What is the expected behavior? The sequence of variants in the cart should exactly match the variant order on the product detail page. What error messages are there? The sequence/order of the variant in the cart are shuffled. Did you replicate? I have successfully replicated the issue and confirmed that the variants appear in the admin cart view in customer page sorted by the same sequence product had at the time it was added. What settings were checked? Product listing/variant setup on the product details page in CommentSold.

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.