Use the Uber Eats Store API to POST a new store resource with address, contact, timezone, and merchant category code fields
Set the tax_config block with the applicable tax rates and indicate whether Uber Eats acts as marketplace facilitator for tax collection in the store's jurisdiction
Configure accepted payment methods and specify whether cash payments are enabled for the location
Associate the store with a menu by POSTing a menu assignment linking the menu_id to the new store_id
Trigger a test order in the Uber Eats sandbox environment and verify the store surfaces correctly in the response with expected hours and fulfillment modes
Activate the store by updating its status to ACTIVE and confirm it appears in the Uber Eats consumer app for the correct service area
Known gotchas
Timezone must be set as an IANA timezone string; mismatches between store timezone and operating hours cause off-by-one hour issues during DST transitions
Marketplace facilitator tax configuration is jurisdiction-specific and must match Uber Eats's own remittance schedule; misconfiguring results in double taxation on consumer receipts
Menu assignment does not automatically publish the menu; a separate menu publish call with channel-level targeting is required before the store goes live
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp