Operations

From the customer order to the shipment, across every system it touches.

We build agents that carry a customer order through each system, from the email to the invoice. Your sales lead approves a price below the list, and your planner approves a date that slips. Every decision goes on a record you can check.

A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.

AI agents for operations teams do the work that sits between systems. Today a person reads the order email, keys it into the ERP, checks stock, asks the warehouse by chat, and copies the ship date back to the customer. Together these small steps decide whether the order ships on the date you promised.

We build that path with you as one workflow. The agent reads the order, enters it, checks stock and dates, drafts the shipping documents and the invoice, and tells the customer what changed. It stops where your rules say a person decides: a price below the list, a date that slips, an order above a credit limit.

What changes for the order desk

  • Your order desk reviews exceptions instead of retyping orders.
  • The planner sees each date change with its reason, before the customer does.
  • Each step, each approval and each refusal is on the record, so a dispute starts from facts.

If an agent in your ERP already works for you, keep it. Its output still has to reach the warehouse, the customer and accounting. That gap is what we build. The procurement page covers the supplier side of the same order.

Follow one workflow

One customer order, five systems, one approval and one refusal.

This workflow is designed and has not run in the sandbox yet. Each step says what the agent does, in which system, who approves, and what goes on the record. The order and the customer are examples.

  1. 01Email

    Take the customer order from the sales inbox. Receive a credential for this order only.

    Who approves
    No approval on this step
    On the record
    credential issued · one order
  2. 02ERP

    Check stock and the promised date for each line.

    Who approves
    No approval on this step
    On the record
    check-stock · allowed
  3. 03ERP

    Enter the sales order with the lines that match the price list.

    Who approves
    No approval on this step
    On the record
    create-order · allowed
  4. 04ERP

    One line asks for a price below the price list. The step waits until the sales lead approves it.

    Who approves
    Sales lead
    On the record
    price-exception · approved by sales lead
  5. 05In-house tool

    Try to move stock reserved for another customer. The permission covers this order only, so the step is refused.

    Who approves
    No approval on this step
    On the record
    reallocate-stock · refused · outside permission
  6. 06Documents

    Draft the packing list and the shipping documents.

    Who approves
    No approval on this step
    On the record
    draft-shipping-docs · allowed
  7. 07Email

    Send the shipping confirmation to the customer. Internal cost fields are taken out before it leaves.

    Who approves
    No approval on this step
    On the record
    confirmation · redacted · internal cost
  8. 08Accounting

    Draft the invoice for the shipped lines.

    Who approves
    No approval on this step
    On the record
    draft-invoice · allowed

In short

  • What does a wrong order entry cost?A wrong line ships the wrong part. The agent enters only lines that match your price list and sends the rest to a person.
  • What happens when the promised date cannot be met?The agent drafts the new date with its reason. The planner approves it before the customer sees it.
  • Can an agent take stock from another order?Not unless its permission covers that order. A move outside the job is refused and recorded.
  • Who answers when a customer disputes a shipment?You do, with the record in hand. It shows what the agent read, what it changed, and who approved each change.

Operations workflows we build, and the state of each.

Three of these run in the sandbox today. Order to shipment and the date and back-order workflows are designed. We scope transfers and returns with you.

Built
We have run it.
Designed
The steps and approvals are designed. It has not run yet.
On request
We scope it with you before we design it.
  • Designed

    Order to shipment

    Order email to ERP entry, stock and date checks, shipping documents and the invoice draft. The steps are shown above.

    See the steps
  • Built

    Supplier follow-up on a late part

    A late part chased across the ERP, email, documents and accounting. The buyer approves the date change.

    Run it in the sandbox
  • Built

    Requisition with a threshold

    The agent drafts an order and checks stock. Above the threshold, the order waits for a person.

    Run it in the sandbox
  • Built

    A quote request to a supplier

    Your agent asks a supplier's agent to price one order line. The permission narrows where the request leaves your company.

    Run it in the sandbox
  • Designed

    Delivery date changes to customers

    The agent drafts the new date and its reason from stock and carrier updates. It sends the date after the planner approves.

  • Designed

    Back orders and partial shipments

    The agent ships what is in stock and keeps the rest open with a date. A person approves any split the customer has not agreed to.

  • On request

    Stock transfers between sites

  • On request

    Returns and credit notes

The five guarantees

Every workflow on this page carries them. Each one has a limit, and we state it.

  1. 01

    Each agent can do only what it was allowed to do, for that job.

    The limit

    Permissions are only as good as the rules you approve.

  2. 02

    Sensitive steps go to a person.

    The limit

    You decide which steps are sensitive.

  3. 03

    Documents are inspected before an agent sees them, and answers are checked before they leave.

    The limit

    Filters cover stated patterns and languages.

  4. 04

    Every decision is recorded, including refusals, in a record an outside party can check.

    The limit

    It shows what agents did, not whether a business rule was wise.

  5. 05

    It can run in your building, on one small machine.

    The limit

    Local models differ from the largest cloud models.

What it does not do

  • It does not replace your ERP, your warehouse tool or a carrier portal. It works between them.
  • It does not set your credit limits, price rules or promise dates. Your people do, and the agent follows them.
  • It reads the order email as written. A line it cannot match to your price list goes to a person, not into the ERP.
  • Order to shipment is designed, not yet run in the sandbox. The sandbox shows the supplier side today.
First step

Assessment, pilot, production.

Each step has a fixed scope and ends with something you keep.

  1. 01

    Workflow assessment

    A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.

    What you get
    A short, paid look at one process, with your process owner.
    What you keep
    A written scope and a price for a pilot.

    Fixed price, quoted after one call.

  2. 02

    Pilot workflow

    One workflow on your systems, supervised, with the record on from the first run.

    What you get
    One workflow at a fixed scope, with your people approving the sensitive steps.
    What you keep
    A working workflow and a measured result.

    Fixed price, quoted after one call.

  3. 03

    Production and run

    The workflow in production on Ares, on your hardware or hosted in your country.

    What you get
    Support, and the next workflows.
    What you keep
    The workflow, and the record of every decision it made.

    Recurring fee for operation and support.

Questions and answers

Tell us about one workflow.

Name one order flow that costs your team time. We will say whether an agent should run it, and what the first step costs. Fixed price, quoted after one call.

A senior member of the team replies within two business days.