Activate a MERGEPORT integration

With the right preparation, connecting your POS system and delivery platforms will be quick and seamless.

Prerequisites for a Fast Setup

Before starting the setup process, please prepare the following details:

1. Check POS compatibility: Make sure your POS system is compatible with MERGEPORT. You can find an overview at mergeport.com/en/integrations.
2. Prepare credentials:
   • Lieferando / JET Connect: Restaurant reference, country and storefront URL
   • Wolt: Merchant account login credentials
   • Uber Eats: Merchant account login credentials
   • Foodora: Restaurant's customer number
3. Prepare item IDs: Items in the POS should include POS IDs (PLU codes or article numbers). These are required for correct item mapping later on.
4. Request approvals early: Since some platforms require activation by their support team, these requests should be submitted as early as possible.
5. Align tablet workflow: Decide whether you want to keep the platform ordering tablets active (e.g., in Hybrid Mode).

Agree menu management before activation

Menu synchronization is supported for Lieferando through JET Connect, Wolt, Uber Eats and foodora when the POS connection, configuration and platform enablement are in place. Choose the appropriate workflow with your POS partner:

• Synchronize the POS menu: Send products and menus through MERGEPORT. Prepare complete customer-facing menu data and check the supported fields for each channel. An upload can overwrite the existing menu.
• Maintain platform menus separately: Agree operation without menu synchronization and use matching POS identifiers/PLUs or supported mapping in the POS. JET Connect requires platform enablement for this mode; active Uber Eats menu synchronization can disable Menu Maker.
• Map in the MERGEPORT Controller: Link platform products to POS items manually or with the experimental Auto Mapper. Review the results; mapping and menu publication are separate operations.

The related articles on menu management, menu requirements and item mapping explain how to choose and configure the workflow.

The 4 Key Setup Steps

Add restaurant in MERGEPORT

Go to controller.mergeport.com and click “Add Restaurant” on the homepage. ➤ Enter the restaurant name and save. 🔐 This will automatically generate access credentials and create an API Key for the restaurant.

Open full-size image

Activate the POS System

Insert the generated API Key into the POS system or apply any additional POS-specific configuration if needed.

Configure Ordering Platforms

In the “Configuration” section, you will find the API Key for the POS connection and the overview of connected ordering platforms.

Initially, the platform list is empty. Click “+” to add platforms and follow the displayed setup steps.

Activate Ordering Platforms

Once your restaurant has been created in the MERGEPORT Controller and the basic setup is complete (customer numbers entered, POS connection active), the integration must be activated on each platform to start receiving orders.

Each platform follows its own activation process. Some work automatically via login, while others require confirmation by the platform’s support team.

Overview of Activation Methods per Platform

Platform	Activation Type	Duration	Tablet Use
Wolt	Account linking via login; verify Wolt-side approval and order routing	Account link immediate; order transmission depends on approval and configuration	Depends on the agreed order workflow
Uber Eats	Account linking via login and permission approval	Account linked after approval; verify the complete order path	Optional
Lieferando / JET Connect	Enablement coordinated with JET and the integration partner	Agreed activation window and test order	Direct or Orderpad-first flow; keep backup available
Foodora	Manual or Automated (via Support or Auto Request)	Manual: Minutes / Automated: 1–3 business days	Optional

Platform Activation Steps

Lieferando / JET Connect

Use JET Connect for new Lieferando connections. JET Connect is intended to replace the previous integration as the standard; existing restaurants migrate in coordination with JET and the integration partner.

• Have the restaurant reference, country and storefront URL ready and have the JET Connect connection configured.
• Agree the activation window, Orderpad acceptance or direct routing, and menu management with JET and the integration partner.
• Wait for JET's enablement confirmation and verify a test order through to acceptance in the POS.
• The earlier Lieferando login or keep-alive signal is not required for JET Connect. Saving alone does not activate the connection.

See the related article “Set up Lieferando through JET Connect” for the complete guide.

Existing connections only, until migration

Previous activation guidance applies only to restaurants that are still connected through the older Lieferando POS API. An existing automated activation request for that connection does not establish JET Connect enablement. Plan migration with Lieferando and the integration partner; do not treat previous activation times as a commitment for JET Connect.

Wolt

• Set up the Wolt shop and make sure it is online. Before linking, check whether your POS can process unknown items. If it cannot, the platform item IDs must match the POS item IDs.
• Log in using the operator’s Wolt account.
• Either click “Authorize” in the MERGEPORT Controller or copy the login link and share it with the restaurant.
• After successful login, the Wolt account is linked. Also verify that Wolt has approved the POS integration and that tablet and routing settings match in both systems. A successful login alone does not confirm order transmission.

Uber Eats

• Set up the Uber Eats shop and make sure it is online. Before linking, check whether your POS can process unknown items. If it cannot, the platform item IDs must match the POS item IDs.
• Log in using the operator’s Uber Eats account.
• Either click “Authorize” in the MERGEPORT Controller or copy the login link and share it with the restaurant.
• Grant the required permissions and confirm the correct shop assignment. Then use a test order to verify that the order actually reaches the POS.

Foodora

• Ask Foodora Support for the Remote Code or restaurant ID used for the POS connection and to enable the MERGEPORT interface.
• Set up the Foodora shop and make sure it is online. Before linking, check whether your POS can process unknown items. If it cannot, the platform item IDs must match the POS item IDs.
• Enter the restaurant’s Foodora customer number in the MERGEPORT Controller and check the Chain Code for the restaurant’s country.
• Activation of the POS API can also be done in two ways:
  • Manual activation: The restaurant or POS partner contacts Foodora Support by phone or email and requests activation of the POS integration for MERGEPORT. Activation is usually completed within minutes.
  • Automated activation: When adding Foodora in the MERGEPORT Controller, select the checkbox “Automated activation request.” MERGEPORT sends the request directly to Foodora. Activation typically takes 1–3 business days.

Austria and Norway: Chain Code

Country	Chain Code
Austria	MergePort-AT-2
Norway	MergePort-NO

For Norway, explicitly enter MergePort-NO in the “Chain Code” field when adding Foodora. This value routes the automated activation request to the responsible Norwegian contact.

If no Chain Code is provided, MergePort-AT-2 is used. Do not leave the field empty for Norwegian restaurants. For other countries, first arrange country enablement and confirm the appropriate Chain Code with Delivery Hero.

Manual activation request

Alternatively, request activation at pos-support@deliveryhero.com. Include the country, restaurant name, Foodora customer number, and Chain Code. You can adapt this example request:

Subject: Foodora POS activation via MERGEPORT – [restaurant name], Norway

Hello,
Please activate the Foodora POS integration via MERGEPORT for:
Restaurant: [restaurant name]
Country: Norway
Foodora restaurant/customer ID: [restaurant ID]
Chain Code: MergePort-NO

Please confirm the activation date and the agreed tablet workflow.
Thank you.

Tablet and menu synchronization

Tablet behavior and menu synchronization are identical in Austria and Norway. In the indirect order flow, an order is accepted on the Foodora tablet or app before it is forwarded to the POS. In the direct order flow, the tablet is not required.

With Item Synchronisation enabled, the POS is the source of truth for the menu. A full menu upload can overwrite the existing Foodora menu, so review the first upload before using it in production.

What does the access status mean?

Open your restaurant in the Controller and select Configuration. Check the affected platform there.

Display	Meaning and next step
Confirmation pending	Access has not yet been verified successfully. Check that login is complete and the correct shop is assigned. Verification of a new connection may take some time.
Access verified	Access to the configured connection was successfully checked. Also place a test order to verify the complete path to the POS.
Authorization status unknown	The reported status is not recognized. Check login and shop assignment; contact support if the display remains unchanged.

“Access not confirmed” describes a missing confirmation. The current status label is Confirmation pending. Older connections may still display Online or Offline instead.

For Wolt, Uber Eats and Foodora, MERGEPORT checks access through the platform. Pending checks are normally retried after about one hour; this does not guarantee activation within an hour. For JET Connect, access is confirmed through an authenticated order notification.

Access status does not continuously monitor incoming orders. Pending confirmation alone does not prove a fault, and verified access does not prove that every order reaches the POS. Do not remove a working platform solely because of this display.

After Activation

Check the access status as described above. The following image shows the older Online display; the current access check uses Confirmation pending or Access verified.

Open full-size image

To verify functionality:

• Create a test order on the platform (if possible).
• Check whether the order appears under Orders in the Controller.
• Verify that the POS receives and processes it correctly.

Open full-size image

If the status remains “Offline”, check the platform-specific activation process and credentials. Re-login applies only to connections with a login process; for JET Connect, check enablement and actual order receipt.

Operational Settings

• Tablet usage: Agree with the platform whether the tablet is required for acceptance or backup.
• For Foodora, this can be configured via the toggle in the integration settings in MERGEPORT.
• For Lieferando / JET Connect, Orderpad use follows the agreed direct or Orderpad-first flow. Keep the agreed backup process available.
• Ensure configurations in both systems (MERGEPORT and the platform) match.

Troubleshooting and further resources

If orders still do not appear or activation seems incomplete, use the related articles for Wolt and missing orders.

For assistance, contact: support@mergeport.com