specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: PAR Punchh
providerId: punchh
created: '2026-06-03'
modified: '2026-06-03'
reconciled: false
tags:
  - FinOps
  - FOCUS
  - Loyalty
  - Restaurant
description: >-
  FOCUS-aligned FinOps shape for PAR Punchh: an enterprise loyalty/marketing
  platform billed as a negotiated subscription rather than per-API metering, so
  cost is anchored on the platform license and module mix rather than request
  volume.
sources:
  - https://punchh.com/
  - https://punchh.com/solutions/loyalty/
  - https://developers.partech.com/
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: ParTech, Inc.
serviceCategory: Loyalty + Guest Engagement
billingModel:
  pricingCategory: Subscription
  billingFrequency: Annual
  billingCurrency: USD
  chargeCategories:
    - Purchase
    - Usage
    - Tax
focusColumns:
  ServiceName: PAR Punchh
  ServiceCategory: Loyalty + Guest Engagement
  ProviderName: PAR Technology
  PublisherName: ParTech, Inc.
  InvoiceIssuerName: ParTech, Inc.
  BillingCurrency: USD
meters:
  - name: platform_subscription
    unit: month
    aggregation: max
    dimensions:
      - module
  - name: brand_locations
    unit: seat
    aggregation: max
    dimensions:
      - region
  - name: loyalty_members
    unit: varies
    aggregation: max
    dimensions:
      - brand
  - name: api_calls
    unit: request
    aggregation: sum
    dimensions:
      - api
      - channel
principles:
  - name: Visibility
    description: >-
      Brand-level loyalty and transaction activity is observable through the
      Punchh dashboard, Platform Functions reporting, and the Webhooks Manager
      event stream; there is no public per-request usage/billing API since cost
      is contract-based rather than metered.
  - name: Allocation
    description: >-
      Attribute spend by brand, region, and licensed module (Loyalty, Online
      Ordering, POS/Kiosk, Mobile, Webhooks); the store_number and channel
      dimensions on check-ins/redemptions support per-location attribution.
  - name: Optimization
    description: >-
      Optimize by right-sizing the module mix to the brands actually using
      them and consolidating integration surfaces; high API call volume does
      not directly increase cost under the subscription model, so engineering
      can favor real-time integrations without per-call cost pressure.
  - name: Accountability
    description: >-
      The marketing/loyalty program owner owns the PAR contract and renewal;
      integration owners own certification status and webhook reliability.