Skip to main content
A customer family is a parent customer with one or more child customers: a holding company and its subsidiaries, a headquarters and its regional offices. Each child keeps its own subscriptions, contacts and portal access, but the family relationship is what allows a child’s subscriptions to be invoiced to the parent through roll-up billing. Set up a family when a group wants one consolidated invoice while usage and revenue stay attributed to the entity that consumed it. See Manage Customers for the customer record itself.
The parent relationship is set in the dashboard. It is not part of the public customer API, so a customer created with POST /customers has no parent until you assign one in the dashboard.

​
Who uses this

​
How families work

A customer family is a single-level hierarchy:
  • A parent is any customer that has children. There is no explicit “make this a parent” action; a customer becomes a parent when another customer is assigned to it.
  • A child has exactly one parent.
  • A standalone customer has neither.
Nesting is one level deep: a parent cannot itself be a child.

​
Configuring a family

​
Assign a parent when creating a customer

  1. Go to Customers and click New Customer.
  2. Fill in the standard fields (name, email, address, currency).
  3. In Parent Customer (Optional), select the parent. Only customers that do not already have a parent are offered, which prevents circular or multi-level hierarchies.
  4. Save.

​
Change or remove a parent

Open the child customer’s profile, change or clear the Parent field, and save.

​
See the relationship

A child’s profile shows its parent as a link; a parent’s profile lists its children.

​
System behaviour

​
Edge cases

  • Removing a parent from a child with roll-up subscriptions: schedules are recalculated and future invoices go to the child directly. Issued invoices are not changed.
  • Moving a child to a different parent: schedules for the old parent, the new parent and the child are all recalculated.

​
Impact elsewhere

​
Example

Acme Corp has three regional offices and finance wants a single invoice. Each office has its own subscription. With roll-up billing enabled on each child subscription, Acme Corp receives one invoice with line items grouped by subsidiary, while usage, entitlements and revenue remain attributed to each office.

​
FAQ

Can a customer be both a parent and a child? No. Only one level is supported. What happens to children if I delete the parent? They become standalone customers. Any roll-up billing on their subscriptions is recalculated. Does assigning a parent consolidate billing automatically? No. The family is the prerequisite; enable roll-up billing per child subscription. See Roll-up billing. Can I change a parent after subscriptions are active? Yes. Billing schedules for everyone affected are recalculated. Issued invoices are untouched; the change applies to future periods. Is there a limit on children per parent? No system-enforced limit.