Skip to content
Reorbit

Celebrate Your Birthday — Earn Rule Example

Give loyalty members points on their birthday. The exact fields, a worked example, the eligibility lead time that stops abuse, and where customers enter the date.

Points on a member’s birthday. One of the few loyalty messages people are genuinely pleased to receive.

Where: Settings → Earn points → Create rule → Account → Celebrate Your Birthday

What it does

Awards points on the member’s birthday, every year.

Shopify has no birthday field, so members enter theirs in your loyalty widget — month and day only. The widget says so plainly: “Just the day and month — we never ask for your birth year.” Once saved, it shows as Birthday on file.

That means this rule pays nobody until members start entering dates. It builds an audience over time rather than starting with one.

The fields

Section Field Notes
Rule Name Rule Name Required. E.g. Happy birthday — 250 points.
Rule reward Reward Required. The birthday points.
Eligibility lead time Number of days Required, minimum 7. 14 is recommended.
Eligibility Period Start / end date Optional.
Earning Limits — Fixed: once per customer, per birthday. Nothing to set.
Inclusions & exclusions Customer tags, products Optional.
Rule Status Active / Disabled

There is no Points Holding Period on this rule. There’s no order to claw back, so it doesn’t offer one.

What the lead time does. Members must save their birthday at least this many days before it arrives to earn on it. Without it, a shopper enters tomorrow’s date and claims the points immediately — then does it again next month. Someone who enters a date inside the window doesn’t lose out permanently: they earn on their next birthday.

Worked example: 250 points on the day

  1. Go to Settings → Earn points and click Create rule.
  2. Under Account, choose Celebrate Your Birthday.
  3. Fill in:
Field Value
Rule Name Happy birthday — 250 points
Reward 250
Eligibility lead time 14 days
Rule Status Active
  1. Save.

Why 250 rather than a discount. Points spend against your existing rewards, so a birthday gift costs you what it costs and never becomes a stackable coupon in the wild.

Why 14 days. Long enough that nobody games it, short enough that a member who joins in early March still earns on a late-March birthday.

Tips

  • Ask for the birthday when they join, not later. The widget prompt does the work, but a mention in your welcome email doubles the capture rate.
  • You can’t over-award it by accident. The rule pays once per member per birthday and there’s no limit to configure — so the only number that matters is the reward itself.
  • Give them somewhere to spend it. Birthday points against a 500-point reward, with 250 already banked, is a nudge. Against a 5,000-point reward it’s noise.
  • Never ask for the birth year. Reorbit doesn’t, and neither should your own forms — it’s personal data you have no use for.

FAQ

Where do customers enter their birthday?

In the loyalty widget on your storefront. They pick a month and a day; the year is never asked for. (See Adding Reorbit to your storefront.)

Can I import birthdays from another platform?

Not through this rule — it reads what members have saved in the widget.

What about 29 February?

It’s handled — a leap-day birthday is celebrated in non-leap years too.

Someone entered their birthday and got nothing.

Check the Eligibility lead time. If their birthday was inside the window when they saved the date, they earn on the next one instead.

Next steps

Common questions

Where do customers enter their birthday?
In the loyalty widget on your storefront. They pick a month and a day; the year is never asked for.
Can I import birthdays from another platform?
Not through this rule — it reads what members have saved in the widget.
What about 29 February?
It's handled — a leap-day birthday is celebrated in non-leap years too.
Someone entered their birthday and got nothing.
Check the Eligibility lead time. If their birthday was inside the window when they saved the date, they earn on the next one instead.