What is a connection? The way an agent reaches one of your systems: reading where the data already is, writing only what you have allowed, with its own login and its own permissions. It is not an integration project.

# Built around the systems you run. Nothing is replaced.

Agents read your ERP, your customs window, your e-invoicing provider, WhatsApp and email where the data already is, and write back only what you allow, after the checks you set. Your team keeps the tools it knows.

[Talk to the team](https://qantara.systems/contact) / [Read the thesis](https://qantara.systems/original/thesis)

Every system you run was bought to keep something safe. We leave it where it is and work inside it.

## Read where it is, never copied

Most integration projects start by copying your data into a second system, which then has to be kept in step. An agent reads your ERP where the data already is, keeps a reference in the record, and writes back only past your threshold.

A reference, not a second copy. On the left, the usual way: your data copied into a second system, struck through, with what a copy costs. On the right, the agent reads your ERP in place and keeps only a reference; what it writes back waits at your threshold, the orange ring, until a person approves.

## What it reads, writes and never touches

One card per system, the same three lines on each. Your IT team sets the permissions behind every line before anything goes live.

| System | Reads | Writes | Never |
| --- | --- | --- | --- |
| ERP and accounting | Customers, prices, stock and open invoices. | Sales orders and delivery notes, after approval. | Changes master data. |
| Customs window | Nothing. | A declaration draft, for your broker. | Files on its own. |
| E-invoicing | Your invoices. | The e-invoice, once it passes the checks. | Issues one that fails. |
| WhatsApp Business | Messages from customers and suppliers. | Replies and reminders. | Messages a customer who has not consented. |
| Email | The shared inbox. | Drafts and replies. | Deletes anything. |
| Dealer management | Bookings, bays and parts. | A booking. | Moves a job without the adviser. |

## For your IT team

The only technical part of the page: how each connection signs in, what it may reach, and who can switch it off.

- **Its own login.** Each agent signs in with credentials of its own, never a person's, with the permissions your IT team chooses.
- **Scoped and revocable.** Credentials are scoped to one deployment and yours to revoke at any time. Every read and every write is a line in the log.
- **Built for each system.** Each connection is built during the embed, with your IT team, for the system it reaches.
- **When a system has no interface.** Connections are built system by system during the embed, starting with the ones the first process needs.

## In Arabic and English

The same order, as your ERP holds it and as the customer reads it on WhatsApp, in both scripts.

ERP field: Sales order 4471: ghee, 12 cartons; WhatsApp reply: Your 12 cartons of ghee are confirmed for Thursday.

## Three countries, three filing deadlines, one record

Saudi Arabia, the UAE and Oman each bring e-invoicing in on their own dates and their own rules, and every invoice reaches the authority through your e-invoicing provider. It is the connection every company here needs next, and the agent checks each invoice against its own country's rules before it goes.

## What IT teams ask

**Do we need to replace our ERP?** No. The agent reads it and writes back only what you allow; your ERP stays where your accounts are kept.

**Who gives the agent a login?** You do, with the permissions you choose. It never uses a person's login.

**What if our system has no API?** We build the connection during the embed, system by system, with your IT team.

**What if we change our ERP?** The record stays as it is, and the connection is rebuilt for the new system.

**Will it slow our systems down?** It reads the way a person does, on a schedule you set, so your systems carry no more than a busy clerk puts on them.

**What does it never touch?** Master data, payments, and anything you have not listed. It reads only what its process needs.

## Where the connections carry the most

- [E-invoicing and compliance](https://qantara.systems/solutions/e-invoicing): Every invoice checked before it is issued.
- [Orders and confirmations](https://qantara.systems/solutions/orders): Every order acknowledged and tracked.
- [Logistics and freight](https://qantara.systems/solutions/logistics): Quotes, bookings, customs and delivery, on time.

## Tell us what you run

Name the systems and the processes, and our engineers come on site knowing which connections to build first.

[Talk to the team](https://qantara.systems/contact) / [Email us](mailto:hello@qantara.example)

Muscat and across the Gulf

Next: [Control](https://qantara.systems/platform/control)

---

This is the Markdown twin of the page at https://qantara.systems/platform/connections