Private Pro category · 11 compositions
Pricing
Plan-comparison structures with placeholder commercial data only. These records are manifest-derived and source-free; an implemented status does not imply manual verification, release readiness, entitlement protection, or availability for purchase.
Manifest items
All 11 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Seat comparison
Feature matrix
Usage dimensions
Organisation inquiry
Update period explainer
Licence scope explainer
FAQ with plan context
Plan switcher shell
Add-on structure
Checkout handoff summary
Category contract
- Purpose
- Plan-comparison structures with placeholder commercial data only.
- Declared dependencies
- gummy-card, gummy-table, gummy-toggle-group, gummy-button
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Pricing blocks
Choose a pricing composition that matches the approved offer structure and the customer’s comparison task. Plans, billing intervals, seats, update periods, taxes, renewal behavior, and one-time terms need direct language; placeholder commercial values are never suitable for publication.
Render amounts and entitlements from one maintained commercial source and connect each action to the corresponding server-created checkout. Keep monthly, yearly, and lifetime distinctions explicit. Do not expose secret price identifiers or infer access from a client-side plan label.
Reconcile visible figures against live provider products before every release, then test currency presentation, tax handoff, failed checkout, cancellation, refund, and access outcomes. Licence and refund links must remain nearby, and unavailable purchase actions must say so rather than simulate success.
Handoff one versioned offer table containing plan names, billing intervals, amounts, seats, update windows, entitlements, renewal terms, provider references, and approved destinations. Record who reconciled it and when. Product UI, checkout creation, confirmation email, account access, refund behavior, and support guidance should all consume or verify that same commercial contract.
Boundary
Public pages contain only approved names, purposes, dependency aliases, requirements, status, and any future reviewed image preview. Editable paid source, test paths, release locations, and entitlement details remain private.