Packages
Teams bundle services/classes into periods, prices and session allowances. Sales create subscriptions; bookings redeem sessions.
Teams bundle services/classes into periods, prices and session allowances. Sales create subscriptions; bookings redeem sessions.
Where to find it
Web: open Sales. Desktop: Business → Sales, using the same record paths. Disabled modules or missing read permission remove the navigation entry.
| Screen / tab | Web path | Usage | Desktop |
|---|---|---|---|
| Packages | /packages | List, view or tab | Native screen |
| New package | /packages/new | List, view or tab | Native screen |
| Subscriptions | /packages/subscriptions | List, view or tab | Native screen |
| Record details | /packages/[id] | Record or editor | Native screen |
Start working
Step 1
Create a package with period, price and renewal default.
Step 2
Add services/classes and allowances.
Step 3
Start the customer subscription.
Step 4
Redeem or release sessions on bookings.
Step 5
Retire the package to stop new sales.
Settings
Option-by-option configuration and screen paths: Settings guide.
- Package rules ·
/settings/packages
Permissions and limits
Before you start
Editing does not change locked subscription prices. Retiring leaves running subscriptions intact. Releasing a session does not cancel a booking.
Role capabilities: Read (read), Write (write), Delete/archive (delete), Manage (manage), Export (export), Comment (comment), Handle automated delivery/jobs (handle).
Own-record restrictions apply equally to lists, records and Era. Record state or missing data can refuse an otherwise permitted action.
Ask Era
Create a monthly four-session service package.
Select relevant records for Era context. Era respects modules/roles; external or confirmation-sensitive work can stop for approval. Use era tools in the terminal to inspect currently available tools.
Automation and events
These declared events are available to module-event triggers. Subscribing does not configure the next operation; choose recipients, conditions and actions separately.
Operation details
The inventory includes record, configuration, visitor and background flows. IDs support Era/automation; not every row is a menu button. Asterisks mark required inputs. Unmapped rows do not imply a visible control.
| Operation and ID | Inputs | Permission | Screen or flow |
|---|---|---|---|
Create a package · packages.create_package | Name *, Months * (1–120), Price (minor units) *, Currency, Renews by default, What it covers * | Manage | /packages |
Edit a package · packages.update_package | Package *, Name, Months (1–120), Price (minor units), Currency, Renews by default | Manage | /packages, /packages/[id] |
Change what it covers · packages.set_items | Package *, What it covers * | Manage | /packages/[id] |
Take off sale · packages.retire_package | Package * | Manage | /packages/[id] |
Use a package session · packages.redeem | Subscription *, Booking kind *, Booking * | Write | /appointments/new |
Give a session back · packages.release | Session * | Write | Record/API/visitor flow; no separate screen button mapped |
Use my package · packages.use_on_my_booking | Package *, Booking * | Write | Record/API/visitor flow; no separate screen button mapped |
Related guides
Settings
Options, screen paths and defaults.
Workflows
Operations managers connect triggered blocks on a canvas with conditions, loops and approval waits.
Sales
Sales — modules and detailed settings
Technical sources
packages/os-kernel/src/modules/packages.ts, packages/os-kernel/src/modules/index.ts, apps/studio/lib/os/navigation.ts, apps/studio/lib/os/settings-groups.ts, apps/era-station/apps/web/src/era/business/screens.ts.