specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: Kroger
providerId: kroger
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - FinOps
  - FOCUS
  - Groceries
  - Retail
  - Partner API
description: FinOps framing for Kroger Developer APIs. Public APIs are free-to-register; Partner APIs
  carry no published per-call pricing and are governed by a partner contract. FOCUS columns reflect Kroger
  as the publisher and merchant of record for any negotiated commercial terms.
sources:
  - https://developer.kroger.com/
  - https://developer.kroger.com/manage/documentation/policies
notes: No public unit pricing exists; FinOps shape is contract-driven. Meters describe what an integrator
  should track internally rather than what Kroger invoices.
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: The Kroger Co.
serviceCategory: Retail / Grocery APIs
billingModel:
  pricingCategory: Contract / Partner
  billingFrequency: Per-Contract
  billingCurrency: USD
  chargeCategories:
    - Usage
    - Purchase
    - Adjustment
focusColumns:
  ServiceName: Kroger Developer APIs
  ServiceCategory: Retail / Grocery
  ProviderName: Kroger
  PublisherName: The Kroger Co.
  InvoiceIssuerName: The Kroger Co.
  BillingCurrency: USD
meters:
  - name: api_requests
    unit: request
    aggregation: sum
    dimensions:
      - api
      - environment
      - application
  - name: order_transactions
    unit: order
    aggregation: sum
    dimensions:
      - store_id
      - fulfillment_type
  - name: product_lookups
    unit: request
    aggregation: sum
    dimensions:
      - location_id
  - name: cart_operations
    unit: request
    aggregation: sum
principles:
  - name: Visibility
    description: Capture Kroger API call volumes per application and per endpoint; the platform does
      not expose a usage API, so client-side telemetry is required.
  - name: Allocation
    description: Tag outbound API requests with the consuming product line (digital cart, locker, fulfillment)
      so internal chargeback can be performed against the partner contract.
  - name: Optimization
    description: Cache static catalog and location data; batch product lookups; refresh OAuth tokens
      rather than re-issuing them per call.
  - name: Accountability
    description: Partnership owner reviews API call volumes against the partner agreement quarterly to
      anticipate any renegotiation triggers.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com