The layer

Everything reads in. Nothing writes out without a person.

The layer sits on top of the systems you already run and reads them into one record. It works one workflow at a time: each reads the record, proposes an action, and a person commits it. Nothing is replaced.

Order 417, Kestrel Coast Produce and the numbers in the examples below are made up. The arithmetic is consistent so you can check it.

Figure 04 · The stack

What happens between the inbox and the ERP.

  1. Reads

    Everything reads in.

    Documents are read where they already land. Nothing is migrated. The layer keeps its own copy of what it reads and leaves the original where it is.

    • Shared inboxes
    • Scheduled ERP exports
    • Confirmations from carriers and suppliers
    • Certificates and permits
    • The spreadsheets your team already keeps
  2. One record

    Every order, as one record.

    Order, booking, shipment, documents, clocks and exceptions, linked. Every value cites its document.

  3. Roles

    Named roles with a fixed job.

    Each one may read certain things and propose one kind of action. None can send or change anything without an approval.

    • Clerk
    • Checker
    • Clock
    • Reconciler
    • Tracker
    • Status Drafter
  4. The gate

    A person on every write.

    Anything that leaves the building waits for a named person, with the exact change spelled out.

  5. Writes

    What comes out.

    • An answer to a question, with its sources
    • A draft in your drafts folder
    • An approved ERP change, shown as a diff
    • One email per person each morning
    • The monthly report
What it reads

It reads where the documents already land.

A forwarding rule on the addresses your operation already uses, a scheduled export from your ERP, and a shared folder. No live connection to your systems to start. Any system that can email a report or export a file can usually be read without a native integration.

You choose which addresses and folders it can see before it sees anything, and you can see exactly which threads it touched.

  • Gmail
  • Outlook
  • Google Drive
  • Google Sheets
  • Microsoft Excel
  • NetSuite
  • QuickBooks
  • Xero
  • Salesforce
  • HubSpot
  • Shopify
  • Slack
  • Microsoft Teams
  • Notion
  • Stripe
  • DocuSign
Provenance

Every value shows the document it came from.

Click any number and see the page it was read from. When the layer cannot read something with confidence it asks a person. It never fills a blank with a plausible number, and a blank stays marked unknown.

GmailThe supplier, via the shared inbox

Loaded today, order 417: 18 pallets, 1,800 cartons, table grapes, set point 32°F. Seal attached.

Gmail
Loading confirmation
Supplier email · page 1 · received Tuesday 4:00pm
The roles

Named roles, each with a narrow job.

Each one has a job description: a narrow check, a fixed set of things it may read, and one kind of action it may propose. None can send or change anything without an approval. Most of them are plain code. The ones that read documents classify and file. They never make a business decision.

Clerk

Files everything.

Reads
Every email and attachment on the watched addresses
Does
Decides what each document is and which order it belongs to, and files it
Never
Guesses. Anything unclear goes to the needs-a-look tray.

Checker

Guards the booking.

Reads
The order, the carrier's confirmation, the handling rule table
Does
Compares temperature, vent, quantities and dates. Says READY, CHECK or STOP.
Never
Sends instructions. A person clears every CHECK and STOP.

Clock

Watches the clocks.

Reads
Deadlines, ship dates, payment terms, document ages
Does
Counts down every clock on every order and lists what is missing against it
Never
Chases anyone itself. It writes the list.

Reconciler

Catches short loads.

Reads
Purchase order, loading confirmation, sales order, supplier invoice
Does
Compares what was ordered, what shipped and what was billed. Proposes the correction to what was billed, and asks about the rest.
Never
Decides what happens to the order. That question goes to the trader.

Tracker

Follows shipments in transit.

Reads
Shipment references against carrier data
Does
Notices when an arrival moves and lists which customers are affected
Never
Tells the customer. It drafts the note for the trader.

Status Drafter

Answers "where are my documents".

Reads
The order record
Does
Drafts the status reply with what has arrived, what is missing and when it is due
Never
Presses send.
Skills

Your team's know-how, written down and kept current.

The rules each desk carries in its head: which documents a destination needs, how a commodity is handled, how a status reply should read. We write them down, test them against real orders, and keep them current with the people who own them.

Every check and every draft reads them. A change is a diff the owner approves, logged like any other decision. The know-how stays with your company when people move on.

One record, many desks

One record. Shaped for every desk.

Nobody is asked to live in a new app. A morning email per person carries only what is theirs and what needs attention next, and every line links back to the record.

  • The traderAny order's status in seconds, and a drafted reply when a customer asks.
  • The documentation deskWhat arrived, what is missing, and hours to the deadline, per order.
  • The logistics deskThe booking check, the short loads, and any shipment that moved overnight.
  • The controllerThe approval queue as a diff, and the monthly report in plain arithmetic.
Your morning list · the traderWednesday 6:45am
  • 417
    1,800 of 2,000 loaded. Customer note drafted, and the open 200 cartons are your call.Loading confirmation, page 1 · sails Saturday
  • 412
    Customer asked where the documents are. Reply drafted.Shared inbox · 1:40pm yesterday · 4 of 5 documents in
  • 414
    Sails Thursday as booked. Nothing to do.Carrier data · arrival unchanged
Your morning list · the documentation deskWednesday 6:45am
  • 417
    5 of 6 in. Phytosanitary certificate missing, requested at 2,000, must match 1,800.Document deadline Thursday 4:00pm · 33 hours
  • 412
    4 of 5 in. Certificate of origin not yet received. Follow-up drafted.Document deadline Wednesday 10:00am · 3 hours
  • 409
    Certificate issued. Invoice released.Certifying office · yesterday 11:05am
Your morning list · the logistics deskWednesday 6:45am
  • 417
    Ordered vs loaded STOP. 2 pallets short. Booking check READY.Loading confirmation vs sales order
  • 418
    Booking confirmed, 32°F, vent closed, matches the rule.Carrier PDF, page 2 · cargo deadline Friday 12:00pm
  • 405
    Arrival moved 6 days. 3 customers affected. Updates drafted for the trader.Carrier data · overnight
Your morning list · the controllerWednesday 6:45am
  • Staged
    Invoice 417 · Quantity 2,000 → 1,800. Proposed by Reconciler from the loading confirmation.Waits on you · Approve or decline, both logged
  • Staged
    Hold proposed on invoice 417 until the certificate matches 1,800.Reason on the record · the documentation desk clears it
  • Month
    Documents read, exceptions raised, exceptions that were real, false alarms, hours returned.Measured against the baseline taken before anything turned on
The gate

Nothing leaves the building until a person approves the exact change.

Approval is a property of the action, not a setting. One door performs every outside write, and it refuses without an approval on record. Declines are logged the same as approvals.

Proposed change · Invoice 417Unsigned
Draft invoice quantity: 2,000 → 1,800ERP · invoice 417 · quantity, cartonsStaged
Waits on: the controllerProposed by Reconciler, from the loading confirmation, page 1
Boundaries

What it is not.

  • Not a system of record.Your ERP stays the ERP. The layer reads it by export and writes back only through the gate, and only if you turn that on.
  • Not a place you have to go.Ask a question when you need an answer. Otherwise the agreed checks run in the background and reach you by email, in your drafts folder, and as a row in a grid your team can export.
  • Not a workflow you have to start.The checks are fixed, versioned and traced, and they run whether anyone is watching or not.
  • Not a new app to live in.Many people will meet it only in their inbox and their drafts folder. The email and the drafts folder are the surface.
Keep what you have

Keep what you have.

Each of these is a reasonable answer. Here is what each one still leaves on the desk.

The answerWhat it does wellWhat stays on the desk
Your ERP's own assistantActs on records that are already in the ERP.Your problem is the documents that are not in the ERP yet. The layer reads those and feeds the ERP through the gate.
Your ERP vendor's add-onsReporting and forecasting on the vendor's own data.Nothing on the booking confirmation, the loading confirmation or the certificate that arrived by email this morning.
A document generatorProduces a clean invoice and packing list from the order.Generation is the easy half. The labor is in reading what comes back from suppliers, carriers and agencies, and checking it against the order.
Scanning software plus an internTurns a PDF into text cheaply.Reading a page is the cheap part. The record, the rules, the approval queue and the audit trail are the work, and none of it survives the handover.
The enterprise versionThe same architecture, proven at scale.The wrong price and timeline for one operation. The layer is the same idea, scoped to your company, live in weeks.
Two more people on the deskAdds hands, and hands are needed.Hiring adds capacity, it does not add a check. A new hire inherits the same inbox and the same re-keying, and the mismatch still gets found on arrival.
Your ERP implementation partnerConfigures the ERP well.Partners configure the ERP. Document reading, reconciliation and an approval queue are usually outside that engagement. We work alongside them.
Let's talk

Bring the tracking sheet your team rebuilds by hand.

We will show you what it looks like as one record, with every cell pointing at the document it came from.

Book a call

Nothing gets connected on the call and nothing is ever sent without you.