If you set up a discount but customers do not see a struck-through price in the cart, that is usually expected. Where the savings appear depends on the type of discount.
Where the strikethrough shows
Product-level discounts display the original price struck through with the sale price next to it, on that cart line, for every customer regardless of role. This applies to:
- A dollar or percent amount off a specific SKU
- BOGO (buy one get one) on a specific SKU
Example on the cart line: $3,799.99 $3,791.99.
Where the strikethrough does not show
Cart-level promotions do not change the line item price. Instead, the savings appear in the totals area of the cart. These include:
- An amount off the cart subtotal (for example, $200 off when a qualifying item is present). This shows as a Discount line beneath the Subtotal.
- Free shipping promotions. This shows as the shipping charge dropping to zero.
This is by design. The discount is not tied to a single product, so there is no single line to strike through.
Turning on the before-discount price
The product-line strikethrough is controlled by a FocusPoint setting (FocusPointShoppingCartSettings.DisplayPriceBeforeDiscountAsStrikeout). If you have a product-level discount and the original price is still not showing struck through, contact FocusPoint support to confirm the setting is enabled for your store.
A note on SAP and sale pricing
Product-level sale pricing can come from SAP through special prices, discount groups, or dated price-list rules. Those are mastered in SAP and read by the storefront when the page loads. Do not try to flag an item as on sale by editing it in the portal. Portal edits to product or price records get overwritten on the next SAP sync.
Still not displaying correctly?
If a product-level discount still shows no strikethrough, open a ticket with the SKU, the discount setup, and a screenshot of the cart so we can check the configuration.
Source tickets
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article