Set up foodora: activation, tablet handling and item synchronization

For foodora, the restaurant assignment in MERGEPORT must match foodora's enablement of the POS connection. Saving a restaurant ID alone does not activate order transmission.

Prepare the connection

Have the customer number, restaurant ID or Remote Code that foodora has confirmed for POS integration. Use the value foodora specifies for this connection; do not assume a universal ID length.

The foodora store and MERGEPORT-to-POS connection must be set up. Agree with your POS partner whether the foodora tablet will remain in use, whether the restaurant delivers orders itself and how items will be matched or menus maintained.

Configure and request activation

1. Open the restaurant in the MERGEPORT Controller and go to Configuration. Use + under Linked platforms to add foodora.
2. Enter the confirmed values in Restaurant IDs and check the Chain Code for the restaurant's country.
3. Choose the intended workflow using Without tablet. For an appropriate direct workflow, also enable Vendor Delivery if the restaurant delivers orders itself.
4. If MERGEPORT should coordinate activation, enable Let MERGEPORT handle the activation or Automated activation request and save. The default is off. If activation has already been arranged, coordinate the remaining steps rather than submitting an unnecessary new request.
5. Alternatively, the restaurant or POS partner can contact foodora Support to request the MERGEPORT POS connection. Include the country, restaurant name, restaurant ID, Chain Code and intended order workflow. Manual requests can also be sent to pos-support@deliveryhero.com.
6. Wait for activation confirmation, then check an order all the way through to the POS. foodora confirms the processing time and activation date; saving a request is not confirmation of enablement.

Chain Code for Austria and Norway

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

Without an entered Chain Code, the activation request uses the Austrian value. Always enter MergePort-NO for Norway. For other countries, confirm enablement and the correct Chain Code with foodora or Delivery Hero first. Being able to enter another value does not establish availability in that country.

Configuration settings

These defaults apply to new configurations. Some fields appear under Additional functions; existing connections can have other saved values.

Setting	Meaning
Restaurant IDs (restaurantIds)	The foodora-confirmed restaurant assignment for the POS connection.
Chain Code (chainCode)	Default: empty; the activation request then uses the Austrian value. For restaurants outside Austria, enter the confirmed country-specific code.
Automated activation request (autoActivation)	Default: off. Requests coordination of platform enablement. Turning it on later also requests activation; it does not confirm completed activation.
Without tablet (directIntegration)	Default: off. When enabled, orders should go directly to the POS; foodora must also configure the corresponding workflow.
Vendor Delivery (vendorDelivery)	Default: off; shown only with Without tablet enabled. Identifies the agreed own-delivery workflow and affects status forwarding. It does not book a courier.
Item Synchronization (catalogSync)	Default: off. Prepares POS-led menu synchronization. Independent of Without tablet; compatible POS support, synchronization channels and enablement are also required.
Item mapping via MERGEPORT (mapping)	Default: Disabled. The definition also offers api, controller and tool. Use the method agreed with the POS partner; use tool only for an explicitly supported tool-based workflow.
Access status (status)	Read-only authorization verification: pending or verified. Not the restaurant's opening status.
Dev mode (inDevelopment)	Default: off; administrators and coordinated testing only.

Direct routing or tablet acceptance?

With Without tablet disabled, acceptance on the foodora tablet or app remains part of the workflow before orders reach the POS. Check for orders awaiting acceptance there if the POS has not received them yet.

With direct integration, the POS handles the agreed workflow. Ensure orders are processed promptly and the required acknowledgements are sent. Only remove the foodora tablet from normal operation after coordinated activation and a successful test order. Tablet mode in the MERGEPORT Controller is a separate acceptance step.

Item mapping and menu synchronization

Without POS-led menu uploads, item matching can use foodora-side IDs, an agreed item/PLU handoff or MERGEPORT mapping. First confirm which method the POS supports. In the foodora Vendor Portal, the relevant item field is Item SKU Number; it may only become available after POS integration is activated.

With Item Synchronization enabled, the POS supplies the synchronized menu data. A full upload can overwrite the existing foodora menu. Review categories, items, prices, modifiers and text before the first upload, then check the published result. Enabling the switch alone is not a successful menu upload.

Verify the first order

Check receipt in both the Controller and POS, item mapping, modifiers, quantities, prices, payments and the intended acceptance step. For own delivery, also check the agreed delivery workflow. Access verified does not replace this test.

foodora handles platform enablement and routing changes. Your POS partner checks POS processing. For the MERGEPORT connection, contact support@mergeport.com.