what others make and ship for you

Suppliers and subcontractors.

We run the documents between your orders and the businesses that make and ship for you: purchase orders raised from your orders, confirmations checked against them, deliveries matched, and every slip, short shipment and substitution chased and settled. Routine chasers go out automatically; your buyers approve whatever the agent recommends before it reaches a customer or your ledger.

Rules post what fits, within limits you set. The AI works what doesn’t and recommends. Nothing it proposes posts until a named person approves it.

Book a 30-minute assessment of your back office How we work, and how we charge →
Illustration: order, purchase order, confirmation, delivery arrive and are matched by rules; what agrees moves to ready to invoice. A mismatch goes to the AI agent, which resolves it and recommends, and a person approves before it posts. OrderPurchase orderConfirmationDelivery Ready to invoice 48 orders today SO 51219 PO 8841 CNF 2207 DN 3342 SO 51220 PO 8842 CNF 2208 DN 3343 SO 51221 PO 8843 Date +7 days DN 3344 SO 51222 PO 8844 CNF 2210 DN 3345 AI resolves Date +7 days Reading the supplier’s note People approve Buyer approved
01Who it’s for

For distributors, brand owners and manufacturers who buy in, subcontract or drop-ship, and whose purchasing lives in a spreadsheet beside the order book.

If someone else makes, ships or stores what you sell, your back office is mostly documents that have to agree with each other: the order you took, the purchase orders it implies, the confirmations that come back, what was delivered, and what was invoiced. When they agree, nothing should need a person. When they don’t, someone has to notice, chase and settle it.

02The chain

From the customer’s order to the subcontractor and back.

When someone else makes or ships what you sell, six documents have to agree across three companies. Here is the chain, and where it breaks.

  1. Customer order

    What the customer wants (your sales order). Must match a product you have supply rules for.

    • No supply rule

  2. Purchase orders

    What that order implies for each supplier or subcontractor, generated by your product rules. Must agree with the customer order on quantity and date.

    • Lead time longer than the customer’s date

  3. Order confirmations

    What each supplier promises. Must agree with the purchase order on quantity, price and date.

    • Price variance
    • Date slip
    • Unconfirmed

  4. Delivery note and goods receipt

    What arrived, where. Must agree with the confirmation.

    • Short shipment
    • Substitution
    • Over-delivery

  5. Supplier invoice

    What they charge. Must agree with what was delivered, not with what they shipped.

    • Invoiced as shipped, not as ordered

  6. Customer invoice

    Raised when the delivery is complete. Must agree with the customer order and what reached them.

    • Partial delivery to invoice

The correspondence with each supplier and the customer stays attached to the purchase order or invoice it concerns.

03How the work is split

Rules record. AI resolves. People approve.

01

What rules handle.

  • Purchase-order lines from an order, generated using the rules you give us for each product.
  • Confirmations matched to purchase orders on quantity, price and date.
  • Deliveries matched to confirmations.
  • Invoices matched to deliveries.
02

What the AI resolves.

  • A customer order with no supply rule, or a lead time longer than the customer’s date.
  • A price variance, a date slip, or an order still unconfirmed.
  • A short shipment, a substitution or an over-delivery.
  • A supplier invoice invoiced as shipped, not as ordered; a partial delivery to invoice to the customer.
  • It reads the correspondence, contacts the supplier, and recommends.
03

What people approve.

  • Anything the AI recommends, before it reaches your ledger or your customer.
  • Any message that changes a date, quantity, price or substitution, before it goes out. Chasing a confirmation or asking for a delivery note goes out automatically.
04What we measure

Measured on your documents, not quoted from someone else’s.

  • Documents handled without a person.
  • Open items by age.
  • Confirmations outstanding.
  • Days from delivery to invoice.
05One worked exception

A confirmation that slipped.

  1. Rule A customer order for 40 units generates two purchase-order lines, one per subcontractor, by your product rules.
  2. Agent One confirmation comes back a week later than the customer’s date. The agent reads the supplier’s note, asks whether a part-shipment is possible, and recommends splitting the delivery.
  3. Person The buyer approves the split before anything is sent to the customer.
Illustrative example, not a customer record

See node 3, order confirmations ↑

06Which ERPs and systems it touches

We don’t replace your ledger.

  • Your ERP, read and written through its API where one exists and through its user interface where it doesn’t: SAP Business One, Sage and Exchequer deepest; NetSuite and Business Central in production; others integrated.
  • Where there is no ERP module for orders and purchasing, Opnua holds those documents and posts invoices, credits and cash to your accounts package.
  • Mail and documents: Microsoft 365, Graph, Outlook, SharePoint, OCR.
  • Supplier and carrier portals; UI-driven agents where no API exists.
How the platform works

Start with the confirmations nobody is chasing.

Thirty minutes, your process, no slides. You leave with a next meeting booked, or a clear reason we’re not the right fit.

Book a 30-minute assessment How we work
Everything we run