> ## Documentation Index
> Fetch the complete documentation index at: https://docs.centipidbilling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Packages

> Create, order, publish, restrict, duplicate, and retire internet plans.

# Define the service you sell

Packages connect commercial terms—price and duration—with network policy such as access type, speed, data, device limits, schedule, burst, and NAS availability.

## Plan before creating

Decide:

* subscriber/access type;
* customer-facing name;
* price in the account currency;
* duration or data allowance;
* upload/download or combined speed policy;
* allowed devices;
* schedule and burst behavior;
* whether the package is visible/available on buy pages;
* whether it is limited to selected NAS devices.

## Create a package

1. Open **Network → Packages** and choose **Create Package**.
2. Select the package type.
3. Enter the name, price, duration, and current form-required fields.
4. Set speed, data, device, and other policy limits.
5. Configure advanced burst/schedule behavior only when the network supports it.
6. Add NAS restrictions if the plan should exist only at selected sites.
7. Save and review the detail page.
8. Test with one subscriber or captive purchase before broad publication.

## Visibility and merchandising

The package workspace supports status, popular/on-offer flags, ordering, and portal visibility. An active internal package can still be hidden from public buy pages. The package list calls out plans hidden from buy pages so operators can resolve accidental merchandising gaps.

Reordering changes how offers appear where ordering is respected. Use clear names and avoid several indistinguishable plans with different hidden limits.

## NAS restrictions

Leave the restriction empty to allow the package on every applicable NAS. Select routers to limit it. A restricted package can disappear from a captive portal reached through another NAS and cannot be assigned everywhere.

Use **Clear NAS restriction** only when the plan is intentionally becoming account-wide.

## Duplicate and edit

Duplicate a package to create a related plan while preserving an auditable source. Immediately review every copied field—especially price, duration, status, portal visibility, schedule, and NAS restriction—before enabling it.

Editing a package can affect future assignment and, depending on how network policy is applied, existing subscribers. Test consequential changes and communicate commercial changes deliberately.

## Retire or delete

Prefer disabling/hiding a package when subscriber or historical records still refer to it. Before deletion, review subscriber count, portal visibility, vouchers, invoices, and NAS restrictions. The application may block deletion when related records make it unsafe.

## Common issues

* **No packages in subscriber form:** choose the subscriber type first and confirm a compatible active package exists.
* **No packages on captive portal:** check Hotspot type, active/on-offer/public visibility, NAS restriction, and router context.
* **Wrong expiry:** inspect package duration and account timezone, then the subscriber's explicit expiry override.
* **Speed policy not applied:** verify subscriber assignment, active session reauthentication, NAS/RADIUS policy, and router service state.