Choosing the architecture

Loyalty in ERP or on the web: how to choose

A loyalty module inside the ERP or a web center: how they differ, when each fits, how to switch without losing history and when to use both.

A chain has to decide where discount rules and bonuses live. One option is loyalty in the ERP, as part of the accounting system. The other is a separate web loyalty system that serves the tills of all stores. The choice affects how fast changes arrive, how the store works without a connection and the cost of ownership, so it pays to compare both before you choose a loyalty platform, not after.

The two approaches in brief

ERP module

  • Rules, customers, bonuses and analytics run inside your ERP system. No separate server is needed, the data sits next to your accounting, and the team uses the familiar interface.

Web center

  • A separate service for the whole chain: rules, bonus accounts and an API for tills. It runs in the cloud or on your server and is managed through a web admin.

Both are part of Synngate Loyalty, so the comparison below is not about "better" or "worse": it is about what fits your chain today.

A comparison that matters

QuestionERP moduleWeb center
Where it runsInside your ERP systemA separate web service, in the cloud or on your server
InfrastructureNo separate serverA service and its hosting are needed
Rules25 kinds of conditions, 13 kinds of actions, 12 event types17 conditions, 11 actions
Coupons, certificates, punch cardsAvailable in the ERP moduleNot supported yet
Lifecycle analytics12 segments, 12 reports, 60 indicatorsSegments and 5 reports, including promotion effect
Link to the tillA web service for exchange with the tillA till API: identification, calculation, confirmation
Working without a connectionThe till does not block a sale if the server is unavailableThree modes: center, store node, core inside the till
Where rules are changedIn the familiar ERP interfaceIn the web interface; changes reach the store within seconds

The table reflects what is possible today: verify the current state at a demo.

When the ERP module fits

Many complex mechanics

Coupons, certificates, punch cards and extended rules are needed in your program right now.

The chain's whole life is in the ERP

Stock, prices and customers in one place, and you do not want extra infrastructure.

Analytics matter more than speed

You need lifecycle segments and detailed reports about the customer base.

When the web center fits

Many stores and tills

Rules change often and a change must reach all stores quickly.

Work without a connection is needed

The store must not depend on the link: the calculation runs on the store node or inside the till.

An app and messaging

The card in the phone, offers and the marketer's workspace are easier to build around a separate center.

If you hesitate, ask yourself: what hurts more, speed and reliability at the till, or the depth of mechanics and analytics? The answer shows where to start.

How to compare without getting lost

First write down your own conditions and only then look at products. Otherwise the brightest features will decide, not your needs.

  • How many stores and tills you have today and how many you will have in two years
  • Which mechanics you use now and which you only want to try
  • How often the marketer changes rules and how quickly that has to reach the till
  • What happens in the store when the connection drops
  • Who will administer the system: your programmers or a contractor
  • Whether you need a card in the phone, messaging and a marketer's workspace
  • What must be moved from the previous system and how you will verify the result

What goes into the cost of ownership

Compare not the license price but all the cost items over several years. For the ERP module these are customizations and updates inside the accounting system and programmers' time. For the web center: hosting the service, administration and integration with tills. In both cases there are costs for training, data transfer and support. Ask the vendor for a list of what is included in the work and what is paid separately, and compare the lists.

Switching from the ERP module to the web center without losing history

The choice is not for life. Many chains start in the ERP and move to the web center later, when the number of stores grows. What is moved: customers, cards, groups and rules. The web center's calculation can be checked against the previous one on a set of real receipts, and the differences are reviewed before going live.

  1. Preparation

    Decide which rules stay and clean up duplicate customers.

  2. Trial transfer

    Load a copy of the data, compare the number of customers, cards and the bonus total.

  3. Check the calculation

    Recalculate a set of real receipts in the new system.

  4. Run in parallel

    One or two stores run on the new system, the rest on the old one.

  5. Switch over

    The other stores move, and the previous module stays read-only.

An important limit: coupons, certificates and punch cards are not moved to the web center yet; they stay in the ERP module. If you need them, use both solutions together.

When to use both

Sometimes some mechanics need the ERP, while the tills need the speed and autonomy of the center. Then the chain runs on the web center, and the specific mechanics stay in the ERP module. This is an intermediate stage, not a permanent answer: treat it honestly, with a plan for what moves and when.

A practical tip: before deciding for the whole chain, run a pilot in one or two stores. A pilot shows what a presentation does not: how cashiers react to the new flow, how clear the admin is for the marketer, which differences appear when receipts are compared. Agree success criteria and a deadline for the pilot in advance, otherwise it will drag on without a decision.

What we offer

In Synngate Loyalty you can start with any part. Details are on the pages of the ERP module and the web center; what the move looks like is explained in the article on moving from plastic cards, and analytics is described on the lifecycle page. To choose the option for your chain, request a demo.

Frequently asked questions

Can we start with the ERP and move to the web later?

Yes. Customers, cards, groups and rules are moved, and the calculation is checked against the previous one. It is the standard path.

What is not moved?

Coupons, certificates and punch cards stay in the ERP module. If you need them, use both solutions in parallel.

Does the web center need a separate server?

It runs as a web service: in our cloud or on your server.

Do we have to replace our till?

No. We have our own till with loyalty built in, and an open API is provided for other tills.

See the solution on your own network

A 30-minute conversation about your loyalty program, with no generic slides.