Customer orders by email, ready for your ERP.

Order Intake reads orders from email, PDF and Excel, checks every line against your product catalog and shows a person what does not fit. Approved orders leave as a clean file your ERP can import.

Example: three order lines. Two are matched to the catalog, one is not in the catalog and waits for a person.

The tool prepares. A person decides.

Does this sound familiar?

  • An order arrives as a PDF. Someone types every line into the ERP.
  • The customer writes their own article number. Someone looks up yours.
  • They order 2 rolls. Your ERP counts metres.
  • The same order arrives twice. Nobody notices until both are entered.

Order Intake does the checking. A person keeps the decision.

How it works

  1. It reads the order

    Email text, PDF and Excel attachments. Quantities, units, prices and delivery dates, copied as the customer wrote them.

  2. It checks every line

    Against your catalog, your customers’ own article numbers and your unit conversions. Duplicates, inactive items and missing fields are flagged.

  3. A person approves

    The review screen shows the original next to the extracted lines. You correct, approve or reject. Approved orders are exported as JSON or CSV.

The AI reads. Rules check.

The AI model only reads the order. Every line is then checked by rules you can read and test. An order with an open error cannot be approved, and every correction is logged.

Order Intake

Reads, matches articles, converts units and flags what does not fit.

A person

Corrects, approves or rejects. Nothing goes to the ERP without that step.

How do your orders arrive?

By email, PDF, Excel, or all three? Which ERP do they end up in? I read every message and reply myself.

Portrait of Osmel P. Teran

Osmel P. Teran, Teran Studio. I build integrations between CRM, ERP and everyday tools, inside an industrial company in Switzerland.