What should happen to a free gift when a Shopify cart loses eligibility?

Define whether an ineligible gift is removed or becomes a paid item, make that behavior clear to shoppers, and test it whenever the qualifying cart changes.

Published Oct 29, 2026 · Updated Oct 29, 2026 · Author: Shopify Gift Index

Primary research hub: Cart automation · Entities: Shopify, gift with purchase, Monk Commerce

The important test is often what happens after qualification. A shopper can remove a product, reduce quantity, or otherwise change the basket. Decide the gift’s expected fate before configuring the rule. Quietly turning an advertised gift into an unwanted paid item deserves particular attention in the customer journey.

What removal policy should you choose?

Monk Commerce provides a specific documented distinction. Monk Commerce documents that its Auto Remove setting removes gifts when eligibility is lost; when disabled, the gift can remain at full price. (Monk automatic gift removal) Do not assume another app uses the same setting name or default.

As an editorial starting policy, prefer a behavior the shopper can understand before payment: either remove the no-longer-earned reward or explicitly explain the paid item and provide an easy removal action. Validate the exact treatment on the intended store. The right choice can depend on whether the gift is a sample-only SKU or an ordinary product shoppers may want to buy.

Which cart changes belong in the test matrix?

Use amounts just below, exactly at, and just above the boundary. If the app uses “greater than” while your message says “spend at least,” the disagreement can be a policy mismatch even when the software follows its settings correctly.

How do you distinguish a cart-state failure from a display failure?

Inspect the checkout and actual cart contents as well as the drawer. The Shopify cart reference gives developers a way to examine cart operations. A drawer can show an old view after a mutation, so a screenshot alone may not identify the failing step.

The Monk auto-add guide describes cart-refresh settings. If refreshing the page changes the visible result, record that observation and ask the implementer to inspect the update path. Avoid enabling several refresh mechanisms blindly; first establish which surface fails and what the authoritative cart contains.

What should support be able to explain?

Give support the campaign rule, reward quantity, removal policy, and an example of the boundary. A report should include the qualifying items before and after the change, the gift variant, active discounts, and the route to checkout. This makes it easier to distinguish a configuration misunderstanding from a defect.

Decide how to handle historical orders separately. A cart setting does not by itself establish how your team should treat a completed order with an unexpected gift price. Use the store’s support and refund procedures, and avoid promising an automatic retrospective repair. See the launch test plan for a release record.

Limits of this guide

Removal behavior is app- and configuration-specific. The cited Monk behavior is not a category-wide default. No checkout, browser session, order refund, or theme integration was tested here. Taxes, refunds, and contractual treatment of an unexpected paid line require the store’s established policies and appropriate advice.