Skip to main content
A product is the top-level folder in Paygentic’s billing system — it groups the items, metrics, fees, and plans for a single service or offering you provide to customers.

​
What’s a product?

A product groups everything related to a single service:
  • The items you sell
  • The metrics you track
  • The pricing plans available
  • Customer subscriptions
  • Usage data and analytics
Think of products as separate business lines. If you offer both an LLM service and a data warehouse, those would be two different products. Billable metrics and fees always carry a productId — it’s how they belong to a product. You can additionally tag one with an item, and then its productId is resolved from that item’s product for you. Tagging is optional; it exists so invoice lines can be mapped to an external accounting identity, not to replace productId.

​
Creating products

Products require minimal configuration:
  • Name - Customer-facing display name (e.g., “Neural Network Training”, “Cloud Analytics”)
  • Description - Brief explanation shown during checkout
  • Metadata - Optional key-value pairs for internal tracking

​
When to create products

Create separate products when you have:
  • Distinct services with different metrics
  • Independent pricing strategies
  • Separate customer bases
  • Different billing cycles or payment terms

​
Examples

Single-product strategy A machine learning platform might have one product:
  • Product: “ML Training Platform”
  • Metrics: GPU hours, model storage, inference requests
  • Plans: Researcher, Startup, Enterprise
Multi-product strategy A data company might separate services:
  • Product 1: “Data Warehouse”
    • Metrics: Storage TB, compute hours, queries
    • Plans: Developer, Business, Enterprise
  • Product 2: “Stream Processing”
    • Metrics: Events processed, throughput GB
    • Plans: Basic, Professional, Scale
  • Product 3: “ML Pipeline”
    • Metrics: Training jobs, model deployments, predictions
    • Plans: Starter, Growth, Custom

​
Best practices

Keep it simple. Don’t over-segment. One product can support multiple plans and customer types. Think customer-first. Products should align with how customers think about your services. Plan for growth. Structure products to accommodate future features without major refactoring.

​
Analytics

Paygentic provides product-level analytics:
  • Revenue breakdown
  • Usage patterns
  • Customer distribution
  • Growth metrics
This segmentation helps you understand which services drive your business.

​
Next steps

With products defined, you’ll need to:
  1. Add items for the SKUs you sell
  2. Add billable metrics to track usage
  3. Create plans for different customer segments
  4. Set prices for each metric