Order exclusion

Order exclusion lets you control which orders count toward your forecast. Some orders aren’t real demand — provisional deposits, internal test orders, unpaid placeholders — and you don’t want them inflating what Logistified thinks you sell. Order exclusion filters those orders out of the forecast’s sales history without deleting them.

It lives on the same page as product data exclusion: Settings → Data exclusion → Orders tab.

On this page

• How it differs from product exclusion
• Two modes
• Building a rule
• Saving vs. rebuilding
• Automatic re-inclusion
• What it does not affect
• See also

How it differs from product exclusion

Product data exclusion hides whole products from analytics. Order exclusion is narrower: every order is still saved and visible — order exclusion only governs whether an order’s quantities feed the forecast’s order history (the sales signal behind demand forecasting and suggested purchase / transfer quantities).

Note

Filtered-out orders are never deleted. They stay in Logistified exactly as before — they simply don’t contribute to the forecast.

Two modes

A toggle at the top of the Orders tab decides what your rules do:

Mode	Meaning
Exclude matching orders (default)	An order is dropped from the forecast if it matches any rule. Everything else is kept. (A denylist.)
Keep only matching orders	Only orders that match a rule are kept; all others are dropped. (An allowlist — e.g. “only count Paid + Fulfilled orders.”)

In both modes, having no rules means no filtering — every order feeds the forecast. (So “Keep only matching” with zero rules doesn’t accidentally empty your forecast.)

Building a rule

Click Add rule. Each rule combines up to three conditions:

Condition	What it matches
Order tags (any of)	The order carries any of the tags you list. Pick from your store’s existing order tags, or type a custom tag.
Payment status	Paid only, Unpaid only, or Any (don’t filter by payment).
Fulfillment / order status (any of)	The order’s fulfillment status is one of those you list (e.g. Unfulfilled, Fulfilled, On hold). Pick from the statuses seen in your store.

How the matching works:

• Within a rule, every condition you set must match (AND). Leave a condition on Any to ignore it.
• Across rules, an order matches if it matches any rule (OR).
• A rule with no conditions does nothing — set at least one.

Each rule shows a plain-English preview as you build it, for example: “Excludes orders that are tagged Bank Deposit and Unpaid.”

Tip

Common use case: a store tags provisional orders (deposits, reduced-VAT placeholders) and wants them out of the forecast while they’re still unpaid. A single rule — tag Bank Deposit + Payment status Unpaid only, in Exclude mode — does exactly that. Once such an order is paid, it stops matching and re-enters the forecast on its own (see below).

Saving vs. rebuilding

These are two separate steps:

1. Save order rules — applies your rules to new incoming orders from this point on.
2. Rebuild order history — re-applies the rules to orders already in the database. Logistified recomputes the forecast’s order history for every variant from scratch (deleting and rebuilding in batches), so existing orders respect the current rules. A progress bar shows how far it’s got.

Caution

Saving alone does not retroactively change existing orders. After you change your rules, click Rebuild order history to apply them to past orders. For large catalogs the rebuild can take a while.

Automatic re-inclusion

You don’t have to babysit individual orders. When an order changes in a way that flips its decision — an unpaid order gets paid, or its fulfillment status changes — Logistified automatically re-applies your rules to that order and updates the forecast. A provisional order that was excluded while unpaid quietly re-enters the forecast once it’s paid, with no manual rebuild needed.

(The manual Rebuild order history button is only needed after you change the rules themselves, to reconcile past orders.)

What it does not affect

• It does not delete orders. They stay fully intact in Logistified.
• It does not change your sales dashboard or ABC analysis. Those report your actual sales — order exclusion only shapes the forecast’s demand signal.
• It does not touch Shopify. Nothing is written back.

See also

• Settings → Data exclusion — the product/variant sibling on the same page.
• Forecast → Overview — where the order-history signal drives demand.

Last updated: 9 June 2026