Hierarchy for customers

We have numerous customers that are part of a chain. These customers are owned and governed by one head office and they are the primary contact for accounts for all stores. These customers do not want to be receiving 20 statements for 20 stores. They would like one consolidated statement for their entire account. Additionally, having no link for the stores in our system does not reflect important factors of the accounts to our team members.
Can a hierarchy system be implemented where applicable stores can be grouped under one head office?

4 people like this idea
  • I have worked with several businesses that would like this feature, in particular, because QuickBooks Online (QBO) has a hierarchical customer structure and when integrating with DEAR they need to get rid of the hierarchy which is painful.  There are workarounds, but a true hierarchical parent-child customer structure would be much better.

    1 person likes this
  • Thanks Stan, a very valid point. Our accounting is with Xero so not sure how the integration would be affected. However, sounds like a parent-child relationship would indeed be more beneficial.

  • In the meantime, you could create an Additional Attribute for customers, and add the parent as the additional attribute.  It is far from a hierarchical structure but could provide you some reporting on a parent customer basis.

  • Yes very needed feature

    1 person likes this
  • Thanks Stan, will keep the attributes option in mind. Unfortunately, it doesn't help me with creating with consolidated statements.

    1 person likes this
  • To be clear, and to reiterate, I think this is a feature that many companies would like and some have been upset when learning that DEAR does not support it, particularly when coming from QuickBooks.  For those using hierarchical customers in QBO, integrating with DEAR has required them to change their accounting operations, or do some integration gymnastics the maintain the parent-child customers to QBO.

  • This looks like a great idea! In our use case a hierarchy could help with tracking relations between dealers and end-users who we also need to keep in our records (currently using another crm).

    So a way to manage it in the UI as well as via the API would be beneficial.

Login or Signup to post a comment