02 Reference workflow · Expand

In-Product Seat Expansion

A customer adds seats at the moment of need while PeakCommerce resolves the current subscription, prorated price, permissions, and resulting entitlements.

Initiated byCustomer or product agent

Intended outcome

Seats are added to the existing subscription, prorated billing is applied, and access is provisioned immediately.

ProductBillingEntitlementsCRMRevenue

Transaction path

From intent to completed outcome.

Usage reaches a seat threshold or a customer asks to invite more teammates inside the product.

01 · Detect

Recognize expansion intent

The in-product surface or agent identifies that the account needs additional capacity.

02 · Price

Resolve the exact amendment

Current contract terms, unit pricing, effective date, and proration produce an authoritative preview.

03 · Amend

Update the existing subscription

The transaction modifies the right account and subscription instead of creating disconnected new business.

04 · Provision

Make capacity available

Entitlements update immediately and billing, CRM, and revenue systems receive the result.

Commerce contract

One action. Explicit context and control.

Context required

Current subscription and contract term
Existing seat entitlement and usage
Account-specific unit price
Billing and revenue treatment

Guardrails applied

Authorized account role
Allowed seat range
Proration preview before commitment
No duplicate amendment on retry

REFERENCE REQUEST

POST /api/v1/subscriptions/sub_2048/change-quantity
Idempotency-Key: req_9b31
{
  "accountId": "acct_2048",
  "chargeId": "chg_seats",
  "newQuantity": 75,
  "editedField": "quantity",
  "catalogChargeId": "cat_seats"
}

PeakCommerce result

200 OK
{
  "status": "changed",
  "subscriptionId": "sub_2048",
  "quantity": 75
}

Availability and downstream effects depend on the billing and product integrations configured for the tenant.

Take the next step

Map this action to your commerce stack.

Start with this workflow already selected, then identify the billing, customer, and product systems involved in executing it.

Map this workflow →In-Product Commerce View API documentation