What AIOTIC does

Start here

AIOTIC reads the purchase orders your customers send you — as e-mail attachments, PDFs, scans, photos or direct uploads — and turns each one into a structured, validated order that your ERP can book as a sales order. Operators review anything the AI is not sure about in the AIOTIC app; you receive the final result through one HTTPS call.

The 30-second version

1. Intake. A purchase order arrives (mailbox watched by AIOTIC, or your system uploads a file through the API).
2. Classification. AIOTIC decides whether the e-mail is a purchase order at all. Quotations, invoices, delivery notes and marketing mail are recorded as rejected and never extracted.
3. Extraction. AIOTIC reads the document and the e-mail body and produces a purchase order: header, customer, ship-to, line items. E-mail instructions ("change line 3 to 200 pieces") override the attachment.
4. Resolution. In a series of deterministic stages, AIOTIC identifies which of your customers sent the order (using the customer records you synced) and resolves each line to your article number (using your product catalog and customer item mappings). This is where the product's ontology and semantic layer do their work.
5. Review. Clean orders land as Processed. Anything uncertain — an unknown article, an unidentified customer, an unreadable quantity — lands as Attention for a person to decide.
6. Hand-off. When an operator (or your code) sends the order, AIOTIC POSTs it to your ERP receive endpoint and stores the order reference your ERP returns.

Rendering diagram…

One tenant per company. Your side is the blue part: a receive endpoint and a sync job.

What you build

Component	Required?	Typical build time for your team
ERP receive endpoint — one POST handler that books an order and answers {"success": true, "order_number": "…"}	Yes	A few hours
Master-data sync — push customers, products and customer item mappings to AIOTIC whenever they change	Yes (accuracy depends on it)	Half a day to a day, depending on whether your ERP emits change events
Order polling / own review UI — only if you do not want operators to use the AIOTIC app	No	Several days
Processing webhook receiver — early signal when extraction finishes	No	Under an hour

The last column is an indication of the development effort on your side when you use the Python SDK or follow the contracts in this guide; it excludes testing against your ERP and the master-data clean-up that most projects discover along the way. The SDK implements all four components, including a validation pipeline for ERPs that cannot validate orders themselves.

What AIOTIC is not

• It is not a document archive — it keeps originals and artifacts for processing and support, but your ERP remains the system of record.
• It never sends an order to your ERP on its own. Sending is an explicit action: an operator in the app, or your code calling POST /erp/send/{request_id}.
• It does not need to know your prices or stock. It needs to know which articles exist and which customers exist.

Vocabulary

Term	Meaning
Tenant	One AIOTIC deployment for one company, with its own base URL (https://<tenant>.aiotic.ai) and keys.
Purchase order	The document your customer sends you: their order, from their point of view a purchase. This is what AIOTIC reads and what the API field purchase_order contains.
Sales order	What your ERP creates from it. Your receive endpoint turns a purchase order into a sales order and returns its number.
Order / request	The neutral word for one purchase order moving through AIOTIC, identified by a request_id (UUID).
Supplier	You — the company receiving the purchase order. Pinned from tenant configuration, not extracted.
Customer	The debtor who sent the order. Identified against your customer records; carried as customer_id (= your debtor number).
Article number	Your SKU. Line items are resolved to it; unknown ones trigger ATTENTION.
Customer item mapping	"Customer 58931 calls PROD-001 LT-ART-001". Lets AIOTIC translate customer codes to yours.
ERP receive endpoint	The URL AIOTIC calls with a reviewed order.
Processing webhook	Optional URL AIOTIC calls the moment extraction finishes, before review.

Next: Integration models →