Free Gift
A gift offer only the shopper can accept. Press it and it lands as a real WooCommerce product priced $0.00 — stock deducted, cart total unmoved.
Built for WordPress · WooCommerce
A LUMÉ demo store, on its cart page. The cart already holds two lines and three units: Classic White Tee at $18.00 with a quantity of two, so $36.00; Zip Hoodie at $54.00. The Subtotal reads $90.00, shipping is calculated at checkout, and the Total is therefore $90.00 as well. The cart badge in the store header reads 3, because it counts units rather than lines. Above the items table — the position the article’s own Display Settings screenshot is set to, Before Cart items table — sits the one element SalesMax draws: a heading reading A gift with this order inside a dashed card carrying a dark Free gift badge at its right corner and this page’s own SalesMax tag at its left. Inside the card: the Ribbed Beanie, a green FREE chip, its $12.00 shelf price struck through beside $0.00, a quantity of one, and a dark button reading Claim gift. A pointer crosses to the two prices and rests on them, then crosses to the button and presses it once. A fourth unit lands in the cart table below the hoodie as a line of its own, flagged Gift, carrying the beanie’s SKU, its $12.00 struck beside $0.00, a plain quantity of one rather than a stepper, and a line subtotal of $0.00. The cart badge steps from 3 to 4. Nothing else moves: the Subtotal still reads $90.00, the Total still reads $90.00, the tally in the store header still reads $90.00, and no script on this stage writes a figure of money at any point — every price here is authored markup. The pointer then crosses to the totals column and rests on the arithmetic, which has not changed, moves down to Proceed to checkout and presses it once. The button lights and the loop ends there — nothing navigates, no page changes. Nothing dims, nothing floats over the page and no popup appears. The gift is never added on its own: the single press is the only thing that puts it in the cart. The two original rows, their quantities and their line subtotals never change, and neither does the step breadcrumb. After a pause the cart is cut back to its opening state and the loop restarts; that cut is instant, never an animation, because a gift line seen fading away would stage a removal that never happens here.
LUMÉ is a demo store — every product, price, quantity and button label is its catalogue’s, not the plugin’s.
▲ typically +10% conversions** The one figure 8theme publishes for free gifts, and printed here with its source attached: their own SalesMax page reads “Free gifts can boost conversions by 10%” and credits it to Accenture. It is a line on a marketing page — no study is linked, and nothing in it measures this plugin. SalesMax’s own booster registry leaves this booster’s field empty, where it prints “typically +10–30%” for the cart-page booster next door. Read it as somebody else’s industry figure for gifts of this kind — not a study, not a promise and not a SalesMax measurement. Your own number appears per booster in the SalesMax dashboard.
A LUMÉ demo store, on its cart page. The cart already holds two lines and three units: Classic White Tee at $18.00 with a quantity of two, so $36.00; Zip Hoodie at $54.00. The Subtotal reads $90.00, shipping is calculated at checkout, and the Total is therefore $90.00 as well. The cart badge in the store header reads 3, because it counts units rather than lines. Above the items table — the position the article’s own Display Settings screenshot is set to, Before Cart items table — sits the one element SalesMax draws: a heading reading A gift with this order inside a dashed card carrying a dark Free gift badge at its right corner and this page’s own SalesMax tag at its left. Inside the card: the Ribbed Beanie, a green FREE chip, its $12.00 shelf price struck through beside $0.00, a quantity of one, and a dark button reading Claim gift. A pointer crosses to the two prices and rests on them, then crosses to the button and presses it once. A fourth unit lands in the cart table below the hoodie as a line of its own, flagged Gift, carrying the beanie’s SKU, its $12.00 struck beside $0.00, a plain quantity of one rather than a stepper, and a line subtotal of $0.00. The cart badge steps from 3 to 4. Nothing else moves: the Subtotal still reads $90.00, the Total still reads $90.00, the tally in the store header still reads $90.00, and no script on this stage writes a figure of money at any point — every price here is authored markup. The pointer then crosses to the totals column and rests on the arithmetic, which has not changed, moves down to Proceed to checkout and presses it once. The button lights and the loop ends there — nothing navigates, no page changes. Nothing dims, nothing floats over the page and no popup appears. The gift is never added on its own: the single press is the only thing that puts it in the cart. The two original rows, their quantities and their line subtotals never change, and neither does the step breadcrumb. After a pause the cart is cut back to its opening state and the loop restarts; that cut is instant, never an animation, because a gift line seen fading away would stage a removal that never happens here.
Goal Order DiscountWhere it shows
Eleven values in the Display Location select, of which one is the shortcode; seven in Mini cart location, of which one is Do not display.
Every field name, option and default on this page is read off one article: 8theme’s Free Gift, dated 12 January 2025, plus the ten screenshots it embeds. Nothing was invented to fill a gap, and where the source is silent this page says so. Two arithmetic notes first, because the suite has got them wrong before: ten cart-and-checkout positions plus a shortcode is the correct reading of the eleven-value select, and six mini-cart positions plus an off state of the seven-value one. Neither count is 8theme’s — the article prints no number for either list. Everything below is unanswered by the source, so nothing here is asserted either way:
Confirmed and worth stating plainly: the gift is a real WooCommerce product and is deducted from stock like any other item during checkout; it appears at $0 in the cart and in the order summary at checkout; it is hidden or removed automatically when the cart stops qualifying; the shortcode is [smax_free_gift]; the Elementor route is documented with two screenshots and restricted in writing to Cart or Checkout page templates; and the admin preview carries desktop and mobile toggles alongside an Advanced preview button.
Templates & appearance
Two templates, one accent and six strings you type — the card stops looking like a plugin and starts looking like your store.
Emptying a field drops its element here — this preview’s reading, not a documented behaviour. The admin’s Offer title field holds a merge token, {discount}, which their capture renders as FREE; the token vocabulary is unpublished, so this field prints a literal.
The math
Say 400 orders a month, 12 in 100 qualifying carts press the button, and each beanie costs you $4 to put in the box: 400 × 12% × $4 = −$192/mo, and 48 gifts out the door. Press the keys.
The control room
Four decisions carry this booster — the gift, its quantity, its price and how often it may be claimed. Everything else is targeting.
Tap the chips — the rule sentence rewrites itself. Every chip here is an option the article or a screenshot names.
The shopper still has to press Claim gift — nothing is added for them.
The admin panel labels these Choose a Gift Product (placeholder Choose product) and Offer Quantity (placeholder Custom). The prose calls the first one Offer Product and describes it as “the product that will receive a discount or special treatment when the combo is triggered” — combo being one of several strings in this article that belong to a different booster. Where the two disagree, the screenshot is what merchants will actually see.
Four options, quoted: Percentage — e.g. 20% off; Fixed — e.g. $5 off; Free — price is reduced to $0; No discount — offer product will be shown with their regular price. A Discount Value field is described in the prose (enter 15 for 15% off, 10 for $10 off; “not applicable” under Free or No discount) and does not appear in the one screenshot of that panel, which has Gift type set to Free. Hidden or ignored is unresolved.
Total Usage Limit — “the maximum number of times this offer can be used across all customers”, with the tip “useful for running limited-time campaigns or stock-controlled offers”. Usage Limit Per Customer — “how many times an individual customer can claim the offer”, with the tip “helps prevent abuse of the promotion by restricting repeated use per user”. Both carry the placeholder Unlimited usage, so unlimited is the shipped state.
Ticked in the General capture, and in no sentence of the article: “Allow customers to remove Add-ons from the cart?”. It still says Add-ons, which is the name of a different booster. What it governs here is a guess we are not going to make — and note that every rendering of the claimed line, theirs and ours, carries an ordinary WooCommerce Remove link regardless.
The live panel holds Title, Subtitle, Subtitle badge, Offer title, Offer CTA button text and an Image Source select reading Product image. The prose instead lists Offer Title, Offer Title Badge, Offer Subtitle and Offer Subtitle Badge — and gives the title and subtitle character-identical descriptions, and the two badges another pair of identical ones. Offer title in the screenshot holds a merge token, {discount}, documented nowhere.
Captured, unlike the prose’s generic four groups: Template styles with a Reset All, Border radius (px) 12, Border: Medium, Border style: Dashed, Border Color #e1e1e1, Background color #ffffff, Body padding 20 left/right and 12 top/bottom, Header font size 25. The capture stops there. That dashed border and 12px radius are the plugin’s shipped default, which is why every card on this page wears them.
Display Location, eleven values, one of which is Use a shortcode; Mini cart location, seven values, one of which is Do not display. The screenshot shows Before Cart items table and Do not display. Neither is called a default anywhere, and the article prints no count for either list.
This booster has no Apply to panel at all, so the article’s own triggers — spend over $75, buy 3 or more bags — are only reachable here. The panel’s own help text: “Add conditions if you would like to personalize based on the items in the cart, order total etc. (optional)”. Grouped as Order: products, categories, tags, SKUs, number of line items, item quantity, applied coupons, order total. Purchase History: first order, number of orders made, orders with specific products, total spent. User: role, logged in, specific users. Date & Time: time, days.
SalesMax → Sales Boosters → + New Booster, choose Free Gift, then — their spelling, quoted — “Name your booster, configurate settings and save”.
The panel at the foot of the configuration holds Priority (10 in the screenshot — in the picture and in no sentence of the article), a Start date (20.03.2025), a ticked Set end date checkbox and the End date it reveals (23.04.2025). Only the dates are written up. Scheduling is day-granular, so a time-of-day window is Conditions → Date & Time → Time; the timezone is unpublished.
Confirm the booster is enabled in the boosters list. Ensure the conditions (cart total, products, quantity) are being met. Check that the gift product is published, in stock, and visible. Disable aggressive caching plugins temporarily. Make sure the booster is assigned to the correct display location. Avoid conflicts with other boosters that modify the cart or apply discounts simultaneously.
The FAQ adds three: confirm the selected display position is compatible with your theme; a custom or heavily modified theme may be missing WooCommerce hooks; and switch to Use a shortcode and place [smax_free_gift] by hand. Or take the Elementor route — open the Cart or Checkout page editor, find the SalesMax widget, drag it in, choose Free Gift, save. That widget is restricted to Cart or Checkout page templates in its own panel.
No booster-specific analytics, no A/B split and no claim-rate reporting is documented for this booster. Translation, RTL behaviour and AJAX are likewise unpublished — which matters more than usual for a block that has to appear in a mini cart.
FAQ
The article answers this twice and then contradicts itself once, so here are all three passages, in the order they appear. Frontend Result: “The gift will not be added automatically. Instead, the customer will see a Claim Gift button that allows them to manually add the free item to their cart.” The FAQ question “Can I auto-add the gift to the cart?”: “No. The Free Gift booster currently supports manual gift selection only. Customers must actively click the “Add Gift” button to include the gift in their cart once the conditions are met.” The FAQ question “What happens if the customer removes the qualifying product?”: “The booster will automatically re-evaluate the conditions. If they’re no longer met, the gift will be removed from the cart if it was auto-added.” The third sentence presupposes a state the first two deny exists. What is settled either way is the removal: Frontend Result states independently that if the cart no longer qualifies the gift will be hidden or removed automatically, so a gift that stops qualifying goes, however it arrived. What is not settled is whether any auto-add path exists at all. Our reading — and it is a reading, not a fact — is that the third sentence is boilerplate carried over from a booster that does add automatically, in an article that also calls this offer a “combo”, calls the block a “recommendation block” and calls the gift an “Add-on”; three other leaked strings, all visible on the same page. This site’s demo therefore never adds the gift on its own, and never will until 8theme says otherwise. Test it on a staging copy before you write a policy around it. One more thing the same passages leave open: the button’s wording. Frontend Result calls it Claim Gift, the FAQ calls it “Add Gift”, and all three of 8theme’s screenshots show Add gift to cart typed into the Offer CTA button text field. It is free text with no published default — ours reads Claim gift.
The field exists and it has four values, but the two sources name it differently: the prose calls it Discount Type, the admin screenshot labels it Gift type. Its options, quoted: Percentage, for example 20% off; Fixed, for example $5 off; Free, where the price is reduced to $0; and No discount, where the offer product will be shown with their regular price. A Discount Value field is described in the prose — enter 15 for 15% off, enter 10 for $10 off, not applicable if Free or No discount is selected — and it does not appear anywhere in the one screenshot of that panel, which has Gift type set to Free. So whether the field is hidden or merely ignored under Free is unresolved. Two more silences worth naming. Nothing published says whether a discounted, non-free gift still renders with the FREE wording and the gift framing on the storefront, so this page chips that line green only when the price is actually zero: a line that states an offer gets the chip, a line at its regular price does not. And nothing says how a percentage or fixed gift interacts with a coupon, a tax rule or a shipping calculation.
Display Location is one select with eleven values, of which one is Use a shortcode: four read as cart-page positions — Top of the Cart page, Before Cart items table, After Cart items table, After Cart items within the table — and six as checkout positions — Before Payment Gateways, Before Place Order Button, After Place Order Button, Bottom of the Checkout Page, Before Billing section, After Order notes. So: ten positions and a shortcode. Mini cart location is a second select with seven values, of which Do not display is an off state, leaving six positions: Top of the Mini Cart, Before Cart items, After Cart items within the list, Before buttons, After buttons, Bottom of the Mini Cart. The article prints no count for either list, and it names no default for either: the one screenshot of that panel shows Before Cart items table and Do not display, which are shown values and not stated defaults. Their own two tips: placing the booster after the cart items or before the payment section can increase visibility and engagement right before conversion, and adding the gift offer near the mini cart buttons is effective for last-minute upsell actions. There is also an Elementor route, and its own panel carries the restriction in writing: this booster can only be used on Cart or Checkout page templates. What nobody publishes is whether all eleven values are offered on both page types or filtered per page.
Yes on both counts, and the article is unusually direct about it. Asked whether the gift reduces stock, it answers: “Yes. The gift item is a real WooCommerce product and is deducted from stock like any other item during checkout.” Frontend Result adds that once added, the gift appears as a regular product in the cart with a price of $0, and will also be included in the order summary at checkout. Every rendering of the claimed line — theirs and this page’s — carries its own Remove link, like any other cart row. One thing sits in the admin panel with no sentence attached to it: a ticked checkbox reading “Allow customers to remove Add-ons from the cart?”. It is undocumented in the prose, and it still says Add-ons, which is the name of a different booster. What it governs here is a guess we are not going to make.
Two fields, both documented. Total Usage Limit sets the maximum number of times this offer can be used across all customers, and the article’s own tip calls it useful for running limited-time campaigns or stock-controlled offers. Usage Limit Per Customer defines how many times an individual customer can claim the offer, and its tip says it helps prevent abuse of the promotion by restricting repeated use per user. Both fields carry the placeholder Unlimited usage in the screenshot, so unlimited is the shipped state. Read the FAQ answer about this carefully, though, because of one word: it says the setting ensures each logged-in user can claim the gift only once. Nothing published says how a per-customer limit is enforced against a guest checkout, and nothing says what happens if a limit is reached while a shopper is mid-session with the offer already on screen.
One gift per booster: asked whether multiple free gifts can be applied at once, the article answers that only one gift per booster is possible and that if you want to offer multiple gifts you can create separate boosters with their own rules. It also confirms the multiple-campaign route for targeting: create several Free Gift campaigns and set different product, category or cart condition filters for each one. What is not published is what happens when two of those campaigns qualify on the same cart. A Priority field exists — it sits in the Optional Settings screenshot reading 10 — and no sentence anywhere says what it orders or which direction wins. Note too that this booster has no Apply to panel of its own, so the trigger behind their own examples, spend over $75 or buy 3 or more bags, is only reachable through Conditions: Order total, Order items quantity, Products in Order. The article never says that in words.
Works well with
A gift is one thing that can happen on the way to checkout. The row starts with the boosters that share the same screen, then runs through the rest of the suite.
Offers shown right in the cart, on top of what the shopper already has.
▲ typically +10–30%*Learn moreSmall upgrades and companion products, one tap from the cart summary.
▲ +29% sales*Learn more“Spend $80, get 10% off” — tiered rewards that pull the total upward.
▲ +18% avg. spend*Learn more“You’re $11 away from free shipping” — the most effective sentence in e-commerce.
▲ +30% AOV*Learn moreTiered quantity discounts that make the bigger order the obvious choice.
▲ +30% order value*Learn moreA last relevant order bump right before payment — accepted with one checkbox.
▲ +35% conversions*Learn moreShow the products that naturally belong with this one, added in one click.
▲ +35% sales*Learn moreCondition-based suggestions by category, cart contents, order history or totals.
▲ +31% revenue*Learn moreOffer catalogue extras on the product page — ticked in one go, each with its own discount.
▲ +20% AOV*Learn moreA relevant offer the moment something is added to cart — one popup, not a maze.
▲ +20% conversions*Learn moreLive inventory counts that create honest urgency — real stock levels, never fabricated.
▲ +17% conversions*Learn moreSubtle purchase notifications — from your real recent orders, or from name lists you write.
▲ +15% conversions*Learn moreLet buyers duplicate their purchase with a single click — popular for consumables and gifts.
▲ +73% uptake*Learn moreUpsells on the order-confirmation page, where trust is already established.
▲ up to 3.1% conversion*Learn moreOne-click additions right after “Place order” — no re-entering payment details.
▲ +10% revenue*Learn more* Industry benchmarks and vendor-observed averages for each booster type — not a guarantee. SalesMax publishes none for Free Gift, which is why this page carries no figure of its own.
Free Gift
A gift nobody asked for is packaging. A gift someone reached for is a reason to come back — on every plan, no feature gating, ever.