> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Build a Client Registry That Feeds Everything
- URL: https://blog.jestor.com/build-a-client-registry/
- Published: 2026-09-17T22:40:06.000Z
- Updated: 2026-09-17T22:40:06.000Z
- Author: Bruno Bannach

To **build a client registry**, the client has to exist once and be referenced everywhere. Every process that stores its own copy of a client is a process that will eventually disagree with the others.

## What separate copies cost

The divergence is invisible until someone compares.

- The same company entered three ways across three processes
- Contact details updated in one place only
- No view of everything relating to one client
- Reporting that cannot group reliably

## What the registry should hold

| Element               | Why                                               |
| --------------------- | ------------------------------------------------- |
| **Identification**    | Registration number, so duplicates are detectable |
| **Readable name**     | Set as the display label for selection            |
| **Status**            | Active, inactive, or blocked                      |
| **Responsible owner** | Someone accountable for the relationship          |
| **Connections**       | Deals, tickets, contracts, and payments           |

## How to set it up in Jestor

1. Register clients in **Omie** so they appear automatically in **Jestor**.
2. Set the name field as the display label so selection shows names.
3. Connect deals, tickets, contracts, and receivables to the same record.
4. Surface those connections on the client card, filtered and read-only.
5. Scope permissions so account owners see their own clients.

## Why Jestor is the best complement to Omie for client data

The integration is native, with no middleware — so clients registered in the **ERP** appear as selectable records without a synchronization routine that could drift.

Because **Jestor** is relational, the client card becomes the single place to see the commercial, support, and financial relationship at once.

## Frequently Asked Questions

### Where should clients be registered?

In the ERP; they appear automatically. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Why set a display label?

So selection shows names rather than identifiers.

### Can one card show everything about a client?

Yes, through connected records.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.