{"id":1828,"date":"2026-09-25T15:15:00","date_gmt":"2026-09-25T15:15:00","guid":{"rendered":"https:\/\/bizdom.app\/?p=1828"},"modified":"2026-09-25T15:15:00","modified_gmt":"2026-09-25T15:15:00","slug":"demand-signal-substitution-log","status":"publish","type":"post","link":"https:\/\/bizdom.app\/en\/loyalty-sommelier\/demand-signal-substitution-log\/","title":{"rendered":"The demand signal your subscribers generate and nobody reads"},"content":{"rendered":"

Your subscribers tell you what to ship every cycle in the substitutions they make to their own packages. Read those swaps in aggregate and they become the only unprompted statement of preference your program produces, at no cost, from exactly the people whose spending you are forecasting. Members who can edit their packages show 20.7% higher order value and roughly half the churn.<\/strong><\/p>\n\n

Pull the substitution records for your last three shipment cycles and read them as one ranked list: what members took out, what they put in, how many made a change at all, and how many left the default alone. Most DTC teams have never looked at that list in aggregate, because the platform presents substitutions one member at a time, as service requests to be fulfilled rather than as information to be read. Filed that way, each swap is an exception someone handles. Stacked up, the same swaps are the only unprompted statement of preference your program produces, and they arrive on a schedule, at no cost, from exactly the people whose spending you are forecasting.<\/p>\n

That is not a reporting complaint. It is a signal that exists, has a known shape, and currently terminates in a fulfillment queue.<\/p>\n

The Choice Signal<\/h2>\n

The Choice Signal is a reading habit, not a system purchase. It turns the substitutions your members already make into a ranked demand statement, then puts that statement in front of the two audiences who can act on it. Three components.<\/p>\n

Component 1: Turn the choice on<\/h3>\n

Some programs do not produce this signal at all, because members cannot change what arrives. If that is your situation, the first move is not analysis; it is giving members the ability to edit.<\/p>\n

There is a real number attached to that decision. Members who can edit their packages show 20.7% higher average order value and roughly 50% lower churn, measured across 1.4 million memberships at 17,000 programs (Commerce7 Data Drop, June 2026). That is the largest, most recent, most directly relevant figure available on this question, and it is worth being precise about what it does and does not say. It is an observed association across a very large sample, not a controlled experiment, and it does not promise that switching the setting on produces those deltas at your winery next quarter.<\/p>\n

What it does support is the direction and the size of the prize, which is enough to move an internal conversation. The common objection is that editing will collapse the allocation plan as everyone takes the same two wines. That is a fulfillment constraint, and it is solved the way every allocation is solved: caps, windows, and a default that stays good. It is not a reason to keep members silent.<\/p>\n

Component 2: Read the aggregate, not the individual<\/h3>\n

The individual swap is a service event. The aggregate is a forecast.<\/p>\n

Build one list per cycle with four columns: wine swapped out, wine swapped in, count, and share of members who changed anything at all. That fourth number matters more than people expect. A cycle where 6% of members touch the package and a cycle where 30% do are telling you two completely different things about how well the default is landing, and neither reading requires you to know which member did what.<\/p>\n

Read it against the constraint rather than in isolation. The DTC channel fell 15% in volume and 6% in value in 2025, the steepest decline since the report series began in 2010, and wines above $50 now account for 71% of DTC value, up from 52% in 2020 (Sovos ShipCompliant and WineBusiness Analytics, DTC Wine Shipping Report 2026). In a channel shaped like that, the question of what your existing members will actually take is worth more than it was five years ago, and you are the only person who can answer it for your list.<\/p>\n

One cut is worth making and no more: split the ranking by tenure, first-year members against everyone else. Those two groups are usually reaching for different things, and the difference is the most actionable thing in the whole exercise, because the first-year cohort is the one you are most likely to lose and the only one whose preferences you have almost no history on. Beyond that split, resist the urge to segment. A ranking cut five ways stops being a signal and becomes a research project, and research projects do not survive a busy quarter.<\/p>\n

Component 3: Send the signal back in both directions<\/h3>\n

A ranked list that stays in your file is half the exercise. The signal has two destinations.<\/p>\n

The first is the allocation and release plan. Bring the ranking to the meeting where next cycle’s contents are decided, as a document rather than an opinion. A Director who can say “38% of the list swapped out the white last cycle, and two-thirds of them took the same red” has changed the nature of that conversation, and it will be the first time most of the room has seen member preference stated as a quantity.<\/p>\n

The second destination is the member who is choosing right now. Somewhere in your customization flow there is an ordered list of what a member can select, and that order is currently set by your commerce platform or by whoever configured it. Ordering it by what the list actually chose last cycle costs nothing and changes what a deciding member sees first.<\/p>\n

Keep that second destination aggregate. The temptation is to turn the ranking into a per-member recommendation, and that is a different project with a different cost, a different failure mode, and a much longer path to anything shippable. What you are doing here is simpler and needs no model: showing the list what the list did. Ordering a page is a configuration change; predicting an individual is a program.<\/p>\n

What the Aggregate Will Tell You<\/h2>\n

The first finding usually arrives inside one cycle and is uncomfortable: the default is carrying less agreement than anyone assumed. That is not a failure of the winemaking. It is the difference between a package designed to represent the estate and a package designed for what this particular list drinks, and the two were never the same document.<\/p>\n

The second finding is about who changes things. Members who customize are not the difficult members, which is how substitutions get discussed when they live in a fulfillment queue. They are the members who cared enough to open the window before it closed. Reading the log by tenure usually shows the habit concentrated in the members you would least like to lose.<\/p>\n

The third takes a year and is the one that pays. Once you have four cycles of rankings, you can compare the swap rate with what happened next: who renewed, who lapsed, who moved up. Annual retention in this category runs roughly 64% to 77%, with about 40% of members canceling inside the first year (Silicon Valley Bank, State of the US Wine Industry 2026). Those are the odds you are playing against, and a member who actively chose their last three shipments is a different proposition from one who simply did not cancel.<\/p>\n

The Objection You Will Hear Internally<\/h2>\n

Somebody will say that members do not know what they want, that the point of a curated program is the curation, and that ranking bottles by popularity is how a premium program becomes a supermarket shelf.<\/p>\n

That objection is worth taking seriously rather than talking around, because the person raising it is protecting the thing that makes the program worth joining. The answer is that the signal informs the default; it does not replace it. Nobody is proposing that the list votes on the blend. The claim is narrower: when you build a package, you are making a prediction about what this list will keep, and you currently make that prediction without looking at the last three answers.<\/p>\n

The second objection is quieter and comes from whoever runs fulfillment, who will point out that every substitution is a pick, a pack, and sometimes a phone call. That is true, and it is the reason substitutions get framed as a cost center in the first place. Put the two ledgers side by side rather than arguing from principle. On one side sits the handling cost of the swaps, which your operations lead can quantify in an afternoon. On the other sits the order-value and retention difference associated with members having the choice at all. You do not need the second number to be precise at your winery to know which side of that comparison is larger, and framing it as a comparison rather than as a complaint is what gets the conversation to a decision.<\/p>\n

This Week’s Action<\/h2>\n

Export the substitution records for your last three cycles and build the four-column ranking. It is an afternoon in a spreadsheet, and the export already exists in your commerce platform.<\/p>\n

Then take one number from it, the share of members who changed anything at all, and bring it to the next release planning meeting. Not a recommendation, just the number. The conversation it starts is the point.<\/p>\n

P.S.<\/strong> There is a second thing your members produce that nobody reads: the sentences they write back to you. Somewhere in your reply folder is a description of your wine that will outperform anything written in-house, for a reason that has nothing to do with how good the writing is. Monday’s email is about that.<\/p>\n\n

Learn more<\/a><\/div><\/div>","protected":false},"excerpt":{"rendered":"

Across 1.4 million memberships, the effect lives in the choosing, not the bottle.<\/p>\n","protected":false},"author":1,"featured_media":1827,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"class_list":["post-1828","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-loyalty-sommelier"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t