What the Lobyco platform consists of, and the three points in a purchase where your POS talks to it.
Lobyco is a modular loyalty platform, run as a service. It gives you a white-label mobile app, the Lobyco Admin Portal and the APIs behind both. You build the loyalty programme on top and connect it to your POS and your other systems. This page says what the pieces are, where the integrations sit, and how the API reference is organised.Each client has its own tenant. Customers, marketers and support staff reach it through the app, the admin portal and reporting; your own infrastructure connects through the integration layer
Each client runs on its own tenant, with its own application instances and databases. Lobyco operates all of it. Nothing is installed or maintained on your side; your part of the work is the integration.
Component
What it is
Who uses it
White-label mobile app
The iOS and Android app, branded for you
Customers
Lobyco Admin Portal
Where campaigns, offers, content and customers are managed
Marketers and customer support
Backend services
The services behind the app and the portal, open to your systems through REST APIs
Your POS, website and backend
Integration layer
Optional. Connectors Lobyco builds between its services and your ERP, PIM, POS or database
A loyalty programme only works when Lobyco sees what happens at the till. That is either a live connection from your POS to the Lobyco APIs, or data the POS produces, sent afterwards. You can build against the REST APIs yourself, or Lobyco can build an integration layer between your systems and its services.A purchase meets Lobyco at three points, shown below. Each is optional, and each can be done in more than one way. Together they run the loyalty programme end to end. That is enrolment, identification at the POS, coupon and reward redemption, and purchase processing, so that points and rewards accumulate.Identify, verify, settle: the customer is linked to the sale, the offers are applied, and the finished sale is loaded
The customer checks in at the POS with their preferred method: the app’s QR code, a membership card, or another identifier. That links the transaction to a customer in the Members API. It can happen at any point in the transaction, depending on the flow you implement.
The POS asks Lobyco which offers apply. There are two ways. The POS fetches the customer’s active coupons with GET /v2/customers/{customerId}/coupons and applies them itself. Or the POS sends the basket to the Discounts API, and Lobyco returns the offers that apply and the discounts it calculated.
When you sign a contract, Lobyco gives you a test environment and a production environment. Each has its own APIs, admin portal and app builds. What an environment offers differs per client, because Lobyco releases new versions continuously and tailors functionality per contract. Treat this documentation as the overview, and your own environment as the truth.
