Use the QCMM Plan Details Page as a Customer

Read the Plan overview, features, term, price, imagery, comparison context, and Choose Plan action on the dedicated Plan Detail view.

This guide follows the accepted QC Memberships & Meetings 2.0.21 implementation and applies to All plans; customer. This category follows the commercial path from checkout through payment, discounts, tax, Site Credit, invoices, receipts, refunds, and preserved billing history. When older walkthrough or project-manual wording conflicts with 2.0.21 source or later accepted Authorized-Domain behavior, the current implementation takes precedence.

Before You Begin

• Confirm the Plan is published and its price, currency, duration, renewal behavior, and customer-entered fields are correct before accepting live payments.
• Use PayPal Sandbox for payment testing and Live credentials only after the complete test path is verified.
• Record the expected Promotion, Coupon, Site Credit, tax, and invoice result before testing so each adjustment can be checked independently.

Current QCMM Behavior

Step-by-Step Workflow

1. Open the QCMM screen that owns this workflow and identify the exact Plan, subscription, billing record, booking, user, or setting involved.
2. Review the current stored state, user role, Effective tier, and related automation before changing anything.
3. Perform the documented action with the narrowest appropriate permissions and a safe test object where possible.
4. Check the resulting administrator record and the real frontend experience for the intended customer/Host/editor role.
5. Record the final state so later troubleshooting can distinguish a configuration change from lifecycle or task-driven behavior.

the QCMM Plan Details Page as a Customer

Read the Plan overview, features, term, price, imagery, comparison context, and Choose Plan action on the dedicated Plan Detail view is part of the current QCMM 2.0.21 behavior. Treat the stored QCMM record and server-side authorization as authoritative: frontend controls guide the user, but QCMM still validates identity, ownership/access, current object state, entitlement, and request integrity when an action is submitted.

Keep the distinction between a reusable Plan definition and a purchased subscription snapshot. Administrators can improve or retire future catalog offers without rewriting the commercial and access context that belongs to an existing membership unless a dedicated migration/change workflow intentionally does so.

How This Fits into QC Memberships & Meetings

This category follows the commercial path from checkout through payment, discounts, tax, Site Credit, invoices, receipts, refunds, and preserved billing history. A reliable QCMM configuration keeps Joomla authoritative for users, groups, access levels, sessions, mail transport, and Scheduled Tasks while QCMM owns Plan, subscription, billing, scheduling, Meeting, Custom Field, resource, and member-facing state.

For Use the QCMM Plan Details Page as a Customer, verify the behavior with the role that will actually use it. Administrator, member, Host, and Fulfillment Editor experiences intentionally differ. A successful test as Super User does not prove that a normal user has the correct ownership, access, timing, or feature entitlement.

Permissions, Entitlement, and Data Safety

• Joomla menu access, QCMM object ownership/access, role-specific permissions, and commercial feature entitlement are separate checks.
• QCMM re-authorizes state-changing requests server-side; never treat a visible or hidden frontend control as the security boundary.
• Do not expose PayPal credentials, encrypted settings, legacy keys, private room credentials, or other secrets in screenshots, URLs, public documentation, or community posts.
• Preserve subscription, billing, booking, attendance, Custom Field, credit, and entitlement history when correcting a problem; current QCMM is designed to repair in place rather than erase evidence.
• When Effective tier falls, premium configuration/history is preservation-first: features can become unavailable without deleting the saved data.

Verify the Result

• The amount captured or credited matches the final QCMM balance after discounts, tax, and Site Credit.
• The billing record retains the intended Promotion/Coupon and payment-method snapshot.
• A membership checkout activates or updates the correct subscription; a standalone invoice payment remains a standalone billing payment.
• The customer can see the appropriate paid/due state and Pay Now action in the frontend when applicable.

Common Mistakes to Avoid

• Testing Live PayPal credentials before the Sandbox path and return/capture flow are proven.
• Assuming every PayPal funding button is always available; PayPal determines eligibility for optional methods such as Venmo or Pay Later.
• Recalculating historical discount context from a Plan that has since changed instead of preserving the billing snapshot.
• Using an unrelated membership checkout to collect a standalone invoice balance.

Troubleshooting

• Reproduce the exact action with the same user role and record identifiers before changing unrelated configuration.
• If the UI and stored state disagree, refresh the real frontend after checking the owning record and relevant Scheduled Task.
• Reproduce the exact action with the smallest safe test and record the user role, Plan/subscription/booking/billing identifiers, current state, and time zone where relevant.
• If a control is missing, check Joomla access, QCMM permission/ownership, record state, Effective tier, and task health before assuming packaged files are damaged.
• If behavior is asynchronous, inspect the owning Scheduled Task and its last result instead of repeatedly performing the business action.
• After a correction, rerun the same scenario from the real frontend; a successful Administrator save alone is not end-to-end verification.

Operational Best Practice

Treat the billing ledger as history, not a scratchpad. Test commercial rules in Sandbox or with a controlled zero/low-risk path, reconcile provider and QCMM states, and use dedicated invoice/credit/refund actions so later support can understand exactly what happened.

Community Discussion

Want to compare membership or Meeting workflows, share practical QCMM tips, or discuss how other Joomla site owners use this feature? Visit the QC Memberships & Meetings Community. For private support, bug reports, account-specific entitlement or billing problems, or feature requests, use the QuantaCade support system.