Setup guide
Set up Lieferando through JET Connect
Set up Lieferando through JET Connect: order acceptance, Orderpad handling, menu synchronization and verification of the first order.
- Topic
- Integrations
- Last reviewed
Use JET Connect for new Lieferando connections through MERGEPORT. JET Connect is intended to replace the previous interface as the standard; existing restaurants migrate after coordination. Order receipt, acceptance and menu management are configured for your restaurant. Saving new settings alone does not migrate an existing Lieferando connection to JET Connect.
Before activation
Have your restaurant reference, country and exact storefront URL ready. Your POS must already be connected to MERGEPORT. The current JET Connect configuration supports Germany, Austria and the Netherlands; activation is specific to each restaurant.
Before starting, decide how you want to handle orders:
- When to activate the connection and place the first test order.
- Direct POS routing or orders arriving on Orderpad first.
- Automatic or manual customer-facing acceptance.
- Keeping the existing JET menu or synchronizing menus from the POS.
- Item mapping and the workflow during a POS outage.
Controller settings
These defaults apply to new configurations. Existing connections can have different saved values. Some options appear under Additional functions or only when the activation request is enabled.
| Setting | Meaning |
|---|---|
Country (country) | Germany (DE), Austria (AT) or the Netherlands (NL). Select the restaurant's country. Country selection does not replace JET-side enablement. |
Restaurant IDs (restaurantIds) | JET-confirmed restaurant references. Check every ID; one MERGEPORT site can contain several corresponding JET restaurant references. |
Let MERGEPORT handle the activation (autoActivation) | Default: on. Other views call it Activation request or Automated activation request. Requests enablement during setup; turning it on later can also initiate a request. Saving unchanged settings is not confirmation that a new request has been sent. |
Request Lieferando hybrid mode (autoActivationHybrid) | Default: off; available with the activation request enabled. Requests a workflow in which orders are first accepted on Orderpad or in Live Orders. JET must configure the requested workflow. |
Order acceptance (orderAcceptanceMode) | Default: Accept automatically (autoAccept). Alternative: Confirm via POS (posAccept). Controls technical acknowledgement to JET; the distinction is explained below. |
Online Store URL (shopUrl) | Full address of the correct Lieferando/Thuisbezorgd store. Used, among other things, to import existing catalog items for mapping. Importing does not publish a new menu. |
Item Synchronization (menuSync) | Default: off. For POS-led menu transmission; compatible POS support, synchronization channels and JET enablement are also required. A full upload can overwrite the existing storefront menu. |
Item mapping via MERGEPORT (mapping) | Default: Disabled. The definition also offers api, controller and tool. Agree item matching with the POS partner; use tool only for an explicitly supported tool-based workflow. |
Access status (status) | Read-only: pending or verified. Describes authorization verification, not an open store or successful POS processing. |
Dev mode (inDevelopment) | Default: off; administrators and coordinated testing only. Not a substitute for regular JET enablement. |
MERGEPORT manages the central JET credentials; you do not need to enter your own API key. Coordinate changes to country, acknowledgement mode, hybrid handling or menu synchronization on a working connection with your integration partner and JET. Saving a change does not confirm that JET has applied the requested configuration.
Setup and first order
- Open your site configuration in the Controller. Use + under Linked platforms to add JET Connect and select the country. Enter the restaurant reference in Restaurant IDs. Under Additional functions → Online Store URL, reveal the storefront URL field and enter the full address. Click Continue to save the details. MERGEPORT manages the central JET credentials.
- Tell JET whether orders should go directly to the POS or to Orderpad first, and whether you want automatic or manual acceptance. JET configures this on the platform side. When migrating, specify which existing settings you want to keep.
- Check with your POS provider whether the POS automatically acknowledges incoming orders. This acknowledgement is separate from customer-facing acceptance.
- Check item IDs and mappings. Existing Lieferando or Thuisbezorgd catalog items can be imported for mapping using the configured storefront URL. Review the imported items and assignments before activation.
- Wait for JET's activation confirmation and place a test order. Check receipt, items, modifiers, quantities, payments and acknowledgement at the POS.
- If menu synchronization is included, also verify the published menu and item availability in the storefront.

Saving the configuration in the Controller does not activate the connection on the JET side. Check the first order all the way through to the POS.
What does auto-accept mean?
Three separate decisions matter. The Controller label Accept automatically refers to MERGEPORT's technical acknowledgement; it does not determine all three settings.
| Decision | Owner / setting |
|---|---|
| Where are orders handled first? Directly in the POS or first on Orderpad / in Live Orders? | Restaurant workflow agreed with JET; Request hybrid mode communicates the desired Orderpad-first workflow. |
| Are orders automatically accepted towards the customer? | JET or the restaurant configuration. During migration, explicitly agree which existing settings should be preserved. |
| When does MERGEPORT technically acknowledge transmission to JET? | Order acceptance, using autoAccept or posAccept. |
- Accept automatically (
autoAccept, default): MERGEPORT directly acknowledges an order that was successfully received. This acknowledgement does not wait for the POS to accept the order. Continue checking actual POS processing. - Confirm via POS (
posAccept): MERGEPORT initially reports that the order has not been finally acknowledged. Technical success is confirmed only after the POS submitsacceptedByPOSor an expressly configured automatic POS-acceptance step does so. Fetching the order or settingfetchedByPOSis insufficient. If the POS does not support the required workflow, the acceptance deadline can expire.
Both technical modes can be combined with a direct or Orderpad-first workflow agreed with JET. autoAccept therefore does not automatically mean tablet-free operation; posAccept does not automatically mean Orderpad acceptance. With Orderpad-first handling, staff must still accept there before the order continues to the POS according to the agreed workflow.
A technical failure report is not an automatic customer cancellation or refund. Check failed orders using the agreed fallback process and avoid processing an order twice.
Can we keep Orderpad?
Yes. With direct routing it can remain available as backup without staff handling normal orders there. With Orderpad-first or hybrid operation, forwarding follows the agreed acceptance workflow. There is no universal default configuration.
Only remove or disable the device after explicit agreement with JET. Keep the agreed Orderpad or Live Orders backup process available for outages.
Menu synchronization or orders only?
Both are possible:
- Orders only: Keep the existing JET menu. JET must enable this mode; switching off menu synchronization in MERGEPORT alone is insufficient.
- Menu synchronization: The POS supplies the menu through MERGEPORT to JET Connect. Appropriate configuration and enablement are required. Review customer-facing names, categories, prices, modifiers and item IDs before the first upload.
The menu may not appear immediately after uploading. Check the result in the storefront. Importing existing storefront items for mapping does not publish a new menu.
Can delivery times be changed from the POS?
Yes, for orders delivered by the restaurant itself. The POS integration can submit a delivery-time change with an eligible status transition. Check the order's possibleStateChanges: the transition must offer timeChange: true.
Send the expected delivery time at the customer's address as an absolute ISO 8601 timestamp with an explicit timezone. These time changes are not available for collection, JET courier delivery or unknown delivery ownership. A time-only update without a status transition is not offered.
Confirm the JET-side prerequisites with your integration partner and test the workflow during setup. Acknowledgement of a time-change request does not automatically mean that the new time is already displayed to the customer. Incoming cancellations and driver events are processed independently.
What does “Verification pending” mean?
JET Connect access is verified through authenticated incoming order notifications for the configured restaurant references. If several restaurant IDs are configured, Verification pending remains until a corresponding notification has been received for each reference. An activation request alone does not set Access verified. Conversely, Access verified does not establish the current opening status or POS acceptance of an order. Check the first order end to end; do not remove a working connection solely because of this display.
Support
For setup questions or missing orders, contact your integration partner or support@mergeport.com. Changes to JET-side activation and restaurant workflows must be agreed with JET.
Help Center
Related articles
Integration Explorer