Configure Grubhub Marketplace delivery radius and minimum order amount adjustments via the Location Management API
domain: Grubhub · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate to the Grubhub Partner API and retrieve the current location configuration for the restaurant using the location management endpoint
Identify the delivery_radius_miles and minimum_order_amount fields in the location resource
Issue a PATCH with the updated delivery radius value; note that radius changes are subject to Grubhub's coverage zone approval and may not take effect immediately
Update the minimum_order_amount to enforce a delivery floor (for example to cover increased packaging costs) and confirm the field accepts a decimal value in the same currency as the location
Trigger a test consumer-facing search to verify the new radius boundaries appear correctly on the map and the minimum order warning surfaces at checkout
Monitor the next settlement report to confirm no orders below the new minimum slipped through during the propagation window
Known gotchas
Delivery radius changes may require Grubhub operations approval if the new radius extends into zones already served by competing restaurant partners under exclusive agreements
Minimum order amount changes do not retroactively affect in-progress orders; guard against the edge case where an order was placed just before the change propagated
Grubhub may override the configured radius during high-demand periods as part of Grubhub+ fulfillment optimization; the effective radius in the consumer app may differ from the configured value
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?