Online Order into POS Systems

The Infrastructure Layer for POS Systems.

One standardised REST API connects supported POS systems, ordering platforms and restaurant technology.

Integration directory: 80+ integrations
Operating options: API, Controller or combined

The integration problem

One integration instead of many separate connections.

Every integration with an external ordering source brings its own interface, maintenance work and potential points of failure. Mergeport brings supported product, order and status flows into a single integration.

01Exchange product and menu data.Connect supported product and menu flows between your systems. Available data and direction depend on the integration.
02Bring orders into the POS workflow.Connect supported ordering channels to the configured POS and order workflow.
03Connect order status updates.Exchange the status updates supported by each connection through the same integration layer.

A shared layer structures the connections.Schematic architecture. Available flows depend on the integration.

Integration Explorer

Find the systems you need.

Search 80+ integrations by name or category. Connect ordering platforms to your POS and compare features, activation requirements and item mapping in each profile.

POS: 45+
Ordering platforms: 30+
Delivery services: 4

Search integrations

4 of 83 shown

LieferandoOrdering platforms WoltOrdering platforms Uber EatsOrdering platforms SpeedyPOS

View all integrations

Choose your path

What do you want to connect?

Choose the right starting point for your POS product, ordering platform or restaurant technology.

For POS developers

Connect ordering platforms to your POS.

See which ordering and delivery integrations are listed and what data your POS needs to exchange.

For ordering platforms

Connect your platform to POS systems.

See which POS systems are listed and what product, menu, order and status data your platform needs.

For Restaurant Technology Providers

Connect restaurant software with POS and ordering platforms.

Explore systems and data flows for logistics, analytics, kiosk and back-office products.

Architecture choice

More focus on your product.

Decide where provider-specific integration work lives — in your product or in the shared MERGEPORT integration layer.

Integration work	Direct connectionsIn your product	Shared integration layerWith MERGEPORT
Interfaces	Implement interfaces and authentication separately for each provider.	Use one standardised API pattern for supported data flows.
Provider changes	Handle each provider's changes in your own connectors.	Provider-specific translation stays in the shared layer.
Expansion	Develop additional connections as more providers are added.	Build on the same integration pattern for further supported systems.

Your operating model

Choose how your team operates.

API: Your own interfaceConnect your ordering backend by API and keep your own product interface.
Controller: An operational frontendUse the MERGEPORT Controller for setup and supported workflows.
Combined: Both togetherConnect the ordering backend by API and use the Controller as the operational frontend.

Before implementation, we scope the data flows and operating model for the selected systems.Review technical documentation

Reliable infrastructure