Çentik vs LOKE: UK Loyalty Platform Comparison

Çentik vs LOKE: the quick answer

Çentik is the more focused proposition if you primarily want digital loyalty without replacing your existing till or requiring customers to install a dedicated app. Its public UK-facing product information centres on browser-based loyalty cards, a standalone NFC Çentik Stamp, personal QR codes, Apple Wallet and Google Wallet passes, customer management, campaigns and repeat-visit analytics. Çentik +1 LOKE is broader: its public materials combine loyalty with ordering, payment, delivery, collection, payment terminals, customer data, personalised promotions and reporting, delivered through branded web and mobile experiences. LOKE +2 LOKE +2

Çentik vs LOKE feature comparison

The biggest difference is the operating model, not the word loyalty

Both products can support a browser journey, so it would be inaccurate to describe LOKE simply as an app-only alternative. The more useful distinction is operational. Çentik treats loyalty as an independent layer around the existing counter workflow: staff can issue a stamp through the Çentik NFC device or a QR flow without a mandatory POS integration. LOKE aims to connect more of the transaction journey itself, including ordering and payments, and its latest terminal documentation describes automatic loyalty earning when a customer's payment method is already linked. Çentik +2 Loke Support +2

• If the requirement is primarily a digital replacement for a paper stamp card, compare the number of steps at the counter, staff training, fraud controls and how quickly customers can see their reward progress.
• If you want loyalty to be automatically associated with card or phone payments, ask LOKE to demonstrate its Terminal flow against your exact POS configuration. Loke Support
• If you want a physical loyalty touchpoint that is separate from payment processing, Çentik's documented NFC Stamp is directly relevant. Çentik
• If Apple Wallet or Google Wallet loyalty passes are important, Çentik publicly documents them; verify equivalent LOKE support rather than assuming that Apple Pay or Google Pay payment support means loyalty-pass support. Çentik +1

Who is Çentik best suited to?

Çentik is likely to suit an independent café, bakery, coffee group or other repeat-visit business that already has a working POS and does not want loyalty to dictate its payment stack. Its strongest documented combination is a browser-based card, NFC and QR interactions, optional Apple/Google Wallet access, reward tiers, customer segments, campaigns, analytics, staff accounts and multi-location support. Çentik +1 The trade-off is scope: businesses wanting online ordering, delivery orchestration, pay-at-table or a branded native ordering app would need to keep those functions elsewhere or verify future Çentik capabilities.

Who is LOKE best suited to?

LOKE is likely to suit hospitality operators that want loyalty to sit inside a larger digital ordering and payment ecosystem. Its current public materials cover branded mobile and web apps, personalised marketing, order-to-table, pay-at-table, collection, delivery, payment terminals and reporting. LOKE +2 LOKE +2 This can be attractive to restaurants, pubs and multi-site hospitality groups seeking a more unified transaction and customer-data stack. The corresponding due-diligence question is implementation scope: determine which POS integrations, payment configuration, app components, setup services and ongoing fees your specific deployment requires.

Limitations and trade-offs to check before choosing

• Çentik: its current public proposition is narrower than LOKE's ordering-and-payment platform. Do not assume it replaces an ordering system, payment terminal or full hospitality commerce stack.
• Çentik: resolve the conflicting English-language public pricing before using a numerical UK price in sales material or procurement comparisons. Çentik +1
• LOKE: public pricing transparency is limited because the published UK agreement places fees in individual commercial documents and treats fee information as confidential. Ask for platform, setup, customisation, transaction, hardware and exit-related charges in writing. LOKE +1
• LOKE: its broader platform may create more configuration choices than a loyalty-only rollout. Verify the exact POS, payment gateway, terminal, web-app and native-app components included in your proposal.
• Both: ask for a live demonstration of the exact customer journey you intend to deploy rather than comparing feature names alone.

Migration from LOKE to Çentik: what should be preserved?

Migration should be treated as a data-and-entitlement project, not simply a CSV upload. LOKE's public feature page states that data can be downloaded and exported, while its published UK merchant agreement defines transition services that can include making Customer Data available and providing reasonable assistance with moving to a replacement service; the agreement also defines a Transition Services Fee, so the commercial terms should be checked before exit. LOKE +1 Çentik does not currently publish a one-click LOKE migration workflow, so import format, balance mapping and cut-over support should be confirmed with Çentik before promising a migration date.

• Export customer identifiers and deduplicate accounts before import.
• Map current points, stamps, credits, vouchers, reward entitlements and expiry dates into an agreed target model rather than silently resetting them.
• Preserve location membership and programme/tier information where it affects an existing customer's entitlement.
• Keep marketing-consent evidence, opt-out and suppression states separate from ordinary loyalty membership.
• Agree how historical transactions and visits will be handled: full history, summary values or opening balances.
• Run a sample migration first and reconcile customer counts, reward balances and high-value accounts before final cut-over.
• Publish customer-facing communication explaining what changes, what remains valid and how customers access the new programme.

UK GDPR and PECR considerations for loyalty migrations

A loyalty database is not automatically a permission to send marketing. ICO guidance states that unsolicited electronic marketing to individual subscribers generally requires consent unless the requirements of a relevant soft opt-in are satisfied, and recipients must have an appropriate way to opt out. ICO +1 During migration, preserve evidence of how and when marketing permission was obtained rather than copying only email addresses or mobile numbers. If personal information is made available to a separate organisation outside the UK, assess whether the UK GDPR restricted-transfer rules apply and which transfer mechanism is appropriate. ICO This is a procurement and implementation consideration, not a claim that either vendor is or is not legally compliant.

Commercial questions to ask both vendors

• What is the complete monthly and annual cost for the number of UK locations we operate?
• Are setup, branded-app, hardware, payment-processing, transaction, customisation, support or migration fees charged separately?
• Can we export customers, balances, reward states, consent records and transaction history in a usable format at any time?
• What happens to existing rewards and customer data when the contract ends?
• Which functions work without a POS integration, and which require one?
• Which POS and payment integrations are supported for our exact UK configuration?
• Can we pilot one location before committing the full estate?
• What contractual notice, minimum term, transition or termination provisions apply?

For LOKE in particular, the currently published UK merchant agreement refers to Platform Setup Fees, Platform Use Fees, possible customisation charges, transaction fees and paid Transition Services, with the actual amounts governed by the Term Sheet or Order Form. LOKE +1 For Çentik, confirm the canonical UK subscription price because its current English public pages are inconsistent even though the 30-day trial and core feature set are clear. Çentik +1

How to decide between Çentik and LOKE

Start with the customer journey you actually need. If the goal is to add a low-friction loyalty layer to an existing counter setup, with a dedicated NFC touchpoint, QR fallback, browser access and Wallet passes, Çentik is the more directly aligned product based on the public features reviewed. If the project is meant to unify loyalty with ordering, payment terminals, collection, delivery, branded apps and transaction-driven personalisation, LOKE's broader architecture is more directly aligned. The practical decision should then be made on live workflow testing, integration fit, total commercial cost, data portability and the complexity your team is prepared to operate.