specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Thanx providerId: thanx created: '2026-06-03' modified: '2026-06-03' reconciled: false tags: - FinOps - FOCUS - Loyalty - Guest Engagement - Restaurant description: >- FOCUS-aligned FinOps for Thanx: a custom, contact-sales platform subscription whose cost scales with restaurant/location count and average unit volume, with the Consumer, Partner, and Loyalty APIs included rather than separately metered. Consumption is observed through loyalty, marketing, ordering, and data-export activity rather than per-API-call billing. sources: - https://www.thanx.com/pricing - https://docs.thanx.com/overview - https://docs.thanx.com/data/overview.md alignedWith: framework: FinOps Foundation Framework frameworkUrl: https://www.finops.org/framework/ dataSpec: FOCUS dataSpecVersion: '1.3' dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/ publisherName: Thanx, Inc. serviceCategory: Customer Engagement + Loyalty billingModel: pricingCategory: Subscription billingFrequency: Annual billingCurrency: USD chargeCategories: - Purchase - Usage - Adjustment focusColumns: ServiceName: Thanx ServiceCategory: Customer Engagement + Loyalty ProviderName: Thanx PublisherName: Thanx, Inc. InvoiceIssuerName: Thanx, Inc. BillingCurrency: USD ChargeCategory: Purchase meters: - name: platform_subscription unit: month aggregation: sum dimensions: - module - name: managed_locations unit: location-month aggregation: max dimensions: - merchant - region - name: enrolled_members unit: member aggregation: max dimensions: - merchant - name: rewards_issued unit: reward aggregation: sum dimensions: - campaign - merchant - name: purchases_processed unit: transaction aggregation: sum dimensions: - merchant - location - name: data_export_volume unit: GB aggregation: sum dimensions: - destination principles: - name: Visibility description: >- Use the Connex data-export integrations (Snowflake, BigQuery, Redshift, Databricks, S3, and others) and the documented data models (purchases, points transactions, campaigns, memberships, rewards) to land Thanx activity in the warehouse and observe consumption by merchant and location. - name: Allocation description: >- Attribute spend across brands, merchants, and locations using the merchant_id / location_id dimensions present on purchases, campaigns, and metadata endpoints; tag campaigns to allocate reward-issuance activity to marketing programs. - name: Optimization description: >- Batch reward issuance (up to 10,000 identifiers per request) to reduce API overhead, scope subscriber ingestion to active programs, and right-size data-export frequency to the destinations actually consumed downstream. - name: Accountability description: >- Because pricing is a custom platform subscription, assign an owner for the Thanx contract who reconciles location count and AUV against the negotiated tier at renewal and reviews module usage (loyalty, ordering, data exports) for fit.