Orders

The dashboard provides order visibility and management actions for the active organization's store.

Order list

Route: /orders

Paginated table of orders:

Filters: status, payment status, date range.

Order detail

Route: /orders/[id]

Displays full order information:

Order summary

• Order ID, status, creation date
• Customer info (email, name, phone)
• Payment status and provider
• Fulfillment status
• Order totals (subtotal, tax, shipping, discount, grand total)

Line items

Each item shows product name, variant, quantity, unit price, and line total.

Addresses

Shipping and billing addresses as provided during checkout.

Actions

Actions are conditionally shown based on current status:

Server actions in app/(dashboard)/orders/actions.ts:

'use server'
export async function fulfillOrderAction(id: string, input: FulfillOrderInput) { ... }
export async function cancelOrderAction(id: string, note?: string) { ... }
export async function refundOrderAction(id: string, note?: string) { ... }

Order timeline

The detail page includes a timeline card showing the full history of status changes, with timestamps and notes. Data is fetched from GET /v1/admin/orders/{id}/history.

Customer card

Displays the customer's name, email (contactEmail captured at checkout), and phone number from the shipping address.

Order status model

Orders use a three-dimensional status model inspired by Commerce Layer, separating order lifecycle, payment, and fulfillment into independent fields.

Order status (lifecycle)

Payment status

Fulfillment status

Lifecycle timestamps

Typical flow

Customer places order
  → status: placed, paymentStatus: unpaid, fulfillmentStatus: unfulfilled

Stripe webhook confirms payment
  → status: approved, paymentStatus: paid

Admin ships the order
  → status: fulfilled, fulfillmentStatus: fulfilled

--- OR ---

Payment fails
  → status: cancelled, paymentStatus: voided

Refund flow

1. Merchant clicks Refund on order detail page
2. Dashboard sends POST /v1/admin/orders/{id}/refund with amount and reason
3. API calls payment provider's refund() method with tenant credentials
4. Order status updated to cancelled, payment status to refunded
5. Webhook from provider confirms refund completion

API endpoints used

Related pages