Register a webhook endpoint URL with ezCater via the partner portal; configure the endpoint to receive order event notifications
Implement the webhook handler to parse the incoming order payload; extract order ID, customer name, delivery address and time, line items with quantities and modifiers, and any special instructions
Acknowledge the webhook with an HTTP 200 response immediately upon receipt before executing downstream processing to prevent retry storms
Translate the ezCater order format into your POS's native order structure; inject the translated order into the POS so kitchen production tickets are generated
Use the ezCater API to send order status updates back (e.g., confirmed, in preparation, ready, delivered) so the customer and ezCater platform are kept informed
Handle order modification and cancellation webhook events: update or void the corresponding POS order and trigger any required customer communication
Known gotchas
Catering orders typically have long lead times but high value — a missed or unacknowledged webhook is more costly than in standard delivery; implement redundant alerting if webhook delivery fails
ezCater order payloads may include catering-specific fields not present in standard delivery orders (e.g., headcount, serving utensil requests, setup instructions); ensure your POS translation layer handles or stores these fields rather than silently discarding them
Order modification windows on ezCater can extend up to the day of delivery; build your integration to handle inbound update events at any point in the order lifecycle, not only at creation
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