Distributors and trade suppliers running a few hundred SKUs, who need one figure for stock on hand that nobody has to remember to update.
Stock on hand is a number somebody types, so it is wrong within a week and everyone quietly stops believing it.
Here it is not typed at all. Qty Purchased totals what arrived on purchase orders, Qty Sold totals what went out on sales orders, and Qty On Hand is the difference - a calculation, so it cannot drift away from the orders underneath it.
A stock count disagrees with the system and nobody can say which order caused the gap, because the figure has no history behind it.
Every unit in the total is traceable to a line on a real order. The number is not an assertion, it is a sum you can open and walk back through to the purchase or the sale that produced it.
Reorder decisions get made from memory, usually the week after the shelf emptied.
Products carry a Reorder Level beside the calculated Qty On Hand, the build produced a Stock Levels & Reorder Watch report, and Low Stock Alerts leads the dashboard - so the question is answered on arrival rather than asked.
Working out what a customer is worth, or what you have spent with a supplier, means exporting two things and adding them up by hand.
Total Purchased sits on the customer and Total Spent on the supplier, each summing the line totals of their own orders - and those line totals are themselves calculated from quantity and price, so it is arithmetic all the way down with nothing stored for anyone to overwrite.
“We wholesale electrical components — sales orders with line items, purchase orders to suppliers, and stock that tracks itself”
Every table, link and rollup below was captured from the live build it started. It finished in 2 min 26 sec, with 36 sample records already in it. Nothing here is illustrative.
Each of these is computed by travelling a relationship, so it updates when the records behind it change — nobody retypes a total.
sum of Sales Orders (linked by customer) → Line Total
sum of Purchase Orders (linked by product) → Quantity Ordered
sum of Sales Orders (linked by product) → Quantity
sum of Purchase Orders (linked by supplier) → Line Total
Customers: Grid / Map, Products: Grid / Board, Purchase Orders: Grid / Board, Sales Orders: Grid / Board, Suppliers: Grid / Map
Products
Low Stock Alerts · Revenue (Last 30 Days) · Open Committed Spend · Sales Orders by Status · Incoming Purchase Orders · Top Customer (Total Purchased) · Morning Summary · Recent Activity
Because everything it depends on is already recorded. The quantity on each purchase order adds up to Qty Purchased, the quantity on each sales order adds up to Qty Sold, and Qty On Hand subtracts one from the other. No screen asks anyone to maintain it, which means no screen offers anyone the chance to get it wrong, and correcting a mistyped order quantity corrects the stock figure in the same motion.
Yes, and this build leans on it twice. Line Total is worked out per order from quantity and price, and both Total Spent on the supplier and Total Purchased on the customer add those calculated figures up. Neither level is stored anywhere, so a corrected price flows through the line and into every total that reads it without anyone recalculating a thing.
You reconcile by fixing the orders rather than overwriting the total, which is the point. If ten units went out unrecorded, the missing sales order is the thing that is wrong, and adding it corrects the stock figure, the customer's lifetime value and the revenue reporting together. A system that lets you type over the stock number lets you hide the missing order forever.
Yes. Purchase orders link to a supplier and to a product independently, so the same SKU can arrive from several sources and every one of those receipts still counts toward the same Qty Purchased. Each supplier keeps their own Total Spent, so you can see who you actually buy from without that splitting the product record in two.
No, and a distributor who needs a general ledger, landed costs or warehouse management should buy those. What this is: the order-and-stock spine, modelled so the numbers derive from the transactions, working this afternoon and changeable by you on a Tuesday. Plenty of businesses spend two years implementing an ERP to reach a worse version of exactly this.
It is real, editable data that exists so the workspace demonstrates itself rather than opening empty - thirty-six records here, including orders whose quantities are what make the stock calculation show a believable number on the very first screen. Delete it in bulk when you are ready for your own, or edit the rows into your first real orders.
There is no template to wait for. Type a sentence about what you run and RowFold assembles the tables, links, views and dashboard around it — then you change whatever does not fit.