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

# Orders

> Create and track customer purchase history

Orders represent customer purchases. If you connect your system to the [**Orders API**](/api-reference/orders/order-calculated-object), you will see new entries every time your customers create a new order. The **Orders** tab helps you track your customers' orders and all transactional activities.

You can manage orders by using the Dashboard or the Orders API.

## Orders view

The **Orders** section displays a list of all transactional records. Use this view to monitor sales activity and manage existing data.

Each line in the order list contains:

* **Status**: The current state of the order:
  * **Order created**: The order has been logged.
  * **Order paid**: The order was finalized.
  * **Order canceled**: The order was canceled. Using **redemption rollback** automatically switches a status from *paid* to *canceled*.
  * **Order fulfilled**: A flexible status indicating the order was created but not yet paid.
* **ID**: A unique identifier (click this to open the **Order detailed view**).
* **Customer**: The customer who placed the order.
* **Items**: The number of items in the cart.
* **Amount**: Total value before discounts.
* **Discounted amount**: Total value after discounts.
* **Created**: The timestamp when the order was logged.

Click an order ID to open its details and see its **Dashboard** with transaction data and cart structure, **Metadata**, and **Activity**. You can change its status or edit the order.

## Add an order

You can add order records manually for individual entries or automatically for high-volume transactional data.

### Add manually in Dashboard

Use the Dashboard to manually add an order record for testing or offline sales.

Go to **Campaign hub** > **Orders** to **Create order**.

<Steps>
  <Step title="Details">
    Add the following:

    * **Source ID**: Your internal reference identifier for the order (optional).
    * **Status**: Select the current state – **Created**, **Paid**, **Canceled**, or **Fulfilled** (optional).
  </Step>

  <Step title="Items">
    **Add item** to specify products or SKUs that should be in the order.

    For each item, you can set the **Quantity** and **Price**.

    Click **Calculate** to update the **Total order amount**.

    Optionally, add **Total order amount** only, without specific cart items.
  </Step>

  <Step title="Customer (optional)">
    **Choose customer** or create a new one to link the order to that customer.

    This order will then appear in the customer's profile.
  </Step>

  <Step title="Referrer (optional)">
    **Choose customer** or create a new one to assign them as a referrer if the order was driven by a [referral campaign](/build/referral-campaign-overview).
  </Step>

  <Step title="Metadata (optional)">
    Add custom attributes for tracking, optimizing, or experimenting.

    You can either:

    * **Use an existing metadata schema**.
    * **Add unknown property**: Metadata that isn't defined and won't be added to the schema.
    * **Add to schema**: Define new metadata schema. Once saved, reload the schema to use the new metadata.

    <Note>
      Read [Metadata](/prepare/metadata) to learn more about custom attributes.
    </Note>
  </Step>

  <Step title="Summary">
    Review all entered details. **Save** to add the order to the order list.
  </Step>
</Steps>

## Order data export

You can download a CSV file with the order data for external reporting.

Go to **Campaign hub** > **Orders** to **Export** orders.

<Steps>
  <Step title="Select attributes">
    Choose which standard fields and custom attributes (metadata) to include in the exported CSV.

    The date and times of the exported data are in the UTC time zone.
  </Step>

  <Step title="Export">
    Once ready, **Export** your list. The file will be generated and delivered to your **Notifications Center**.

    You can also find all your exported files in **Audit log** > **Exports**.

    <Note>
      The download stays available for 90 days. Voucherify removes the file after 90 days, or immediately if you delete the export.

      The file can be any size and can include any number of objects. Larger exports may take longer to generate.
    </Note>
  </Step>
</Steps>

## Related features

Experiment with other features to improve your incentive results.

<AccordionGroup>
  <Accordion title="Developer setup: Order API">
    For production environments, use the [POST Create Order API endpoint](/api-reference/orders/create-order) to sync your storefront with Voucherify in real-time.

    You can also automate the import of historical data with the [POST Import orders](/api-reference/orders/import-orders)

    <Tip>
      Syncing orders with the API ensures that **Validation rules** based on cart content are triggered instantly during the checkout process.
    </Tip>
  </Accordion>

  <Accordion title="Validation rules">
    You can create **validation rules** that define the required cart structure:

    * **Cart volume**: Limit redemptions to specific order amounts (for example, "Spend at least \$50").
    * **Cart content**: Restrict discounts to specific products or quantities.

    Read the [Validation rules article](/optimize/validation-rules-reference) to learn more about them.
  </Accordion>

  <Accordion title="Metadata">
    Use **Metadata** to store custom attributes (like `shipping_method`) to build specific [validation rules](/optimize/validation-rules-reference).

    Read the [Metadata article](/prepare/metadata) to learn more.
  </Accordion>

  <Accordion title="Customer segments">
    Divide customers into segments based on their purchase history:

    * **High-spenders**: Customers with a total amount spent over a specific threshold.
    * **Loyal buyers**: Customers who have reached a specific number of orders.

    You can use those segments then for [distributions](/integrations/distributions-overview) or [validation rules](/optimize/validation-rules-reference).

    Read more in the [Customer segments](/prepare/customer-segments) article.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.