Data models
Customer, product, supplier, and reference data, with golden records, cross-references, lineage, stewardship, and a change log. SQL models show how each one lands in your warehouse.
Match rules for customer, product, and supplier records, tested on your own data first.
Download the PDFA short PDF to share with your team. It covers what is in the package, how it works, and a worked example.
Your download has started.
We also emailed the link to . It works for 7 days.
Download didn't start? Get the PDF
Want to try it on your own data? Talk to us.
Names are spelled differently, emails carry tags, phones come in four formats, and two different people share a name and a ZIP code. Most MDM programs spend months configuring match rules before anyone sees a single result.
Customer, product, supplier, and reference data, with golden records, cross-references, lineage, stewardship, and a change log. SQL models show how each one lands in your warehouse.
Rules live in plain configuration files. Comparators include exact, Jaro-Winkler, token set, name tokens, and numeric. Survivorship can take the most recent, most frequent, or most complete value, or follow source priority.
Pairs the engine is unsure about go to a data steward. The steward’s decision overrides the score on every later run.
The evaluate command measures precision and recall against a labeled sample and fails CI below a floor you set. The explain command shows field-by-field scores for any pair. Each source gets a data contract template.
Names folded and nicknames expanded, emails normalized, phones put into E.164, addresses and IDs cleaned.
Only records that share a key, such as email, phone, or last name plus ZIP, get compared.
Each field has a comparator and a weight. The score is the weighted average over the fields both records have.
A threshold sorts each pair into match, review, or no match. Hard rules win, such as never merging two different tax IDs.
A steward decides the review pairs, and those decisions stick on every later run.
Matched records become one golden record. Survivorship picks each value, and lineage records where it came from.
Records from a CRM, an ERP, and an online store describe 150 real customers, with the mess real data has.
With the rules as shipped, the engine makes no false merges. Pairs with mistyped phones go to the steward queue, and the steward’s calls raise recall on the next run. The two James Smiths stay apart.
Ask about the Master Data Starter
Dex answers from our own pages and links to where it found the answer.
Bring a sample of your messiest records. We will walk you through a match run on them.