Configure and enforce catering order lead-time and cutoff rules so ezCater orders aren't accepted with insufficient prep notice
domain: api.ezcater.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Set a store-level lead time in ezCater reflecting how much advance notice the kitchen realistically needs — ezCater's guidance is to start conservative (roughly 24-48 hours) before lowering it to capture same-day catering demand
For stores that need more than a day's notice, use ezCater's multiple-days-notice option and a day-before cutoff time so all next-day orders must be submitted during the current day's operating hours
Sync menu availability and lead-time-sensitive items via the Menus API so real-time changes (e.g., temporarily disabling large-tray items) push without waiting on manual email updates to ezCater
Handle customer-initiated modification requests only up until your configured lead-time cutoff; requests after cutoff should route to staff review rather than auto-applying
Remember ezCater customer service can still execute a modification after your cutoff with store approval — build a manual-approval path for that case rather than assuming cutoff is absolute
Known gotchas
Lowering lead time too aggressively increases order volume but raises the risk of orders you can't reliably fulfill — treat it as an operational tuning knob, not a one-time setting
A tight cutoff configuration measurably reduces order visibility/volume on ezCater, so lead-time changes have a direct demand tradeoff, not just an operational one
Order modification rules after cutoff aren't fully enforced client-side — ezCater support can still push a late change through with store sign-off, so your system needs a path to accept that scenario
Give your agent this knowledge — and 15,500+ 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?