I've seen many posts about Parent-Child customer relationships, but none provide a complete definition of what actually happens in the application. Neither the Online Help, LCS nor Suite Answers offers a detailed explanation of how this works when configured—and you need to already know the right questions to ask to find anything useful.
After testing in our sandbox, I have a few concerns:
- How Child customers are displayed after setup
- The system doesn't automatically inactivate the former standalone customer, causing CSR confusion
- Opportunities created under the Parent aren't visible to the Admin role in global search, but are visible to Sales Manager
Other questions I'm trying to figure out:
- How are credit limits, open balances, and payment application handled?
- How does pricing work (standard and Sales Contract)?
- Is transaction history preserved under the Child or rolled up to the Parent?
- Is there effective dating?
- Do workflows, saved searches, or scripts need updating?
- What permissions are required, and are there other visibility issues?
- Can a Child have its own Child (multi-level hierarchy)?
- What happens if the relationship ends later?
Any documentation, best practices, or lessons learned would be greatly appreciated.