What is the operating record? One memory of what moved, where, when, for whom and at what cost, written by your agents and your people. It is not a new ERP; it sits beside the one you have.

# One record of how your company runs.

Every order, shipment, invoice, declaration and promise your agents and your people touch is written to one record: what moved, where, when, for whom, at what cost and why. The next agent starts from what the last one wrote.

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

The record, filling one row at a time. Each row comes in from the channel on the left and says what moved, where, when, for whom, at what cost and why. The orange column is the one no ERP keeps.

| What | Where | When | For whom | Why | Written by |
| --- | --- | --- | --- | --- | --- |
| Order confirmed | Sohar branch | Sun 08:40 | A caterer | Weekly order | Written by the orders agent, from a WhatsApp message. No approval needed: inside the thresholds. |
| Delivery moved | Muscat warehouse | Sun 11:05 | A hotel group | Supplier late | Written by the supplier follow-ups agent, from the supplier's email. No approval needed. |
| Invoice issued | Head office | Mon 09:20 | A caterer | Delivered in full | Written by the orders agent, from the delivery recorded in your ERP. No approval needed. |
| Discount given | Dammam branch | Mon 14:10 | A contractor | Repeat buyer | Written by the sales manager, from their note of the call. Approved by the sales manager, above the agent's limit. |
| Short delivery | Sohar branch | Tue 07:55 | A supermarket | Carton short, signed | Written by the orders agent, from a photo of the signed delivery note. Approved by the warehouse lead. |

A decision made on a call leaves no record. Every agent writes one, so the next can read it.

## What is in it, and what may be done to it

In the record: parties, orders, shipments, invoices, declarations, promises, thresholds, approvals, log entries.

What an agent may do to it: reads, proposes, writes within your thresholds, asks above them.

## The next agent starts where the last one ended

Nobody tells the collections agent an invoice went out. It reads the row the orders agent wrote, on the day your terms say, and the next agent after it reads both.

Two agents, one record. The orders agent writes three rows. Nobody tells the collections agent about the invoice: it reads that row, along the orange wire, and writes its own.

## Whose record it is

What an owner asks about the record before anything else: whose it is, where it lives, what it is not, and what each line of it keeps.

- **Whose it is.** The record is to your operation what a spreadsheet is to its cells: ours is the software, the contents are yours, and you can take them with you whenever you like.
- **Where it lives.** In your country. Where it is stored, and where each model that reads it runs, is set out country by country. [See where it runs](https://qantara.systems/platform/where-it-runs)
- **What it is not.** This is not a dashboard. It is the record under every agent, kept beside your ERP rather than instead of it.
- **What every line keeps.** Who wrote it, from which channel, and who approved it, so each line traces back to a message, a call or a person.

## In Arabic and English

One row of the record, as your team reads it. The fields are the same in both scripts, so the agent that writes it and the person who checks it see the same thing.

What: Order confirmed: ghee and oil; Where: Sohar branch; For whom: A caterer; Why: Their weekly order

## Today the record is a WhatsApp group

A delivery note is printed, signed on a tailgate and photographed. The photo goes to a WhatsApp group, and someone types it into a spreadsheet the next branch never sees. The record already exists; it is scattered across phones.

## What owners ask about the record

**Is this a new ERP?** No. It reads yours and writes back only what you allow; your ERP stays the place your accounts are kept.

**Do we have to move our data into it?** No. Agents read where the data already is, and the record keeps what was done with it: what moved, for whom, and why.

**Can the next company in the group use it?** What was learned carries to the next company, so it starts further on. Each company's data stays in that company's record.

## Where the record does the most work

- [Orders and confirmations](https://qantara.systems/solutions/orders): Every order acknowledged and tracked.
- [Collections](https://qantara.systems/solutions/collections): Payments followed up on schedule.
- [Supplier follow-ups](https://qantara.systems/solutions/supplier-follow-ups): Deliveries chased before they are late.

## Start the record with one process

The first workflow is the hardest. Every one after it starts from what the record already knows.

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

Muscat and across the Gulf

Next: [Agents](https://qantara.systems/platform/agents)

---

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