This guide is intentionally simple. It explains the normal shape of billing and plan changes without pretending there are already detailed public policies where they do not exist yet.
Billing should stay separate from server management
The billing area should handle:
- Orders
- Invoices
- Payment methods
- Service-level account details
The server panel should handle the server itself. Keeping those roles separate makes the account flow easier to understand for new customers.
Upgrades should be straightforward
If a plan is no longer enough, the expected path should be clear:
- Review the next plan up on the pricing page.
- Use the billing area to request or purchase the change.
- Confirm timing and any service impact before assuming the change is immediate.
The exact upgrade flow can evolve, but customers should not need to guess where to start.
Downgrades should be handled carefully
Downgrading is different from upgrading because resource limits matter. Before moving down a tier, confirm that the smaller plan still fits the server you are running.
If the server is already close to its limits, downgrading just to save money can create more problems than it solves.
Keep support language truthful
Until the business publishes precise policies, support and marketing copy should avoid promising:
- Instant plan changes in every case
- A specific refund outcome
- Migration behavior that has not been documented
- Detailed billing automation that may not exist yet
That keeps the public site accurate and avoids creating policy debt.
What to do next
If you are still picking a plan, start with How to choose the right Unturned hosting plan. If you already have a service and need day-to-day server tasks, go to How to restart, back up, and manage your server from the panel.