Overview#
A national park visitor management system processes forty thousand tourist check-ins in a single summer weekend. The back-office team needs accurate invoicing that reflects actual volume, not a flat monthly fee. They configure a per-tourist pricing tier with a summer surge threshold, and invoices generate automatically at the close of each billing cycle with full line-item breakdowns. That flexible, usage-driven billing is what the Tourism Pricing domain provides.
The domain handles subscription and billing management for tourism organisations. It supports multiple pricing tiers, usage tracking, invoice generation, and billing cycle management, enabling tourism operations to handle check-in tracking with flexible per-tourist and per-employee pricing models. All subscription data is stored in PostgreSQL with multi-tenant organisation isolation.
Key Features#
-
Pricing Tier Management: Define and manage multiple subscription tiers with different feature sets, capacity limits, and pricing levels to accommodate organisations of varying sizes.
-
Usage Tracking: Monitor tourist check-ins, employee counts, and feature usage in real time to support accurate billing and capacity planning.
-
Invoice Generation: Automatically generate invoices based on subscription tier, usage metrics, and billing cycle configuration with detailed line-item breakdowns.
-
Billing Cycle Management: Configure billing cycles (monthly, quarterly, annual) with automatic invoice generation and payment tracking at each cycle boundary.
-
Subscription Lifecycle: Manage subscriptions from creation through activation, renewal, upgrade, downgrade, and cancellation with appropriate proration handling.
-
Per-Unit Pricing: Support flexible pricing models based on tourist check-in volume and employee counts, allowing pricing to scale with actual usage.
Mermaid Diagram#
Use Cases#
-
Tourism Operations: Manage subscription plans for tourism organisations that track visitor check-ins and need flexible billing that reflects seasonal volume changes rather than fixed monthly fees.
-
National Parks & Heritage Sites: Use usage tracking data to understand demand patterns and plan staffing and infrastructure capacity for peak tourism seasons.
-
Hospitality Groups: Generate accurate invoices and track payment status across a portfolio of tourism properties with detailed usage breakdowns per site.
-
Travel & Visitor Economy: Help organisations select the right pricing tier based on actual usage patterns and operational needs, avoiding over-provisioning during low seasons.
Integration#
The Tourism Pricing domain supports tourism operations across the platform:
- Organisation Management: Subscriptions link to organisational tenants.
- User Management: Employee counts feed into billing calculations.
- Analytics: Usage data contributes to operational dashboards.
- Reporting: Billing and usage reports support financial management.
Open Standards#
- GraphQL (June 2018 Specification): All subscription, usage, and billing operations are exposed via a GraphQL API, enabling flexible querying of pricing tiers, usage summaries, and invoice data through typed queries and mutations.
- OAuth 2.0 (RFC 6749) Scopes: Access to billing and subscription resources is gated via OAuth 2.0 scope-based permissions (prefixed
scope:), enforced on every GraphQL resolver before data is returned or modified. - JSON Web Token, JWT (RFC 7519): Every API call is authenticated with a platform-issued RS256 JWT verified against a published JWKS endpoint; the decoded claims carry the user identity and permission scopes used for organisation isolation.
- OASIS Common Alerting Protocol, CAP v1.2: IPAWS public-alert dispatches are a first-class billable event type within the usage model; the platform's CAP v1.2 connector produces the underlying alerts whose issuance this domain tracks and invoices.
- ISO 8601 (Date and Time): All subscription start dates, billing cycle boundaries, invoice due dates, and usage event timestamps are serialised as ISO 8601 strings, ensuring interoperability with downstream finance and reporting systems.
- RFC 4122 UUID: Every subscription, usage event, and invoice is identified by a version-4 UUID, providing globally unique, collision-resistant keys across multi-tenant organisation data.
- JSON (RFC 8259 / ECMA-404): Usage breakdowns, per-event metadata, and invoice line-item detail are stored and exchanged as JSON, making billing records consumable by third-party finance integrations without additional transformation.
Last Reviewed: 2026-02-23 Last Updated: 2026-04-14