Word of mouth is the oldest acquisition channel there is, and for most stores it is also the most wasted. A customer who genuinely likes what they bought will tell a friend — but only if the moment lines up, only if telling is easy, and usually only once. A referral program is the system that turns that one accidental mention into a repeatable channel: it gives your happiest customers a reason to share, a frictionless way to do it, and a reward when it works. Done well, it quietly becomes a sales team you don't pay a salary to.

This post is about the strategy — why referrals out-convert cold traffic, how to design rewards that pay for themselves, when to ask, and how to keep the program from being gamed. The hands-on PrestaShop wiring (cart rules, attribution cookies, reward fulfilment, launch sequence) lives in its own guide: referral programs for PrestaShop, turning customers into salespeople. Read this one to decide what to build; read that one to build it.

Last updated: June 2026.

Why a referred customer is worth more than a cold one

Two people passing a glowing referral reward token between their phones, illustrating word-of-mouth recommendation
A referral program turns a happy customer's recommendation into a repeatable channel, passing rewards from one person to the next.

A referral arrives pre-sold. Someone the buyer already trusts has vouched for you, which collapses the part of the funnel that normally costs the most — the "is this store legit, will the product actually be good, will they ship it" doubt. Industry write-ups consistently report that referred customers convert at a noticeably higher rate than cold traffic and stick around longer; the figures cited vary by source and category, so treat them as directional rather than a number you can bank. The mechanism, though, is not in dispute: trust transfers, and trust is the expensive thing to manufacture with ads.

So what does that mean for your store? Two things worth real money. First, a referral channel tends to produce a lower cost per acquisition than paid ads once it's running, because your reward only fires after a sale — you're paying for outcomes, not impressions. Second, the customers it brings in look more like your best existing customers than the ones a broad ad campaign drags in, because people refer friends who are actually a fit. You're not just acquiring cheaper; you're acquiring better.

The "give and get" mechanic — and why both halves matter

The structure that works is two-sided: the friend gets an incentive to try you, and the referrer gets a reward for the introduction. Drop either side and the program stalls. A reward only for the referrer feels like you're asking customers to spam their friends for your benefit. A discount only for the friend gives your customer no reason to bother sharing. Both halves together make the share feel like a gift the customer is handing over, with a thank-you waiting for them.

A concrete shape: "Give a friend 10% off their first order; you get €10 in store credit when they buy." The friend has a low-risk reason to try a store they'd never heard of. The referrer has a tangible, store-bound reason to do the work of sharing. Keep the offer to one sentence each side — if a customer has to read a paragraph to understand what they get, you've already lost most of them.

Choosing a reward structure

The reward type changes both your cost and the behaviour you encourage. The four common structures, and what each one is actually good for:

StructureWhat the referrer getsCost to youBest for
Discount + discountPercentage or fixed discount on their next orderLow — only redeemed against a future purchaseMost stores; the simplest thing that works
Store credit + discountCredit to spend on their next orderLow, and it drives a repeat purchaseStores wanting referrals to also lift retention
Cash / PayPal + discountReal money outHigh — pure expense, no repeat-purchase upsideHigh-AOV stores where one referral is worth a lot
Tiered rewardsBigger rewards as referral count climbsVariable; rewards your most active advocatesStores with a loyal core who will refer repeatedly

For most PrestaShop stores, store credit for the referrer is the quiet winner. It costs you less than cash, and because the credit only converts to value when the customer comes back and spends, it pulls double duty as a retention nudge — the referrer is holding a voucher/credit code assigned to them that nags them to return. On PrestaShop that credit isn't a wallet balance; it's just a cart rule (voucher) restricted to their account, unless you add a wallet/loyalty module; the mechanics are covered in the implementation guide.

Setting the reward amount: it's an acquisition cost, so price it like one

The single most useful framing: a referral reward is a customer acquisition cost, and it should come in under what you already pay to acquire a customer elsewhere. If a paid-ads customer costs you €15 to win, a €10 total referral reward is a bargain — you pay less and get a higher-quality customer who's more likely to stay. If your reward creeps above your ad CAC, you've built a more expensive channel, not a cheaper one.

Sensible starting points, to calibrate against your own numbers:

  • Friend's discount: roughly 10–15% off the first order — enough to tip a hesitant first-timer, not so much that you've trained people to expect a permanent discount or devalued the product.
  • Referrer's reward: a fixed amount in the €5–15 range depending on your average order value, or a small percentage of the referred order — generous enough to feel like a genuine thank-you.
  • The ceiling: friend discount plus referrer reward should sit below your typical acquisition cost from paid channels. That's the line that keeps the program honest.

If you don't know your acquisition cost, that's the first thing to fix — without it you're guessing. Tie the program's reward spend and the resulting orders into your reporting so you can see the real per-customer cost; our Financial Revolution module surfaces revenue and cost data per channel from the back office, which is what lets you compare "referral" honestly against "ads" instead of trusting a hunch.

When to ask — timing decides participation more than the reward does

You can have a generous reward and a beautiful share page and still get near-zero participation if you ask at the wrong moment. The reliable principle: ask when the customer is feeling good about you, and never before they've actually experienced the product. The high-value moments:

  • Post-purchase confirmation. Right after checkout the customer is at peak excitement about their decision. A light "Love what you ordered? Give a friend 10% off" rides that feeling. It belongs in your post-purchase flow — what else goes there is covered in post-purchase emails, what to send after someone buys.
  • A few days after delivery. Five to seven days out, once they've actually used the thing, "Enjoying your [product]? Your friends might too" lands when the satisfaction is real, not anticipated.
  • After a positive interaction. A resolved support ticket or a five-star review is a peak-goodwill moment — the customer just had a good experience with your brand and a referral ask feels natural rather than grabby.
  • The account dashboard. A persistent, low-key "Refer a friend" section is always available without pestering anyone — it catches the customer in the rare moments they go looking.

The one rule that overrides all of these: don't ask before the product has arrived and been used. A referral request that lands while the box is still in transit feels presumptuous and slightly desperate — you're asking someone to vouch for an experience they haven't had yet.

Make sharing effortless, or it won't happen

Every extra step between "I'd recommend this" and "I sent the link" loses people. Drive that friction toward zero:

  • A one-click link or code. Copy in a single tap, shareable however the customer actually talks to friends — WhatsApp, email, a group chat, wherever.
  • A pre-written message they can edit or send as-is. "I got [product] from [store] and it's great — here's 10% off: [link]." Most people won't compose their own; hand them one.
  • Channel buttons. A WhatsApp button matters in markets where that's how people share — and meeting customers on the channel they already use is a recurring theme; see WhatsApp chat for PrestaShop.
  • Visible reward tracking. Show the referrer how many people clicked, how many bought, and their current balance. Seeing a reward edge closer is itself motivation to share again.

Designing against abuse — without strangling the program

Any program that hands out money attracts people trying to game it. The goal is not to eliminate every cent of leakage — that's impossible and the policing costs more than the fraud. The goal is to design out the systematic abuse while letting genuine referrals flow. The main patterns and the design choices that blunt them:

  • Self-referral. A customer makes a second account and refers themselves. Blunt it by restricting the friend's reward to genuinely new customers (no prior orders) and watching for matching addresses, payment methods or IPs.
  • Coupon-site farming. Referral codes get posted on public deal sites and used by strangers, not friends. A minimum order value and a "new customers only" rule cut most of the value out of that.
  • Circular referrals. A clique refers each other in a loop to harvest rewards. Caps — a maximum number of rewarded referrals per period — flatten this without punishing a customer who legitimately refers several real friends.

The honest framing: a small amount of abuse is just a cost of running the program, and usually a tiny one against the total value. Build the structural guards in once — some come from a referral module, and others are plain PrestaShop cart-rule settings (minimum spend, total usage limit, per-customer usage limit, restricting a voucher to a single customer) — and then stop worrying about policing every individual referral. The implementation guide walks through where these settings actually live: referral programs for PrestaShop.

Referrals are one lever in a retention system, not a standalone trick

A referral program works best bolted onto customers who already have a reason to be loyal — and it shares a lot of plumbing with the rest of your retention stack. It's worth seeing where it sits:

Measuring whether it's actually working

Run a referral program on instinct and you'll either kill a channel that was working or pour rewards into one that isn't. Track a small, honest set of numbers instead — and give it volume before you judge it, not a noisy first fortnight:

  • Referral rate. What share of customers refer at least one friend? This tells you whether the asking works — low numbers usually mean wrong timing or too much friction, not a stingy reward.
  • Referred-visitor conversion rate. Compare it to your organic and paid conversion rates. If referred visitors aren't converting better, your attribution may be broken, or the friend's incentive is too weak.
  • Cost per referred customer. Total rewards paid divided by customers acquired — the number that decides whether this beats your ad spend. Put it next to your other channels in Financial Revolution rather than eyeballing it.
  • Referred-customer retention and lifetime value. The whole premise is that referred customers are better customers; this is where you confirm it on your store rather than trusting an industry average.

Frequently asked questions

How big should the referral reward be?

Treat it as an acquisition cost and keep the friend's discount plus the referrer's reward below what you already pay to win a customer elsewhere. If a paid-ads customer costs you €15, a €10 total referral reward is a bargain for a higher-quality customer. Sensible starting points: roughly 10–15% off the friend's first order, and a €5–15 fixed reward for the referrer depending on your average order value. If your reward creeps above your ad acquisition cost, you've built a more expensive channel, not a cheaper one.

Why is store credit usually better than cash for the referrer?

Because it costs you less and pulls double duty. Cash is pure expense with no upside; store credit only becomes real value when the customer comes back and spends, so it doubles as a retention nudge. On PrestaShop that credit is typically a cart rule (voucher) restricted to the referrer's account, not a wallet balance — unless you add a wallet/loyalty module.

When should I ask a customer to refer a friend?

When they're feeling good about you and have actually experienced the product — never before it arrives. The strong moments are post-purchase confirmation, a few days after delivery, after a resolved support ticket or five-star review, and a persistent low-key "Refer a friend" section in the account dashboard. A request that lands while the box is still in transit feels presumptuous.

How do I stop people gaming the program?

Design out the systematic abuse and stop worrying about the rest. Restrict the friend's reward to genuinely new customers (no prior orders), set a minimum order value, cap rewarded referrals per period, and watch for matching addresses, payment methods or IPs. Most of these are plain PrestaShop cart-rule settings — minimum spend, total usage limit, per-customer limit, and restricting a voucher to a single customer. A small amount of leakage is just a cost of running the program.

The underlying idea is unglamorous and durable: your happiest customers will recommend you anyway, and a referral program is just the system that makes that recommendation easy, well-timed and rewarded. Get the economics right — reward under your acquisition cost, store credit that doubles as retention, an ask that lands at peak goodwill — and you've added a channel that gets cheaper and better the more your existing customers like you. When you're ready to wire it into PrestaShop, the step-by-step is in referral programs for PrestaShop, turning customers into salespeople.

Share this post:
David Miller

David Miller

Founder, mypresta.rocks

David Miller is a PrestaShop specialist with over a decade of hands-on experience and the founder of mypresta.rocks, a software studio in Tychy, Poland. He builds and maintains a catalogue of 152 PrestaShop modules — including 21 "Revolution" suites spanning SEO, checkout, security, performance, marketing, search, support, and warehouse operations — that improve real stores every day, all tested against PrestaShop 1.7.8, 8.x, and 9.x. He also acts as caretaker for production stores turning over millions in annual sales, so his work is judged on live revenue, not demos. His experience runs the full breadth of ecommerce — performance, security, SEO, and marketing — and reaches beyond PrestaShop to WooCommerce, Shopify, and custom-built systems. On the blog he writes about the code-aware side of PrestaShop: what the platform really does under the hood, what breaks in production, and which fixes hold up.

Enjoyed this article?

Get our latest tips, guides and module updates delivered to your inbox.

Comments

No comments yet. Be the first!

Be the first to ask a question or share useful feedback.

Loading...
Back to top