Product
Everything Setful does, and everything it doesn’t.
21 of 28 modules are available today. The rest are listed here too, because a feature list that only mentions the good news is not a feature list.
| Module | What it does | Status |
|---|---|---|
| Enquiries and customers | Capture and triage enquiries, with customers, contacts, venues and history attached. | Available |
| Quotes and revisions | Live availability beside each line. Every sent revision is frozen. Optional extras reserve nothing until chosen. | Available |
| Availability ledger | Stock truth by time and location, with turnaround folded in and the conflicting job named. | Available |
| Promise Check | Nine constraints with evidence: stock, turnaround, warehouse, crew, vehicles, route, supplier, margin, payment. | Available |
| Jobs and acceptance | Acceptance locks the stock and re-checks inside the transaction, so two people cannot both win it. | Available |
| Change orders | A change after acceptance is proposed, not applied. The original stands until the customer approves. | Available |
| Cancellation | Releases the stock and records what the policy retained. Refunding stays a separate, deliberate act. | Available |
| Customer portal and proposals | A private link to read, question, adjust, sign and track. No account for your customer to forget. | Available |
| Documents | Quote, hire agreement and invoice as printable pages that stay readable in black and white. | Available |
| Warehouse and picking | Pick waves built from the day, kits exploded into components, exceptions flagged rather than fudged. | Available |
| Crew app, offline | Scans saved on the device and synced when there is signal, with manual SKU entry as a fallback. | Available |
| Returns and damage | What comes back is checked in. What does not keeps its claim. Damaged stock is quarantined out of availability. | Available |
| Dispatch and routes | Vehicles, stop order, access notes and proof of delivery. Works with no map provider connected. | Available |
| Crew scheduling | People, skills, certifications with expiry, shifts and overlap warnings. | Available |
| Suppliers and sub-hire | Stock you do not own is still your promise, so an unconfirmed sub-hire blocks the check. | Available |
| Storefront | A public catalogue where a customer builds an event list and requests a quote. | Available |
| Migration from Booqable | Scan an export, see what will and will not come across, import without reserving, reconcile, then cut over. | Available |
| Reports | Conversion, booked against collected, utilisation as unit-days, and a shortage list from checks that were blocked. | Available |
| Automations | Quote chasing, balance reminders, delivery reminders and overdue returns. Each starts paused with a dry run. | Available |
| API and webhooks | Scoped keys, a documented v1 over catalogue, jobs and availability, and signed webhooks that retry. | Available |
| Data export | Your whole account as JSON, or per-entity spreadsheets. Includes the availability ledger and audit log, and is itself audited. | Available |
| Approval workflows | Discount and margin thresholds that need a manager to sign off are not built. | Not built yet |
| Supplier price lists | Suppliers and sub-hires are recorded. Negotiated price lists and RFQ comparison are not built. | Not built yet |
| Card payments | Invoices are raised from the accepted figures and payments recorded by hand. Taking a card is not built. | Not built by choice |
| Xero and QuickBooks | The interface, mapping and error queue exist and run against a sandbox. No live credentials are accepted. | Not built yet |
| Venue floor plans | Venues hold access notes and contacts. Placing items on a scaled plan is not built. | Not built yet |
| Multi-location transfers | Stock is tracked per location. Moving it between locations is not built. | Not built yet |
| SMS | All customer and crew messaging is email today. | Not built yet |
How we decide
Why some of this says “not built by choice”
Card payments are the clearest example. Taking money is easy to demonstrate and hard to get right, and a half-finished payment flow causes more damage than no payment flow at all. It waits until the rest is proven in a real business.
The same rule runs inside the software. A Promise Check constraint with nothing behind it reports “not evaluated” and explains why, and the overall answer never comes back clear while one of them is unresolved. You should never be told a job is fine because the software forgot to look.
See it against your own catalogue.
We will set Setful up with your products and run a booking you already know the answer to.