Export orders

Your business already runs a POS, an ERP or an accounting system. Sela takes orders from WhatsApp, Instagram, Messenger, Telegram, your website, your storefront and phone calls, and Export moves those orders into your own system without a custom integration.

Every export uses one order structure, sela.order.v1, described at the end of this page. The same structure is in the downloads, the REST API and the order webhooks, so you map it once.

Who can export#

Exporting needs the export reports permission. Owners, admins, branch admins, managers and finance members have it; agents, designers and viewers do not. A member without it sees the Export button, and the dialog explains who can export for them. It also works in a read-only workspace. See Team, roles and permissions.

Downloads are part of the Store area, so they cover every workspace with a Store. The REST API and webhooks need the Scale or Enterprise plan, see Plans and billing.

Download orders#

1. Open Store, then Orders (the board or History) or Reports, and choose Export.
2. Pick the dates: Today, Yesterday, This week, Last week, This month, Last month or Custom with a From and To date.
3. Under Orders, pick Completed (delivered or picked up, the default and the right choice for accounting), Not cancelled (every order except rejected and cancelled ones) or All. Optionally narrow Source to Storefront, AI chat, Dashboard, Phone or API.
4. Pick a Format (below) and choose Export.

Sela fetches the orders, shows how many it has so far, then downloads the file. You can Cancel at any time. Each export is recorded in the workspace's audit trail: who exported, the dates and filters, the format, how many orders, and whether phone numbers were full or masked. When it finishes you see the number of orders and the sales total, with Download again and Export something else. The dialog remembers your last choices on that browser.

How the dates work:

• Dates are business days in your workspace's time zone (set in your environment), not your computer's. An order placed at 1 a.m. belongs to that day.
• Weeks start on Saturday.
• One export covers up to 400 days and up to 50,000 orders. If a range holds more, Sela asks you to choose a shorter range and export it in parts.
• Orders are listed oldest first.

Formats#

CSV files are UTF-8 with a byte order mark and Windows line endings, so Excel shows Arabic correctly when you double-click them. Column headers are fixed English names that never change, so an import you set up once keeps working. Text that a spreadsheet would treat as a formula (starting with =, +, -, @) gets a leading apostrophe; phone numbers such as +9647701234567 and all amounts are left as they are.

The daily summary#

The Daily summary sheet has one row per business day and currency:

Rejected and cancelled orders are not sales, as on Store, Reports. A Total row per currency closes the sheet.

Phone numbers#

Customer phone numbers follow your phone privacy setting, exactly as the orders board shows them to you. Members who may export contacts (owners, admins and branch admins) always get full numbers. When numbers are masked for you, the dialog says so before you export. The REST API and webhooks always carry full numbers, since they belong to the workspace's own integrations.

Orders without items#

Staff can record an order as an agreed amount with no menu items, described in its notes, and orders made from an extracted invoice can look the same. In sela.order.v1 these have "amount_only": true and an empty lines list. So that line-based imports never drop them, the Order items CSV and the Items sheet give each one a single row:

Map SELA-AMOUNT to a general "sales" or "misc" item in your POS or accounting system.

Import into your POS or ERP#

1. Export Order items (CSV) for a test day and import it into your system.
2. Map the columns once: number (or order_id) is the order, sku identifies the item, quantity, unit_price and line_total are the line, and order_total with currency is the bill.
3. Use number or order_id to skip orders you imported before, so exporting overlapping dates never creates duplicates.
4. Run it daily, or automate it with the REST API.

sku is Sela's item key: product:<id> for store products, dish:<key> for menu items, offer:<id> for offers, or empty for orders taken before items had keys. Give your items the same codes in your system, or keep a mapping table.

Orders CSV columns#

Order items CSV columns#

The sela.order.v1 structure#

The JSON download, GET /api/v1/store-orders and the order_v1 webhook field all carry this object. Fields are never renamed or removed in version 1; new fields can be added, so ignore ones you do not know. Amounts are numbers in major units, times are ISO 8601 strings with your workspace's UTC offset, and fields without a value are null.

Each entry of lines:

{
  "schema": "sela.order.v1",
  "id": "jh72...",
  "number": "ORD-7K3M",
  "created_at": "2026-10-05T14:03:22.123+03:00",
  "updated_at": "2026-10-05T14:40:00.000+03:00",
  "business_date": "2026-10-05",
  "timezone": "Asia/Baghdad",
  "status": "completed",
  "source": "storefront",
  "channel": null,
  "branch": null,
  "customer": { "id": "k57...", "name": "Ali", "phone": "9647701234567" },
  "fulfillment": { "type": "delivery", "area": "Karrada", "address": "Street 14, House 3", "landmark": "Near the mosque", "maps_url": null },
  "amount_only": false,
  "lines": [
    {
      "line_no": 1,
      "sku": "dish:shawarma",
      "name": "Shawarma",
      "name_ar": "شاورما",
      "variant": "Large",
      "variant_ar": "كبير",
      "modifiers": [{ "group": "Extras", "group_ar": "إضافات", "option": "Cheese", "option_ar": "جبن", "price_delta": 500 }],
      "modifiers_text": "Extras: Cheese",
      "quantity": 2,
      "unit_price": 4500,
      "line_total": 9000,
      "note": "No onion"
    }
  ],
  "totals": { "subtotal": 9000, "delivery_fee": 2000, "discount": 0, "tax": 0, "total": 11000, "currency": "IQD" },
  "payment": { "method": "cash_on_delivery", "status": "paid" },
  "delivery": { "driver_name": "Mustafa", "status": "delivered" },
  "invoice": null,
  "notes": null,
  "cancellation_reason": null,
  "timeline": {
    "accepted_at": "2026-10-05T14:04:10.000+03:00",
    "ready_at": "2026-10-05T14:20:00.000+03:00",
    "out_for_delivery_at": "2026-10-05T14:22:00.000+03:00",
    "completed_at": "2026-10-05T14:40:00.000+03:00",
    "cancelled_at": null,
    "rejected_at": null
  },
  "taken_by": null
}

Keep your system in sync automatically#

For a system that should always have the latest orders, without anyone downloading files:

1. Create an API key with orders:read under API Keys (Scale or Enterprise).
2. Once, pull everything: GET /api/v1/store-orders?from=2026-01-01, following next_cursor until is_done is true. Keep meta.next_updated_since from the first page.
3. Then poll with updated_since set to the saved value, follow next_cursor to the end, and save the last page's meta.next_updated_since for the next poll. Every change to an order (a new status, payment, delivery, address, its invoice's status) moves its updated_at, so you receive it again with its new state.
4. Save orders by id, overwriting what you have. Polls overlap by design (a couple of minutes), so the same order can come back; overwriting makes that harmless.
5. For instant notice of new orders, subscribe a webhook to order.created and order.status_changed; both carry order_v1.

See REST API and Webhooks.