Resolve partner authority
The partner sees and acts only on assigned accounts, products, and transaction types.
← Action Library
06 Reference workflow · Channel
Partner-Assisted Transaction
A partner configures and executes an order or amendment using customer-specific catalog, pricing, and permissions while the merchant retains control.
Initiated byPartner or reseller agent
Intended outcome
The partner creates the order against an assigned customer account while the merchant’s portal permissions, pricing policy, audit trail, and commission model remain in control.
Partner portalCRMCPQ or catalogBillingCommission data
Transaction path
From intent to completed outcome.
A reseller or implementation partner identifies a purchase, upgrade, renewal, or account-service opportunity.
Build the customer transaction
Existing products, pricing, contracts, and entitlements shape the available order or amendment.
Apply commercial controls
Exceptions route through the merchant’s approvals without breaking the partner workflow.
Execute and record the outcome
The standard commerce APIs record the order while the partner portal retains attribution for reporting and commission workflows.
Commerce contract
One action. Explicit context and control.
Context required
- Partner identity and assigned accounts
- Customer contract and subscription
- Partner-specific catalog and pricing
- Attribution and commission rules
Guardrails applied
- Partner-scoped account access
- Permitted transaction types
- Pricing and discount boundaries
- Approval requirements for exceptions
REFERENCE REQUEST
POST /api/v1/orders
Idempotency-Key: req_partner_42
{
"organizationId": "org_2048",
"items": [{
"productId": "prod_analytics",
"quantity": 1,
"priceCents": 40000
}],
"totalCents": 40000,
"currency": "USD"
}PeakCommerce result
201 Created
{
"id": "ord_partner_42",
"status": "confirmed",
"organizationId": "org_2048"
}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.