Online Order into POS Systems
The Infrastructure Layerfor POS Systems.
One standardised REST API connects supported POS systems, ordering platforms and restaurant technology.
- Integration directory
- 75+ integrations
- Operating options
- API, Controller or combined
Integration layer
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.
Integration Explorer
Find the systems you need.
Search 75+ integrations by name or category. Each profile shows the available details for that system.
- POS
- 40+
- Ordering platforms
- 30+
- Delivery services
- 3
Choose your path
What do you want to connect?
Choose the right starting point for your POS product, ordering platform or restaurant technology.
Connect ordering platforms to your POS.
See which ordering and delivery integrations are listed and what data your POS needs to exchange.
Connect your platform to POS systems.
See which POS systems are listed and what product, menu, order and status data your platform needs.
Connect restaurant software with POS and ordering platforms.
Explore systems and data flows for logistics, analytics, kiosk and back-office products.
From real operations
Connected orders. A shared operational flow.
See how connected ordering and POS workflows support an established delivery operation.
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. |
Reliable infrastructure
Reliable in day-to-day operations.
Clear commitments for reliable operations, from availability and data protection to planned technical changes.
- 99.95%Uptime SLA
- EUInfrastructure
- GDPRData protection
- 90 daysBreaking-change notice
- CertifiedProvider integrations
Resources
Find the right place to continue.
Search integrations, read the documentation, get help or open the Controller.
Insights
Decisions behind better integrations.
Practical notes for product, engineering and operations teams working across restaurant systems.
View all insightsIntegration strategy
MERGEPORT API, Controller or both: choosing the operating model
A practical guide to deciding whether your integration needs a direct backend connection, an operational frontend or a combination of both.Integration strategy
One integration layer instead of repeated point-to-point connectors
Why a shared integration layer can make restaurant technology easier to extend, operate and maintain as the number of connected systems grows.Implementation
What to define before connecting restaurant technology systems
A focused planning checklist for teams connecting a POS system, ordering platform or restaurant-technology product through MERGEPORT.
Built in Vienna
The connection between restaurant systems.
Mergeport is developed by Loomitech GmbH in Vienna and connects supported POS, ordering platforms and restaurant software.
More about MERGEPORT