Dispatch week
The beer club goes out on the first Thursday. The week before, someone exports members from the webshop, cross-checks against the spreadsheet of skips and pauses, chases failed payments, updates addresses from emails, decides the box contents from what is in stock, and prints labels. A member emails to say they got the same beer as last month. Another says they cancelled but were charged.
The club is a good idea. It is steady revenue and your keenest drinkers love it. It just takes more running than anyone planned.
Why the club becomes a chore
Webshop subscription plugins handle the charge but not the rest. Skips, pauses and gifts are handled by email. Box contents are decided at the last minute, with no record of what each member has had. Stock for the club is not held back, so a beer planned for the box sells out on the webshop the week before.
- Skips, pauses and cancellations arrive by email.
- Failed payments are chased by hand.
- Nobody records which beers each member has received.
- Box stock is not set aside in advance.
- Gift memberships are tracked separately.
What the chore costs
Staff days every month. Members who leave because of mistakes or because they could not easily pause. Revenue lost to failed payments that were never chased. Beer that should have gone in the box sold elsewhere, or the box made up of whatever is left.
Churn in a beer club is quiet. Members rarely complain; they just do not renew after the second wrong box or the awkward cancellation email. By the time you notice the numbers falling, the reasons are months old.
A beer club that runs itself
- Subscriptions run on Stripe Billing or your webshop's subscription feature, with automatic retries and emails for failed payments.
- A member page where people skip, pause, change address, change box size or cancel, without emailing you.
- Gift memberships with a fixed number of boxes and a message to the recipient.
- Box planning: you pick the beers for the month, and the system checks stock and holds the quantity back from the webshop.
- A record of what each member has received, so repeats are flagged and swaps can be offered for members who dislike a style.
- On dispatch day, packing lists and shipping labels through your courier's API, with tracking emails.
- A monthly view of members joining, pausing and leaving, and the reasons they give.
| Task | Before | After |
|---|---|---|
| Skip or pause | Email to the office | Member does it online |
| Failed payment | Chased by hand | Automatic retry and email |
| Box contents | Decided the week before | Planned and stock held |
| Repeat beers | Found by complaint | Flagged in advance |
| Labels | Typed or exported | Produced on dispatch day |
What dispatch week looks like
You pick the beers, confirm the stock hold and print the packing lists. Members sort out their own changes. Failed payments are retried without anyone chasing. Complaints about repeats disappear. You can see whether the club is growing and why people leave, which is what you need before changing the price or the box.
The club also becomes a useful testing ground. A small run of an experimental beer can go into the box, and because you know who received it, you can ask those members what they thought and use the answers when deciding whether to brew it again.
Is your beer club like this?
- Dispatch week takes days of admin.
- Members email to skip, pause or cancel.
- Failed payments are chased by hand or not at all.
- Members have received repeat beers.
- Club beers sell out on the webshop first.