The case that should never have left
The club list is exported on Monday so the warehouse can start picking. Cards are charged on Wednesday. Couriers collect on Thursday. In between, a handful of cards decline, two members email to say they are away and would like to skip this month, and one asks to move from the mixed dozen to the six-bottle case.
Some of those messages are read in time. Some are not. On Friday a member rings to say a case of wine has been left with a neighbour while she is abroad, and the payment for it failed anyway.
Why the list is always a few days stale
Picking a wine club takes time, so the list is fixed early. Payments and changes keep happening after it is fixed. The two are joined only by someone remembering to check, and in a busy week that check is the first thing to slip.
- The picking list is an export, not a live view of member status.
- Pause and skip requests arrive by email and phone rather than through the platform.
- Failed payment notices go to an inbox that the warehouse never sees.
- Retried payments that succeed a day later are not reflected either.
- Tier changes need a different case, which may already be packed.
What stale lists cost
A case sent unpaid is stock and courier cost you may never recover, and chasing a member for it is awkward. A case sent to someone who asked to skip is a delivery problem and often a return, and it makes the member feel unheard. Members who cannot easily pause are the ones who cancel instead.
Every one of these also creates a phone call or email that someone has to deal with in the busiest week of the month.
The dispatch check we build
- Member status is read directly from your subscription or payment platform, such as Stripe, rather than from an exported list.
- Pause, skip and tier change requests are captured through a simple self-service link, and any that still arrive by email are logged by staff into the same place.
- At packing time, each case's label is only printed once the member's payment for this month has succeeded and no pause is recorded.
- Cases for members with a failed payment are set aside automatically, and the member receives a message with a link to update their card.
- If the payment then succeeds, the case is released to the next courier collection.
- A short exceptions list shows the manager every held case and why.
| Member status at packing | What happens | Message to member |
|---|---|---|
| Paid, active | Label prints, case ships | Dispatch confirmation |
| Payment failed | Case held on the shelf | Update card link |
| Paid after retry | Case released to next collection | Dispatch confirmation |
| Skip requested | No case picked | Confirmation of skip |
| Tier changed after picking | Case flagged for repack | None until shipped |
How many times to retry a card, and when to cancel a membership after failed payments, are your rules. The check applies them consistently.
A packing day without surprises
The warehouse only ships cases that are paid for and wanted. Members can pause for a holiday themselves without writing an email. Failed payments turn into an update-your-card message rather than an unpaid case on someone's doorstep, and the manager starts Friday with a list of held cases, not a queue of apologetic phone calls.
Signs your club needs this
- You have shipped cases to members whose payment failed.
- Pause requests are handled by email.
- The picking list is exported days before cards are charged.
- The warehouse does not see payment problems.
- Members cancel when they only wanted a break.