Menu requirements for Wolt, Uber Eats, foodora and JET Connect

To synchronize your POS menu through MERGEPORT, prepare customer-facing products, consistent item mappings and the required platform enablement. Additional requirements can depend on the country and product. This overview covers restaurant menus.

Prepare your menu data

Agree the following with your POS partner:

• Unique identifiers for products, variants and options.

• Clear product names and suitable categories, replacing internal POS abbreviations where needed.

• Selling prices and prices for sizes, extras and options, including free options.

• Descriptions explaining ingredients, portion sizes and differences between variants.

• Modifier groups with appropriate minimum and maximum selections.

• Menu hours, fulfillment types and product availability.

• Accurate allergen and additive information, including variants and extras.

• Product images where used or required for the particular platform setup.

This is a preparation checklist. Technical requirements depend on the enabled menu channel and platform.

Platform differences

Platform	Menu data and considerations
Wolt	The Menu API requires currency, primary language and categories. Products must belong to a category to be visible. MERGEPORT can transfer names, descriptions, prices, images, options and configured allergens and additives.
Uber Eats	The API describes item IDs, names, prices, taxes and menu/category relationships. MERGEPORT also supports images, modifier groups and configured allergens, additives and vegan/vegetarian labels.
foodora	MERGEPORT transfers identifiers, names, descriptions, prices, images, options and menu relationships. The current outbound menu transfer contains no allergen or additive fields. Agree how these are maintained and preserved with foodora and your integration partner.
JET Connect	MERGEPORT can transfer item identifiers as PLUs, names, descriptions, prices, images, modifier groups and configured allergens, additives and vegan/vegetarian labels. Menu synchronization requires the appropriate configuration and JET enablement.

See the Wolt Menu Guide, Wolt Menu API and Uber Eats Menu API for platform structure. The fields transferred by MERGEPORT depend on the configured mappings.

Images

Uber Eats treats the item image URL as technically optional. Its Menu API accepts JPG, WEBP or PNG files smaller than 25 MB, with both width and height between 320 and 6000 pixels. These are API processing requirements; additional quality rules can apply. Uber Eats image requirements

For Wolt restaurant menus, foodora and JET Connect, confirm the applicable dimensions, aspect ratios, formats and file-size limits before the first upload. Avoid applying rules from other catalog types or older interfaces.

MERGEPORT transfers image URLs. Transferring a URL does not confirm platform acceptance. Check the images in the published menu.

Allergens and additives

Use the actual recipes to maintain these details, including variants, extras and different combinations. An empty allergen field should not be interpreted as “allergen-free”.

Wolt's Germany guidance calls for specific allergens and additives and additional information for certain products, including prepacked drinks. Its guidance does not consider generic terms such as “gluten” or “nuts” sufficient. Check other countries separately. Wolt Germany requirements

Uber Eats lists allergens as an optional API field. This does not establish an exemption from information required for the relevant country or product. Uber Eats allergen field

For Wolt, Uber Eats and JET Connect, configure the corresponding MERGEPORT mappings. Changes to allergen mappings require a full menu upload. Verify the visible information afterwards. For foodora, agree the separate maintenance process before uploading.

Before your first menu upload

1. Agree which system maintains the menu and confirm synchronization is enabled.

2. Review names, categories, prices, options, images and product information.

3. Preserve the existing menu with the operator and agree the upload time. Full uploads can replace the current menu.

4. Check the visible menu after platform processing completes. An accepted upload request alone does not confirm publication.

5. Test an order with a variant or extra through to POS processing.

For Uber Eats, avoid editing API-managed menus through Menu Maker in parallel. Uber Eats menu management guidance

For setup assistance, contact your POS partner or support@mergeport.com.