Sell more without risking the sale.

Largely, yes — and we would rather say so than pretend otherwise. This is a mature, well-served category. Rebuy, AfterSell, Zipify OCU and ReConvert / Upsell.com all ship a working one-click post-purchase offer, and a competent in-house merchandiser can have a static offer live in an afternoon. What is harder to self-serve is the part that separates the bottom of the published take-rate range from the top: the ranking logic fitted to your own catalogue, margins and pair history, the one-time-to-subscription upgrade path wired into your subscription platform, and the suppression rules that stop the offer contradicting what the customer just bought. If all you need is a single static offer, install the app and keep your money.

It decides which of your approved offers appears for a given completed order, scored on the SKU, variant, pack size and quantity just bought, the margin left after the discount, how often that pair has actually been bought together in your own history, and whether there is a subscription contract behind the order. It does not write the offer, set the price, invent a product claim or override a constraint: suppressions — the item just bought, a contradicted flavour or allergen variant, an active subscriber, the frequency cap — are hard rules, because those are cases where being wrong two percent of the time costs more than any lift is worth. Before launch it is replayed against a quarter of real orders so you can read its choices order by order.

Not for the original order. The offer runs after the payment has been captured, so the order exists whether or not the customer accepts. That is the structural reason this slot is worth building well and the reason it is a much easier internal decision than a product-page or cart upsell. What it can cost you, if built carelessly, is trust and support load — an offer that pitches the item someone just bought, or a flavour that contradicts a dietary choice they made deliberately, is a bad experience attached to an otherwise good order.

We will not forecast a number for your account, and you should be sceptical of anyone who does. The published figures are 4.7–15% take rate across implementations and a 5.6% average AOV lift reported by ReConvert across more than 40,000 merchants. Well-targeted implementations are reported at 10–25% AOV lift, and a full-funnel programme covering product page, cart and post-purchase at 20–30%. Every one of those figures is vendor-reported — measured and published by companies that sell the software — and we have not found an independent third-party study to set against them.

Because a vendor’s average across its own install base is a real measurement of something, but not of what it is usually quoted for. It is not a controlled comparison against the same stores without the app, it is drawn from merchants who chose to install and keep paying for the software, and it is published by a party with an interest in the result. That does not make it false. It makes it a starting hypothesis rather than a forecast, and it is why the only number we will ever quote back at you as yours is one measured in your own store.

Some of them would have. An AOV lift measured on orders that took the offer counts every accepted upsell as new revenue, including the customers who would have come back for that product next month at full price. The honest way to read it is as accelerated revenue with an unknown incremental share, which is why we instrument return rate and downstream subscriber retention alongside take rate. If an offer is pulling forward purchases and adding returns, the average order value goes up and the business does not.

Whichever one your stack argues for. Rebuy is the strongest fit when the targeting logic is doing the heavy lifting across the whole funnel, AfterSell and Zipify OCU when the post-purchase slot is the whole job, ReConvert / Upsell.com when the thank-you page is being rebuilt as well. If you already run one of them, we build inside it rather than migrating you for the sake of it. App subscriptions run $79–$449 a month and you pay the vendor directly — we do not resell software and we take no margin on it.

Yes. The subscription-upgrade offer and the second-SKU offer both have to write into whatever subscription platform you already run, and all four are common in this category. What changes between them is how a contract is created or amended from outside the checkout, and what has to be built around each platform’s limits — that is the part of this build that is genuinely engineering rather than configuration.

They do different jobs at different moments and they should be built to know about each other. The post-purchase offer works in the sixty seconds after payment, while attention and the payment method are both still available. The lifecycle flow works over the following weeks, on replenishment timing rather than on impulse. If the customer took the upsell, the flow should stop selling them that product — coordinating the two is part of the build, and the email side is covered under lifecycle flows.

No, and that is usually the better starting position. Where it goes wrong is when the product-page widget, the cart drawer and the post-purchase page each carry their own rules and nobody owns the sequence. We put one set of rules across all three, so a customer who declined a product in the cart is not shown it again ninety seconds later, and so a single order does not become three separate asks.