Appearance
POS Integration Comparison Guide
Overview
Upvendo integrates with several POS systems, each with different capabilities, scopes, and trade-offs. This guide compares them to help merchants and support staff understand which integration fits each situation.
At a Glance
| Feature | Square | Lightspeed K-Series | MplusKassa | Kassanet (Hendrickx/Vanhoutte) | Shopcaisse |
|---|---|---|---|---|---|
| Scope | Merchant | Merchant | Merchant | Location | Location |
| Region | US, UK, EU | Global (hospitality) | Netherlands | Belgium | Belgium |
| Payment Handling | Included (Square Payments) | Separate (Stripe/Viva) | Separate (Stripe/Viva) | Separate (Stripe/Viva) | Separate (Stripe/Viva) |
| Auth Method | OAuth 2.0 | OAuth 2.0 + PKCE | API credentials (SOAP) | HMAC + Blowfish encryption | JWT token |
| Menu Import | Yes | Yes | Yes | Yes | Yes |
| Menu Export | Yes (bidirectional) | Read-only from Lightspeed | Yes (bidirectional) | No (import only) | No (import only) |
| Order Push | Yes | Yes | Yes | Yes | Yes |
| Inventory Sync | Yes | Yes | Yes | No | No |
| Table/Floor Plan | No | Yes | Yes | Yes | No |
| Webhook Support | Yes | Yes | Yes | No | No |
| Setup Complexity | Low | Medium | Medium | Medium | Low |
| Production Status | Stable | Stable | Stable | Stable | Beta |
Detailed Comparison
Integration Scope
Merchant-Scoped (Square, Lightspeed, MplusKassa)
- One connection covers all locations
- Locations are imported automatically from the POS system
- After import, complete missing location fields (address, coordinates, timezone)
- Ideal when the POS is the source of truth for business structure
Connect POS account (merchant level)
|
v
POS branches imported as Upvendo locations
|
v
Menu items synced across all locations
|
v
Orders from any Upvendo channel pushed to correct POS locationLocation-Specific (Kassanet/Hendrickx/Vanhoutte, Shopcaisse)
- Each location must be connected separately
- Locations must be created manually in Upvendo first
- Select the target location from the topbar before connecting
- Ideal when different locations use different POS systems or configurations
Create location manually in Upvendo
|
v
Select location from topbar
|
v
Navigate to In-House > Settings
|
v
Enter POS credentials for that location
|
v
Menu imported for that location onlyPayment Handling
| Integration | Payment Provider | What This Means |
|---|---|---|
| Square | Square Payments (included) | No separate payment setup needed. Square handles online + terminal payments. Replaces Stripe and Viva Wallet. |
| Lightspeed | Requires Stripe and/or Viva Wallet | Must set up Stripe (online) and/or Viva Wallet (terminal) independently. Lightspeed handles POS-side payments only. |
| MplusKassa | Requires Stripe and/or Viva Wallet | Same as Lightspeed. MplusKassa can relay external payment events via webhooks. |
| Kassanet | Requires Stripe and/or Viva Wallet | POS handles in-store payments. Upvendo channels need their own payment provider. |
| Shopcaisse | Requires Stripe and/or Viva Wallet | Orders pushed to POS only after payment confirmed in Upvendo. |
Key Insight: Only Square bundles payment processing. All other integrations require a separate payment provider (Stripe for online, Viva Wallet for terminals).
Sync Direction and Data Flow
Square
Square POS <=======> Upvendo
bidirectional
- Menu items: bidirectional sync
- Orders: Upvendo -> Square (and Square -> Upvendo for POS orders)
- Inventory: bidirectional
- Payments: all through SquareLightspeed K-Series
Lightspeed POS ------> Upvendo (menu, floor plans)
Upvendo ------> Lightspeed POS (orders)
- Menu items: Lightspeed -> Upvendo (read-only)
- Orders: Upvendo -> Lightspeed
- Inventory: Lightspeed -> Upvendo
- Floor plans: Lightspeed -> UpvendoMplusKassa
MplusKassa <=======> Upvendo
bidirectional
- Menu items: bidirectional (products, categories, modifiers, images)
- Orders: Upvendo -> MplusKassa
- Inventory: MplusKassa -> Upvendo
- Tables: MplusKassa -> Upvendo
- External payments: MplusKassa -> Upvendo (via webhooks)Kassanet (Hendrickx / Vanhoutte)
Kassanet POS ------> Upvendo (menu import)
Upvendo ------> Kassanet POS (orders)
- Menu items: Kassanet -> Upvendo (import only)
- Orders: Upvendo -> Kassanet (Blowfish-encrypted JSON)
- Table sections: linked between systems
- Display groups: auto-created from POS menu structureShopcaisse
Shopcaisse POS ------> Upvendo (menu import)
Upvendo ------> Shopcaisse POS (orders, after payment)
- Menu items: Shopcaisse -> Upvendo (import only)
- Orders: Upvendo -> Shopcaisse (after payment confirmed)
- No real-time sync or webhooksMenu Import Capabilities
| Capability | Square | Lightspeed | MplusKassa | Kassanet | Shopcaisse |
|---|---|---|---|---|---|
| Categories | Yes | Yes | Yes | Yes | Yes |
| Items | Yes | Yes | Yes | Yes | Yes |
| Modifiers | Yes | Yes | Yes | Yes | Limited |
| Images | Yes | Yes | Yes | No | No |
| Prices | Yes | Yes | Yes | Yes | Yes |
| Variants | Yes | Yes | Yes | No | No |
| Display Groups | No | No | Yes | Yes (auto-created) | No |
| Tax Rates | Yes | Yes | Yes | No | No |
| Allergens | No | No | No | No | No |
Features by Integration
| Feature | Square | Lightspeed | MplusKassa | Kassanet | Shopcaisse |
|---|---|---|---|---|---|
| Kiosk Ordering | Yes | Yes | Yes | Yes | Yes |
| Online Ordering | Yes | Yes | Yes | Yes | Yes |
| QR Table Ordering | Yes | Yes | Yes | Yes (with table linking) | No |
| KDS Support | Yes | Yes | Yes | Via POS | Via POS |
| Receipt Printing | Yes | Yes | Yes | Via POS | Via POS |
| Scheduled Orders | Yes | Yes | Yes | Yes | Yes |
| Delivery | Yes | Yes | Yes | No | No |
| Loyalty Integration | No | No | No | No | No |
Decision Guide
Choose Square If
- You want the simplest setup with payments included
- You are already using or plan to use Square POS
- You need a single provider for menu, orders, and payments
- You are in the US, UK, or supported EU countries
Choose Lightspeed K-Series If
- You use Lightspeed Restaurant as your primary POS
- You need floor plan / table management imported from the POS
- You want Upvendo as a customer-facing ordering layer on top of Lightspeed
- You operate in the hospitality industry with multiple locations
Choose MplusKassa If
- You are in the Netherlands
- You use MplusKassa as your POS system
- You need bidirectional menu sync with the POS
- You need external payment event handling (e.g., MplusKassa PIN terminal events)
Choose Kassanet (Hendrickx/Vanhoutte) If
- You are in Belgium
- You use a Hendrickx or Vanhoutte POS system
- You need table section linking for QR ordering
- You want to import your POS menu into Upvendo for kiosk/online ordering
Choose Shopcaisse If
- You are in Belgium
- You use Shopcaisse as your POS
- You need basic menu import and order forwarding
- Note: this integration is in beta and has limited features compared to others
Common Setup Patterns
Pattern 1: POS Integration + Online Ordering
POS (any) + Stripe (for online payments)
|
v
Menu imported from POS -> displayed on Online Ordering
|
v
Customer orders online, pays via Stripe
|
v
Order pushed to POS for kitchen fulfillmentPattern 2: POS Integration + Kiosk
POS (any except Square) + Viva Wallet (for kiosk terminal)
|
v
Menu imported from POS -> displayed on Kiosk
|
v
Customer orders on kiosk, pays via Viva Wallet terminal
|
v
Order pushed to POS for kitchen fulfillmentPattern 3: Square All-in-One
Square (handles everything)
|
v
Menu synced from Square -> all Upvendo channels
|
v
Payments via Square (online + terminal)
|
v
Orders synced back to Square POSMigration Considerations
Switching POS Integrations
- Disconnect the current integration before connecting a new one
- Menu items from the old integration remain in Upvendo
- You may need to re-map or clean up duplicate items
- Order history is preserved regardless of integration changes
Adding Square to an Existing Setup
- Square replaces Stripe and Viva Wallet for payments
- Existing Stripe/Viva Wallet configurations become inactive
- If you disconnect Square later, you must re-enable Stripe/Viva Wallet manually
Multiple Locations with Different POS Systems
- Merchant-scoped integrations apply to all locations
- Location-specific integrations can be mixed (e.g., Location A uses Hendrickx, Location B uses Vanhoutte)
- You cannot have two merchant-scoped POS integrations active simultaneously