Skip to content

Single Source of Truth

A single source of truth provides a shared, reconciled data foundation. Authoritative sources, mappings and freshness must be traceable.

Also known asSSOT
APIs & Integration

Single Source of Truth, or SSOT, describes a shared, reliably reconciled data foundation referenced by people and applications. It can be a combined view of several authoritative systems. The term does not mandate a single physical database.

In a fictional example, a portal displays product data together. The productName field comes from the product information system, while availableStock comes from the ERP. The view links both values through an agreed product identifier. Which source confirms a value remains defined within that shared view.

Keep sources and freshness traceable

Define field meanings, identity mappings, change permissions and provenance. When values conflict, it must be clear which version is used and how the discrepancy is resolved. Simply collecting several exports does not solve that task.

Where transfers lag, show the known update state. A shared view does not make an old stock figure current or reserve an item. SSOT describes the reconciled foundation; synchronisation applies changes, while Master Data Management organises the rules for important master data.

Sources

Related terms

Articles on this topic

Guides · APIs & Integration2 minConnect CRM and ERP: define the data source for each fieldA completed field table defines sources and write directions. It separates contact maintenance, billing address and account state across CRM and ERP.Tobias KrügerNov 13, 2026
Insights · APIs & Integration2 minClarify an interface’s job before replacing itAn outdated connection may still carry important workflows. Its replacement needs clarity about effects, exceptions and open operations.Tobias KrügerNov 13, 2026
Insights · APIs & Integration2 minIntegrations need accountable owners after launchAn operating connection needs decisions about changes and incidents. Technical setup alone does not assign that responsibility.Daniel HartmannNov 13, 2026
Insights · APIs & Integration2 minIntegration effort depends on the data path you needTwo tools with APIs can require different preparation. The deciding factors are the required data, operations and permissions.Tobias KrügerNov 13, 2026
Insights · APIs & Integration2 minA shared data model needs agreed meaningThe same field can mean different things in a CRM and an ERP. The teams need to agree its meaning before defining a shared structure.Tobias KrügerNov 13, 2026
Insights · APIs & Integration2 minWebhook integrations need rules for repeat deliveriesControl the business effects of repeated webhooks. A missing acknowledgement must not trigger another order without checking.Tobias KrügerNov 13, 2026
Insights · APIs & Integration3 minUnclear customer mappings need a defined resolution pathResending does not resolve an unclear customer mapping. An integration needs a documented path from clarification to a confirmed target outcome.Tobias KrügerNov 13, 2026
Insights · APIs & Integration2 minTwo-way synchronisation needs explicit write rulesIf CRM and ERP can write, each shared field needs a conflict rule. The last message to arrive is not automatically the latest business decision.Tobias KrügerNov 13, 2026

APIs & Integration with ASES

ERP, CRM and shop cleanly connected

Request a quoteMore on APIs & Integration