Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
167 changes: 139 additions & 28 deletions modules/crm/index.md
Original file line number Diff line number Diff line change
@@ -1,37 +1,148 @@
# CRM
# CRM Overview

The Customer Relationship Management (CRM) subsystem in @@name is used to manage customer relationships and other front-office activities of a company. It forms the foundation for managing customer interactions, from initial contact and opportunity tracking to final invoicing, ensuring full traceability across all customer-related processes.
CRM in @@name organizes the work with potential and existing customers through clearly defined records and documents — Leads, Contacts, Opportunities, Offers, and Orders.
The system guides users from the first interaction with a potential contact to a completed sale and subsequent invoicing.

## General concepts and processes
CRM in @@name manages the entire commercial process around sales. It is designed to structure sales work through clearly defined records, roles, and responsibilities, making the process intuitive for sales teams and reliable from a data and reporting perspective.

CRM manages the following sequence of documents and activities:
As sales teams grow, the need for structure, ownership, and visibility becomes critical. That is why @@name treats the Sales Representative (Sales Person) as a core element of the CRM process — Leads and Opportunities are owned by sales people, ensuring accountability and clear responsibility for every deal.

> *Activity* → *Opportunity* → *Offer* → *Sales order* → *Invoice order* → *Invoice*
At the same time, CRM in @@name allows you to start with minimal information, add structure only when it becomes logically necessary, and manage deals in a way that remains traceable, controllable, and scalable as the organization and workload expand.

- **Activity** - A generic action related to a party. Supports calendar appointments, reminders, questionnaires, and other activities such as meetings, visits, and contracts.
- **Opportunity** – A sales prospect with expected revenue and probability. Does not include line-level detail.
- **Offer** – A formal sales proposal (quote) that includes line items and allows optional selection of accepted items.
- **Sales order** – The main sales document created from the customer’s order. It initiates the logistics and financial processes related to the sale.
- **Invoice order** – An internal document used to track invoices that must be issued.
- **Invoice** – A legal and financial document that finalizes the sales process.
---

> [!NOTE]
>
> The above diagram shows only the CRM part of the whole process. <br>
> The full process involves many different modules of the ERP system.
## How @@name views the CRM process

## Structure
The **Lead to Cash** process is an established best practice in many CRM systems and describes the path from the first contact to actual revenue realization. @@name builds on these best practices and implements the process in an elegant and practical way, clearly separating the different stages and record types.

The CRM module consists of several **submodules**, each managing a specific aspect of the customer relationship and sales process.
The main CRM flow in @@name looks as follows:

---

Lead → (qualification / identification) → Party (Person / Company) → Opportunity → Offer → Sales Order → Invoice

---

## Lead

A **Lead** is a record representing a potential contact. It can store as much information as needed, but it is designed to be created quickly, without enforcing a large number of mandatory fields.

The purpose of the Lead is to capture interest in the system with minimal friction, while still allowing additional details, classifications, and custom fields to be added whenever they are available or relevant.

---

## Party (Person / Company)

A **Party** is a structured business entity – a registered company or individual for which minimal but required attributes must be provided. These are the data points the system expects in order for the process to continue – deals, offers, orders, and invoices.

@@name requires a Party to be identified before an **Opportunity** can be created. This is not a limitation, but a guarantee that every real deal has a solid data foundation – a system record from which the entire process can continue consistently.

---

## Opportunity

An **Opportunity** represents a potential deal – a business opportunity that is always linked to a specific Party. Multiple Opportunities may exist for a single Party (Person / Company).

An Opportunity reflects a specific expressed interest and a concrete possibility for a deal. From a single Opportunity, multiple offers can be created, which is one of the practical advantages of the system – it provides traceability of how many proposals were made before reaching a **Sales Order**.

Each Opportunity is assigned to a **leading Sales Person**, ensuring clear ownership, accountability, and visibility over who is responsible for advancing the deal through the sales process.

---

### Activities

Activities represent the actual sales work performed by sales representatives — meetings, calls, visits, demos, and other interactions with potential contacts and customers.

In @@name, Activities are closely linked to Opportunities and form the bridge between sales effort and sales results. Sales representatives use Activities to plan and report their work, while managers gain visibility into how deals progress as a result of real actions.

The relationship between Activities and Opportunities reflects real-world sales processes:

- a single Activity may lead to multiple Opportunities;
- a single Opportunity may involve multiple Activities over time.

By combining Activities with Opportunities, @@name provides a complete picture of both sales performance and sales effort.

---

### Lead to Order and Lead to Cash — what is the difference

In CRM documentation, the terms **Lead to Order** and **Lead to Cash** are often used.

**Lead to Order** covers the commercial part of the process — from the first contact to a confirmed sale. It includes:

- qualifying interest (Lead),
- identifying the business partner (Party),
- managing the deal (Opportunity),
- preparing proposals (Offer),
- confirming the agreement (Sales Order).

**Lead to Cash** extends this process to include invoicing and revenue realization:

- preparation for invoicing (Invoice Order),
- issuing invoices,
- tracking payments, depending on configuration and used modules.

If **Lead to Order** answers the question
*“Have we closed the deal?”*,
**Lead to Cash** answers
*“Have we completed it financially?”*.

---

### Lead to Cash

**Lead to Cash** covers the entire process. It includes the steps already described in Lead to Order and continues with the invoicing of the deal.

The process includes:

- preparation for invoicing (Invoice Order),
- issuing an invoice (Invoice),
- tracking due payments (depending on the modules and settings used).

In other words, if **Lead to Order** answers the question
*“Have we closed the deal?”*,
then **Lead to Cash** answers
*“Have we completed it financially?”*.

---

## What follows from the logic of the CRM process

This model has direct practical implications:

- the system controls the creation of Opportunities and requires the necessary company data (Party) that will be needed later in the process;
- the process guides the user and does not allow skipping key stages;
- each subsequent step has the required information available;
- sales activities become structured, visible, and traceable, making it clear which sales person is working on what and how deals progress;
- the process remains clear for sales users, administrators, and management alike.

This makes CRM in @@name predictable, learnable, and sustainable over time.

---

## What you will find in this section

The CRM documentation is organized to guide you gradually from the big picture to the details:

- **[Presales](./presales/index.md)** – working with Leads, Opportunities, and Offers
- **[Sales](./sales/index.md)** – how offers are converted into orders
- **[Pricing](./pricing/index.md)** – defining prices, discounts, and rules
- **[Invoicing](./invoicing/index.md)** – controlling the invoicing process, including Invoice Orders and issued invoices
- **[Marketing](./marketing/index.md)** – planning and executing marketing campaigns and managing distribution channels
- **[Sales Force](./sales-force/index.md)** – managing sales personnel, group structures, task assignment rules, and targets
- **[Subscriptions](./subscriptions/index.md)** – agreements for recurring services and periodic invoicing
- **[POS](./pos/index.md)** – managing point-of-sale operations in physical retail locations
- **[Client Center](./clientcenter/index.md)** – configuring a platform for customer engagement and self-service

---

## Getting started with CRM in @@name

If you are setting up the CRM module for the first time, it is recommended to start simple and follow the natural flow of the sales process.

Begin by exploring the **Presales** functionality to understand how Leads, Parties, and Opportunities work together and how interest is gradually converted into real sales potential. This provides a clear picture of the core CRM logic without requiring complex configuration upfront.

The next logical step is **Sales**, where this potential is turned into confirmed orders and the Lead-to-Order process is completed.

Once the core flow is in place, you can extend the process step by step with additional capabilities such as **Marketing**, **Sales Force rules**, **Subscriptions**, **POS**, or **Client Center**, depending on your business needs.

| Module | Description |
|---------|-------------|
| **[Invoicing](https://docs.erp.net/tech/modules/crm/invoicing/index.html?q=crm%20Invoicing)** | Oversees the invoicing process, including invoice orders and issued invoices. |
| **[Marketing](https://docs.erp.net/tech/modules/crm/marketing/index.html)** | Plans and executes marketing campaigns and manage distribution channels. |
| **[POS](https://docs.erp.net/tech/modules/crm/pos/index.html)** | Manages point-of-sale operations in physical retail environments. |
| **[Presales](https://docs.erp.net/tech/modules/crm/presales/index.html?q=crm)** | Handles opportunities, quotations, and pricing discussions. |
| **[Pricing](https://docs.erp.net/tech/modules/crm/pricing/index.html)** | Creates bonus programs, line discounts, product prices, promotional packages and similar price-related entities.
| **[Sales](https://docs.erp.net/tech/modules/crm/sales/index.html?q=crm%20Sales)** | Manages sales order documents. |
| **[Sales Force](https://docs.erp.net/tech/modules/crm/sales-force/index.html)** | Manages sales personnel, their group structures, assignment rules, and performance targets, providing tools to define, organize, and track the activities and objectives of sales representatives within the CRM framework.
| **[Subscriptions](https://docs.erp.net/tech/modules/crm/sales-force/index.html)** | Handles agreements with customers for periodic delivery of services and billing.
| **[Client Center](https://docs.erp.net/tech/modules/crm/clientcenter/index.html)** | Offers a single platform for customer engagement and self-service. |
Loading