Integrations

This section contains technical setup guides for each integration, including configuration details, sync settings, and troubleshooting.

Looking for guided setup? See the Onboarding Flows for step-by-step Emily-guided setup.

---

POS/In-House Channel Integrations

Integration	Scope	Payment Provider	Onboarding Guide
Square	Merchant-scoped	Square Payments (included)	Square Onboarding
MplusKassa	Merchant-scoped	Requires Stripe/Viva Wallet	MplusKassa Onboarding
Lightspeed K-Series	Merchant-scoped	Requires Stripe/Viva Wallet	Lightspeed Onboarding
Hendrickx	Location-specific	Requires Stripe/Viva Wallet	Hendrickx Onboarding
Shopcaisse	Location-specific	Requires Stripe/Viva Wallet	Shopcaisse Onboarding
Vanhoutte	Location-specific	Requires Stripe/Viva Wallet	Vanhoutte Onboarding
Kassanet	Location-specific	Requires Stripe/Viva Wallet	—

Delivery Platform Integrations

Integration	Type	Payment	Setup Complexity
Deliveroo	Delivery	Handled by Deliveroo	Low
Uber Eats	Delivery	Handled by Uber Eats	Low

E-Commerce Integrations

Integration	Type	Payment	Setup Complexity
Shopify	E-commerce	Handled by Shopify	Medium

Hardware Integrations

There is no third-party hardware integration. Network receipt printers are managed as printer devices under Device Management: the device is born activated with its own device token and polls Upvendo over Epson Server Direct Print (POST /api/print/epson/sdp). The URL + token is revealed only through the permission-gated pairing-session flow, and no back-office or POS screen consumes it yet, so there is no screen an operator can copy it from — see Printers.

---

Integration Scopes

Merchant-Scoped Integrations

• Connects entire merchant account at once
• Locations are imported automatically from the POS system
• After import, complete missing location fields (address, coordinates, etc.)
• Examples: Square, MplusKassa, Lightspeed K-Series

Location-Specific Integrations

• Each location must be connected separately
• Locations must be created manually before connecting
• Select location from topbar before connecting integration
• Examples: Hendrickx, Shopcaisse, Vanhoutte

Delivery Platform Integrations

• Receives orders from delivery platform
• Payment handled by the platform
• No payment profile required
• Examples: Deliveroo, Uber Eats

---

Prerequisites

Before setting up any POS integration, complete these in order:

Task	Route	Required For
Payment Profile	/settings/payments	All except Square
Billing Profile	/settings/billing	All integrations
Branding Profile	/settings/brand	All integrations

Note: Square handles its own payment processing, so Payment Profile is skipped.

---

Quick Reference

Which payment provider do I need?

Integration	Payment Provider	Notes
Square	Square Payments (included)	No separate setup needed
MplusKassa	Stripe or Viva Wallet	Stripe recommended for iDEAL
Lightspeed K-Series	Stripe or Viva Wallet	OAuth connection required
Hendrickx	Stripe or Viva Wallet
Vanhoutte	Stripe or Viva Wallet	One of the three in-house channels, alongside Hendrickx and Shopcaisse
Shopcaisse	Stripe or Viva Wallet
Deliveroo	None	Handled by Deliveroo
Uber Eats	None	Handled by Uber Eats
Shopify	None	Handled by Shopify
Kassanet	Stripe or Viva Wallet	Underlying protocol for Hendrickx/Vanhoutte

Where do I connect each integration?

Integration	Route
Square	/square
MplusKassa	/mpluskassa
Lightspeed K-Series	/lightspeed
Hendrickx	/hendrickx
Vanhoutte	/vanhoutte
Shopcaisse	/shopcaisse
Deliveroo	/deliveroo
Uber Eats	/uber-eats
Shopify	/shopify

The back-office uses file-based routing from src/pages/**, so each integration is a top-level route named after the provider. /in-house/settings is the In-House ordering settings page (tips, table sections, menus, order capacity) — it is not the connect page for any POS provider. There is no /pickup-and-delivery route anywhere in the app.

Deliveroo, Uber Eats and Shopify tiles appear in the Add Channel dialog when the backend's online-channels response marks them applicable (GET /api/back-office/online-channels/{locationId} → OrderingChannelService::onlineChannels()). There is no build-environment gate. uber_eats and shopify are always applicable; deliveroo is dropped for US merchants and when services.deliveroo.enabled is false. A tile that is applicable but not yet usable renders disabled with a reason — pos_integration_required when the merchant has no active POS integration, location_required when no location is selected — and a channel already connected for that location is filtered out of the list entirely.