Products
Attach products and prices to offers so checkout sessions, invoices, and integrations carry clean catalog context.
Products describe what the customer is buying. Prices describe how they pay.
Product fields
At minimum, a product should have:
- name
- description
- image when useful
- one or more prices
- fulfillment or access context if another system needs to react after purchase
Price fields
Prices can represent one-time payments, recurring subscriptions, tiers, volume breaks, trials, or imported Stripe prices where supported by the integration.
Why catalog context matters
Checkout sessions and invoices can carry product and price context into:
- customer records
- invoice line items
- webhooks
- automations
- CRM and email integrations
- tax and accounting-adjacent workflows
API route
Protected API clients can create products and prices through the v1 catalog endpoints.
POST /api/v1/products
Authorization: Bearer <api_key>
Content-Type: application/json
See catalog API for endpoint notes.
Builder context
Build the offer beside the docs.
These pages explain the setup details. The matching product surfaces show where products, prices, checkout layout, invoices, and automation live in the app.
Offers product Hosted checkout, buy buttons, products, prices, coupons, bumps, upsells, invoices, and save offers. Hosted checkout The hosted buying surface for offers. Products The commercial objects attached to an offer. Prices One-time, subscription, package, tiered, and variant pricing. Checkout Optimization Lab A builder stack for improving checkout mechanics.