> ## Documentation Index
> Fetch the complete documentation index at: https://ecommos.co/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Create and handle your first order

> Receive or create your first order and walk it through the queue.

# Create and handle your first order

Your first order is the fastest signal that product, form, staff, and stock are all wired correctly.

## Option A: receive an order from your public form

1. Share your live form URL.
2. A customer submits name, phone, optional WhatsApp, state, address, and offer.
3. The system:
   * Normalizes the phone number
   * Upserts a contact record
   * Creates the order with a sequential per-product number
   * Creates order items from the selected offer
   * Runs round-robin assignment to an eligible Sales rep (if one exists with product scope)
   * Writes an `order.created` event
   * Creates a notification and outbox record for the assigned rep
4. The order appears in **Orders** with status `New`.

## Option B: create a manual order

Use manual creation when a customer calls in, messages you on WhatsApp, or places an order through any channel outside your form.

1. Go to **Orders**.
2. Click **Create manual order**.
3. Select product and offer.
4. Enter:
   * Customer name
   * Phone (and optional WhatsApp)
   * State
   * Address
5. Save.

Manual orders enter the same downstream lifecycle as form orders. They get the same status model, same assignment rules, same dispatch and remittance gates.

## Work the order in the queue

1. Open **Orders**.
2. Find the order (search by name, phone, or order number).
3. Open the order detail drawer (desktop) or bottom sheet (mobile).
4. Confirm the customer is reachable:
   * Tap **Call** to dial the phone number
   * Tap **WhatsApp** to message the WhatsApp number
   * Tap **Copy order text** for a WhatsApp-friendly summary
5. Move the order to the right status.

### Order statuses (queue states)

| Status          | When to use                                              |
| --------------- | -------------------------------------------------------- |
| New             | Just arrived, not yet contacted                          |
| Confirmed       | Customer confirmed they will receive and pay on delivery |
| Rescheduled     | Customer asked to delay delivery                         |
| Could not reach | Rep tried and could not reach the customer               |
| Cancelled       | Customer cancelled, or you cancelled                     |

Once an order is `Confirmed`, it hands off into **Deliveries** for dispatch and delivery. See [Hand off confirmed orders to deliveries](../operations/deliveries).

## Custom statuses

You can add custom pre-confirmation queue statuses (for example "Awaiting callback", "High value") to organize your queue without changing the core lifecycle. Custom statuses are additive — they keep the order in the Orders queue. Any system transition (Confirmed, Cancelled) clears the custom status. See [Set up custom order statuses](../operations/custom-order-statuses).

## Verify on your first few orders

* Order number is sequential per product
* Assignment is visible in the queue and in the assigned rep's notifications
* Status changes appear immediately in the order header
* Order event timeline records every transition
* URL state is preserved when you filter the queue

## What's next

* [Understand the order lifecycle](./order-lifecycle)
* [Work the order queue](../operations/order-queue)
* [Hand off confirmed orders to deliveries](../operations/deliveries)
