Every ID your systems use.
Card barcode, email, phone and the IDs from your till, shop and ERP, all on one member.
Your till knows a card number, your web shop knows a customer ID, your app knows an email. Vendor Loyalty ties all of them to one member, so the balance, tier and history are the same wherever that person shows up.
The same person signs up online, gets a plastic card in store and installs the app. Each system creates its own record, the points split three ways, and nobody trusts the balance. Fixing it later means spreadsheets and support tickets.
Card barcode, email, phone and the IDs from your till, shop and ERP, all on one member.
Balances add up, history moves over and old IDs keep working.
Every write is safe to retry. Get-or-create by external ID is a single idempotent PUT; merged profiles answer with an X-Merged-Into header so your system can update its stored ID.
1PUT /api/v1/members/by-external/webshop/482112X-API-Key: vls_••••34{ "first_name": "Ana", "last_name": "Petrova",5 "email": "ana@example.com" }67→ 200 { "data": { "uuid": "9f3c2a1e-…",8 "barcode_ean13": "2000004812294", … } }
It keeps working. Lookups by the old identifier land on the surviving profile.
Not yet. Account linking codes are sent by email today.
No. The ledger and tier stay, only personal data is removed.
Tell us about your members, your tills and your shop, and we’ll show you where Vendor Loyalty fits.
Launch a store yourself, or talk to us about connecting ecommerce to the systems you already run.
Everything you need to launch, manage and grow an online store. From €39/month.
Explore CommerceLarger catalogs, advanced pricing, complex operations and deeper integrations.
Explore Scale