# IFS Cloud Customer Hierarchy: How to Sort and Manage It

> Source: https://netray.co/erp-help/ifs-cloud-customer-hierarchy-sort-and-manage
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

An IFS Cloud customer hierarchy arranges customers as parents and children under a named hierarchy. The tree order follows the structure you define, so to change what you see you change the structure, the node sequence if offered, or use list sorting and filtering on the underlying customers.

## Kind

how-to

## System

ifs

## Erp

IFS Cloud

## Module

Customer / Hierarchies

## Query

ifs cloud customer hierarchy sort

## Alternate Queries

- ifs customer hierarchy
- ifs cloud customer hierarchy parent child

## Applies To

IFS Cloud with the customer hierarchy functionality. Available sort controls differ by release, so verify on your version.

## Steps

### Organise and sort a customer hierarchy

**Items:**

- Open the Customer Hierarchy page and select the hierarchy you want to work on.
- Review the tree: each node is a customer placed under a parent, with its level.
- To move a customer, change its parent in the hierarchy rather than editing customer data.
- For ordering inside the tree, use the sequence or sort option on the nodes if your release offers it.
- For a sorted flat view, use the list view of the same data and sort by column header, such as name or customer id.
- Save, then reopen to confirm the order persisted.
- If you need a custom sort that the screen does not offer, export the data or read it via the API and sort downstream.

## Sections

### How the hierarchy is built

**Body:**

A hierarchy has a top node and children nested beneath it. Customers can belong to different hierarchies for different purposes, such as legal ownership versus sales territory.

Because the tree reflects relationships, it is not simply a sorted list. Alphabetical order only applies among siblings, and only where the page supports it.

### Why the order looks wrong

**Body:**

- The common causes are customers attached under unexpected parents, a hierarchy being viewed for a different purpose than expected, or sorting being applied to the flat list rather than the tree.
- Fix the structure first. Cosmetic sorting on top of a wrong structure just hides the problem.

### Governance

**Body:**

Decide who may change hierarchies, since a moved node can change credit exposure roll-ups, pricing agreements or reporting. Use permission sets to restrict maintenance and keep a record of changes.

## Pitfalls

- Assuming the tree is sorted alphabetically across levels.
- Moving a node without checking credit or pricing impacts.
- Using one hierarchy for several unrelated purposes.
- Giving broad edit rights to everyone.

## Ai Angle

An assistant over your IFS data can answer questions like which customers sit under this parent and which have no parent, and display the query it used. It is read-only and honours IFS permissions.

## Faq

### Can I sort the customer hierarchy alphabetically?

**Answer:** Where the page offers a sort or sequence option, yes among siblings. Otherwise use the flat list and sort by column. The options depend on your release.

### How do I move a customer to another parent?

**Answer:** Change its parent node in the hierarchy page and save. Check credit and pricing effects first.

### Can a customer be in two hierarchies?

**Answer:** Generally yes, since different hierarchies can serve different purposes. Confirm how your configuration treats this.

### Who should maintain hierarchies?

**Answer:** A small group such as sales administration, enforced through permission sets.

## Search terms

ifs cloud customer hierarchy, ifs cloud customer hierarchy sort, ifs customer parent child, ifs cloud customer structure, ifs cloud sales hierarchy, aurena customer hierarchy

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json