The order matters: identity before invoices, automation before recurring billing, a tested gateway before the first customer.
Before you start
- The public address you will use, with HTTPS.
- An empty MySQL or MariaDB database and its own database user.
- Who owns billing, support and the website in your team.
- Your services, billing cycles, currencies, taxes and payment providers.
- Outgoing email credentials and a support mailbox somebody reads.
In this order
- Install and secure it
Run the installer, delete the
install/folder afterwards, and switch on two-factor sign-in for administrators. - Set the organization identity
Company name, address, sender address, language, currency and how invoices look.
- Start the scheduler
One cron job every five minutes. Without it nothing recurring happens: no invoices, no reminders, no imported replies.
- Connect payments
Activate a gateway, register its callback address and make a test payment that lands on the invoice.
- Build the catalog
Plan groups, plans, prices, add-ons and the welcome email for each product type.
- Prepare support
Departments with real mailboxes, knowledgebase categories and escalation rules.
- Publish the website
Edit the pages in the page builder, set your menus, and check light and dark mode on a phone.
- Test it end to end
Create a test client, place an order, pay the invoice, open a ticket, then remove the test data.
Acceptance test
A page that loads is not a working installation. The order-to-payment-to-ticket test above is what proves the parts are connected.
Full guide
The complete reference is Getting started in the WBAMS documentation.