Product structure (high level)
Scoutello groups work into a few stable product areas. This page is a reader-facing map, not an implementation schema.
| Domain | Conceptual building blocks |
|---|---|
| Tenancy | Organizations, memberships, invitations, billing relationships |
| Guest web apps | Landing pages, configurable tiles, FAQs, embeddable widgets |
| Geo and plans | Places, groups, points of interest, venue site plans, map-oriented layers |
| Tours | Tours, ordered stops, media, assignments, optional monetization tiers |
| Events | Programs, schedules, invitations, ticketing where enabled, attendee state |
| CRM and communications | Customers, interaction history (protocols), tasks, documents, newsletters, mail threads |
| Commerce (checkout) | Orders, payments, price tiers, and access after purchase |
Commerce, orders, and payments
- Prices and amounts: Scoutello stores prices in the smallest unit supported by the currency, such as cents where applicable. This keeps billing precise.
- Presentment currency: Each organization uses one checkout currency. Ticket types, tour tiers, and similar prices inherit that currency from the organization.
- Orders vs payments: An order describes what was bought and which access should be granted. A payment describes the money movement behind that order.
- Support posture: Refunds, disputes, and finance review should start from the order and the payment status shown in approved billing tools.
CRM relationships (dashboard language)
In the dashboard, protocols are structured interaction logs tied to customers (calls, meetings, notes, mail). They connect naturally to tasks, projects, milestones, documents, campaigns, and events when teams link records together.
Support questions usually start from the customer profile. From there, check the related tasks, protocols, project milestones, linked files, newsletter audiences, mail history, or event participation.
Related concepts: Product model, CRM and operations, Customer management overview.