Illustrative scenario. Not a customer reference.Hospitality group
Venue operations and supplier approvals on the same ledger.
A fictional group of twelve venues wants orders, shifts and supplier bills on one platform, with approval workflows its finance team can change without a developer.
Illustrative scenario. Not a customer reference. Saffron Table Group is fictional and the figures are hypothetical.
The situation
- Venue point-of-sale data lands in a separate system from the books.
- Supplier bills are approved by email, with no tolerance rules.
- Every change to the approval process needs a developer.
How it works
- The pack provides venue, menu and shift structures on the shared data model, with daily venue takings posting to the ledger.
- A Studio workflow matches each supplier bill to its order and receipt and routes it by a decision table the finance manager maintains.
- Variances above tolerance go to an agent that investigates and prepares the approval; a person approves.
The outcome to expect
- Designed to keep venue takings and supplier bills in one audited ledger.
- Expected to let finance change the approval rules in a decision table, with no code change.
- Designed to route only exceptions to people, with every agent step in the audit trail.