Every movement leaves a row behind it

Stock in ComOps is a ledger. Every receipt, issue, transfer and adjustment writes a row naming the document that caused it, and what an order has promised is held apart from what is free to sell. Below is what gets recorded, what the system refuses to do, and how it values what is on hand.

The ledger is the record

Every movement is appended to the stock ledger with its type and a reference to the document behind it, and nothing in the running system updates or deletes those rows afterwards. A transfer between warehouses is two rows rather than one: the quantity leaves the source and arrives at the destination as a matched pair, so a half-finished transfer is not a state the ledger can hold. Because the ledger is the record, an on-hand figure traces back to the documents that produced it.

What is promised, and what is free

A sales order line reserves the stock it needs. The reservation is released when the order is cancelled and consumed when the shipment goes out, so the quantity sitting between the promise and the delivery is visible. Stock does not go negative, and three separate guards say so: the movement writer refuses an issue that would take the balance below zero, the manual out and transfer screens check availability before they write anything, and a shipment refuses to post more than the reservation covers.

Warehouses, locations and corrections

Run as many warehouses as you need, each with its own locations under a code that is unique inside that warehouse. Items are found and moved by barcode, including scanning from a phone, and stock items are loaded or updated in bulk from a CSV file. When the count on the shelf disagrees with the count in the system, the correction is a signed adjustment movement with its own type, written under the same negative-stock guard as everything else, so the disagreement leaves a row with a reason on it.

What arrived against what you were billed

Goods receipts are posted against the purchase order, and the order status is recomputed from what has actually arrived. The supplier invoice is then matched against both, and the result is recorded on the receipt as matched, partly matched or not matched, within a tolerance you set. A discrepancy is a state you can see and work through before the payment goes out. Documents on the sales side are described on the invoicing page.

What it cost

Valuation is weighted average cost. Every receipt with a known cost rolls into the running average held on the item, and an issue is costed at the average in force on the day it happens. The stock valuation report values what is on hand on the same basis, so the report and the ledger cannot drift apart. One method, applied everywhere: no per-warehouse variant to configure and no cost layers to reason about.

From components to finished goods

Bills of material and routings describe what a product is made of and the steps it goes through. A production order is raised against a bill and a routing, released, issued its materials and completed, and every one of those steps moves stock through the same ledger as everything else. On the buying side, a reorder point and a reorder quantity on the product turn a low balance into a suggested order.

Questions we get asked

Which costing method does ComOps use?

Weighted average. Every receipt with a known cost rolls into the running average, and issues are costed at that average.

Can it run production?

Yes. Bills of material, routings and production orders, with material issue and completion moving stock through the same ledger as every other movement.