Choose a workflow
This reference describes the reviewed EmailaBiller source release. Features available through a separately installed module depend on that module's exact version, signature, enabled state and connection test. A provider name in a compatibility adapter is not a bundled or activated provider account.
| Work | Detailed guide |
|---|---|
| Business overview, work queue and search | Find staff work |
| Customer records and delegated staff | Customer administration |
| Products, prices, configuration and product addons | Product catalogue |
| Checkout and order activation | Order lifecycle |
| Invoices, PDF, statements and bulk tools | Invoice administration |
| Receipts, refunds, credit and reconciliation | Payment ledger |
| Bank instructions and manual settlement | Offline payments |
| Domains, TLD prices, renewals and nameservers | Domain operations |
| Hosting delivery and provider access | Hosting operations |
| SMTP, templates and delivery recovery | Mail configuration |
| Tickets, departments, replies and help articles | Support workspace |
| Brands, regional storefronts and legal sellers | Brand configuration |
| Scheduler, billing and service policies | Automation reference |
| Themes, modules and premium addons | Module installation |
| Webhooks, hooks, contracts and developer examples | Developer entry point |
Provider coverage and status
The reviewed complete product source contains 29 payment packages, 18 registrar packages, 13 hosting-panel packages and 5 native addon packages, each with an individual manual and exact configuration fields. It also retains compatibility for separately installed NameSilo, ResellerClub and PKNIC assisted modules. Bank Alfalah Alfa remains a configuration-only placeholder; its fields do not enable checkout.
The currently approved licensed product archive can contain an earlier subset. Source availability does not install newer contracts or qualify a provider account. Review the complete integration availability and capability matrix for every package, release boundary and explicit limitation.
Before changing a running installation
Use the exact selected release's package and current permissions. Start external tests in an isolated environment with that provider's genuine test credentials. Preserve .env, APP_KEY, database, private licence identity, storage and provider submission evidence. Documentation describes application behavior; it does not certify merchant approval, delivery, registry acceptance or root-server recovery.