Instead of Semarchy xDM
Stop renting Semarchy xDM. Own your supplier master records.
We build your version around your supplier checks and approval process, map your Semarchy exports and run it for you. Keep the evidence behind every chosen name, identifier and address.
Bring your Semarchy licence and services quote. The free supplier base has no licence fee.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the platform bill covers
Start with the supplier work behind the wider platform
Semarchy offers a broad master-data platform. If your immediate job is checking supplier records from several systems, compare that bounded process with a version you own. Review your actual licence, services and hosting terms before deciding what to replace.
A platform for many kinds of records
Semarchy names vendor data as a use case within its wider platform. This free base concentrates on supplier identity, source evidence and review.
Combining records from different systems
A supplier appears under several source IDs. Keep the relationship between those IDs and one master record, with a reason for each link.
Deciding which details to trust
A newer address can disagree with an older one. Select the source for each field and keep the explanation beside it.
The checking and approval process
Your business still decides who verifies evidence and who approves it. Put those decisions, owners and review dates into a process you control.
An explanation for later questions
Keep source versions and attributed decisions so a future reviewer can see why a record changed. Inspect the original documents when the facts are disputed.
Connections around the record
Source connections and team screens belong in the scope of your custom version. Map them against the features and services in your Semarchy agreement.
What your version does
A supplier record with evidence you can follow
Source intake
Bring in the records before combining them
Keep each source identity and each imported version. A fresh export becomes evidence for review, not an automatic approval.
- check Import a mapped supplier export after a test run
- check Keep the original exported values with their import batch
- check Skip a repeated batch and roll back a file with invalid records
- check Show unlinked sources beside masters that already have an owner
Identity review
Similar names never decide a match on their own
Suggestions show exact identifiers and matching names. The operator inspects identity before linking records.
- check Keep different companies with the same name visible
- check Refuse links with conflicting nonempty identifiers or countries
- check Show which source IDs belong to the same supplier
- check Keep a reason when a mistaken link is removed
Field decisions
Explain why each field won
Choose the name, identifier, country and address from linked evidence. Keep the source and reason for each choice.
- check Compare competing addresses alongside the selected value
- check See fields chosen from a different source than the supplier name
- check Flag masters when a linked source gains a newer version
- check Require fresh field choices when old source evidence is replaced
Weekly review
Keep yesterday’s approval from hiding today’s problem
The ready list checks the evidence each time it is read. Owners see missing fields, ageing sources and overdue reviews.
- check Require a reviewer who differs from every recorded editor
- check Remove records from the ready list when evidence becomes stale
- check Prepare branded review packs and change registers
- check Group unresolved checks by owner and export the current approved list
Make it yours
Design your own Semarchy xDM replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Semarchy xDM. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Semarchy xDM data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Supplier Master for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Supplier Master for Claude Code
Connected to your own database
Which suppliers have overdue checks or missing evidence?
SUP-002
- Rule
- DUE
- Issue
- Owner review is overdue
SUP-002
- Rule
- FIELD
- Issue
- Choose source evidence for name
SUP-002
- Rule
- FIELD
- Issue
- Choose source evidence for business_id
SUP-002
- Rule
- FIELD
- Issue
- Choose source evidence for country
SUP-002
- Rule
- FIELD
- Issue
- Choose source evidence for address
SUP-002
- Rule
- OLD_SOURCE
- Issue
- Evidence older than 180 days: ERP/V200
SUP-002
- Rule
- PURPOSE
- Issue
- Record the business purpose
| Code | Rule | Issue |
|---|---|---|
| SUP-002 | DUE | Owner review is overdue |
| SUP-002 | FIELD | Choose source evidence for name |
| SUP-002 | FIELD | Choose source evidence for business_id |
| SUP-002 | FIELD | Choose source evidence for country |
| SUP-002 | FIELD | Choose source evidence for address |
| SUP-002 | OLD_SOURCE | Evidence older than 180 days: ERP/V200 |
| SUP-002 | PURPOSE | Record the business purpose |
Ask it anything
Ten questions your supplier review can answer now
These reports run on the included demo. They are practical questions for your own records, not claims that Semarchy cannot produce equivalent custom reports.
Switching
How to switch from Semarchy xDM
The move involves exporting supplier collections, mapping your fields into the import, checking the resulting records, then running both systems side by side before you retire Semarchy xDM.
- 1
Export supplier collections
Export the supplier collections you want to move from Semarchy xDM. Semarchy documents CSV and Excel export, and the import accepts CSV. Include stable record identifiers and observation dates where they exist, along with the supplier fields you need. Check your Semarchy account and model to confirm which data you can export.
- 2
Map and test the import
Match the exported column headings to the supplier fields in the new database. Start with the import preview, which lets you test the mapping before loading records. Check that identifiers, dates and supplier values are matched to the right fields. Adjust the mapping if the preview does not reflect your supplier data.
- 3
Review the imported records
After importing, check the batch counts and review the new records and attention lists. Look for missing fields, duplicate suggestions and conflicting supplier values. Similar names are suggestions, not proof that two records belong to the same supplier. Resolve links and field choices using the source evidence before treating a record as ready.
- 4
Run both systems side by side
Keep Semarchy xDM available while you use the new database for the supplier process for a short period. Compare the supplier records, source versions and review decisions you rely on. Check that operators can find and review the evidence they need, and note any fields or rules that still need mapping.
- 5
Switch off Semarchy xDM
When the supplier records and review process have been checked, stop using Semarchy xDM for the supplier process you moved. Confirm which other record types, connections and permissions remain in scope before ending a wider Semarchy installation. Keep any original evidence you need under your own retention and recovery arrangements.
Where the real effort goes
The main work is usually mapping your supplier fields and rules, then deciding how much history to bring. Existing matching rules, attachments, permissions and upstream history need separate mapping. If you have Enterprise DNA install and run your version, they include this migration work in the scope and can customise it for your fields and rules.
Not ready for a call?
Get your Semarchy xDM switch plan by email
We will send you the step-by-step plan for moving your business off Semarchy xDM, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Semarchy xDM switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Choose how your business gets its version
Open source
Do it yourself
Free, open source
- 1 Clone the repo, run npm install and npm run demo
- 2 Open it in Claude Code, Codex, OpenCode or Cursor
- 3 Map your Semarchy CSV columns and test the import before applying it
- 4 Read the compliance guide, inspect source evidence and arrange your backups
Built around your business
We customise it
One setup fee, then a retainer for ongoing work
- check Your supplier fields, review rules and owners
- check Your Semarchy exports mapped and reconciled
- check Your team screen and source connections scoped around the work
- check Your reporting layouts and a different technical foundation if required
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed with access, evidence storage and backups arranged
- check Supplier checks and review packs prepared around your week
- check Mappings and reports maintained as source systems change
- check Run through Omni by Enterprise DNA alongside the rest of your business
Questions
Instead of Semarchy xDM, answered
Can this replace our whole Semarchy installation? expand_more
Start with the supplier process you want to own. The free version handles source evidence, field choices and independent review for trusted operators. We scope the other record types, matching rules, connections and permissions in your installation before recommending a replacement.
What will it cost compared with our Semarchy bill? expand_more
The free version has no licence fee. Hosting, your chosen assistant and your operating time are separate. Enterprise DNA charges a setup fee, then a retainer for customisation and operation. Bring your actual agreement so the comparison covers the work you use.
Can our existing supplier history come across? expand_more
Semarchy documents CSV and Excel exports. Map the columns from your supplier collection and test the import first. The import keeps exported rows and source versions. Existing matching rules, attachments, permissions and upstream history need separate mapping, which we include in the migration scope.
Who decides whether two suppliers are really the same? expand_more
Your authorised operator checks the source evidence. Similar names are only suggestions, and conflicting identifiers block a link. Each field choice keeps a reason. A different named reviewer records the approval. We build authenticated roles and any additional checks into your team’s version.
What happens when a source changes after approval? expand_more
A newer imported source version removes the supplier from the ready list until its links, field choices and review are brought up to date. The original versions remain available. Branded review packs show the evidence and open checks, while a custom team screen can make that review easier.
Bring your Semarchy quote and one awkward supplier record
Spend 30 minutes with Sam. Compare the platform bill with the supplier work you need, trace one conflicting record and agree what your own version should cover. If your current platform is the better fit, we will say so.
Supplier Master for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Semarchy xDM?
Get your version built