Knowella

Compliance — check loads and orders against their rules

See which loads broke their blueprint's rules and which orders broke their purchasing rule, what each exception cost, and record a reason for it.

3 min read Real product screens
app.knowella.com Live walkthrough
Compliance, under Reporting in the Supply Chain sidebar, checks each load that moved against the rules of the blueprint it ran on, and each purchase order against its vendor's purchasing rule. It shows which broke a rule and what that cost. You can give every exception a reason code, so the team knows which were expected and which need fixing.
In this article

Open Compliance under Reporting

In the Supply Chain sidebar, open <b>Reporting › Compliance</b>. At the top right, pick the <b>Distribution Centers</b> and how far back to evaluate (for example <b>Last 3 days</b>), or select <b>Evaluate Now</b> to judge loads again. <b>Showing</b> confirms which loads are listed, such as those moved in the last 30 days.

Read the two summary cards

The cards show how compliant the period was.

  • Loads % — The share of loads that met their blueprint's rules, how many were judged, and how many exceptions are awaiting a decision.
  • Orders % — The share of purchase orders that met their vendor's purchasing rule, and how many were judged.

Search and filter

Type in <b>Search</b> to find a load, PO or blueprint, or turn on <b>Deviations</b>. Narrow the list with <b>Freight</b>, <b>Window</b>, <b>Status</b> and <b>Reason Code</b>, and use <b>Sort</b> to put exceptions first.

Browse the list

Each row shows the <b>Load</b> with its carrier, equipment and pickup time; the <b>Blueprint</b> it was judged against; the <b>System Alert(s)</b> it raised, such as cube over the trailer's capacity or weight under the blueprint minimum; its <b>Order Value</b>; its <b>Status</b>; the <b>Financial Impact</b>; and its <b>Reason Code</b>. Non-compliant loads are marked in red.

Give an exception a reason

Open a row's <b>Reason Code</b> and pick why it happened, for example <b>Accepted</b>, <b>Vendor shortage</b>, <b>Carrier capacity</b>, <b>Buyer request</b>, <b>Weather delay</b> or <b>Data error</b>. Who set it, and when, shows beneath.

Open a load

Select a load number to open it. The header shows the carrier, equipment, pickup and move dates, and its status. A banner names the blueprint it was judged against and the date of the rules used. Below are the carrier code, SCAC, mode, stops, DCs, estimated linehaul, order value and financial impact.

Compare it with the rules

<b>Measured vs the rules applied at evaluation</b> lists weight, cube, pallets, cases, order value and stops against their minimum and maximum. Any deviation is highlighted, such as cube 213 ft³ over. <b>What the run said about this load</b> sums up each issue, such as a PO that broke its vendor's purchasing rule or lanes the load didn't pick up.

Check its purchase orders

<b>Purchase orders on this load</b> lists each PO with its lane, alerts, order value, status and impact. Each PO is judged on its own rule and can have its own reason code.

Why it matters

A blueprint only pays off if loads follow it. Seeing which loads and orders broke their rules, what each exception cost, and why it happened shows whether the fix belongs with the buyer, the vendor, the carrier or the plan.

Ready to build your own?

Start free and ship your first app in minutes — or have us set it up with you.