Catering
Events are priced to a target margin rather than from a price list; the customer sees the quote and edits it on a link, and it then becomes a contract with a lifecycle and a signature.
What it stands on
Catering does not run without these modules. The ones that always run are in every instance, and no plan that includes Catering is accepted without the subscribable ones among them.
- AccountingAlways on
- Accounts & sign-inAlways on
- DocumentsAlways on
- FinanceLicensable
- InventoryAlways on
- Background jobsAlways on
- SalesLicensable
- SettingsLicensable
- FilesAlways on
From the real module registry: what each module needs in order to run.
From the enquiry to the signed contract, without leaving the system
- Pricing by factors and a target margin, and a quote with a configurator the customer opens on a tokenised link
- A contract from a template register, with a full lifecycle: draft, sent, viewed, negotiating, approved, signed, active, amended, ended
- Revisions are added rather than replaced, and an electronic signature with a verification code sent to the signer
- A bilingual PDF with a public verification code that can be scanned from the printed sheet
- Prep orders, event resource scheduling, and event cost and profitability
How far this reaches today
- No three-tier quote (economy / standard / premium)
- No events calendar that surfaces date clashes, and no kitchen capacity check
- No loading list, no labour roster and no pre-departure checklist
- Sending the quote over WhatsApp needs an active messaging provider account