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.

The Numi offer editor with product, theme, automation, invoice, and checkout controls.
The offer editor connects checkout layout, products, prices, invoice settings, and automation.
The Numi checkout element palette showing content, interactive, and selling blocks.
Checkout templates expose reusable blocks for product lists, add-ons, forms, buttons, and offer content.
The Numi offer editor automation tab showing sequence controls beside the checkout canvas.
Automation is configured beside the offer so post-purchase work stays attached to the sale.

Feature detail