> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/model-your-data/model-amplifications/order-filter.md).

# Order filter

## Order filter

{% hint style="info" %}
Note: Our Model Amplifications feature **only accepts files in CSV format at this time.** Please make sure the files you upload are CSV files.
{% endhint %}

## Overview

At Chord, we currently surface Orders and Sales that includes completed and not canceled orders. Additionally, our Orders model includes all orders in our database regardless of processing state.

However, some brands have different needs with regard to orders are filtered. The Order Filter configuration adds a flag for orders that a brand would like to easily remove from analysis.

{% hint style="info" %}
**Note:** Orders that are flagged `filtered_order = true` are orders that the brand would like to filter **out** of their analysis.
{% endhint %}

### Sample use cases

{% hint style="info" %}
Chord has listed several attributes and conditions to create the filter. These are a few sample use cases. However, if a brand needs a an attribute included, these may be expanded by reaching out to <help@chord.co>.
{% endhint %}

Brands may want to exclude orders that meet conditions like:

* Contain certain products, like gift cards or samples.
* Users with emails like `test@`.
* Orders prior to a certain date.
* Specific problematic order numbers.
* Fulfillment state is `fulfilled`.

The configuration allows for conditions to the different dimensions including Equals, Does not Equal, Greater Than, Less Than, Greater Than or Equal to, Less Than of Equal to, Is, and Is Not. Additionally, the configuration allows for dependent conditions.

In the Analytics explores, this filter can be applied to filter out these orders to reduce noise in the analysis.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/model-your-data/model-amplifications/order-filter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.