Status Overview

• pending_approval: Order submitted and awaiting store review. Default for customer orders unless auto-approve is enabled.
• approved: Order approved. Customer can drop off or ship cards. Triggers email with store address.
• denied: Order rejected. Customer is notified via email if enabled.
• pending_drop_in: Approved, customer will bring cards to store (for drop-in orders).
• pending_delivery: Approved, customer will ship cards (for delivery orders).
• received: Cards have been received by the store (dropped off or mailed).
• reviewing: Store is inspecting and verifying conditions and quantities.
• complete: Order fully processed. Totals finalized. Cards can be sent to inventory. Completion email sent.

Typical Status Flow

A typical order moves through these stages:

1. Customer submits ? pending_approval
2. Store approves ? approved ? then pending_drop_in or pending_delivery
3. Customer delivers cards ? Store marks received
4. Store inspects ? reviewing
5. Store completes ? complete

Orders can also be denied at any point before completion. The initial status for new orders can be set via store config: defaultOrderStatus or autoApprove (true = approved, false = pending_approval).

Status History

Every status change is recorded in the order's statusHistory array:

• previousStatus: Status before the change
• newStatus: Status after the change
• changedAt: Timestamp of the change

This provides a full audit trail of when the order moved through each stage.

Custom Statuses

Stores can define custom statuses beyond the defaults. Useful for workflows like "pending_payment," "shipped," or "on_hold." Custom statuses support names and colors for display in the order list and detail views.

Email Notifications

• Order Created: Store gets order details + CSV attachment; customer gets confirmation.
• Approved: Customer gets email with store address for drop-off or shipping.
• Complete: Customer gets thank-you/completion email.
• Status Changes: Store owner can be notified of status changes.
• Configuration: Controlled by store config (emailsEnabled). Templates can be customized with a rich text editor.