Packages and Trials

A package is the product. A line is an account; a package is what a reseller clicks to create one — the price in credits, the duration, the device types allowed and the content included, decided once by you and then sold a thousand times without another decision.

Open Packages → Add Package.

What a package fixes

Price and duration. The credit cost, and how long the subscription lasts — in hours, days, months or years. The reseller pays the credits; the customer gets the time.

What it may create. Line, MAG device, Enigma2 device — tick any combination. One package can cover all three, or you can price hardware subscriptions differently by splitting them.

Connection limit and outputs. How many simultaneous streams, and which delivery formats the subscription may use.

The content. The bouquets included — the entire channel decision, made here instead of at every sale.

Restrictions baked in. Forced server, forced country, ISP lock and the restreamer flag can be part of the product itself, so a “local-only” or a “wholesale” package enforces its own rules.

Trials

A package can be a trial: its own credit cost — often zero — and its own short duration. Trials are counted per reseller against the limits you set on their group, so “three trials per day” is policy, not hope. One switch disables trials panel-wide.

Who may sell it

Assign the package to reseller groups. A group only sees the packages you grant it, which is how the same panel sells a premium line-up through one tier of resellers and a basic one through another — same content, different products, different prices.

Packages are the vocabulary of the Reseller API too: packages lists what the reseller may sell, and create_line against a package debits the right credits automatically. Next: the bouquets those packages bundle.