Every shop looks for reasons to be remembered. A birthday is the only one that belongs to the customer, comes back every year and does not read as advertising. It costs nothing but a few points.
Newsletters compete with every other newsletter of the same day. A birthday email stands alone - it arrives on a day when the recipient expects messages anyway, and it is about them.
That makes the birthday the occasion with the highest attention in the whole year, and one you do not have to plan, schedule or design.
A campaign hits every customer on the same day: a spike in sending, a spike in demand, a spike in cost. Birthdays spread across the whole year - on average one three-hundred-and-sixty-fifth of your customers per day.
With 5,000 customers in the programme that works out at roughly 14 credits a day - a scale that burdens neither sending nor support.
A birthday voucher expires and is then worth nothing. Birthday points land in the same pot as all other points, grow with them and stay until they are redeemed or expire.
For the customer that means the birthday brings them closer to their next goal instead of putting them under time pressure.
A scheduled task checks once a day which customers have their birthday today. For each of them a booking is created with the reason "Birthday bonus" and a key that contains the year.
The key per year is why a run executed twice cannot produce a double credit: the database refuses the second booking outright.
In Shopware the date of birth is an optional field. Anyone who has not given one receives no birthday points - there is no substitute date and no follow-up email.
If you want more customers to take part, the hint on the loyalty page is a better place than a mandatory field at registration.
The event comes with a shipped flow and a shipped email template in both languages. You can change the text, extend the flow with conditions, or switch it off and build your own.
In total the plugin ships four email templates: points credited, loyalty tier reached, goal reached and points expiring soon.
Two settings are enough: the point value and the switch for the scheduled task.
| Setting | Default | What for |
|---|---|---|
| Birthday bonus | 100 | points per birthday |
| Scheduled task: birthday bonuses | on | the daily run |
The birthday bonus is an action bonus and therefore active from the Business plan. A value of 0 switches it off without touching the flow.
A scheduled task runs daily and credits every customer whose birthday falls on that day. There is no lead time and no grace period.
No. Every booking carries a key with the calendar year, and the database allows the same key only once per customer. Even a run executed twice books only once.
They receive no birthday points. The field is optional in Shopware and the plugin does not force it.
Yes. The plugin ships a flow and an email template in German and English. Both can be changed or switched off.
Yes. They are not pending because they hang on no order. The waiting period only concerns points from orders.
Double points on a category, a weekend or a customer group - without touching a single price.
Read on → LaunchAnyone who bought before the programme started would otherwise start at zero. A one-off run picks them up.
Read on → Balance sheetA validity period caps the open liability - and the reminder email before it brings customers back.
Read on →The plugin installs free of charge from the Shopware Store. Earning points, the dashboard and the customer account run straight away, no purchase needed.