Integrations and data
For the IT team, who will ask the right questions
A retailer programme always ends up having to talk to something else: the ERP, the distributor's software, the company directory. Here is what is provided, in plain terms.
What is available
| Topic | What Loyaltix does |
|---|---|
| Partner API | Documented REST API (OpenAPI), OAuth2 authentication, clients and scopes managed in the back office. |
| Webhooks | Outgoing notifications on programme events: sign-up, points, order, mission. |
| Single sign-on | SAML 2.0 and OpenID Connect, to open a partner application from the portal. |
| ERP | Loyaltix is built on ERPNext: items, sales invoices and outlets are already there. Points can be awarded from invoices. |
| Field CRM | Shop accounts and contacts are shared with the sales reps' CRM. |
| Messages | Email, text messages, notifications in the portal. The SMS provider plugs in through a connector. |
| Imports | Members, shops and sales volumes from Excel or CSV files. |
An open foundation, and why it matters
Loyaltix runs on Frappe and ERPNext, two widely used open-source products. In practice: the database is yours, the data model is readable, and you don't depend on a service hosted on the other side of the world.
The platform can run on a server you choose, including in Algeria. For many IT departments, that is the first question, well before features.
Common technical questions
Can we connect our distributors' software?
Through the API if they have one, otherwise by importing sales files. At the start, imports are almost always enough.
Do we have to use ERPNext as our ERP?
No. ERPNext is the technical foundation. Your ERP stays your ERP. We exchange data with it through the API or through files.
How are permissions handled in the back office?
By role: administrator, manager, editor, operator, consultant. Each role has its screens and its actions.
A particular constraint?
Hosting, company directory, a distributor's file format: tell us, and we will give you a precise answer.