A blocked or double-booked date doesn't necessarily stop a request from arriving, but it never gets accepted without you noticing.

At submission time

When a customer submits a request, CaterWay checks the date against your blocked dates and confirmed events. A date you've fully closed all day rejects the submission outright: the customer sees a message and has to pick another date. Everything else, a busy (soft) day, a partial-day closure, or a date that already collides with a confirmed event, still lets the request through, but it's flagged as a conflict and can never auto-confirm, even on a calculator with auto-confirm turned on. It arrives as a normal open request instead.

Where the flag shows up

• Quote list: a warning badge next to the status.
• Quote detail: a note explaining the requested date collides with a busy or blocked day in your calendar (with the specific reason shown when it isn't generic).
• Your notification email: the same warning, with the colliding detail spelled out, for example, which confirmed event is already on that day.

The accept-time guard

Marking a request Accepted or In Progress (whether via the status control or the primary Confirm order button) re-checks the date live at that exact moment, because a new event or block may have appeared since the request first arrived. If there's still a collision, a Date conflict dialog appears naming what's in the way (a colliding event's title and dates, or a note about the blocked/busy day) with Accept anyway and Cancel buttons. Nothing saves until you explicitly choose Accept anyway.

This check is span-aware: a multi-day event or booking is checked against every day of its range, not just its start date, so a clash on day two of a three-day event is caught exactly like a clash on day one. See Multi-day events.

Availability rules themselves (hard vs soft, whole day vs event time) are set up in Block a date you can't cater.