Network Store Catalogue
Assigning a product instead of selling it
Putting a product onto a tribe yourself — for mandatory seats, levies and packages a tribe does not opt into — and what they see when you do.
Last updated September 2, 2026
Not everything a tribe pays for is something they choose. Mandatory software seats, network levies, compliance packages and brand-standard items are decided by head office and billed to the tribe regardless.
Setting a product's purchase mode to Assigned handles this. The product never appears on the storefront; you put it onto tribes yourself, and it bills exactly as if they had bought it.
Storefront or assigned
| Storefront | Assigned | |
|---|---|---|
| Visible in the shop | Yes | No |
| Who starts it | The tribe | You |
| Billed to the tribe | Yes | Yes |
| Appears in their orders and invoices | Yes | Yes |
| Can renew as a subscription | Yes | Yes |
The only real difference is who initiated it. Everything downstream — invoicing, receivables, renewals, reporting — behaves identically.
Assigning one
- Set the product to Assigned and give it the variant that carries the right price.
- From the subscriptions area, create the subscription against the tribe.
- Fill in anything the product asks for, including per-unit details where it collects them.
- Check the payment method — an assigned subscription still needs something to charge.
What the tribe sees
An ordinary order and, where it renews, an ordinary subscription. They can see what it is, what it costs and when it renews. What they usually cannot do is cancel it themselves — that is governed by the product's cancellation rules, and for mandatory items you would normally reserve cancellation to admins.
Assigning in bulk
Rolling something out to the whole network is the common case. Do a single tribe first and check the resulting order, price and renewal date before repeating it — a pricing mistake found on one tribe is a correction, and the same mistake across two hundred is a credit note exercise.