Definitions and Terminology

CRM System: Architecture, Data Flows, and its Role in the App Landscape

A CRM system is the core architectural component that masters customer and commercial process data. Its role is the system of record for accounts, contacts, and opportunities, while consuming real-time data from the ERP regarding stock levels, pricing, and invoice statuses.

The discussion about a "CRM system" differs from "CRM software" in perspective: it focuses not on the UI, but on data ownership and flow direction. This architectural view is critical for IT and leadership, as it determines long-term integration costs and scalability.

The golden rule: every entity has exactly one system of record. Commercial accounts and opportunities belong to the CRM. Inventory, invoices, and accounting entries belong to the ERP. Any deviation from this rule usually leads to expensive manual reconciliations and data silos.

In short

  • System of record for: account, contact, opportunity, quote, and activity.
  • Data consumer for: stock availability, list prices, customer balance, and issued invoices.
  • Synchronisation relies on stable unique identifiers, not names or formatted tax IDs.
  • Data flow direction is established at the design phase, not on a case-by-case basis.
  • Without strict deduplication rules, system integrity degrades within six months.

Data Flow between CRM and the Ecosystem

In a healthy B2B architecture, a confirmed order travels from the CRM to the ERP, which then returns the delivery status and the invoice. The customer balance is displayed in the CRM as read-only information, not as separately stored data. This ensures the sales representative sees credit blocks before promising a delivery date.

Technical Decisions for Initial Setup

Four fundamental decisions determine the long-term maintenance cost of the system:

  • The unique customer identifier across systems (VAT number or internal ID).
  • Sync frequency: real-time for stock levels, batch for historical data.
  • Conflict resolution: which system wins for specific field updates.
  • Data retention: handling records deleted in one system but present in the other.

Frequently asked questions

See how it works in CRMconnect

Native modules for sales, quoting and reporting, integrated with the ERP you already run.

From the same topic: definitions and terminology

All pages about definitions and terminology