Sales & Catering

Sales & Catering overview

A pipeline of opportunities against accounts, with configurable stages, sellable products, and a proposal that becomes a real banquet event order the moment it's accepted.

Cập nhật lần cuối

Who this is for: reach requires sales.crm.read; creating and editing requires sales.crm.manage. Sellable products need sales.product.manage. Where: Sales & Catering → Opportunities / Accounts

Sales & Catering is where a sales team runs the pipeline it books into the property, rather than into a separate CRM: an opportunity moves through stages, is priced against a proposal built from your sellable products, and — accepted — becomes a real banquet event order on the function space it was quoted against.

Two screens: Accounts is who you sell to; Opportunities is the pipeline itself.

Accounts#

An account is the company or organiser behind the business — name, contact, and two sales-qualification fields that are deliberately distinct from anything on a guest or reservation profile:

  • Reason for stay — the sales-side qualification of the business (e.g. Corporate event), a different question from purpose-of-stay on a reservation.
  • Referral source — who sent the business (e.g. Corporate referral), a different question from the booking-source channel a reservation arrives on.

Both are reference lists — see Reference data — and both are visible as columns on the Accounts list, alongside the contact.

Opportunities and pipeline stages#

Each opportunity sits in one stage, shown as a board of columns (or a table, via the view toggle) with each stage's configured win probability in its header — Enquiry (10%), Qualified (25%), Proposal sent (40%), and so on. Manage stages lets an Owner or Manager add, reorder or reweight the stages themselves; moving an opportunity between stages records the transition, and the stage's win probability feeds the weighted pipeline value the Revenue forecast reads.

New opportunity creates one against an account. Selecting an opportunity opens its detail: the activity log (logged against the sales activity types your organisation defines) and its proposals.

Sellable products#

A sales product is what the team actually sells — a room block, a meeting package, a day-delegate rate — configured under Settings: a name, a type, a default price, an optional charge-code mapping (so the product posts to the right revenue account once billed), and free-text inclusions ("Wi-Fi, projector, coffee breaks").

Proposals and acceptance#

A proposal is built from one or more sales-product lines against an opportunity. Send marks it sent; Accept does the work this whole pipeline exists for: it opens a real event order on the banquet function space the proposal quoted, with the proposal's lines carried across as the event's billable items. Reject records the outcome without creating anything. None of this reaches back into POS's own tables directly — it goes through the POS module's exported event API, the same module-boundary rule every cross-module call in Nerve follows.

What's next#