Mapping workspace
Inspect the evidence. Understand the exception. Keep a traceable decision.
| Supplier record | Property | Master identity | Score | Decision | Review |
|---|
Scores are deterministic demo signals, not probabilities. All initial hotel profiles are fictional. Conflicts block automatic mapping.
Bring in supplier records.
Import a CSV with supplier, code, name, country, city, address, lat and lng. Optional columns: masterId, status. Required minimum: supplier, code, name and country.
Start with the sample.
The sample supplier file includes exact matches, aliases, sparse records, conflicts, and source-specific suspensions. Your master catalog remains the supplied demo catalog.
Repeated identical rows are skipped. Changed source records are reevaluated and previous mapping approvals for those rows are cleared. Local source pauses remain until explicitly resumed. A row missing from a file is never silently suspended. A full audit event records the update summary.
Decision coverage
All source records, including unresolved and inactive profiles.
Supplier summary
| Supplier | Rows | Mapped | Review / issue |
|---|
The share of records mapped is a coverage measure. Mapping accuracy requires an independently verified labeled dataset. This demo does not claim a measured accuracy rate.
Local decision history
Imports, rule changes, and review actions on this browser.
Guardrails that stay in place
- Country and material geographic conflicts block automatic acceptance.
- A close alternative candidate requires review.
- A known master ID is corroborated against source evidence.
- Duplicate conflicting source codes are held for investigation.
- Supplier suspension never deactivates the canonical hotel.
- No model trains itself from unverified reviewer choices.