Connected to the event, with a clear data boundary.
Caterfold is part of the ShowFold family. Each connection carries only what the other side needs to do its job.
In development Every connection on this page is in development. None is available until it is tested and accepted for production use.
The data boundary
Comes into Caterfold
From event.clinic, as a review the caterer accepts or questions
- Relevant event context
- Guest-count changes
- Venue information
- Cancellation changes
- Delivery changes
Goes out from Caterfold
Through the event.clinic hub
- Quotations
- Invoices
Stays in Caterfold
Private to your team
- Allergen records
- Prices and costs
- Supplier records
- Guest information
- Kitchen notes
event.clinic
Coordinates the event. Sends the caterer the event context and changes listed above, and carries quotations and invoices back to the organiser.
Venuesta
Provides venue context. Published venue information can sit beside your own Kitchen Playbook notes, and when they disagree both are kept.
Procurevent
Handles structured sourcing. A formal catering tender in Procurevent can be answered from your Caterfold workspace. Procurevent has no paid placement.
Kit boundary with Rigfold
Caterfold owns china, glass, linen and cooking kit. Rigfold owns AV equipment. Each piece of kit has one home, so it is counted once.
catering.directory is separate
catering.directory is a planned public portal for finding event caterers. It is a different product with a different job. Caterfold operational data stays private.