A subscriber receives her third box containing an item she cannot eat. She has mentioned it twice in the feedback form and the boxes keep coming.
She cancels. The service could have excluded one category at no cost, and it lost a subscriber over something it was never told to act on because nothing in the system could record it.
1. Separate safety from preference
Allergies and intolerances are not preferences. They need collecting at signup, storing properly and applying without exception.
2. Collect allergen information at signup, not later
Before the first box, with a clear list rather than a free text box. This is the same rigour described in allergy and ingredient questions from subscription customers.
3. Offer exclusions rather than selections
Letting somebody exclude two or three categories is operationally straightforward and removes most dissatisfaction. Letting everybody pick every item is not.
4. Limit the number of exclusions
Three, or whatever your buying can absorb. A stated limit is fair and it prevents a subscriber excluding so much that no box can be built.
5. Ask for sizes where relevant
Clothing, footwear and anything fitted. Getting this wrong once produces a cancellation and a return in the same week.
6. Offer a small choice, not a full one
One item chosen from three, one cycle in three, or an upgrade slot. It gives a sense of control without dismantling the buying model.
7. Explain why full customisation is not offered
That bulk buying is what makes the value possible. Subscribers accept a limitation they understand and resent one that looks like indifference.
8. Let preferences be changed easily
In the account, with a stated cut off before the next cycle. Preferences that require contacting support are preferences that do not get updated.
9. Confirm what has been recorded
Show the subscriber their stored preferences and allergies. Most of the anger in this area comes from somebody believing they had told you.
9b. Say what happens when a preference cannot be met
A cycle occasionally contains nothing suitable for somebody with several exclusions, and sending the box anyway wastes it. Offering a substitution, a credit or a skipped month, decided in advance rather than improvised, is what keeps that subscriber rather than embarrassing them.
10. Act on the feedback you collect
A feedback form that feeds nothing is worse than none, because it creates an expectation that something will change.
11. Handle the gift subscriptions differently
A buyer cannot set the recipient's preferences, so there needs to be a route for the recipient to do it themselves.
12. Use preferences to reduce waste
Fewer unwanted items means fewer returns, less resale and better margins, which makes the case for building this properly.
13. Watch for the cancellation signals
A subscriber updating preferences repeatedly is close to leaving, which connects to the pause mechanics in skip, pause and cancel questions for subscription boxes.
14. Borrow the constraint framing from elsewhere
Explaining what can and cannot be accommodated is handled well in what can and cannot be stored questions.
15. Handle preference changes automatically
An assistant that records allergies, sets exclusions, confirms what is stored and states the cut off date keeps the information current without a person. Draft the standard replies with a reply generator, and the wider handling is in ai assistant subscription business.
16. What getting preferences right produces
Subscribers who stay past the box containing something they hated. See features, start at try, and the sector view sits under ecommerce.