Naročniški in potrošni izdelki

Kaj storiti, ko redni kupec spremeni velikost ali količino izdelka

Posted on July 19, 2026 by

Ko redni kupec preide s 250-mililitrske stekleničke na 500-mililitrsko ali z enega kosa na tri, je vaša časovnica ponovnega naročila zdaj napačna — in če je ne preračunate, mu boste pisali po starem razmiku in izgledali, kot da niste pozorni. Poteza je preprosto povedati in lahko pozabiti: spremembo velikosti ali količine obravnavajte kot ponastavitveni dogodek. Ponovno izračunajte pričakovani datum ponovnega naročila iz nove količine, posodobite kupčev segment in prilagodite ritem vsakega opomnika, ki sledi. Ta stran govori o obravnavanju te specifične spremembe — o mehaniki ponovnega ocenjevanja naslednjega nakupa in ohranjanju natančnosti toka — ne o tem, kako sploh prepoznati, kdo je pripravljen na večje pakiranje.

Zakaj sprememba velikosti pokvari vašo časovnico

Opomniki za ponovni nakup delujejo na podlagi razmika: koliko časa dana količina izdelka zdrži, preden kupec potrebuje več. Spremenite količino in spremenili ste razmik, pogosto močno.

Recimo, da je kupec prej vsak mesec kupil eno 30-dnevno zalogo dodatka. Preide na 90-dnevno stekleničko. Če vaš tok še vedno sproži email “čas za ponovno naročilo?” na 30. dan, zdaj nadlegujete nekoga, ki je dve tretjini poln — trikrat prezgodaj, vsak cikel. Bere se kot avtomatizirano in nerodno, in če je tega dovolj, nauči kupca, da vaše emaile prezre ali se odjavi. Obrnjeno je za prihodek slabše: kupec s trojnega pakiranja pade na enojno, vi še naprej računate časovnico po starem razmiku treh mesecev na naročilo in za tedne utihnete potem, ko mu je dejansko zmanjkalo. Ponovno naročilo v celoti zgrešite.

Količina deluje enako. Dve steklenički naenkrat zdržita približno dvakrat dlje kot ena. Sprememba števila je sprememba trajanja in datum opomnika se mora premakniti z njo.

Zakaj “kar naprej uporabljaj povprečje” ni dovolj

Pogosta bližnjica je, da se naslonite na kupčev zgodovinski povprečni razmik in pustite, da se počasi sam popravi. Ne popravi se dovolj hitro in popravi se v napačno smer.

Povprečje gleda nazaj. Če ima kupec šest mesecev mesečnih naročil in nato skoči na četrtletno pakiranje, je njegovo drseče povprečje še vedno zasidrano v mesečnem ritmu. Trajalo bo več ciklov, da povprečje odplava proti resnici — in med temi cikli napačno računate časovnico vsakega sporočila. Celotno bistvo spremembe velikosti je, da gre za čist prelom, namerni signal kupca o tem, koliko zdaj porabi. Njegovo vpovprečenje s starimi podatki topi ravno signal, na katerega najbolj želite ukrepati.

To je poseben primer širše napake: izračunavanja pogostosti nakupov na isti način za vsakega kupca in vsako naročilo. Ni enako in obravnavanje sveže spremembe velikosti kot le še ene točke podatkov za povprečenje je način, kako se napaka prikrade — več o splošnem načelu je v zakaj pogostosti nakupov ne bi smeli izračunavati enako za vsakega kupca.

Metanje popusta na težavo se je ne dotakne. Težava je natančnost časovnice, ne cena. Dobro umeščen opomnik po polni ceni premaga slabo umeščenega s 10 % popusta, vsakič.

Kje prihodek uhaja

Dve uhajanji, nasprotni smeri, obe tihi.

Prekomerno pošiljanje kupcu, ki je povečal velikost. Kupil je več, kar običajno pomeni, da je boljši kupec — vaša nagrada pa je, da ga nadlegujete po starem hitrem razmiku. Nekateri prezrejo. Nekateri se odjavijo. Vzeli ste svoje najbolj zavezane kupce in jih naučili, da nehajo brati. Težko neposredno izmerljivo, a se pokaže kot upadajoča vpletenost v vašem najvrednejšem segmentu.

Premalo pošiljanja kupcu, ki je zmanjšal velikost. Izdelek zdaj potrebuje prej in pogosteje, kot predpostavlja vaš stari razmik, a je ura vašega toka nastavljena počasi. Opomnik prispe pozno ali sploh ne, zmanjka mu, in bodisi životari brez njega bodisi — bolj verjetno — dopolnitev kupi pri komerkoli mu je tisti dan pred nosom. Groba skica: kupec, ki znova naroči 35-EUR postavko, če vas napačna časovnica pri zmanjšanju velikosti stane le en povrnjen cikel na leto čez nekaj sto takšnih kupcev, je to na tisoče evrov v ponovnih naročilih, ki uhajajo skozi polje z datumom, ki ga nihče ni posodobil.

Praktična rešitev, korak za korakom

Zaznajte spremembo. Označite vsako naročilo, kjer se SKU, velikost pakiranja ali količina razlikuje od kupčevega uveljavljenega vzorca za to linijo izdelkov. To je ponastavitveni dogodek.
Ponovno izračunajte pričakovani datum ponovnega naročila iz nove količine, ne iz povprečja. Če je novo pakiranje trikrat večje, se naslednji datum opomnika premakne približno trikrat dlje. Začnite z oceno porabe izdelka na enoto in pomnožite z novo količino. Pravilna izvedba tega izračuna je svoja majhna disciplina — uporaba količine naročila za oceno datuma naslednjega nakupa ga razčleni.
Ponovno segmentirajte kupca. Premaknite ga iz segmenta s starim razmikom v tistega, ki ustreza njegovemu novemu ritmu, tako da vsaka nadaljnja avtomatizacija (opomniki, ponudbe za naročnino, toki za ponovno pridobitev) bere pravilno časovnico.
Ponastavite uro opomnika. Zadušite vsak opomnik, načrtovan po starem razmiku, in celotno zaporedje ponovnega naročila znova zasidrajte na novi datum. Ne pustite, da se zastarel načrtovan email sproži.
Nežno potrdite, če je skok velik. Pri veliki spremembi rahla opomba “opazili smo, da ste prešli na večjo velikost — pri naslednjem stiku bomo prilagodili” kupca hkrati pomiri in potrdi, da mu sledite kot posamezniku. Neobvezno, a tihi popravek spremeni v majhen gradnik zaupanja.

Eno opozorilo: ne prilagajajte se preveč enemu samemu naročilu. Kupec, ki enkrat kupi trojno pakiranje kot darilo, nato pa se vrne, ni spremenil svojega ritma. Preverite, ali sprememba obdrži — ali jo povežite s signali namere — preden jo obravnavate kot novo normalo. Enkraten množičen nakup in resnična stopnja navzgor sta na prvem naročilu videti enaka; drugo naročilo vam pove, kaj je bilo.

Kaj natančno avtomatizirati

Sprožilec: naročilo, katerega velikost pakiranja ali količina za sledeni izdelek se razlikuje od kupčeve prejšnje norme.
Logika segmenta: ob tem sprožilcu ponovno izračunajte pričakovani-datum-ponovnega-naročila = nova količina × trajanje na enoto in kupca dodelite v segment z ustreznim razmikom. Izključite očitne enkratne anomalije (eno samo odstopajoče naročilo, ki se naslednjič vrne).
Časovnica: vsa sporočila o ponovnem naročilu takoj znova zasidrajte na nov datum; prekličite vsak opomnik, uvrščen v čakalno vrsto po starem urniku.
Kanal: popravek je večinoma nevidna napeljava. Če pošljete neobvezno potrditev, ji ustreza email; naj bo zadržan.
Vsebina: prihodnji opomniki naj se sklicujejo na novo velikost in preračunano časovnico, tako da kupec vidi sporočilo, ki ustreza temu, kar je dejansko kupil.
Cilj: opomniki, ki pristanejo v pravem tednu za novo količino nakupa — merjeno z natančnostjo časovnice ponovnega naročila, ne z obsegom pošiljanja.

Primer iz trgovine

Kupec trgovine za male živali kupuje 2-kilogramsko vrečo pasje hrane vsake tri tedne — majhen, lačen pes, ali tako namiguje razmik. Nekega meseca preide na 7-kilogramsko vrečo. Naivno tok ohrani svojo tritedensko uro in ga zvrca za ponovno naročilo, medtem ko ima še več kot štiri tedne hrane, nato to stori znova in znova. Namesto tega se sproži sprožilec spremembe velikosti: 7 kg je približno 3,5-krat več od 2-kilogramske vreče, tako da se pričakovani datum ponovnega naročila premakne s treh tednov na približno deset. Kupec je ponovno segmentiran v desettedensko skupino, stari opomnik je zadušen, naslednja spodbuda pa pristane, ko velika vreča dejansko poide.

Ista trgovina, nasproten primer: kupec z 7 kg zmanjša na 2 kg, ker potuje in želi manj za nositi. Tok skrajša razmik na tri tedne, tako da ga opomni, preden mu zmanjka, namesto da bi ga pričakal molk, zgrajen za stari desettedenski ritem. (Velikosti in razmiki so ponazoritveni — svoje zasidrajte v dejanske podatke o porabi svojega izdelka.)

Kako meriti, ali deluje

Natančnost časovnice ponovnega naročila: za kupce, ki so spremenili velikost, kako blizu je naslednji opomnik pristal njihovemu dejanskemu ponovnemu naročilu. Sledite razliki pred dodajanjem logike ponastavitve in po njem.
Stopnja ponovnega naročila po spremembi velikosti: so kupci, ki so povečali ali zmanjšali velikost, še naprej naročali po pričakovani novi stopnji ali ste jih ob prehodu izgubili?
Vpletenost med kupci s povečano velikostjo: opazujte odpiranja in odjave v svojem višje vrednem segmentu z večjim pakiranjem. Padec tam je uhajanje prekomernega pošiljanja, ki se kaže.
Povrnjeni cikli od kupcev z zmanjšano velikostjo: ponovna naročila, ki bi jih po starem razmiku zgrešili.

Če spremembe velikosti kupce vztrajno označujejo kot pripravljene na še več izdelka, je to druga priložnost, ki si zasluži svoj tok — glejte kako prepoznati kupce, ki so pripravljeni na večje pakiranje.

Kako pomaga Omnisend

Praktična ovira je usklajevanje segmentov in časovnice s tem, kar je vsak kupec nazadnje kupil, in tam se Omnisend vklopi. Njegovi segmenti se posodabljajo na podlagi podatkov o nakupih, tako da lahko kupec, ki preide na drugo velikost pakiranja, samodejno steče v segment s pravim razmikom, avtomatizacija pa bere novo časovnico namesto trdo zakodirane zakasnitve. Ponovno sidranje lahko sprožite ob kvalificiranem naročilu in zadušite zastarel opomnik, tako da kupec ne obtiči med starim urnikom in novim.

Iskreno, orodje trajanja vašega izdelka na enoto ne bo izračunalo namesto vas — to dobavite iz dejanske porabe in se razlikuje za vsak izdelek. Prav tako na prvem naročilu ne bo popolnoma ločilo enkratnega množičnega nakupa od resnične stopnje navzgor; ta presoja ali drugo potrjujoče naročilo je še vedno vaše. Kar Omnisend dobro počne, je, da popravljeno časovnico drži stabilno, ko določite pravilo. Omnisend je partner Shopimationa v pridruženem programu; uporabljam ga v lastnih trgovinah, brezplačni paket pa zadostuje, da to logiko ponastavitve zgradite in preizkusite na eni liniji izdelkov.

Vaš naslednji korak

Vzemite en izdelek, ki ga prodajate v več velikostih, in izvlecite kupce, ki so v zadnjih nekaj mesecih spremenili velikost ali količino. Preverite, ali so vaši opomniki še vedno naravnani na njihovo staro količino — stavim, da jih je več napačnih. Najprej popravite logiko ponastavitve za ta izdelek: ponovno izračunajte datum iz nove količine, ponovno segmentirajte, zadušite zastarel opomnik. Nato, da preprečite, da bi se celoten tok prekomerno prožil, ko je časovnica pravilna, preberite kako zgraditi pot ponovnega naročanja brez preveč opomnikov.

Subscription and Consumable Products

What to Do When a Repeat Customer Changes Product Size or Quantity

Posted on July 18, 2026 by

When a repeat customer switches from the 250ml bottle to the 500ml, or from one unit to three, your reorder timing is now wrong — and if you don’t recalculate it, you’ll message them at the old interval and look like you’re not paying attention. The move is simple to state and easy to forget: treat a size or quantity change as a reset event. Recompute the expected reorder date from the new amount, update the customer’s segment, and adjust the cadence of every reminder that follows. This page is about handling that specific change — the mechanics of re-estimating the next purchase and keeping the flow accurate — not about spotting who’s ready to size up in the first place.

Why a size change breaks your timing

Reorder reminders work off an interval: how long a given amount of product lasts before the customer needs more. Change the amount and you’ve changed the interval, often dramatically.

Say a customer used to buy one 30-day supply of a supplement each month. They switch to the 90-day bottle. If your flow still fires a “time to reorder?” email at day 30, you’re now nagging someone who’s two-thirds full — three times too early, every cycle. It reads as automated and clumsy, and enough of it teaches the customer to ignore your emails or unsubscribe. The reverse is worse for revenue: a customer drops from a triple-pack to a single, you keep timing off the old three-months-per-order interval, and you go quiet for weeks after they’ve actually run out. You miss the reorder entirely.

Quantity works the same way. Two bottles at a time lasts roughly twice as long as one. The change in count is a change in duration, and the reminder date has to move with it.

Why “keep using the average” isn’t enough

The common shortcut is to lean on the customer’s historical average interval and let it slowly self-correct. It doesn’t correct fast enough, and it corrects in the wrong direction.

An average is backward-looking. If a customer has six months of monthly orders and then jumps to a quarterly-sized pack, their trailing average is still anchored to the monthly rhythm. It’ll take several cycles for the average to drift toward the truth — and during those cycles you’re mistiming every message. The whole point of a size change is that it’s a clean break, a deliberate signal from the customer about how much they now use. Averaging it in with old data blunts exactly the signal you most want to act on.

This is a specific case of a broader mistake: calculating purchase frequency the same way for every customer and every order. It isn’t the same, and treating a fresh size change as just another data point to average is how the error creeps in — there’s more on the general principle in why purchase frequency should not be calculated the same for every customer.

Throwing a discount at the problem doesn’t touch it. The issue is timing accuracy, not price. A well-timed reminder at full price beats a badly-timed one with 10% off, every time.

Where the revenue leaks

Two leaks, opposite directions, both quiet.

Over-messaging the customer who sized up. They bought more, which usually means they’re a better customer — and your reward is to pester them at the old fast interval. Some tune out. Some unsubscribe. You’ve taken your most committed buyers and trained them to stop reading. Hard to measure directly, but it shows up as declining engagement among your highest-value segment.

Under-messaging the customer who sized down. They now need product sooner and more often than your old interval assumes, but your flow’s clock is set slow. The reminder arrives late or not at all, they run out, and either they limp along without it or — more likely — they buy the refill from whoever’s in front of them that day. A rough sketch: a customer reordering a €35 item, if a size-down mistiming costs you even one recovered cycle a year across a few hundred such customers, is thousands in reorders leaking out through a date field nobody updated.

The practical fix, step by step

Detect the change. Flag any order where the SKU, pack size, or quantity differs from the customer’s established pattern for that product line. This is the reset event.
Recompute the expected reorder date from the new amount, not the average. If the new pack is three times the size, the next reminder date moves roughly three times further out. Start from the product’s per-unit consumption estimate and multiply by the new quantity. Getting this calculation right is its own small discipline — using order quantity to estimate the next purchase date walks through it.
Re-segment the customer. Move them out of the old-interval segment into the one matching their new cadence, so every downstream automation (reminders, subscription offers, recovery flows) reads the correct timing.
Reset the reminder clock. Suppress any reminder scheduled on the old interval and re-anchor the whole reorder sequence to the new date. Don’t let a stale scheduled email fire.
Confirm gently, if it’s a big jump. For a large change, a light “we’ve noticed you moved to the bigger size — we’ll adjust when we check in with you” note both reassures the customer and confirms you’re tracking them as an individual. Optional, but it turns a silent correction into a small trust-builder.

One caution: don’t over-fit to a single order. A customer who buys a triple-pack once as a gift, then reverts, hasn’t changed their cadence. Look for the change to hold — or pair it with intent signals — before you treat it as the new normal. A one-off bulk buy and a genuine step-up look identical on the first order; the second order tells you which it was.

What to automate, precisely

Trigger: an order whose pack size or quantity for a tracked product differs from the customer’s prior norm.
Segment logic: on that trigger, recalculate expected-reorder-date = new quantity × per-unit duration, and reassign the customer to the matching interval segment. Exclude obvious one-off anomalies (a single outlier order that reverts next time).
Timing: re-anchor all reorder messaging to the new date immediately; cancel any reminder queued on the old schedule.
Channel: the correction is mostly invisible plumbing. If you send the optional confirmation, email suits it; keep it low-key.
Content: future reminders reference the new size and the recalculated timing, so the customer sees a message that matches what they actually bought.
Goal: reminders that land in the right week for the new purchase amount — measured by reorder timing accuracy, not send volume.

A store example

A pet store customer buys a 2kg bag of dog food every three weeks — a small, hungry dog, or so the interval suggests. One month they switch to the 7kg bag. Naively, the flow keeps its three-week clock and pings them for a reorder while they’ve got over four weeks of food left, then does it again, and again. Instead, the size-change trigger fires: 7kg is roughly 3.5× the 2kg bag, so the expected reorder date moves from three weeks to about ten. The customer gets re-segmented into the ten-week group, the old reminder is suppressed, and the next nudge lands when the big bag is actually running low.

Same store, opposite case: a customer downsizes from the 7kg to the 2kg because they’re travelling and want less to carry. The flow shortens the interval to three weeks so they’re reminded before they run out, instead of being met with silence built for the old ten-week rhythm. (Sizes and intervals are illustrative — anchor yours to your own product’s real consumption data.)

How to measure whether it’s working

Reorder timing accuracy: for customers who changed size, how close the next reminder landed to their actual reorder. Track the gap before and after you add the reset logic.
Reorder rate after a size change: did the customers who sized up or down keep reordering at the expected new rate, or did you lose them at the transition?
Engagement among size-up customers: watch opens and unsubscribes in your higher-value, larger-pack segment. A dip there is the over-messaging leak showing itself.
Recovered cycles from size-down customers: reorders you’d have missed under the old interval.

If size changes keep flagging customers as ready for even more product, that’s a different opportunity worth its own flow — see how to identify customers who are ready for a larger pack.

How Omnisend helps

The practical hurdle is keeping segments and timing in sync with what each customer last bought, and that’s where Omnisend fits. Its segments update off purchase data, so a customer who moves to a different pack size can flow automatically into a segment with the right interval, and the automation reads the new timing rather than a hard-coded delay. You can trigger a re-anchoring off the qualifying order and suppress the stale reminder, so the customer doesn’t get caught between an old schedule and a new one.

Honestly, the tool won’t compute your product’s per-unit duration for you — you supply that from real usage, and it differs for every product. Nor will it perfectly tell a one-off bulk buy from a real step-up on the first order; that judgement, or a second confirming order, is still yours. What Omnisend does well is hold the corrected timing steady once you’ve defined the rule. Omnisend is an affiliate partner of Shopimation; I use it in my own stores, and the free tier is enough to build and test this reset logic on a single product line.

Your next step

Take one product you sell in multiple sizes and pull the customers who’ve switched size or quantity in the last few months. Check whether your reminders are still timed to their old amount — I’d bet several are off. Fix the reset logic for that product first: recompute the date from the new quantity, re-segment, suppress the stale reminder. Then, to keep the whole flow from over-firing once the timing’s right, read how to build a reorder journey without sending too many reminders.