Status: Configuration: supported, but dependent on creator setup, provider credentials, or backend configuration.
Four readiness layers
- Product behavior - The user can complete the supported path and sees clear loading, success, failure, and recovery states.
- Backend truth - Payment, access, CRM, attribution, finance, and workflow outcomes are created and reconciled by authoritative services.
- Operational proof - Automated tests, browser checks, provider fixtures, observability, support runbooks, and rollback plans exist.
- Commercial readiness - Terms, pricing, payout policy, data processing, support expectations, and roadmap commitments are explicit.
Current gates to keep visible
- Affiliate Marketplace remains coming soon until certification passes.
- Provider-dependent payment, messaging, webinar, KYC, and payout experiences require their configured credentials and environment checks.
- A public partner API, published SLA, and buyer-grade operating metrics should be treated as open diligence work until formally published.
Evidence a future buyer should request
- A complete test fixture from checkout through verified payment, ledger entry, entitlement, refund, and reversal.
- Exactly-once proof for payment, commission, refund, chargeback, and provider retry scenarios.
- Tenant and role-isolation tests plus an incident and support runbook.
- A current capability matrix showing what is available, configured, coming soon, or planned.
- Named owners for unresolved policies such as bundles, coupons, order bumps, payout timing, and partner access.