Set up Wolt: authorization, tablet and menu synchronization

Wolt orders can go directly to the POS or first require handling on the Wolt tablet. Agree the intended workflow with your POS partner before linking the account.

Before you start

Have an established Wolt store, access to the operator's Wolt account and a working MERGEPORT connection to your POS. Also agree how platform items will be matched to POS items and where menus will be maintained.

Connect the account

1. Select the restaurant in the MERGEPORT Controller and open Configuration. Use + under Linked platforms to add Wolt.
2. Decide whether staff will accept orders on the Wolt tablet or handle them directly in the POS. Review Auto Accept/iPad-Free accordingly.
3. Complete and save the setup. Select Authorize, sign in with the operator's Wolt account and grant the required permissions. You can also share the Controller-generated link with the operator. Use the link for the correct connection.
4. After returning, check the restaurant assignment. The login flow supplies the restaurant IDs. Successful authorization does not replace checks of Wolt-side enablement and order routing.
5. Coordinate outstanding routing or menu permissions with Wolt and your POS partner. Obtain their confirmation before relying on the new workflow.
6. Verify a first order all the way through to POS processing.

Configuration settings

These defaults apply to new configurations. Existing connections can have different saved values. Some fields appear under Additional functions or only when the relevant parent setting is enabled.

Setting	Meaning
Authorize (authUrl)	Opens Wolt account authorization. Use the link prepared by the Controller; a generic link or one from another connection may target the wrong connection.
Restaurant IDs (restaurantIds)	Identifies the Wolt restaurant. The standard login flow supplies the assignment; an existing API-key connection needs the correct IDs entered.
Auto Accept/iPad-Free (iPadFree)	Default: on. Requests direct POS handling. Wolt's configuration must match the intended workflow.
Item Synchronization (menuApi)	Default: off. Prepares POS-led menu transmission; a compatible POS, synchronization channels and Wolt permissions are also required.
Item mapping via MERGEPORT (mapping)	Default: Disabled. Other offered methods are Via POS and Via Controller. Choose the method agreed with your POS partner.
Authentication with API KEY (Deprecated) (legacyAuth)	Default: off. For existing connections explicitly set up this way; use account authorization for a new connection.
API Key (apiKey)	Belongs to the legacy authentication method and is needed only when legacyAuth is enabled. Coordinate changes to a working legacy connection.
API Username / API Password (apiUser, apiPass)	Shown for the legacy menu-API method only when both Item Synchronization and legacyAuth are enabled. Operator-account authorization does not require these manual entries.
Access status (status)	Read-only authorization verification: pending or verified. It does not control whether the store is open.
Dev mode (inDevelopment)	Default: off; administrators only. Used for coordinated testing, not normal restaurant operation.

Keep the tablet or handle orders directly?

With Auto Accept/iPad-Free enabled, the POS must handle the agreed order workflow. To keep accepting orders on the Wolt tablet, disable this option and arrange matching Wolt-side iPadLess/Auto Accept settings.

Saving a change in the Controller does not confirm that Wolt has completed the corresponding change. Remove the tablet only after a successful test and agreement on a fallback process. Tablet mode in the MERGEPORT Controller is another, separate acceptance step.

Keep the existing menu or synchronize from the POS?

When Item Synchronization is off, this option does not initiate menu uploads. Item mapping may still be necessary. When synchronization is enabled, the POS supplies the synchronized menu data. A full upload overwrites the existing Wolt menu. Check categories, prices, modifiers and customer-facing text before uploading, then review the published result.

Verify access and the first order

Access verified confirms access, not that the store is open or every order reaches the POS. For Verification pending, first check that authorization was completed and the correct restaurant is assigned. Outstanding access checks are normally retried after about an hour; this is not an activation-time commitment.

For the first order, check items, modifiers, quantities, payments and POS acknowledgement. For multiple stores or brands, configure and test each additional Wolt connection separately. The same Wolt restaurant ID cannot belong to two connections at the same MERGEPORT site.

Contact Wolt for outstanding platform permissions, your POS partner for POS processing, or support@mergeport.com for the MERGEPORT connection.