How KitchenSync Connects to the Rest of CeremonySync

KitchenSync does not stand alone. A catering order always belongs to something.

Weddings and EventSync events

Every catering order links to either a wedding or an EventSync event inquiry. That link is where the order gets its date, its client and its guest count, and it is why the kitchen screens show the event's name rather than a separate catering record.

Both pipelines work identically here — a corporate event and a wedding produce the same kind of catering order.

StaffSync

A catering order's Admin tab carries staffing needs: kitchen staff, servers, bartenders and setup crew, with a total. Request in StaffSync turns those numbers into a staffing request in StaffSync, so the people who fill rosters see what the kitchen needs.

This is one-directional. Staffing numbers you set here are a request; who actually gets rostered is decided in StaffSync, and KitchenSync does not show you the resulting roster.

Invoicing

The Admin tab can generate an invoice from the catering order. Revenue in KitchenSync Reports comes from those invoices once they are PAID — raising one is not enough to make it count.

Guest selections

The client-facing menu pages feed back into the order: what each guest chose, and the dietary summary the kitchen cooks from. That summary is where allergy counts come from, so it matters that the submission completes — if it fails, the venue is told rather than left with dish choices saved and requirements missing.

What does NOT connect

• Inventory is not touched by anything outside KitchenSync. Finalizing a prep plan deducts stock; nothing else does.
• There is no link to FacilitySync. A broken oven is not a kitchen record here.
• Compliance records are not tied to events. A HACCP plan or an exclusion is venue-wide, not per-order.