# How to Flag Customer Orders Above Historical Demand in QuickBooks Desktop Enterprise

> A commercial cleaning products manufacturer in central New Jersey asked for an AI tool that flags purchase order lines ordered above a customer's historical demand. What QuickBooks Desktop Enterprise can do on its own, and how Logistify's demand check, now live, decides and holds an order.

- URL: https://logistify.ai/blog/flag-customer-orders-above-historical-demand-quickbooks-desktop-enterprise/
- Author: Daniel Emaasit, CEO, Logistify AI
- Published: 2026-10-21
- Category: Sales Order Agent

**Summary:** A manufacturer of commercial cleaning and janitorial products in central New Jersey asked for an AI tool that flags purchase order lines ordered above a customer's historical demand, in QuickBooks Desktop Enterprise. QuickBooks shows the history in reports, but nothing checks a new order against it. Logistify's demand check, now live, does: a sales order that would take a customer past their usual quantity plus 15% is held until a person approves it.

## The question

A manufacturer of commercial cleaning and janitorial products in central New Jersey, USA, runs QuickBooks Desktop Enterprise and sent us this through our contact form:

> AI tool that will read customer POs and determine if any line item is being ordered at rate greater than that customer's historical demand
>
> A manufacturer of commercial cleaning and janitorial products in central New Jersey, USA

A similar request reached us in August, and [we described the demand check then](https://logistify.ai/blog/ai-order-processing-quickbooks-desktop-enterprise-demand-checking/). It's now live. This post covers what QuickBooks Desktop Enterprise can do on its own, exactly how the live check decides, and what happens to a flagged order.

## Why a manufacturer watches this

When a manufacturer sells through distributors, each distributor tends to reorder the same items in similar amounts. A line well above that pattern can be a large one-off job, buying ahead of a price change, or a typo that turned 10 cases into 100. Whatever the reason, someone should look before it ships.

## What QuickBooks Desktop Enterprise can do on its own

QuickBooks Desktop shows the history in reports. Intuit's suggested way to see how many of each item one customer bought:

1. Go to Reports, then Sales, then Sales by Item Summary.
2. Select Customize Report, open the Filters tab, choose Name and pick the customer.
3. Set the date range one month at a time to see monthly quantities, or export the report to Excel to lay the months side by side.
4. Memorize the report so the settings are saved.

Enterprise adds Advanced Reporting for more flexible reports. But a report is something a person runs and reads: Intuit's help describes reports for this, not a check that runs when a sales order is entered. At dozens of orders a day, running a report for every line of every order isn't realistic.

Sources: Intuit's QuickBooks Desktop [help on reports](https://quickbooks.intuit.com/learn-support/en-us/help-article/memorize-reports/understand-reports/L6mJBjn2h_US_en_US) and [on customizing reports](https://quickbooks.intuit.com/learn-support/en-us/help-article/report-management/customize-reports-quickbooks-desktop/L1xfYg7Bv_US_en_US), and [an Intuit answer on Sales by Item Summary for one customer](https://quickbooks.intuit.com/community/reports-and-accounting-5/reports-66707), checked 21 Oct 2026.

## How Logistify's demand check decides

The check runs on every line of a sales order before Logistify sends it to QuickBooks Desktop Enterprise. It works per customer and per item:

| Step | What the check does |
| --- | --- |
| History | Imports up to 18 months of your QuickBooks Desktop Enterprise sales orders, with their lines |
| Period | Weekly by default; daily or monthly instead, as a company-wide setting |
| Usual quantity | That customer's average total for that item per period, across the periods in which they ordered it |
| Allowance | The usual quantity plus 15% by default; the tolerance is also a company-wide setting |
| This period | What the customer has already ordered of that item earlier in the same period (cancelled orders left out), plus this order |
| Result | If this period's total would pass the allowance, the line is flagged, with the excess and a suggested quantity that stays within the allowance |

*Logistify's demand check as live on 21 October 2026.*

An example: a distributor usually takes 100 cases of mop buckets a week, so its allowance is 115. It ordered 70 on Monday. On Wednesday a purchase order arrives for 60. This week's total would be 130, so the line is flagged: 15 cases over, with a suggested quantity of 45. On its own, an order for 60 would look routine; the check catches it because it counts the whole week.

## What happens to a flagged order

- It isn't sent to QuickBooks Desktop Enterprise. Sending is paused until a person approves the order.
- A warning naming the items that are over is sent by email and shows in the app.
- A person can approve it, and must give a reason, which is recorded on the order. Or they change the quantity, and the check runs again.
- Editing an approved order clears the approval, so the changed order is checked again.
- If an earlier order in the same period is cancelled or changed, later orders not yet sent to QuickBooks are checked again.
- If the history can't be read, orders wait rather than going to QuickBooks unchecked.

## What the check doesn't do

- An item a customer hasn't ordered in the lookback has no history, so it isn't flagged. New customers and new items pass.
- The history comes from QuickBooks Desktop sales orders. If your team invoices without creating sales orders, there's no history to compare against, so tell us before switching it on.
- The tolerance and the period apply company-wide, not per customer or per item.
- It compares quantities with the customer's own history, not with stock on hand.

## How orders reach QuickBooks Desktop Enterprise

[Logistify reads purchase orders](https://logistify.ai/agents/sales-order/) from email messages, PDF, Word, Excel and CSV attachments, EDI, WhatsApp, SMS and voicemail, and matches each line to your QuickBooks items. Orders that pass the demand check, and any other checks, go into QuickBooks Desktop Enterprise as sales orders through the QuickBooks Web Connector. It doesn't read faxed orders.

## How to start

1. Send a few weeks of real purchase orders, and tell us which customers' ordering patterns matter most.
2. Logistify connects to QuickBooks Desktop Enterprise through the Web Connector and imports your sales order history.
3. Choose the period and the tolerance; the defaults are weekly and 15%.
4. Run the 30-day pilot ($1,000, up to 150 completed tasks). It's credited if you sign an annual Core or Business plan within 14 days of the pilot ending.

## Frequently Asked Questions

### Can QuickBooks Desktop Enterprise flag an order above a customer's usual quantity?

Not on its own. Its sales reports, such as Sales by Item Summary filtered to one customer, show what that customer bought, but a person has to run and read them. They don't check a new sales order as it's entered.

### How does Logistify work out a customer's historical demand?

From up to 18 months of QuickBooks Desktop Enterprise sales orders. For each customer and item, it averages the totals of the periods, weekly by default, in which that customer ordered that item.

### What's the default tolerance?

15% above the customer's usual quantity for the period. The tolerance and the period (daily, weekly or monthly) are company-wide settings.

### Does it look at the whole period or just the new order?

The whole period. It adds the new order to what the customer has already ordered of that item earlier in the period, so several ordinary-looking orders that add up to too much are caught.

### What happens to a flagged order?

It isn't sent to QuickBooks Desktop Enterprise until a person approves it with a reason, or the quantity is changed and the check passes.

### What about new items or new customers?

With no history for that customer and item, there's nothing to compare against, so the line isn't flagged.

## Related Articles

- [AI Order Processing for QuickBooks Desktop Enterprise: Order Demand Checking](https://logistify.ai/blog/ai-order-processing-quickbooks-desktop-enterprise-demand-checking/)
- [Customer-Specific Pricing in QuickBooks Desktop Enterprise: How AI Handles Price List Complexity](https://logistify.ai/blog/ai-customer-specific-pricing-quickbooks-desktop-enterprise/)
- [How AI Reads PDF Purchase Orders and Enters Them into QuickBooks Desktop Enterprise](https://logistify.ai/blog/how-ai-reads-pdf-purchase-orders-quickbooks-desktop-enterprise/)