Druge platforme in integracije spletnih trgovin

Kako nastaviti Omnisend za PrestaShop

Posted on July 18, 2026 by

Povezovanje Omnisenda s PrestaShopom se strne v pet potez: namestite modul Omnisend v zaledje PrestaShopa, ga povežete s svojim računom Omnisend, počakate, da sinhronizira kontakte in naročila, dodate obrazec za prijavo ter vklopite tok za opuščene košarice in pozdravni tok. Tipična trgovina PrestaShop v enem dnevu zajema nove naročnike in obnavlja košarice. Deli, ki ljudi spotaknejo, so značilni za PrestaShop — združljivost modulov med večjimi različicami, predpomnilnik, ki skriva vaše spremembe, in ravnanje s privolitvijo, ki je tu pomembnejše, ker je PrestaShop tako pogost med evropskimi trgovinami, ki živijo pod GDPR.

Predpostavljam, da že vodite trgovino PrestaShop z ustaljenimi naročili. To je pot za nastavitev in nastavitve, ki dejansko štejejo, ne razlaga za začetnike.

Začnite s preverbo različice

Zgodovina različic PrestaShopa je prva stvar, ki jo je treba razrešiti, ker določa, katero pot uberete.

PrestaShop 1.6, 1.7 in linija 8.x se razlikujejo dovolj, da se modul, zgrajen za eno, na drugi morda ne obnaša pravilno, 1.6 pa je še posebej star. Preden karkoli namestite, si zabeležite točno različico PrestaShopa, nato potrdite, da jo trenutni modul Omnisend podpira. Različice modula in platforme se obe premikata, zato obravnavajte katerikoli konkreten zaslon ali pot v tem vodniku kot splošno obliko in najprej preverite trenutno dokumentacijo Omnisenda za PrestaShop glede na svojo različico. Če domorodni modul ne pokriva vaše postavitve, PrestaShop ponuja spletno storitev API in webhooke, prek katerih se lahko povežete namesto tega — kompromisi domorodnega proti povezovalniku so v kako izbrati med domorodnimi integracijami in Zapierjem, pristop, ki temelji na API-ju, pa je pojasnjen v kako uporabljati Omnisend s trgovino, ki temelji na API-ju.

Ko ste že pri tem, poglejte, kaj iz te trgovine že pošilja e-pošto. PrestaShop pride z lastnimi funkcijami za pošto, morda pa imate nanj privijačen tudi modul za novice. Izberite en merodajni vir podatkov, preden pride Omnisend, sicer boste ljudem pošiljali e-pošto dvakrat in napihnili število kontaktov.

Namestitev modula

Domorodna pot je modul Omnisend za PrestaShop, nameščen iz vašega zaledja.

Pridobite modul. Prenesite ga od Omnisenda ali ga namestite prek kataloga modulov PrestaShop, odvisno od tega, kako se trenutno distribuira.
Namestite in konfigurirajte. V zaledju pod Moduli ga naložite ali omogočite, nato odprite njegovo konfiguracijo. Tu ga boste povezali s svojim računom Omnisend, običajno z API-ključem, ki ga ustvarite v Omnisendu in prilepite.
Izpraznite predpomnilnik. PrestaShop agresivno predpomni. Če namestite modul in trgovina izgleda nespremenjena — obrazec se ne prikaže, nastavitve se ne shranijo — izpraznite predpomnilnik PrestaShopa, preden karkoli domnevate. Ta en korak razreši presenetljiv delež trenutkov “ne deluje”.
Pustite, da sinhronizacija steče. Obstoječe stranke, naročila in izdelki pritečejo v Omnisend. Na velikem katalogu z leti zgodovine to traja — od minut do ur — zato pustite, da se zaključi, preden gradite.

Privolitev uredite pravilno že prvič

To si zasluži svoj razdelek, ker je občinstvo PrestaShopa močno evropsko, napačno ravnanje s privolitvijo pa je drago.

Ko se vaše stranke sinhronizirajo, mora njihov status naročnine odražati resnično prijavo. Stranka, ki je enkrat kupila, a nikoli ni pristala na trženjsko e-pošto, ni naročnik, in njen uvoz kot naročnika je tako težava po GDPR kot težava z dostavljivostjo — pošiljanje brez privolitve pritegne pritožbe glede neželene pošte, ki škodijo vašemu ugledu pošiljatelja za vse na vašem seznamu. Po sinhronizaciji preverite, da so prijavljeni in neprijavljeni kontakti pošteno ločeni. Ko gradite obrazec za prijavo, uporabite jasno potrditveno polje za privolitev, kjer to zahteva vaša pristojnost, in vodite zapis o tem, kako in kdaj je vsak kontakt privolil. To je dolgočasno postaviti in boleče naknadno vgraditi, zato to storite zdaj.

Preverite, da so podatki res prispeli

Sinhronizacija je temelj, PrestaShop pa ima dovolj gibljivih delov, da bi jo morali potrditi in ne zaupati.

V Omnisendu, ne v PrestaShopu, preverite:

Kontakti — obstoječe stranke prisotne, status naročnine pošten.
Naročila — odprite nekaj kontaktov in potrdite, da se pretekla naročila prikažejo s pravilnimi izdelki in zneski. To poganja vaše najboljše segmente: enkratni kupci, veliki porabniki, kupci po kategorijah.
Izdelki — imena, slike, cene, zaloga se prenašajo čisto, saj se iz tega vira izrisujejo vaše e-pošte za košarice in priporočila.

Če naročila ali izdelki pridejo skozi prazni ali napačni, se ustavite in popravite, preden gradite. Pogost vzrok pri PrestaShopu je nepopolna sinhronizacija ali vrzel v dovoljenjih API-ja; kako odpraviti manjkajoče podatke o naročilih v e-poštnih platformah je kontrolni seznam, ki najde, na katerega ste naleteli. In če je vaše število kontaktov videti nenavadno visoko, morda drugo povezano orodje dvojno piše — izogibanje podvojenim kontaktom med integracijami pokriva, kako to ustaviti.

Zajemite kontakte z enim obrazcem

Povezana trgovina brez načina za zajem e-pošte je razpoka, ki jo plačujete. Vsak obisk, ki ste ga kupili in ga niste spremenili v kontakt, je izgubljen v trenutku, ko zaprejo zavihek.

Za začetek dodajte en obrazec za prijavo — pojavno okno ob namenu izhoda ali zdrsni obrazec z majhno spodbudo, varno za marže, prekosi predelan obrazec z več polji, saj vas vsako dodatno polje stane zaključenih prijav. Sprožite ga ob izhodu ali po kratkem zamiku, ne v trenutku, ko nekdo prispe. En obrazec, katerega številke lahko preberete, prekosi kup obrazcev, ki jih ne morete primerjati.

Vklopite dve avtomatizaciji

Tukaj povezana trgovina PrestaShop začne služiti, namesto da bi le hranila podatke.

Opuščena košarica. Sprožilec: kupec doda v košarico in ne dokonča nakupa. Najvišji donos katerega koli zgodnjega toka, ker je nakupni namen že prisoten. Solidna prva različica:

Opomnik po približno eni uri z natančnimi izdelki v košarici in neposredno povezavo nazaj.
Sledenje po približno 24 urah — ista košarica, majhno zagotovilo glede dostave ali vračil, brez popusta zaenkrat.
Neobvezni zaključek po 48–72 urah s skromno spodbudo, če vaše marže to dopuščajo.

Nastavite ga tako, da se ob nakupu ustavi, da nihče ne dobi opomnika, potem ko je že kupil.

Pozdravni tok. Sprožilec: nova prijava. Dostavite obljubljeno spodbudo, v vrstici ali dveh predstavite trgovino, usmerite k najbolje prodajanemu izdelku. Druga e-pošta dan pozneje lahko obravnava pogost pomislek ali pove kratko zgodbo o blagovni znamki. Pretvori nove naročnike, dokler je zanimanje na vrhuncu.

Vse ostalo — opuščanje brskanja, navzkrižna prodaja, po nakupu, ponovno pridobivanje — počaka, dokler ta dva nista v delovanju in izmerjena.

Realističen primer

Vzemite trgovino PrestaShop, ki ustvari 30.000 € na mesec z okoli 1.500 opuščenimi košaricami mesečno. Predpostavimo, da osnovni tok obnovitve pridobi nazaj 8 % teh pri povprečnem naročilu 50 € — to je okoli 120 naročil in grobo 6.000 € mesečnega prihodka iz enega toka, zgrajenega enkrat. Stopnje obnovitve nihajo široko glede na trgovino, izdelek in občinstvo, zato to obravnavajte kot ponazoritev in ne cilj. Tudi pri polovici predpostavljene stopnje se tok večkrat povrne za ceno orodja. Denar je bil že v prometu, ki ste ga plačali za pridobitev; avtomatizacija ga je le nehala puščati skozi vrata.

Kaj meriti

Prihodek na prejemnika na tok — ali avtomatizacija dejansko služi.
Stopnja obnovitve košaric — obnovljena naročila glede na opuščene košarice.
Pretvorba prijav — naročniki glede na tiste, ki so obrazec videli.
Stopnje odjav in pritožb glede neželene pošte — zgodnje opozorilo o ciljanju ali ugledu; med nastavitvijo overite svojo pošiljajočo domeno (SPF, DKIM), da ju ohranite nizki.
Število podvojenih kontaktov — naraščanje pomeni, da se dve orodji borita.

Preverjajte tedensko na začetku, nato mesečno, ko se stvari umirijo.

Kam se Omnisend prilega, pošteno

Omnisend uporabljam v svojih trgovinah, potem ko sem ga preizkusil proti Klaviyu, in za trgovca PrestaShop je praktična privlačnost v tem, da modul poskrbi za sinhronizacijo strank/naročil/izdelkov, tako da ne vzdržujete lastnega mostu, zgornje avtomatizacije pridejo kot predloge za urejanje, e-pošta, SMS in spletni potisk pa sedijo na eni platformi z vgrajenim segmentiranjem in priporočili izdelkov. Cene ponavadi pristanejo pod Klaviyo pri primerljivih velikostih seznama, kar postane pomembno, ko rastete. Omnisend je pridruženi partner Shopimationa in ga priporočam iz resnične vsakodnevne uporabe — brezplačna raven zadostuje za povezavo PrestaShopa, preverbo sinhronizacije in preizkus obeh tokov na živem prometu, preden plačate.

Pošteni del: orodje sinhronizira podatke in pošilja sporočila dobro, a ne bo napisalo vaše ponudbe, popravilo okornega postopka nakupa ali premaknilo šibkega izdelka. Povezovanje modula je hitrih 20 %. Tokovi in besedilo so tam, kjer živi donos.

Vaš naslednji korak

Potrdite različico PrestaShopa, namestite modul, preverite, da so se naročila in izdelki sinhronizirali, nato pa še danes vklopite tok za opuščene košarice — to je najhitrejši evro nazaj. Ko vaši podatki tečejo čisto, je večja zmaga v tem, da jih uporabite: segmenti strank, ki bi jih morala ustvariti vsaka spletna trgovina je naravno naslednje branje za pretvorbo povezane trgovine PrestaShop v ponavljajoč se prihodek.

Other Ecommerce Platforms and Integrations

How to Set Up Omnisend for PrestaShop

Posted on July 18, 2026 by

Connecting Omnisend to PrestaShop comes down to five moves: install the Omnisend module in your PrestaShop back office, link it to your Omnisend account, let it sync contacts and orders, add a signup form, and turn on an abandoned cart flow and a welcome flow. A typical PrestaShop store is capturing new subscribers and recovering carts within a day. The parts that trip people up are specific to PrestaShop — module compatibility across major versions, the cache that hides your changes, and consent handling, which matters more here because PrestaShop is so common among European stores that live under GDPR.

I’m assuming you already run a PrestaShop store with steady orders. This is the setup path and the settings that actually matter, not a beginner explainer.

Start with a version check

PrestaShop’s version history is the first thing to sort out, because it decides which route you take.

PrestaShop 1.6, 1.7, and the 8.x line differ enough that a module built for one may not behave on another, and 1.6 in particular is old. Before you install anything, note your exact PrestaShop version, then confirm the current Omnisend module supports it. Module and platform versions both move, so treat any specific screen or path in this guide as the general shape and check Omnisend’s current PrestaShop documentation against your version first. If the native module doesn’t cover your setup, PrestaShop exposes a webservice API and webhooks you can connect through instead — the trade-offs of native-versus-connector are in how to choose between native integrations and Zapier, and the API-driven approach is walked through in how to use Omnisend with an API-based store.

While you’re at it, look at what already sends email from this store. PrestaShop ships with its own mail features, and you may have a newsletter module bolted on too. Pick one system of record before Omnisend arrives, or you’ll email people twice and inflate your contact count.

Installing the module

The native path is Omnisend’s PrestaShop module, installed from your back office.

Get the module. Download it from Omnisend or install it through the PrestaShop module catalog, depending on how it’s currently distributed.
Install and configure. In the back office under Modules, upload or enable it, then open its configuration. You’ll connect it to your Omnisend account here, usually with an API key you generate in Omnisend and paste in.
Clear the cache. PrestaShop caches aggressively. If you install the module and the store looks unchanged — form not showing, settings not saving — clear the PrestaShop cache before assuming anything is broken. This one step resolves a surprising share of “it doesn’t work” moments.
Let the sync run. Existing customers, orders, and products flow into Omnisend. On a large catalog with years of history this takes time — minutes to hours — so let it finish before you build.

Get consent right the first time

This deserves its own section because PrestaShop’s audience is heavily European, and getting consent wrong is expensive.

When your customers sync in, their subscription status has to reflect real opt-in. A customer who bought once but never agreed to marketing email is not a subscriber, and importing them as one is both a GDPR problem and a deliverability one — unconsented sends draw spam complaints that damage your sending reputation for everyone on your list. Check, after the sync, that opted-in and non-opted-in contacts are separated honestly. When you build your signup form, use a clear consent checkbox where your jurisdiction requires it, and keep a record of how and when each contact opted in. This is dull to set up and painful to retrofit, so do it now.

Verify the data actually landed

The sync is the foundation, and PrestaShop has enough moving parts that you should confirm it rather than trust it.

In Omnisend, not in PrestaShop, check:

Contacts — existing customers present, subscription status honest.
Orders — open a few contacts and confirm past orders show with correct products and totals. This powers your best segments: one-time buyers, high spenders, category buyers.
Products — names, images, prices, stock pulling through cleanly, since your cart and recommendation emails render from this feed.

If orders or products come through empty or wrong, stop and fix it before building. A common PrestaShop cause is an incomplete sync or an API permission gap; how to troubleshoot missing order data in email platforms is the checklist that finds which one you’ve hit. And if your contact count looks strangely high, a second connected tool may be double-writing — avoiding duplicate contacts across integrations covers shutting that down.

Capture contacts with one form

A connected store with no way to capture email is a leak you’re paying for. Every visit you bought and didn’t turn into a contact is gone the moment they close the tab.

Add one signup form to start — an exit-intent popup or a slide-in with a small, margin-safe incentive beats an over-engineered multi-field form, because each extra field loses you completions. Trigger it on exit or after a short delay rather than the instant someone arrives. One form you can read the numbers on beats a stack of them you can’t compare.

Turn on two automations

This is where a connected PrestaShop store starts earning instead of just storing data.

Abandoned cart. Trigger: a shopper adds to cart and doesn’t complete checkout. Highest return of any early flow, because the buying intent is already there. A solid first version:

Reminder at about one hour with the exact cart items and a direct link back.
Follow-up at about 24 hours — same cart, a small reassurance about shipping or returns, no discount yet.
Optional closer at 48–72 hours with a modest incentive if your margins allow it.

Set it to exit on purchase so nobody gets a reminder after they’ve bought.

Welcome. Trigger: a new signup. Deliver the promised incentive, introduce the store in a line or two, point to a bestseller. A second email a day later can handle a common objection or tell a short brand story. It converts new subscribers while interest is at its peak.

Everything else — browse abandonment, cross-sell, post-purchase, win-back — waits until these two are live and measured.

A realistic example

Take a PrestaShop store doing €30,000 a month with about 1,500 carts abandoned monthly. Suppose a basic recovery flow wins back 8% of them at an average order of €50 — that’s around 120 orders and roughly €6,000 in monthly revenue from one flow built once. Recovery rates swing widely by store, product, and audience, so treat this as illustrative rather than a target. Even at half the assumed rate, the flow pays for the tool several times over. The money was already sitting in traffic you’d paid to acquire; the automation just stopped it walking out the door.

What to measure

Revenue per recipient per flow — whether the automation actually earns.
Cart recovery rate — recovered orders over abandoned carts.
Signup conversion — subscribers over form viewers.
Unsubscribe and spam-complaint rates — early warning on targeting or reputation; authenticate your sending domain (SPF, DKIM) during setup to keep these low.
Duplicate contact count — climbing means two tools are fighting.

Check weekly at first, then monthly once things settle.

Where Omnisend fits, honestly

I run Omnisend in my own stores after testing it against Klaviyo, and for a PrestaShop merchant the practical draw is that the module handles the customer/order/product sync so you’re not maintaining a custom bridge, the automations above come as editable templates, and email, SMS, and web push sit in one platform with built-in segmentation and product recommendations. Pricing generally lands below Klaviyo at comparable list sizes, which matters as you grow. Omnisend is an affiliate partner of Shopimation, and I recommend it from real daily use — the free tier is enough to connect PrestaShop, verify the sync, and test both flows on live traffic before you pay.

The honest part: the tool syncs data and sends messages well, but it won’t write your offer, fix a clunky checkout, or make a weak product move. Connecting the module is the quick 20%. The flows and the copy are where the return lives.

Your next step

Confirm your PrestaShop version, install the module, verify orders and products synced, then switch on the abandoned cart flow today — it’s the fastest euro back. Once your data flows cleanly, the bigger win is using it: the customer segments every online store should create is the natural next read for turning a connected PrestaShop store into repeat revenue.