Set up Uber Eats: select the store and configure order acceptance

For Uber Eats, authorization must be followed by selection of the correct store. Before activation, also decide whether orders need acceptance on the Uber tablet or Restaurant Dashboard and where menus will be maintained.

Before you start

Have an established Uber Eats store, the operator account with the required permissions and a working MERGEPORT connection to your POS. Agree with your POS partner which item IDs or mappings the POS requires.

Authorize and select the store

1. Open the restaurant in the MERGEPORT Controller and go to Configuration. Use + under Linked platforms to add Uber Eats.
2. Complete and save the setup. Select Authorize, sign in with the operator account and grant the required permissions. Alternatively, share the authorization link prepared for this connection with the operator.
3. During authorization, MERGEPORT may already select a store automatically and activate its POS integration with Uber. Reopen the connection immediately afterward and check the store name and assignment under Restaurant IDs, especially for accounts with several restaurants. Select and save the correct store if needed. If another store was activated, resolve the assignment with MERGEPORT before continuing.
4. If No shops available appears or the correct store is missing, check the operator account and permissions. Do not enter an invented ID or placeholder. Resolve missing stores with Uber or MERGEPORT.
5. Coordinate outstanding POS-integration and order-delivery permissions with the integration partner. Authorization and store selection alone do not verify the complete order workflow.
6. Verify the first order all the way through to POS processing.

Configuration settings

Defaults apply to new configurations. Existing saved values remain authoritative. Some options appear under Additional functions.

Setting	Meaning
Authorize (authUrl)	Opens Uber account authorization. Use the link generated for this connection.
Restaurant IDs (restaurantIds)	Store selector for this connection. No store is selected before authorization; during authorization, MERGEPORT may already select and activate a store automatically. Check the assignment afterward.
Manual acceptance (manualAccept)	Default: off. When enabled, staff must first accept orders on the Uber tablet or Restaurant Dashboard before they continue to the POS.
Item Synchronization (menuApi)	Default: off. Enables POS-led menu transmission; compatible POS support, synchronization channels and platform configuration are also required.
Special instructions (allowSpecialInstructions)	Default: off. Controls permission for customer special instructions in Uber's integration configuration. With menu synchronization, it also controls corresponding menu options during a full upload.
Item mapping via MERGEPORT (mapping)	Default: Disabled. Other offered methods are Via POS or Via Controller. Agree the appropriate method with your POS partner.
Access status (status)	Read-only authorization verification: pending or verified. It does not confirm that the store is open or an order has been processed by the POS.
Dev mode (inDevelopment)	Default: off; administrators and coordinated testing only. Not a setting for normal operation.

Manual acceptance and tablet-free operation

With Manual acceptance enabled, acceptance on the Uber tablet or Restaurant Dashboard remains part of the workflow. Check this step when the POS has not received an order yet.

For direct POS handling, leave the option off and coordinate Uber's corresponding configuration. The additional Uber-side RD-optional setting can be relevant when operating without a continuously active tablet. Obtain confirmation and test the intended workflow before removing the tablet from normal operation. Tablet mode in the MERGEPORT Controller is independent.

Menu synchronization and Menu Maker

Before the first upload, decide whether the POS will supply menus or you will maintain them at Uber. With synchronization enabled, the POS supplies the synchronized menu data; full uploads can overwrite the existing menu.

Uber can disable Menu Maker editing after POS integration is activated. If you still need it, coordinate re-enablement with Uber or MERGEPORT. A request is not confirmation that access has been restored. Even with Menu Maker available again, subsequent POS uploads can overwrite manual changes.

What does “Special instructions” do?

allowSpecialInstructions controls a capability at Uber; it does not remove instructions from orders already received. When menus are synchronized, an existing menu needs a successful full menu upload to update the corresponding menu options. Price-only or availability-only changes are insufficient.

If the Controller reports that settings were saved but the provider did not confirm the change, the external update has not been verified. Have the failure investigated; saving unchanged settings is not a guaranteed retry.

First order and additional stores

Check items, modifiers, quantities, payments, special instructions and the agreed acceptance workflow. Review the order in both the Controller and the POS. If menu synchronization is enabled, also check the published menu.

Configure additional stores or brands as separate Uber Eats connections. Authorize, select and test each one separately. The same Uber store ID cannot belong to two connections at the same MERGEPORT site.

Uber handles account permissions, store enablement and Menu Maker. Your POS partner checks POS processing. For the MERGEPORT connection, contact support@mergeport.com.