Order

Order. Created with POST /orders (body: `OrderCreate`), which drives the very same pricing + cart pipeline as the dashboard's manager checkout. Once placed, an order is IMMUTABLE: PUT accepts a small whitelist ({void, internal_notes}) on `/orders/{id}`. No DELETE. `items` is a FLAT vector of rows, one per (producto, opcion). Financial fields (`subtotal`, `discount`, `surcharge`, `tax`, `total`) are flat at the top level, all ABSOLUTE. Invariant: total = subtotal − discount + surcharge + tax `discount` rolls up ALL reductions (order-level % discount + amount- promo). `surcharge` rolls up ALL additions (payment-method surcharge + shipping). `tax` is the IVA amount the merchant adds on top when the negocio is configured to display prices NET (tax-exclusive); zero when the negocio's stored prices already include tax. TAX CONVENTION (read carefully): - If the negocio displays prices NET (i.e. `:negocio/sumar-iva` is true internally), line `:item/precio` storage is pre-tax. The API resolves `tax = (subtotal − discount + surcharge) × iva%` and adds it to `total`. Consumers see the FINAL amount due in `total`. - If the negocio displays prices GROSS (default), line storage already includes tax. `tax` is 0 and `total` carries the gross number. Either way the customer-pays number is `total`. Consumers integrating for invoicing (AFIP / SAT / DIAN) still need to apply their own per-country fiscal breakdown — `:cliente/condicion-iva` (responsable- inscripto / monotributo / consumidor-final / exento) is metadata for that downstream flow and does NOT alter `total`.

{
  "id": "5",
  "created_at": "2026-05-15T12:00:00Z",
  "customer_id": "8801",
  "status": "...",
  "voided": false,
  "subtotal": 13500.0,
  "discount": 675.0,
  "surcharge": 0.0,
  "tax": 2691.25,
  "total": 15516.25,
  "items": [
    { "product_id": "9201", "name": "Remera", "option_id": "555", "option_name": "Azul / M", "sku": "REM-001-AZ-M", "quantity": 3 }
  ]
}