← All case studies
Case study 01
Event operationsCustom software

One event record for the sales desk, kitchen and warehouse

A planner promises a sharing menu. The kitchen needs to know how to serve it, and the warehouse needs to know which boards to put on the van. We built a custom catering system that carries that decision through to the pick list.

The situation

The original AppSheet setup grew out of day-to-day event work. It held hard-won knowledge about dishes, serving vessels and substitutions. When a menu changed, a rebuild had to back up the planner’s adjustments, recalculate the requirements and restore those choices. Choosing a different plate for one dinner meant making sure the next recalculation remembered it.

The decision

Give the event planner ownership of substitutions. Each change belongs to a specific booking, so the kitchen can update a menu without undoing a warehouse decision.

What we built

  • We traced a menu choice through the old system with a practical question in mind. What would the warehouse actually pick, and why?
  • We connected enquiries, proposals, menu selections, kitchen instructions and equipment requirements to the same event record.
  • We separated the standard allowance for a dish from a planner’s change for one event. The warehouse can see which dishes share an item and the combined quantity to pack.

How we checked it

In a four-day event rehearsal, the menu and tasting handover retained all 40 source selections. Before any event-specific substitutions were applied, all 150 combinations of menu selection and equipment code matched an independent calculation.

Work with WovenFlow

What would you
change first?

You might have a brief ready or just know that something takes too long. Tell us where you’d like to start.

Talk through your project