Write a purchase order from what you’ve used
A purchase order is arithmetic. What you used over the last twelve weeks, how long the supplier takes, what is on hand, what is already on order, and the price on the current sheet. QuickBooks Desktop holds two of those five. When the other three are in the same database, the purchase order is one sentence, and it comes back as a document you can send.
What we do about it
We take your data out of QuickBooks as reports, put it in a database, and connect it to your Claude or ChatGPT. QuickBooks stays as it is.
The first step is small on purpose. We model one year of your sales data and get on a live call where you ask and your own numbers answer. You give us the three questions you most want answered, and we get you those answers or figure out how we can deliver them. You keep the database, connected to your Claude or ChatGPT.
The first step is $950, credited in full toward your setup if you go ahead. If you don’t, we delete the project and your data doesn’t stay with us. If it earns its place, we keep it current every week and send the reports you pick.
Nothing we build can write to your books.
Why QuickBooks cannot write it
QuickBooks knows what you sold, because the sales lines are there, and what is on order, because the open purchase orders are there. It does not know the supplier’s lead time, it does not trust its own quantity on hand on most files, and the supplier’s price sheet is a PDF in someone’s email.
So the purchase order is written by hand, from memory of what moves, on a Friday afternoon, and it is either too big or too small.
What the sentence needs
The sales lines are already in the database from the weekly QuickBooks export. The stock count is the weekly count. The open purchase orders are a QuickBooks report. The supplier’s price sheet, with the lead time and the unit cost, is loaded as they sent it. From there the question is the one an owner would say out loud, and the answer is the purchase order.
It is the last rung of the demo because it is the thing an owner cannot get from QuickBooks, a spreadsheet, or a bookkeeper by Friday.
The purchase order, from a fictional company
Asked in one sentence of the window supplier’s items. The supplier’s price sheet in the database also holds the increase that takes effect in August, which is why the order is priced today and not next month.
Write a purchase order to our window supplier for the next four weeks, based on what we’ve used over the last twelve weeks, what’s on order, and what’s on hand.
The supplier takes 21 days to ship, so the order has to carry the yard through the lead time and then four weeks: seven weeks of usage at the last twelve weeks’ pace, less what is on hand at both yards, less what is already on order, priced at the sheet in force today.
| Vendor SKU | Item | Used, 12 wks | Need | On hand | On order | Order | Unit cost | Line total |
|---|---|---|---|---|---|---|---|---|
| VW-CSMT-2436 | Windows:Vantera Csmt 2436 | 122 | 71 | 6 | 32 | 33 | $292.11 | $9,639.63 |
| VW-DH-3252-WHT | Windows:Vantera DH 3252 Wht | 204 | 119 | 98 | 0 | 21 | $314.58 | $6,606.18 |
| VW-AWNING-3020 | Windows:Vantera Awning 3020 | 135 | 79 | 12 | 57 | 10 | $234.33 | $2,343.30 |
| VW-BASEMENT-HOPPER-3216 | Windows:Basement Hopper 3216 | 101 | 59 | 17 | 23 | 19 | $115.56 | $2,195.64 |
| VW-DH-2842-WHT | Windows:Vantera DH 2842 Wht | 150 | 88 | 54 | 28 | 6 | $269.64 | $1,617.84 |
| VW-EGRESS-KIT-4848 | Windows:Egress Kit 4848 | 29 | 17 | 14 | 0 | 3 | $426.93 | $1,280.79 |
| VW-SLIDER-6040 | Windows:Vantera Slider 6040 | 111 | 65 | 12 | 52 | 1 | $329.56 | $329.56 |
7 lines, 93 windows, $24,012.94. Placed before the supplier’s August sheet takes effect, it is priced off the current one. Everything in it came from four things the owner already had: the weekly stock count, the sales lines, the open purchase orders and the supplier’s own price sheet.
How that was computed
with usage as (
select i.canonical_id as item_id, sum(l.qty) as used_12_weeks
from txn_lines l
join txns t on t.id = l.txn_id
join items i on i.id = l.item_id
where t.date >= '2026-05-04' and t.date < '2026-07-27'
group by i.canonical_id),
stock as (
select item_id, sum(on_hand) as on_hand, sum(on_order) as on_order
from stock_snapshots
where week = '2026-07-27'
group by item_id),
sheet as (
select c.item_id, c.vendor_sku, c.pack_size, c.unit_cost, c.lead_time_days
from vendor_catalog c
join vendors v on v.id = c.vendor_id
where v.name = 'Vantera Window Mfg'
and c.effective_date = (select max(effective_date) from vendor_catalog x
where x.item_id = c.item_id and x.effective_date <= '2026-07-27'))
select s.vendor_sku, i.name as item,
u.used_12_weeks,
round(u.used_12_weeks / 12.0 * (s.lead_time_days / 7.0 + 4)) as need_thru_lead_plus_4wk,
st.on_hand, st.on_order,
round(u.used_12_weeks / 12.0 * (s.lead_time_days / 7.0 + 4)) - st.on_hand - st.on_order as order_qty,
s.unit_cost,
(round(u.used_12_weeks / 12.0 * (s.lead_time_days / 7.0 + 4)) - st.on_hand - st.on_order) * s.unit_cost as line_total
from sheet s
join items i on i.id = s.item_id
join stock st on st.item_id = s.item_id
left join usage u on u.item_id = s.item_id
where round(u.used_12_weeks / 12.0 * (s.lead_time_days / 7.0 + 4)) - st.on_hand - st.on_order > 0
order by line_total descNorthgale Building Products is a fictional company. Every name, figure and supplier on this page is made up, built to behave like a real three-and-a-half-year QuickBooks Desktop file so we can show real screens without showing anyone’s real numbers. Data as of the 2026-07-27 refresh; the last invoice in the file is dated 2026-07-24.
Short answers
- Does the purchase order go into QuickBooks?No. Nothing we build writes into QuickBooks. The order comes back as a document. Someone keys it, the same as today.
- What if we have more than one supplier for the same item?The price sheet says which supplier the item is ordered from. Where it is both, the question names the supplier.
- Does this need the supplier’s price sheet?Yes, for the price and the lead time. Most suppliers send one as a spreadsheet or a PDF. It is loaded as they send it.