13th August 2009 by Henrik Liliendahl Sørensen
When doing B2C (business-to-consumer) activities often you really want to do B2H (business-to-household). But sometimes you also actually want B2C, having a dialogue with the individual customer. So yet again we have a Party Master Data hierarchy, here households each consisting of one or several consumers (typically a nuclear family). In Data Model language there is a parent-child relationship between households and consumers.
The classic reason for wanting to identify households is that it’s a waste of money sending several printed catalogues and other offline mailings to the same household. But a lot of other good reasons based on a shared household budget exist too.
Data captured about consumers could look like this (name, address, city):
Here it seems fair to assume that we have:
(About party master data entity types please have a look here.)
But this is an easy example compared to what you see when working with names and addresses. Among complications I have seen are:
In other words: The real world is not that simple and the picture of how households are forming does change.
Available composable methods for maintaining household information are:
(Original online location)
Practical International Data Management Online. A free resource from GRC Data Intelligence. For comments, questions or feedback: email@example.com