Hosted vs self-hosted loyalty for PrestaShop: an integration-first checklist

A loyalty programme is not a feature checklist. It is a small financial system: orders issue a future liability, refunds may reverse it, customers redeem it, scheduled work releases or expires it, and support staff correct exceptions. The right software is the one that can operate that exact system on your current PrestaShop stack.

Hosted platforms such as LoyaltyLion or Smile.io and native PrestaShop modules have very different operating models. Do not assume a provider supports PrestaShop because it has an API or a JavaScript widget, and do not assume a native module reproduces the integration and analytics ecosystem of a mature hosted platform.

1. Eliminate any option without an evidenced PrestaShop integration

Ask each hosted vendor to document the current production path in writing:

• the supported PrestaShop connector and versions;
• authentication, initial import and ongoing sync ownership;
• order, payment, refund and cancellation events;
• customer-account, product-page, cart and email surfaces;
• sync latency, retry behaviour, monitoring and incident support;
• complete export and cutover procedure.

If the answer is “use our API”, price the integration as a software project. The API may be capable, but the connector, event mapping, monitoring and long-term maintenance still need an owner.

2. Compare cost from current written inputs

Hosted pricing can depend on monthly orders, plan level, add-ons and services. Native modules can carry implementation, hosting, maintenance and compatibility work even when the licence is one-time. Use these inputs instead of a copied marketing range:

• current subscription quote and currency;
• expected order tier and overage rule;
• features or integrations that require another plan or add-on;
• implementation, migration and theme work;
• ongoing monitoring, support and upgrade testing;
• tax and payment costs.

NP Rewards Pro currently publishes a €129 one-time licence and optional €39 / 6-month updates. That known price is only one side of the decision. Use the PrestaShop loyalty buyer lab to model the face-value points reserve against your contribution margin; it deliberately makes no repeat-purchase or payback forecast.

3. Compare data ownership as responsibilities, not slogans

In a hosted model, verify the processor, sub-processors, data location, retention, deletion, incident process and export contract. Also determine what the shopper sees when the service or sync is unavailable.

In a self-hosted model, the loyalty ledger can stay in the store database, but the merchant becomes responsible for database access, backups, recovery, security patches, cron health, retention and lawful processing. “Your data” does not mean “no work”.

4. Build the comparison from real workflows

Test the same synthetic customer through both candidates:

1. place and validate an eligible order;
2. verify pending and available balances;
3. refund part of the order and cancel the rest;
4. redeem a voucher or gift and reconcile the ledger;
5. pause scheduled work, observe the failure and restore it;
6. export and erase the customer;
7. export the complete programme for a potential future migration.

Score the evidence, not the demo script. Screenshots prove that an interface exists; only a staging workflow proves that it works with your order states, theme, email setup and staff process.

5. Decide which operating model fits

Cash redemption needs a separate legal decision

A cashout-request feature does not make a programme legal, tax-correct or KYC-compliant. Vouchers, gifts and cash can receive different accounting and regulatory treatment by country and programme design. Keep cashout off until your adviser approves the legal, tax, invoicing, identity and payment process.

A reversible selection process

1. Write the programme rules and unit economics before choosing software.
2. Remove any candidate without a supported integration and complete export path.
3. Run the same failure-path test on staging.
4. Compare the complete current cost over a fixed horizon.
5. Launch one programme with a baseline and an explicit rollback window.

You can inspect NP Rewards Pro’s real launch, storefront and customer-message path on its guided product experience. The product page publishes the price, current release, tested compatibility boundary and install path so the decision can remain evidence-led.