The Zuora partner portal Experiences doesn't ship — production-ready for resellers today.
Zuora Experiences is Early Access and focused on direct My-Account-to-storefront surfaces. PeakCommerce is the GA, Zuora-native partner portal for channel commerce — co-branded, partner-scoped amendments, proration, multi-entity, and real-time commissions sourced from Zuora invoices.
Trusted by Leading Companies
Zuora-powered businesses like Act! and Campaigner use reseller channels to grow — partners who manage end-customers' subscriptions much like an internal CSR would. PeakCommerce gives those resellers a co-branded portal that runs the same Zuora amendment workflows, scoped to their book of business.
A Zuora-native partner portal — built for resellers
Every partner action flows through your Zuora billing engine, with the catalog, amendments, and invoices scoped to each partner's end-customers.
Native Zuora integration for partner transactions
Partners transact directly against your Zuora product catalog and rate plans — no middleware, no duplicate catalog. PeakCommerce reads rate plans, charge models, and amendment types from Zuora and presents only the SKUs each partner tier is allowed to sell.
Partner-scoped subscription management
Resellers run the same Zuora amendment workflow a CSR would — upgrades, downgrades, add-ons, seat changes, mid-term changes — but constrained to the customers in their book of business. Proration, subscription versions, and effective dates all come from Zuora.
Revenue and commission tracking from Zuora
Commissions are calculated from posted Zuora invoices — not estimates. PeakCommerce attributes every Zuora invoice line to the responsible partner and exposes real-time commission earnings, tier progression, and revenue forecasts inside the portal.
Co-branded, white-label experience
Partners log into a portal that looks and feels like their own. Brand the header, colors, and email notifications per partner — while transactions still flow through your Zuora tenant under your billing relationship.
Access controls and permission tiers
Define exactly what each partner tier can see and do in Zuora — from read-only invoice access for referral partners up to full amendment authority for gold-tier resellers. All permissions are enforced at the API layer, not just hidden in the UI.
No middleware between partners and Zuora
Resellers see only their own end-customers
Calculated from posted Zuora invoices
Reseller channel live on your Zuora tenant
A reseller upgrading an end-customer's Zuora subscription
See how a Campaigner-style reseller runs a mid-term Zuora amendment from inside the partner portal.
Marcus Rivera
Senior Account Manager at a Zuora-powered reseller
"An end-customer wants to grow from 50 to 200 seats on the Pro Plan, mid-term, with prorated billing on their existing Zuora subscription."
Marcus signs into the co-branded Zuora partner portal
He sees only the end-customers in his book of business — their active Zuora subscriptions, current rate plans, subscription versions, and upcoming renewal dates — all read directly from Zuora.
Opens the customer's Pro Plan subscription
PeakCommerce surfaces the subscription's current Zuora rate plan charges, effective dates, and term. The customer is on a per-seat tiered rate plan, currently provisioned for 50 seats.
Initiates a Zuora amendment to expand seats
Marcus selects "Update quantity" and changes seats from 50 to 200. PeakCommerce calls Zuora's amendment API to preview the proration, showing the credit for unused seats and the new charge for the remaining term.
Applies the partner-tier discount within guardrails
His gold-tier permissions allow up to 25% discount. He applies 15% — the API rejects anything higher. Zuora recalculates the amended subscription with the new pricing.
Posts the amendment to Zuora
PeakCommerce writes the amendment to Zuora, creating a new subscription version. The end-customer receives a co-branded confirmation; the next Zuora invoice reflects the prorated change automatically.
Commission updates from the Zuora invoice
When Zuora posts the invoice, PeakCommerce attributes it to Marcus's partner account and updates his commission earnings — no manual reconciliation, no spreadsheets.
Experiences focuses on direct customers. Channels need a different surface.
Zuora Experiences is positioned as "My Account today, full e-commerce tomorrow" — for end customers. Reseller and channel workflows aren't part of the announced scope. PeakCommerce already runs a Zuora-native partner portal in production.
| Channel commerce capability | Zuora Experiences (EA, direct customers) | PeakCommerce Zuora Partner Portal (GA) |
|---|---|---|
| Partner-scoped Zuora catalog | Not in scope — Experiences surfaces the direct customer's view of the catalog. | Each partner sees only the rate plans, charge models, and SKUs their tier is allowed to sell, scoped per partner from your single Zuora catalog. |
| Partner-initiated Zuora amendments | Not in scope — Experiences Agent + Builder are oriented to end-customer self-service. | Resellers run upgrades, downgrades, add-ons, seat changes, mid-term changes, renewals, and cancellations via Zuora's native amendment API — with tier-defined guardrails enforced at the API. |
| Commissions from posted Zuora invoices | Not addressed by Experiences. | Every Zuora invoice line attributed to the responsible partner; percentage, tiered, hybrid, and multi-currency commission models in production. |
| Multi-entity / multi-currency partner routing | My Account framing assumes a single direct relationship per customer. | Partner transactions are routed to the correct Zuora entity by geography, business unit, or product line; multi-currency rate plans surfaced per partner. |
| Co-branded / white-label portals | Builder is your brand, for your direct customers. | Per-partner branding, logo, color scheme, emails, and custom domains so each reseller's end-customers see the partner's brand. |
| Identity, RBAC, governance | Pre-wired identity in EA Experiences for direct customers. | Production RBAC enforced at the API layer — referral, silver, gold tiers with discount caps, amendment-type restrictions, and data isolation per partner. |
| Agent surface | Experiences Agent is part of the EA Experiences platform, aimed at direct customer flows. | API-first commerce that is a first-class client for any agent. Agents quote, transact, amend, and service Zuora subscriptions through the same APIs as the storefront — including partner-scoped reseller copilots reconciling commissions on a partner's book of business. |
| Architecture / agent-first foundation | Experiences is a new UI/agent layer on top of Zuora's 18+ year-old billing core — not designed agent-first. | Headless, agent-first architecture from day one. Every commerce capability is an API tool, not a UI screen retrofitted for agents. |
| Billing provider flexibility | Zuora only. | Multi-billing: Zuora, Stripe Billing, Maxio, Orb, Metronome. Resellers can transact on the right billing backend per region or product line. |
| Third-party integration components | Closed Zuora ecosystem. | Native integration components for Salesforce, HubSpot, Zendesk, Intercom, Segment, Snowflake — partner activity flows into the systems your channel team already uses. |
| Tailored experience per user | Builder produces shared direct-customer surfaces. | Per-partner, per-tier, per-user tailoring of catalog, pricing, branding, entitlements, and UX — co-branded for every reseller. |
Zuora and Zuora Experiences are trademarks of Zuora, Inc. PeakCommerce is an independent commerce platform built natively on the Zuora API.
Zuora partner portal vs. generic reseller tools
Why a Zuora-native partner portal beats bolt-on PRM tools and middleware-based reseller integrations.
Generic PRM / Middleware
PeakCommerce (Zuora-native)
Zuora partner portal — common questions
Looking at Zuora ecommerce more broadly?
The Zuora partner portal is one of six surfaces PeakCommerce powers on your Zuora tenant. See how storefronts, self-service, CSR, conversational commerce, and payment pages share the same Zuora APIs.