Post Filters in Datachamp: What They Are and What Makes Them Different

Post Filters

Post Filters are applied after the data has already been loaded into the report. Post Filters are especially useful when working with custom columns, calculated fields, or conditions that cannot be applied at the data source level. They support conditions such as is empty, is not empty, contains, <, > and =.

Example Post Filters:

Bundle SKU is not empty

→ Shows only bundle orders

Please take a look at our article and YouTube video on how to export bundle orders in Datachamp – here we also used a post filter: How to Export Bundels

Product Title contains “Bundle”

→ Filters orders that include bundle products

If your plan is limited to e.g. 1000 items, but you apply a post-filter to a dataset containing more items (e.g., 5000), the export will not be possible. This is because the system must first process all 5000 items in order to apply the post-filter. That total processing volume exceeds the 1000-item limit of your plan.

Therefore, it is recommended to restrict the data volume at the source level whenever possible — e.g. filter by date, status, or other criteria — so that fewer than 1000 items are loaded in the first place. If your workflow requires scanning a large database, you will need a higher pricing plan to support the required processing volume.

Regular Filters

These Filters are applied before the data is loaded into the report. They limit the data directly at the source, meaning that only matching records are retrieved from Shopify. This helps reduce the overall data volume and improves report performance.

Example Filters:

Created at after 01/01/2026

→ Loads only orders created after this date

Fulfillment Status = fulfilled

→ Loads only fulfilled orders

Updated on: 04/02/2026

Was this article helpful?

Thank you!