P
EVO Product
Maintain a central internal product that can participate in different sales and fulfillment workflows.
Evoxup Membership Features
Everything Behind Your Membership Lifecycle.
Evoxup connects products, memberships, licenses, entitlements and external commerce in one WordPress-native platform — with a provider-neutral integration model that can grow with your business.
The Evoxup Feature System
MembershipsPlans, members, access lifecycle
LicensingIssue, verify, activate, stop
Products & PlansCentral product relationships
Universal IntegrationsWebhook, API, provider profiles
Product MappingExternal → internal routing
Product SyncProvider metadata synchronization
Security & FulfillmentVerify, deduplicate, record
Marketplace & UpdatesModular expansion and delivery
Membership Management
Memberships Built Around Real Products.
Create membership plans, connect them to products, manage members and keep access rules tied to the commercial event that created them.
PlansMembersExpirationEntitlementsProduct RelationsAccount Linking
Instead of treating membership as an isolated list of users, Evoxup makes the product relationship part of the membership lifecycle. A sale can lead to the correct product, plan, license and final entitlement without rebuilding the logic for each provider.
MEMBERSHIP OVERVIEW
PRO MembershipACTIVE
SUPER MembershipACTIVE
Expired AccessEXPIRED
Product-linked PlanMAPPED
LICENSE CONTROL
EVO-82AK-19PZACTIVE
EVO-4LMN-77QXSTOPPED
EVO-9KTR-31BDBLOCKED
EVO-1QWA-84TYEXPIRED
Licensing
Licensing That Belongs to the Product Lifecycle.
Issue, verify, activate, deactivate and control licenses alongside the product and membership that created the entitlement.
Issue KeysVerifyActivateDeactivateStopBlockPolicies
A membership product can grant access and licensing together, while a non-membership product can use licensing independently. The goal is one consistent product lifecycle rather than separate manual systems.
Products & Plans
One Internal Product Model Across Different Commerce Paths.
EVO Product acts as the central internal product identity so external providers do not have to define your membership architecture.
↔
Product ↔ Plan Relationships
Connect products and membership plans flexibly instead of forcing a one-product-one-plan model.
✓
Entitlement Outcome
Use the product relationship to determine membership, licensing and access outcomes after fulfillment.
SaleProvider or WordPress
EVO ProductCentral identity
PlanMembership relationship
LicenseOptional product policy
EntitlementsFinal customer access
Universal Integrations
Connect Providers Without Rebuilding Your Membership System.
Evoxup uses a provider-neutral integration layer. The provider can use signed webhooks, API verification, authenticated APIs or a custom workflow.
↗
Signed Webhooks
Use HMAC, provider signatures or webhook secrets when the platform supports them.
✓
API Verification
Verify incoming transaction data directly with the provider API before fulfillment.
≈
Unsigned Webhooks
Support providers that do not offer native signatures using an appropriate verification policy.
+
Custom Providers
Connect platforms beyond the ready-made profiles using the universal integration editor.
Ready-made profiles simplify known providers.
Explore Integrations →
Custom Provider keeps the advanced integration path open for everything else.
Automation
Product Mapping and Product Sync Solve Different Problems.
Routing and synchronization are separated so external metadata can change without altering your internal fulfillment logic.
Decide where the product goes.
Connect an external provider product to the correct EVO Product, Membership Plan or supported internal target.
- Discovered products
- Mapped / unmapped views
- Provider product IDs
- Plan inheritance
- Live route visibility
- Manual mapping when required
Keep provider metadata current.
Refresh external catalog data without rewriting your internal business routing or fulfillment configuration.
- Name and provider status
- Price
- Purchase URL
- Variants when available
- Manual synchronization
- Scheduled synchronization
- Missing-product detection
Provider Profiles
Simple for Known Providers. Advanced When Necessary.
A known provider should not force the user to understand every technical field behind the integration.
Ready-made Provider Profiles can expose only the settings that matter — for example credentials, verification policy and status — while the Custom Provider path retains the full advanced editor.
Secure CredentialsGuided SetupAdvanced EditorProvider Defaults
GUIDED PROVIDER
API CredentialSAVED SECURELY
Verification PolicyRequired
StatusACTIVE
Advanced Technical SettingsHidden by default
Security & Fulfillment
Verification Should Match the Provider — Fulfillment Should Happen Once.
Security is not one checkbox. Evoxup separates provider authenticity, transaction verification, duplicate protection and fulfillment recording.
Provider Verification
Use the strongest verification mechanism actually available from the provider.
Duplicate Protection
Repeated events should not create another membership, license or fulfillment email.
Secure Credentials
Provider credentials can be stored without being exposed back into the normal editor UI.
Traceable Processing
Keep enough processing context to understand verification, mapping and fulfillment outcomes.
EventReceive
VerifyAuthenticate
NormalizeProvider-neutral data
MapResolve product
FulfillGrant once
Modular Platform
Build the Evoxup Environment You Actually Need.
Advanced capabilities can remain modular instead of forcing every workflow into one oversized core plugin.
EXTENSIONProduct Mapping
External product routing.
EXTENSIONProduct Sync
Provider metadata synchronization.
EXTENSIONProvider Profiles
Guided provider integrations.
PLATFORMMarketplace
Discover and access Evoxup components.
PLATFORMUpdate Manager
Manage compatible updates and delivery.
Why Evoxup
A Feature Set Designed Around Architecture — Not Just Checkboxes.
1
Provider-Neutral
Commerce providers connect to your platform instead of defining your internal membership model.
2
Central Product Logic
Products, plans, licenses and entitlements remain part of one lifecycle.
3
WordPress-Native
Administration remains inside WordPress rather than requiring a separate external control panel.
4
Modular Expansion
Add advanced components when they are useful without turning the core into a monolith.
5
Security by Capability
Verification follows the provider's actual security model instead of applying one rule to every platform.
6
Clear Separation of Responsibilities
Mapping, synchronization, verification and fulfillment remain distinct so the system is easier to understand and maintain.
Explore Evoxup
Start With Membership. Expand Into Licensing and Universal Commerce.
Use Evoxup as the center of your WordPress product, membership and entitlement workflow — then connect the providers your business needs.