Sold Count Display in GT Extensions for FluentCart

Sold Count Display adds a sales-quantity badge to a product, such as 76 sold. The count comes from the product’s completed and processing FluentCart orders, giving shoppers context about past demand.

Treat the number as a product quantity, not a count of unique customers. One order containing 4 units contributes 4 to the quantity total.

Configure the Badge

Enable Sold Count Display under FluentCart → GT Extensions, open Configure and save your choices.

• Badge Text uses {count}, such as {count} sold.
• Count multiplier scales the number the badge shows. It stays at 1, the real count, until you change it.
• Minimum Count controls when the badge becomes visible.
• Show on archive cards controls listing-page placement.
• Show on single product page controls product-page placement.

Use the Count Multiplier

The badge shows the real count times the Count multiplier, rounded up to a whole number:

• 12 sold × 6.32 = 75.84, which shows as 76 sold.
• 10 sold × 1.5 = 15, which shows as 15 sold.
• The multiplier accepts any number from 0.01 to 100. Anything outside that range falls back to 1 or is capped at 100.
• A product with no sales stays at 0, whatever the multiplier.

One use that holds up: you sold the same product on another platform before moving to FluentCart, and the multiplier brings the badge closer to your lifetime total. Use it to reflect sales that really happened, not to invent demand. A count that doesn’t match real sales can mislead buyers and may break consumer-protection rules where you sell.

Example: Wait for a Meaningful Count

Set Minimum Count to 10 and Badge Text to {count} sold. A product with 7 sold units has no badge; a product with 12 displays 12 sold. This keeps small or empty counts from cluttering the catalog.

Minimum Count is compared with the count the badge shows, after the multiplier. With a multiplier of 2 and a Minimum Count of 10, a product with 5 real sales shows 10 sold.

What the Count Includes

The count sums item quantities for the product from orders with a completed or processing status. Orders in any other status are left out.

It is not a financial report of net sales after every refund or adjustment. Use FluentCart reports for accounting and reconciliation.

Check Missing or Unexpected Counts

Check that the module and the relevant display location are enabled, the Minimum Count is met and the orders are completed or processing. If a badge looks higher than your orders, check the Count multiplier first. A request-level cache avoids repeating the same calculation during one page render; it is not a persistent sales-report cache, so a page cache on your product pages can still show an older number until it refreshes.

Developers can use the sold-count endpoint or the gt_extensions_fluentcart/sold_count filter. The filter runs on the real count, before the multiplier. Keep any customized count truthful and document what it includes. The hooks and REST guides show the integration points.