Compatibility
Keep supported Moodle, PHP, payment gateway, privacy, cron, and browser behavior dependable across releases.
Open-source roadmap
Build the roadmap with us.
ModernCommerce evolves through source-backed product needs, Moodle compatibility work, reproducible issues, and community contribution. The roadmap describes direction, not a paid entitlement or guaranteed delivery schedule.
Current releaseModernCommerce 2.1.8Moodle 5.2 · PHP 8.3+ · GPL-3.0-or-later
How priorities are set
Evidence before promises.
A roadmap item becomes credible when the user problem, Moodle boundary, operational impact, security implications, and maintainable implementation are understood.
Operational depth
Improve the workflows staff use to investigate payments, fulfil access, serve customers, and reconcile commerce records.
Extension quality
Strengthen documented events, services, add-on contracts, test coverage, and stable boundaries for Moodle developers.
Open-source value
Prioritize capabilities that make Moodle a stronger place to sell learning without imposing a closed platform dependency.
Active direction
What the project is working to improve.
Sequence changes as source review, testing, contributor capacity, and release readiness allow.
Release quality and Moodle compatibility
Regression coverage, upgrade safety, documentation accuracy, dependency hygiene, accessibility, performance, and supported-environment verification.
Payment and fulfilment resilience
Clearer webhook evidence, reconciliation, failure recovery, order-state visibility, subscription operations, and administrator diagnostics.
Add-ons and integration contracts
Stable patterns for optional gateways, tax services, communications, reporting, fulfilment, and organization-specific workflows.
Documentation and implementation guidance
More task-led examples, production checklists, architecture explanations, troubleshooting paths, and contributor onboarding.
Influence the roadmap
Bring evidence that maintainers can act on.
Describe the Moodle context, user outcome, current behavior, reproduction steps, affected version, operational impact, and a safe definition of done.
A roadmap is not a contract
Items may change when source constraints, Moodle APIs, security findings, compatibility requirements, contributor availability, or stronger evidence changes the right solution.
Learn how to support developmentHelp turn priorities into maintained releases.
Funding expands the time available for compatibility, payment resilience, documentation, and careful delivery—not promises or private control of the roadmap.
Support development
Voluntary support. The core stays GPL.