Autonnel v1.7.0

Orders overview

The order list, fields exposed, and per-order detail page.


The Orders section lists every order recorded by Autonnel, including orders that have not yet been paid. Order numbers are plain integers — no letter prefix.

Prerequisites

  • The ORDERS feature permission assigned to your role.
  • An active payment provider configured under Settings so that payment data appears on the order detail page.

Order list

The list table exposes the following columns:

ColumnNotes
NumberPlain numeric order number, no prefix.
DomainThe storefront domain (brand) the checkout was submitted on. Older orders show the domain of the visitor’s entry URL.
StatusOne of PENDING, PAID, SHIPPED, DELIVERED, PARTIALLY_REFUNDED, REFUNDED.
AmountOrder total in the order’s currency.
CurrencyISO 4217 currency code (e.g. USD, EUR).
CustomerCustomer name and email from the order snapshot.
Payment methodThe payment provider, shown as a badge.
Postback stateWhether the conversion postback for this order succeeded, is pending, failed, or is retrying.

You can filter by date range, order number, status, domain, currency, payment method, traffic source, and customer country. The payment method filter lists the payment providers registered on the deployment (core and plugins), and is also available as a ?payment=<PROVIDER> query parameter on the list URL. The domain filter lists every bound domain; Export CSV exports exactly the filtered list, with a Domain column. The order detail page and the Orders → Emails log show the domain too (for an email, the domain it was sent for). Filters that depend on enumerated values (status, payment method, traffic source, country) are populated dynamically from the orders already in the database.

Order detail page

Open any order row to reach the detail view. The detail page is divided into tabs and panels:

Summary panel

  • Customer info — name, email, phone, and shipping address as submitted at checkout.
  • First-visited URL — the full URL (including all query parameters such as fbclid, utm_source, and anid) of the first page the customer visited. This URL is the authoritative source for ad attribution.
  • Checkout URL — the checkout page URL the customer used, with all original query parameters preserved.
  • All visited pages button — expands a panel listing every page this customer visited, in chronological order.

Metadata panel

Besides the core fields, the Metadata panel lists extra rows contributed by plugins (see writing plugins). Rows with a link are clickable.

Transactions tab

Charges and refunds linked to this order appear here in a unified view. Each row shows the transaction type, status, amount, currency, provider, and provider transaction ID. Refund rows include a link back to the original charge.

Refunds tab

The refund panel on the detail page provides the refund action interface. See the Refunds page for full details on initiating a refund.

Caveats

  • The “all visited pages” panel may be slow on deployments with long visit histories.
  • An order can have multiple postbacks (one per ad platform binding). The postback state column shows the aggregate worst-case state across all platforms.
  • Orders include both paid and unpaid entries. PENDING orders are visible alongside completed orders so that recall (abandoned cart recovery) flows have a full view of the pipeline.
  • Order states — state machine, transition triggers, and constraints.
  • Refunds — full, partial, and percentage refunds.
  • Order emails — the EmailQueue tab for receipt, shipped, delivered, refunded, and recall emails.