An order is an incoming purchase order (Bestellung): a customer places a firm order and Mercura extracts the order metadata, matches the line items against your article catalogue, and prepares it for ERP export. Orders are one of the two entry points of the workflow (the other is tenders).
POST /orders is the programmatic twin of forwarding a purchase-order email: send the order document(s) and Mercura runs the same intake pipeline. Accepted files, size caps, primary-file selection, context, customer resolution, idempotency, and the async JobAck → poll / webhook flow are all identical to POST /tenders — see the Tenders chapter. The only difference is the request type: an order skips LV parsing and runs the order-processing agent (metadata extraction + line matching).