1. What Is This Feature?
Organisations (sellers) in Virta are arranged in a tree hierarchy — every organisation has a parent, forming a chain up to a root organisation. The Change Parent feature allows moving an organisation from one parent to another.
This is needed when organisations restructure, get acquired, or need to be reassigned for operational reasons.
Changing a parent is a sensitive operation because it can affect billing, pricing, roaming connections, loyalty plans, and module access. For this reason, the system runs a comprehensive set of checks before allowing any change.
2. When Can a Parent Be Changed?
A parent change is allowed when:
The organisation has the Change Parent module (
cs_change_parent) enabledThe user has the required permission (
organisation_change_parent)Both the organisation and the new parent exist
None of the blocking conditions listed below apply
There are also two special cases that are always allowed without checks:
Moving to "Deleted Customers" — this is always permitted (used when decommissioning an organisation)
Same parent — if the new parent is the same as the current parent, no changes are made
Please note: This feature is currently available to selected customers only. Please contact your Customer Success Manager for more information.
3. When Is a Parent Change Blocked?
The system checks the following conditions. If any of them apply, the change is blocked and an error message is shown.
Organisation Structure
Condition | Why it's blocked |
|---|---|
The new parent is an individual-type seller | Individual sellers cannot have sub-organisations |
The move would create a loop (e.g., making a child the parent of its own ancestor) | Circular hierarchies are not allowed |
The organisation has CPO pricing groups | Pricing group memberships would become invalid |
Charging Solutions
Condition | Why it's blocked |
|---|---|
The organisation belongs to a charging solution, and the new parent is outside that charging solution | Organisations must stay within their charging solution boundary |
Pricing
Condition | Why it's blocked |
|---|---|
The organisation inherits pricing from its current parent and has no pricing setup of its own | It would lose its pricing configuration after the move |
The Pricing Engine detects tariff plan participation conflicts | Active tariff plan memberships would become invalid |
Billing
Condition | Why it's blocked |
|---|---|
The organisation uses Procountor billing, has a different contractual CPO than both itself and the new parent, and has no billing record | Billing configuration would be broken after the move |
Modules
Condition | Why it's blocked |
|---|---|
The organisation has paid modules that the new parent doesn't have | Module access would be lost |
The organisation has any modules (paid or unpaid) that the new parent doesn't have | Module access would be lost |
Loyalty Plans
Condition | Why it's blocked |
|---|---|
The organisation is a direct CPO participant in its current parent's loyalty plans | Loyalty plan participation would become invalid |
The organisation's sub-sellers are EMP members in the current parent's loyalty plans | Sub-seller loyalty memberships would become invalid |
Roaming Connections
Condition | Why it's blocked |
|---|---|
The organisation or any of its sub-organisations has an active Hubject roaming connection | Active roaming connections must be deactivated first |
The organisation or any of its sub-organisations has an active OCPI connection (Hub CPO, Hub EMP, Sub CPO, or Sub EMP) | Active OCPI connections must be deactivated first |
4. What Happens After a Parent Change?
When a parent is successfully changed:
The organisation moves to the new parent in the hierarchy. All its sub-organisations move with it (they keep their relationship to this organisation, but the whole subtree is now under the new parent).
Downstream systems are notified — search indices are updated and a domain event is published so other Virta services can react to the change.
If the organisation is private, its OCPI location visibility may be updated.
Stations are not affected — they remain assigned to the same organisation. Only the organisation's position in the tree changes.
5. How to Change a Single Seller's Parent
Use Virta Hub to change the parent from the organisation edit page. The system validates the change before saving. If validation fails, an error message explains why the change was blocked.
6. Required Permissions
To change an organisation's parent, the user needs:
Requirement | Description |
|---|---|
| Must be assigned to the user's role for the target organisation |
| Must be enabled for the organisation |
7. Frequently Asked Questions
1. What happens to sub-organisations when I change a parent?
They stay attached to the organisation you're moving. The whole subtree moves together. Sub-organisations keep their existing parent (which is the organisation you moved).
2. Can I move an organisation to a completely different part of the tree?
Yes, as long as it passes all validation checks. The main constraints are charging solution boundaries, module compatibility, and inactive roaming connections.
3. What if the validation fails?
The error message tells you exactly which rule blocked the change. Common fixes:
Deactivate roaming connections before moving
Ensure the new parent has the same modules
Set up the organisation's own pricing before moving away from a parent that provides it
4. Can I undo a parent change?
Yes — change the parent back to the original value. The same validation rules apply in reverse, so make sure the original parent still meets all requirements.
5. Why is the bulk tool limited to 100 organisations?
Each parent change triggers validation, database updates, and event propagation. Processing too many at once could impact system performance.
6. I changed the parent but nothing seems different — is that expected?
If the organisation was already under the specified parent, the system detects this and makes no changes. This is shown as a green "already correct" status in the SAM tool.
7. Do stations move when I change the parent?
No. Stations belong to an organisation, not to a position in the tree. They stay assigned to the same organisation regardless of where it sits in the hierarchy.