Integration models

Start here

There are three ways to put AIOTIC into your process. They differ only in who reviews and what triggers the send. The ERP receive endpoint and master-data sync are the same in all three.

Rendering diagram…

A: operators use the AIOTIC app. B: you build the review step. C: your rules decide.

A — App in the loop (default)

Operators work in the AIOTIC app: they see incoming orders, fix what the AI flagged, and press Send to ERP. Your integration is the receive endpoint plus the sync job.

• Best for: most companies. Fastest to go live; the app already handles corrections, cancellations, split e-mails, rejected mails and audit trails.
• You build: receive endpoint, sync. Optionally the processing webhook as an early signal.

B — Your own review UI

Your application shows the extracted order to your users (for example inside the ERP), and calls AIOTIC's API to send it. Documents still arrive through the AIOTIC mailbox or through your uploads.

• Best for: vendors who want the review inside their own product.
• You build: everything in A, plus polling of GET /order_status/list and a Send action on POST /erp/send/{request_id}.
• Know before you start: today the public API has no endpoint to submit corrections or to cancel an order. Corrections made in your UI must be applied on your side (in the receive endpoint) before booking; the payload AIOTIC sends is the AI's reading. See Headless limits today and the proposal appendix.

C — Fully automated

Your service polls for Processed orders, runs its own rules, and sends without a human. Attention orders are routed to a person (a ticket, an e-mail, or the AIOTIC app).

• Best for: high-volume, low-risk order streams where the customer base and catalog are complete in AIOTIC.
• You build: everything in B, plus a rule set. The SDK's pipeline is designed for exactly this: it applies the validation a functional ERP API would perform, so a data-only ERP does not receive garbage.
• Non-negotiable: never auto-send ATTENTION. It is AIOTIC explicitly asking for a human.

Choosing

Question	A	B	C
Operators willing to use a second screen?	✔	—	—
Need corrections before booking?	app	your side	your rules
Catalog and customers complete in AIOTIC?	helpful	helpful	required
Time to first order in production	days	weeks	weeks

Most integrations start with A and add C for a subset of trusted customers later. Nothing in the API forces you to choose up front.