The reports

This is the reference for all fourteen reports. For each one: what a row is, the columns it ships with, the columns you can add from Display options → Columns, the figures in the totals strip, and what a row breakdown opens.

Manufacturing

Build output

What your shop built in the period, per item, with the work orders and build runs behind it.

One row per item, period and location.

Column	What it is	Shown by default
Item	The finished good, sub-assembly or variant that was built	Yes
Location	The production location the run happened at	Yes
Item type	BOM, Sub-assembly or Variant	Yes
Units built	Units produced by build runs in the build direction	Yes
Units reworked	Units run again as rework	Yes
Units disassembled	Units taken apart again	Yes
Net units	Units built minus units disassembled. Rework is replacement, not new output, so it stays out	Yes
Work orders	How many work orders contributed	Yes
Build runs	How many build runs contributed	Yes
Average per run	Built plus rework, divided by the build-direction runs	Yes

Totals strip: Units built · Build runs · Units reworked · Units disassembled · Items.

Breakdown: every build run behind the row, named by its work order and run id, with the units it contributed. A disassembly counts negative, so the lines sum to built plus rework minus disassembled.

Scrap and quality

What quality control approved, failed, scrapped and sent back for rework, per item.

One row per item and period.

Column	What it is	Shown by default
Item	The finished good, sub-assembly or variant reviewed	Yes
Item type	BOM, Sub-assembly or Variant	Yes
Approved	Units the reviewer passed	Yes
Failed	Units the reviewer failed	Yes
Scrapped	Failed units the reviewer scrapped	Yes
Sent to rework	Failed units the reviewer sent back	Yes
Scrap rate	Scrapped as a share of what was reviewed	Yes
Top failure category	The failure category with the largest quantity on this row	Yes
Reviews	How many reviews contributed	No

Voided reviews are excluded entirely, so a reversed build run’s approvals and failures leave the figures.

Totals strip: Approved · Failed · Scrapped · Sent to rework · Items.

Breakdown: the failure categories behind the row, with the units failed under each. A failure with no category reads Uncategorized.

Cost per build

Planned against actual cost for every completed work order, with the variance per unit.

One row per completed work order. Work orders in progress are not in this report.

Column	Shown by default
Work order	Yes
Completed	Yes
Units completed	Yes
Planned total	Yes
Actual total	Yes
Actual cost per unit	Yes
Variance	Yes
Planned materials · Planned sub-assemblies · Planned labour · Planned overhead	No
Actual materials · Actual sub-assemblies · Actual labour · Actual overhead	No

Variance is measured against the latest plan, not the plan as it stood when the work order was created: editing a material or a quantity recomputes the planned figure.

A work order that recorded no consumption at all — a material-list-only one, for instance — reports no actual cost rather than zero, and its units leave the average.

Totals strip: Actual cost · Planned cost · Average cost per unit · Units completed · Work orders.

Breakdown: the work order’s items, each with the units completed, the unit cost it was costed at, and the quantity scrapped.

Manufacturing consumption

What manufacturing picked, consumed and returned, per material and location.

One row per material, period and location.

Column	What it is	Shown by default
Material	The raw material, sub-assembly or finished good consumed	Yes
Location	Where the movement happened	Yes
Material type	Raw material, Sub-assembly or BOM	Yes
Picked	Units picked for a run	Yes
Consumed	Units actually consumed, net of any reversal	Yes
Returned	Units returned to stock	Yes
Cost at consumption	What those units cost at the moment they moved	Yes
Work orders	How many work orders contributed	Yes

This is the one report whose money is the cost at the moment of the event rather than today’s cost. A fully reversed run reads nothing consumed beside what it returned. There is no scrap column here: scrapped units are Scrap and quality’s question.

Totals strip: Consumed · Consumption cost · Returned · Materials.

Breakdown: the work orders behind the row, each with what it consumed, picked and returned.

Throughput

How long work orders took from creation to completion, and how many met their due date.

One row per completed work order.

Column	What it is	Shown by default
Work order	The completed work order the row measures	Yes
Created · Started · Completed · Due	The work order’s own timestamps	Yes
Lead time	Creation to completion	Yes
On time	Whether completion fell on or before the due date	Yes
Wait before start	Creation to start	No
Time in build	Start to completion	No
Units completed	Units the work order finished	No
In progress at period end	How many work orders were still open when the period (or bucket) closed. Marked Estimate, because exactly where the boundary falls changes it. Only meaningful with a Group by	No

On time compares calendar days in your shop’s time zone on both sides, because a due date is a day and not an instant. A work order that is re-opened counts as work in progress again.

Totals strip: Work orders · Average lead time · On time · Units completed.

Breakdown: the work order’s lifecycle steps in order — Created, Marked ready, Started, Paused, Sent to quality control, Completed and the rest — with the time each one took.

Bill of materials

All five read what your order executions demanded. Three of them also answer on the Sold basis; see Basis.

Finished goods demand

What orders demanded of each finished good, and how much of it came off the shelf.

One row per finished good, period and location. Two bases.

Column	What it is	Shown by default	Basis
Finished good	The finished good the orders demanded	Yes	Both
Location	The location the execution resolved to	Yes	Both
Net units	Demanded minus restored	Yes	Both
Orders (counted per bill)	Distinct orders touching this bill	Yes	Both
Executions	How many executions contributed	No	Executed only
Units demanded	What orders asked for	No	Executed only
Units restored	What refunds and cancellations put back	No	Executed only
From the shelf	Units met from pre-assembled stock	No	Executed only
From components	Units built out of components at order time	No	Executed only
Revenue	The discounted total of the units sold, net of refunds and edits	No	Sold only

Totals strip (Executed): Net units · Units demanded · Units restored · From the shelf · Finished goods. Totals strip (Sold): Net units · Orders · Revenue · Finished goods.

Breakdown: the components one level below this bill — its sub-assemblies and raw materials — with what each was demanded for. Not available on the Sold basis.

Sub-assembly demand

What executions demanded of each sub-assembly, and whether it came off the shelf, out of components, or fell short.

One row per sub-assembly, period and location. Two bases.

Column	What it is	Shown by default	Basis
Sub-assembly	The sub-assembly the executions demanded	Yes	Both
Location	The location the execution resolved to	Yes	Both
Demanded	What executions asked for	Yes	Both
Parent finished goods	How many bills demanded it	Yes	Both
Orders (counted per sub-assembly)	Distinct orders touching this sub-assembly	Yes	Both
From the shelf	Met from pre-assembled stock	No	Executed only
From components	Built out of its own components	No	Executed only
Shortfall	Demanded but met by neither	No	Executed only
Cut off	How many executions found this sub-assembly limited to its pre-assembled stock — the Only consume pre-assembled setting	No	Executed only
Shelf share	From the shelf as a share of demanded	No	Executed only

Totals strip (Executed): Demanded · From the shelf · From components · Shortfall · Sub-assemblies. Totals strip (Sold): Demanded · Parent finished goods · Orders · Sub-assemblies.

Breakdown: the finished goods this sub-assembly was demanded by, with the quantity each one demanded. Not available on the Sold basis.

Raw material demand

What orders consumed of each raw material, what refunds put back, and what it is worth.

One row per raw material, period and location. Two bases.

Column	What it is	Shown by default	Basis
Material	The raw material the orders demanded	Yes	Both
Location	The location the material was demanded at	Yes	Both
Net demand	Demanded minus restored	Yes	Both
Orders (counted per material)	Distinct orders touching this material	Yes	Both
Finished goods	How many bills demanded it	Yes	Both
Unit cost	The material’s cost per unit today	Yes	Both
Demand value	Demanded quantity at today’s unit cost. Marked Estimate	Yes	Both
Demanded	What executions asked for	No	Executed only
Restored	What refunds and cancellations put back	No	Executed only

Demand value is priced at today’s cost, because the demand record stores quantities and not the price of the day. For what a consumption actually cost when it happened, read Manufacturing consumption.

Totals strip (Executed): Net demand · Demanded · Restored · Demand value · Materials. Totals strip (Sold): Net demand · Demand value · Orders · Materials.

Breakdown: the assemblies the material was pulled through, with the quantity each path carried. A material that hangs off the bill itself is reported under that bill. Not available on the Sold basis.

Pre-assembled usage

How much of what your shop assembled came off the pre-assembled shelf instead of being built from components.

One row per assembly and period, where an assembly is a finished good or a sub-assembly at any depth. One basis. No Location column, though the location scope still decides which executions count.

Column	What it is	Shown by default
Assembly	The bill or sub-assembly	Yes
Assembly type	BOM or Sub-assembly	Yes
Demanded	What executions asked for	Yes
From the shelf	Met from pre-assembled stock	Yes
From components	Built out of components	Yes
Shelf share	From the shelf as a share of demanded	Yes
Shortfall	Demanded but met by neither	Yes

Totals strip: From the shelf · From components · Shortfall · Assemblies · Shelf share. The strip’s shelf share is the ratio over the whole period, not the average of the per-row shares, so a one-unit assembly does not weigh as much as a thousand-unit one.

Breakdown: the orders the assembly was pulled for, with what each demanded and how it was met.

Execution health

How many order executions ran in each period, how many failed, and how long they took.

One row per period. It is the one report whose row is a stretch of time rather than a thing, so it opens grouped by week. It has no location control (one execution can touch several locations), no search box (there is no name in it) and no row breakdown — a stretch of time has no named parts to open.

Column	What it is	Shown by default
Period	The week, day or month	Yes
Executions	Executions that ran	Yes
Failed	Executions that failed	Yes
Nothing to build	Executions that matched no bill at all	Yes
Average processing time	How long the app itself took	Yes
Average time from order to done	From the order notification arriving to the execution finishing	Yes

Totals strip: Executions · Failed · Average processing time.

Sales

Both sales reports read a local copy of your Shopify orders. See Order sync.

Unmodelled sales

Variants you sold in the period that have no bill of materials behind them.

One row per variant and period. No location control: a variant with no bill consumes nothing anywhere.

Column	Shown by default
Product	Yes
SKU	Yes
Units sold	Yes
Orders	Yes
Revenue	Yes

This is the list of things you might want to model. Sorted by units sold, the top of it is where modelling pays off first.

Totals strip: Units sold · Revenue · Variants.

Breakdown: the orders this variant was sold on, with the units on each.

Orders without execution

Orders that contain a finished good you model, and for which no bill of materials was ever executed.

One row per order, newest first. No location control, and no row breakdown.

Column	What it is	Shown by default
Order	The order number. Selecting it opens the Historical Orders tool with that order already selected	Yes
Created	When the order was placed	Yes
Modelled lines	How many lines on it match a bill	Yes
Units	How many units those lines carry	Yes
Status	Never seen, or Seen, no BOM matched	Yes

The two statuses mean different things:

Never seen. The app has no record of the order at all. Either it was placed before you installed the app, or its notification never arrived.
Seen, no BOM matched. The app processed the order and executed nothing, because nothing on it matched a bill of materials at the time.

To take several at once, tick their rows and choose Replay selected, which opens the same tool with all of them loaded.

The report never replays anything itself. The Historical Orders tool checks each order first, tells you which ones it will skip and why, and asks you to confirm, because replaying an order consumes its components for real and cannot be undone.

Totals strip: Orders · Units.

The summaries

Both are scorecards: five figures for the period, and the same five for the period before it. They have no rows, so no Group by, no filters, no columns, no breakdown and no export.

Manufacturing summary

Figure	Where it comes from
Units built	Build output
Scrap rate	Scrap and quality
Cost per unit	Cost per build
On time	Throughput
Consumption cost	Manufacturing consumption

Carries the period control and the location scope.

Sales summary

Figure	Where it comes from
Net units sold	Your orders, net of refunds and removed units
Revenue	Your orders, net of refunds and edits
Orders	Distinct orders with at least one line still sold
Unmodelled units	Unmodelled sales
Orders without execution	Orders without execution

Carries the period control only. There is no location scope: an order line has no location of its own, only its shipments do, and this scorecard counts the shop.

Where to next

Reading a report — the toolbar, charts, saved views and export.
Order sync — the copy of your Shopify orders the sales reports read.
Overview — the catalogue and the three families.