By the time a shopper reaches the cart, the product choice is made. A product page widget moves the offer upstream to the moment the decision is still open — which changes what the shopper adds, not just how much they add afterwards.
Add the app block. Place it in your theme editor next to the buy button. No theme code, no Liquid edits, and it is removable in one click.
Scope it to products. Show it on specific products, a collection, or everything. A widget on every product is a widget nobody reads.
It states the live condition. "Add one more and the second is free" or "spend $20 more for a free serum" — evaluated against the current cart, not hardcoded copy.
It carries through to the cart. The offer the shopper saw on the product page is the offer that resolves in the cart, so nothing changes under them.
The cart is where quantity decisions happen. The shopper has committed to a product and is now deciding how much. Threshold gifts, progress bars, and cross-sells all belong there because they operate on a cart that exists.
The product page is where selection decisions happen — which product, which variant, how many. Offers that change selection belong here: quantity breaks, BOGO on this specific item, bundle pricing. Telling a shopper in the cart that buying two of something would have been cheaper per unit is information arriving one step too late, and it produces the frustrating experience of having to go back.
The practical rule: if the offer would change what the shopper puts in the cart, it goes on the product page. If it would change how much they spend overall, the cart is fine.
The product page's job is the add to cart. A widget that pushes the button below the fold on mobile costs more conversion than any offer recovers, and this is the most common way product page offers go wrong.
Static offer copy on a product page ages badly and frequently lies. "Buy 2, save 15%" sitting on a page after the campaign ended is a promise checkout will not keep. Copy generated from the live rule cannot drift, because there is nothing to update by hand.
Specificity also raises performance. "Add 1 more for a free travel serum" names the action and the reward; "multi-buy discounts available" names neither. Where the shopper's current cart is relevant, use it: a shopper at $42 reading "spend $18 more" is being given an arithmetic answer, which is strictly more useful than being given the threshold and left to subtract.
Product page offers are harder to attribute than cart offers, because their effect appears one step later — in what gets added, not in a click on the widget. Judging them by widget clicks will understate them badly.
Use two measures instead. Units per order on products where the widget runs, compared with products where it does not, and the share of sessions reaching the cart with a qualifying cart composition. Funnel analytics track the offer from product-page view through to order so the upstream impression is credited for the downstream order, and an A/B test on placement settles the mobile-position question for your theme specifically.
Directly under the add to cart button. Above-button placement delays the primary action for every visitor in order to serve the minority who engage with the offer, and on mobile it frequently pushes the button below the fold.
No. The widget is a theme app block you place in the theme editor, and removing it is a single click. No Liquid edits and nothing left behind if you uninstall.
They do different jobs. Offers that change what the shopper selects — quantity breaks, BOGO on that item, bundle pricing — belong on the product page. Offers that change total spend, like threshold gifts, work in the cart.
No. Scope it to the products the offer actually applies to. A sitewide widget hedging with "selected products qualify" is noise on every page where the offer does not apply.
Yes. The widget evaluates the live rule against the current cart, so it can say "spend $18 more" rather than stating a threshold and leaving the shopper to do the arithmetic.
Yes. It inherits your theme's typography, spacing, and button styling by default, with a visual editor for deliberate overrides.
Yes. Every NUO AI feature is included at $0 — no paid tier, no order cap, no revenue share.
