ERP mode

هذا المحتوى غير متوفر بلغتك بعد.

Each company runs in an ERP mode. It decides whether Slflo waits for your ERP before an order counts as booked.

Mode	What it means for orders
None (`DISABLED`)	No ERP is connected. The office confirms orders itself; nothing waits on an ERP.
API (`API`)	Your ERP pulls through this API. Orders released for fulfilment wait as `ERP_PENDING` until your ERP acks them: `ERP_CONFIRMED` when accepted, `ERP_FAILED` when rejected (the office can send it again).
Push to Dynamics 365 (`DYNAMICS365`)	Slflo sends orders to D365 itself. Not offered yet; the API mode is the supported route.

Only pre-sale orders wait. A van sale is delivered and invoiced on the spot and never waits for your ERP; invoices are always issued by Slflo, and you read them from the invoice feed.
Order acks need mode API. Against a company in another mode, an order ack answers 409 ERP_MODE_NOT_API.
Invoices, payments and returns take acks in any mode, so you can read them into your books even while orders are still run in Slflo alone.
Pushing master data and lookups work in any mode.

Try it

The API doesn’t report the mode directly; an order ack shows it. On the sandbox (mode API) an ack of a delivered order is refused because the order isn’t waiting — not because of the mode:

id=$(curl -sg "$SLFLO_BASE/orders?filter[version_after]=0&per_page=1" -H "Authorization: Bearer $SLFLO_TOKEN" | jq -r '.data[0].id')
curl -s -X POST "$SLFLO_BASE/orders/$id/ack" -H "Authorization: Bearer $SLFLO_TOKEN" \
  -H "Content-Type: application/json" -H "Idempotency-Key: mode-check-$id" \
  -d '{"outcome":"ACCEPTED","external_ref":"SO-TEST"}' | jq -r .error.code
# ORDER_NOT_AWAITING_ACK    (a company not in mode API answers ERP_MODE_NOT_API)