Where it fits
Merchants able to operate a WordPress store and validate payment, tax and fulfilment integrations.
Trade-offs and limitations
Extensions, gateways and external services have their own costs and terms. Core ownership does not transfer payment tokens or app data automatically.
Deployment and technology
WordPress, PHP and MySQL/MariaDB with scheduled store tasks. Self-hosting requires a supported deployment, capacity planning and a named maintainer. Consult the official installation guide for the current version.
Portability and integration
| API | REST APIs and webhooks; protect keys and validate extension endpoints |
|---|---|
| Authentication | WordPress users, roles and API credentials |
| Data export | Product exports, APIs and full database/files backups; verify extension-owned records |
Migration considerations
Reconcile products, variants, orders, refunds and stock. Rehearse checkout and preserve URL redirects.
Security and ongoing costs
Budget for infrastructure, implementation, monitoring, patching, backups, restore tests and user support. Check the supported release and current advisories with the project. An open licence is not a security guarantee.
Freedom score and exit difficulty
A complete, evidence-backed assessment of all 15 criteria is required before publishing a score. Exit difficulty depends on your customisations, data model, integrations and operating documentation. This profile does not claim a hands-on benchmark or a complete security assessment.
Primary sources
Profile reviewed 2026-09-13. Verify the exact release, edition and extensions before implementation.