Operator Dashboard
Plans
Create and maintain the offers sold in a Wi-Fi zone.
Before creating a plan
Select the zone, define the commercial model and confirm the currency. A plan must have a name, price and limits consistent with the infrastructure. Test its portal display and purchase flow afterwards.
Plan types
| Type | Use | Controls |
|---|---|---|
period-based | Unlimited access for a period | duration, validity and session count |
time-based | Time quota | consumed duration and validity |
data-based | Data quota | allowed volume and exhaustion behavior |
smart-device-based | Smart device connection | MAC address, account required, device reconnect |
batch-based | Batch or bulk generation when enabled | quantity, prefix and generation rules |
Available types can depend on the backend and portal version. If a field is not offered by the UI, do not simulate it in another field.
Fields to check
- Name, description, badge: customer-facing presentation.
- Price and currency: amount actually requested.
- Duration and validity: consumption duration and activation window.
- Data volume: MB/GB limit or unlimited behavior.
- Concurrent sessions: number of allowed devices.
- Download/upload rates: infrastructure limits.
- Features: descriptive benefits associated with the plan.
- Guest purchase: only when supported by the type and flow.
- Active/popular/trial: visibility and promotion on the portal.
Publication lifecycle
- Create the plan after checking all values.
- Associate features and define the purchase mode.
- Save and verify the row in the list.
- Test the portal: price, duration, purchase options and displayed information.
- Disable a plan instead of deleting it when purchases or sessions already exist.
Changing an existing plan may affect new purchases but should not rewrite rights already delivered. For a new commercial rule, usually create a new plan version.