Spletna potisna obvestila

Kako uporabiti potisna obvestila za ponovno zalogo

Posted on July 18, 2026 by

Potisna obvestila so najboljši prvi kanal za obvestilo o vrnitvi izdelka na zalogo, ker gre pri tem predvsem za hitrost. Ko se priljubljen izdelek vrne, se kupci, ki so ga želeli, med seboj prehitevajo — in potisno obvestilo pristane na njihovem zaslonu v trenutku, ko se zaloga posodobi, medtem ko e-pošta lahko ostane neodprta do večera. Postavitev je kratka: na vsako razprodano stran izdelka dodajte gumb »obvesti me«, ob prehodu zaloge nad nič samodejno sprožite potisno obvestilo, povežite ga neposredno z izdelkom in eno do dve uri pozneje pošljite še e-poštno različico kot rezervo. A eno opozorilo že takoj na začetku. Če napolnite pet kosov in hkrati obvestite dvesto ljudi, ki čakajo, ustvarite več razočaranja kot prihodka. Kako to obvladati, je polovica tega članka.

Tiha cena razprodane strani izdelka

Razprodana stran je eno redkih mest, kjer vam obiskovalec povsem jasno pove: »Točno ta izdelek si želim in denar imam pripravljen.« Nato mu večina trgovin odgovori s sivim gumbom, ki pravi »Ni na zalogi«, in ničemer drugim.

Obiskovalec odide. Morda se še vrne. Običajno se ne — kupi podoben izdelek pri tistem, ki je v Googlu naslednji po vrsti, in povpraševanje, za katerega ste plačali, se pretvori v prodajo v tuji trgovini.

Tukaj je groba ponazoritev, kako izgleda tak izpad (ponazoritvene številke — vstavite svoje): recimo, da izdelek za 45 € poide za dva tedna, njegova stran pa še vedno dobi 30 obiskov na dan. To je 420 obiskov ljudi z nadpovprečno nakupno namero. Če bi jih le 5 % kupilo takoj, ste za en izdelek in en cikel dopolnjevanja zaloge spregledali približno 900 € prihodka. Pomnožite to s številom izdelkov v katalogu, ki v običajnem četrtletju poidejo, in številka ni več majhna.

Zakaj »vrnili se bodo, ko bo spet na zalogi« ni načrt

Nekateri lastniki predpostavljajo, da bodo najbolj zagreti sami preverili. Nekaj se jih bo. A od kupca zahtevate, da ponavlja ročno delo — se vrača, preverja, se spet vrača — v vašo korist, brez vsakega vašega znaka o tem, kdaj se to sploh splača. To je narobe obrnjeno. Zainteresirani obiskovalec je svoje že storil, ko je prišel; nadaljnji korak bi moral biti vaša naloga, in bi moral biti samodejen.

Druga pogosta rešitev je pošiljanje obvestil o zalogi zgolj po e-pošti. Bolje kot nič, seveda. Zatakne pa se pri času. Odpiranje e-pošte je počasno — veliko ljudi preveri predal enkrat ali dvakrat na dan — in vroč izdelek lahko razproda, še preden povprečni naročnik sploh vidi zadevo sporočila. Za omejeno zalogo zmaga kanal, ki vljudno prekine v realnem času. To so potisna obvestila.

Ta članek govori le o vračanju izdelkov na zalogo. Če je izdelek še vedno na zalogi in namesto tega čakate na spremembo cene, je to druga avtomatizacija z drugačno logiko — obravnavana je v članku kako uporabiti potisna obvestila za znižanja cen.

Zakaj potisna obvestila k temu obvestilu pašejo bolje od katerega koli drugega sprožilca

Spletna potisna obvestila imajo kot kanal prave slabosti — ni predala, kamor bi se dalo vrniti, zlahka jih uporabljate preveč, naročnikov ne morete prepoznati po imenu. Vrnitev na zalogo je primer uporabe, kjer skoraj nič od tega ni pomembno in se prednosti poravnajo:

Hitrost. Obvestilo se pojavi na zaslonu naročnika v nekaj trenutkih po dopolnitvi zaloge, ne glede na to, ali je vaša stran odprta ali ne. Pri izdelku, na katerega čaka 200 ljudi, o tem, kdo ga bo dobil, odločajo minute.
E-poštni naslov ni potreben. Obiskovalec se lahko na potisna obvestila naroči z enim klikom, brez tipkanja, zato vaš gumb »obvesti me« pretvori ljudi, ki polja za e-pošto nikoli ne bi izpolnili.
Popolno ujemanje z namero. Vsako obvestilo gre samo tistim, ki so vprašali po točno tem izdelku, zato je ustreznost vgrajena — zato so obvestila o vrnitvi na zalogo med najbolj uspešnimi potisnimi obvestili, ki jih trgovina pošlje. (Natančne stopnje klikov se med trgovinami in izdelki zelo razlikujejo; preverite svoje številke, namesto da bi zaupali panožnim povprečjem.)

A potisna obvestila ne bi smela biti edini kanal. Najprej pošljite potisno obvestilo, nato eno do dve uri pozneje še e-pošto, da ujamete ljudi, katerih brskalnik je bil brez povezave. Poganjanje obeh iz enega sprožilca je natanko vzorec, opisan v članku kako združiti email, SMS in potisna obvestila v eni avtomatizaciji.

Postavitev korak za korakom

Prijavo postavite tja, kjer je namera. Na vsaki razprodani strani izdelka mrtvo stanje »Ni na zalogi« zamenjajte z delujočim gumbom »Obvesti me, ko bo spet na voljo«, ki obiskovalca naroči na potisna obvestila za ta izdelek. Splošno potisno obvestilo za celotno stran tega ne bo opravilo — potrebujete povezavo na ravni izdelka. (Za rast splošnega seznama naročnikov obstaja ločen priročnik: kako zbrati naročnike na spletna potisna obvestila v spletni trgovini.)
Sprožite ob dogodku zaloge, ne ob ročnem pošiljanju. Obvestilo naj se samodejno sproži, ko raven zaloge v vaši trgovini prečka nič. Če se mora nekdo iz vaše ekipe spomniti, da ga pošlje, bo šlo ven prepozno ali pa sploh ne.
Sporočilo napišite za eno dejanje. Ime izdelka, »spet na zalogi« in nujnost, ki je resnična: »Spet na zalogi — omejena količina« je pošteno, kadar to drži. Povežite neposredno na stran izdelka, ne na domačo stran. Več o tem, kako iz teh nekaj besed iztisniti največ, v članku kako pisati potisna obvestila, ki jih ljudje kliknejo.
Sledite z e-pošto, nato nehajte. Eno potisno obvestilo, eno rezervno e-poštno sporočilo, konec. Če se na obvestilo o vrnitvi na zalogo za izdelek, po katerem so povprašali, niso odzvali, tretji poriv ne bo pomagal in vas bo stal naklonjenosti.

Kaj natančno avtomatizirati

Sprožilec: zaloga sledenega izdelka se premakne z 0 na več kot 0.
Segment: samo naročniki, ki so za ta izdelek zahtevali obvestilo. Nihče drug.
Časovni razpored: potisno obvestilo takoj; e-poštno sledenje po 1–2 urah vsem, ki še niso kupili.
Kanal: najprej potisno obvestilo, nato e-pošta. SMS le, če je izdelek dragocen in imate soglasje — sporočilo o vrnitvi izdelka za 12 € na zalogo bolj vznemiri, kot prinese.
Vsebina: ime izdelka, izjava o vrnitvi na zalogo, resnična redkost, neposredna povezava do izdelka.
Izhodni pogoj: naročnik kupi izdelek ali pa izdelek spet poide — kar koli od tega naj tok nemudoma ustavi. Obvestilo, ki prispe potem, ko izdelka spet ni, je slabše od tišine.
Cilj: nakupi ponovno založenega izdelka v 24–48 urah po obvestilu.

Težava z majhno zalogo, na katero nihče ne računa

Zdaj neprijeten del. Obvestila o vrnitvi na zalogo predpostavljajo, da ponudba približno ustreza povpraševanju čakajočih. Pogosto ni tako.

Dve situaciji, ki ju je treba obravnavati premišljeno. Prva, drobcena dopolnitev zaloge: čaka 150 ljudi, prispe pa 8 kosov. Obvestite vse in 142 ljudi klikne na razprodano stran — potrpežljivo zanimanje ste dvakrat pretvorili v razdraženost. Če vaša orodja to dopuščajo, obveščajte v paketih (najstarejše zahteve najprej), velikih toliko, kolikor zaloge dejansko imate, ali pa vsaj strogo držite izhodni pogoj ob razprodaji, da se obvestila ustavijo v trenutku, ko zaloga spet pade na nič.

Druga, navidezna dopolnitev zaloge: eno samo vračilo ali popravek zaloge dvigne zalogo z 0 na 1, vaša avtomatizacija pa vestno oznani vrnitev na zalogo, ki komaj obstaja. Preden vklopite tok, se splača preveriti, kako vaša platforma šteje vrnjeno zalogo — prag najmanjše količine na sprožilcu (sproži šele, ko zaloga naraste nad, recimo, 5) odfiltrira večino tega šuma.

Nobena od teh težav ni razlog za opustitev avtomatizacije. Obe sta razlog, da porabite deset dodatnih minut za pogoje sprožilca.

Kako to izgleda v pravi trgovini

Ponazoritveni primer, velik kot tipična trgovina v našem občinstvu: trgovina, ki v omejenih serijah prodaja priljubljen model superg. Izdelek v večini velikosti poide v nekaj dneh po vsaki izdaji. Trgovina doda potisno obvestilo »obvesti me« za posamezno velikost, tako da kupec velikosti 42 sliši le o vrnitvi velikosti 42 na zalogo. Ko prispe 60 parov, potisno obvestilo takoj odide čakajočim, stran izdelka v roku ene ure zabeleži skok, e-poštno sledenje pa zvečer pobere preostanek. Izhodno pravilo toka ustavi vsa obvestila v trenutku, ko posamezna velikost spet poide. Nihče ni načrtoval kampanje, nihče ni pisal glasila — trženje je opravil sistem za upravljanje zaloge.

Kako izmeriti, ali deluje

Rezultatska tabela naj bo kratka:

Stopnja obvestilo-v-nakup — koliko obveščenih je kupilo v 48 urah. To je številka, ki šteje.
Stopnja klikov na potisno obvestilo — presoja sporočilo in čas.
Prihodek na dogodek dopolnitve zaloge — vrednost toka naredi vidno ob boku vašim kampanjam.
Stopnja prijav na razprodanih straneh — koliko obiskovalcev razprodane strani pritisne »obvesti me«. Če je nizka, je težava v postavitvi gumba, ne v obvestilu.

Prihodek pravilno pripišite nazaj, da tok dobi zasluge — stran pripisovanja je obravnavana v članku kako izmeriti prihodek iz spletnih potisnih obvestil.

Kako to narediti v Omnisendu

V svojih trgovinah uporabljam Omnisend in vrnitev na zalogo je ena tistih avtomatizacij, kjer se izplača: poveže se s katalogom izdelkov vaše trgovine, tako da se sprožilec za vrnitev na zalogo sproži ob dejanskih spremembah zaloge, isti tok pa lahko drži korak potisnega obvestila in korak zakasnjene e-pošte z izhodom na podlagi nakupa — brez ločenih orodij, ki bi jih bilo treba sešiti skupaj. Zgradite ga enkrat v vizualnem urejevalniku in teče ob vsaki prihodnji dopolnitvi zaloge.

Poštena opozorila: da to sploh deluje, morajo biti vaši podatki o zalogi točni, naročanje na potisna obvestila za posamezni izdelek je odvisno od postavitve vaše spletne trgovine, in nobeno obvestilo ne reši izdelka, ki ga ljudje niso želeli že v izhodišču. Omnisend je partner Shopimationa v pridruženem programu; priporočilo izhaja iz vsakodnevne uporabe, ne iz povezave.

Vaš naslednji korak

Odprite analitiko svoje trgovine in poiščite tri najbolj obiskane razprodane strani izdelkov v zadnjih 90 dneh. Ta promet je povpraševanje, ki ga trenutno pošiljate konkurenci. Ta teden na te strani postavite potisno obvestilo »obvesti me«, priključite sprožilec za vrnitev na zalogo in pustite, da naslednja dobava zaloge tok preizkusi namesto vas.

Web Push Notifications

Using Push Notifications for Back-in-Stock Alerts

Posted on July 17, 2026 by

Push is the best first channel for a back-in-stock alert because the whole game is speed. When a popular item returns, the customers who wanted it are racing each other — and a push notification lands on their screen the moment inventory updates, while an email might sit unopened until the evening. The setup is short: put a “notify me” prompt on every sold-out product page, trigger an automated push the moment stock goes above zero, deep-link straight to the product, and send the email version as backup an hour or two later. One warning up front, though. If you restock five units and alert two hundred waiting people at once, you create more disappointment than revenue. How to handle that is half of this article.

The quiet cost of a sold-out product page

A sold-out page is one of the few places where a visitor tells you, with total clarity, “I want this exact product and I have money ready.” Then most stores answer with a grey button that says “Out of stock” and nothing else.

The visitor leaves. Maybe they check back. Usually they don’t — they buy a similar product from whoever ranks next in Google, and the demand you paid to generate converts on someone else’s store.

Here’s a rough illustration of what that leak looks like (illustrative numbers — swap in your own): say a €45 product goes out of stock for two weeks and its page still gets 30 visits a day. That’s 420 visits from people with above-average intent. If even 5% of them would have bought on the spot, you’ve walked past roughly €900 in revenue for one product, one restock cycle. Multiply by however many products in your catalog go out of stock in a normal quarter and the number stops being small.

Why “they’ll come back when it’s in stock” isn’t a plan

Some owners assume the keen ones will check back. A few will. But you’re asking a customer to do repeated manual work — revisit, check, revisit again — for your benefit, with no signal from you about when it’s worth doing. That’s backwards. The interested visitor already did their part by showing up; the follow-up should be your job, and it should be automatic.

The other common fix is running email-only restock alerts. Better than nothing, clearly. The catch is timing. Email open behavior is slow — plenty of people check their inbox once or twice a day — and a hot restock can sell through before the average subscriber even sees the subject line. For scarce inventory, the channel that wins is the one that interrupts politely in real time. That’s push.

This article is only about restocks. If the product is still in stock and you’re waiting for the price to move instead, that’s a different automation with different logic — covered in how to use push notifications for price drops.

Why push fits this alert better than any other trigger

Web push has real weaknesses as a channel — no inbox to return to, easy to over-use, subscribers you can’t identify by name. Back-in-stock is the use case where almost none of that matters and the strengths line up:

Speed. The notification appears on the subscriber’s screen within moments of the restock, whether or not your site is open. For an item 200 people are waiting on, minutes decide who gets one.
No email address needed. A visitor can opt into push in one click without typing anything, so your “notify me” button converts people who would never fill in an email field.
Perfect intent match. Each alert goes only to people who asked for that specific product, so relevance is built in — which is why restock alerts tend to be among the best-performing pushes a store sends. (Exact click rates vary a lot by store and product; check your own numbers rather than trusting industry averages.)

Push shouldn’t be the only channel, though. Send the push first, then an email an hour or two later to catch people whose browser was offline. Running both from one trigger is exactly the pattern described in combining email, SMS, and push in one automation.

Setting it up, step by step

Put the opt-in where the intent is. On every out-of-stock product page, replace the dead “Out of stock” state with a working “Notify me when it’s back” button that subscribes the visitor to push for that product. A generic site-wide push prompt won’t do this job — you need the product-level tie. (For growing your general push list, there’s a separate playbook: how to collect web push subscribers on an ecommerce website.)
Trigger on the inventory event, not on a manual send. The alert should fire from your store’s stock level crossing zero, automatically. If someone on your team has to remember to send it, it will go out late or not at all.
Write the message for one action. Product name, “back in stock,” and urgency that’s true: “Back in stock — limited quantity” is honest when it is. Deep-link to the product page, not the homepage. More on making these few words work in writing push notifications that get clicks.
Follow with email, then stop. One push, one backup email, done. If they didn’t act on a restock alert for a product they asked about, a third nudge won’t help and will cost you goodwill.

What to automate, precisely

Trigger: inventory for a tracked product moves from 0 to above 0.
Segment: only subscribers who requested an alert for that product. Nobody else.
Timing: push immediately; email follow-up after 1–2 hours to anyone who hasn’t purchased.
Channel: push first, email second. SMS only if the item is high-value and you have consent — a text about a €12 restock annoys more than it earns.
Content: product name, back-in-stock statement, truthful scarcity, direct product link.
Exit condition: subscriber purchases the product, or the product sells out again — either one should stop the flow instantly. An alert that arrives after the item is gone again is worse than silence.
Goal: purchases of the restocked product within 24–48 hours of the alert.

The small-restock problem nobody plans for

Now the uncomfortable part. Restock alerts assume supply roughly meets the waiting demand. Often it doesn’t.

Two situations to handle deliberately. First, the tiny restock: 150 people are waiting and 8 units arrive. Alert everyone and 142 people click through to a sold-out page — you’ve converted patient interest into irritation, twice. If your tooling allows it, alert in batches (oldest requests first) sized to the stock you actually have, or at minimum keep the sell-out exit condition tight so the alerts stop the moment inventory hits zero again.

Second, the phantom restock: a single return or an inventory correction bumps stock from 0 to 1, and your automation dutifully announces a restock that barely exists. Worth checking how your platform counts returned stock before you switch the flow on — a minimum-quantity threshold on the trigger (fire only when stock rises above, say, 5) filters most of this noise out.

Neither problem is a reason to skip the automation. Both are reasons to spend ten extra minutes on the trigger conditions.

What this looks like in a real store

An illustrative example, sized like a typical store in our audience: a store selling a popular sneaker model in limited runs. The product sells out in most sizes within days of each drop. The store adds a per-size “notify me” push prompt, so a size-42 buyer only hears about size-42 restocks. When 60 pairs arrive, the push goes out instantly to waiters, the product page sees a spike within the hour, and the email follow-up mops up the rest that evening. The flow’s exit rule stops all alerts the moment a size sells out again. No campaign was planned, no one wrote a newsletter — the inventory system did the marketing.

How to measure whether it’s working

Keep the scoreboard short:

Alert-to-purchase rate — of the people notified, how many bought within 48 hours. This is the number that matters.
Click-through rate on the push — judges the message and timing.
Revenue per restock event — makes the flow’s value visible next to your campaigns.
Opt-in rate on out-of-stock pages — how many sold-out page visitors press “notify me.” If this is low, the button placement is the problem, not the alert.

Tie the revenue back properly so the flow gets credit — the attribution side is covered in how to measure revenue from web push notifications.

Doing this in Omnisend

I run Omnisend in my own stores, and back-in-stock is one of the automations where it earns its keep: it connects to your store’s product catalog, so the restock trigger fires from actual inventory changes, and the same flow can hold the push step and the delayed email step with a purchase-based exit — no separate tools to stitch together. You build it once in the visual editor and it runs on every future restock.

The honest caveats: your inventory data has to be accurate for any of this to work, per-product push subscription depends on your storefront setup, and no alert rescues a product people didn’t want in the first place. Omnisend is an affiliate partner of Shopimation; the recommendation comes from daily use, not the link.

Your next step

Open your store analytics and find your three most-visited out-of-stock product pages from the last 90 days. That traffic is the demand you’re currently sending to competitors. Put a “notify me” push prompt on those pages this week, wire the restock trigger, and let the next inventory delivery test the flow for you.