Implementation and migration
One question drove the whole design: where is the inventory value now. The answer required a state machine, an audit trail on every movement, and an honest note about two parallel ledgers.
01Key numbers
02The situation
Stock lived in a separate system and in spreadsheets. The value of what sat in the warehouse, what was in transit and what had been consumed on a job site could not be stated at a point in time.
The production forecast was parsed from workbooks with a fixed cell map, which covered 25 orders. One workbook template shifts a key cell down by one row, and that was enough to break it.
Recognise this in your own org?
03What we built
A state machine from purchase order placed, to warehouse, to in transit, to on site, to consumed, to invoiced.
Material leaving the warehouse is a cost to that project whether or not the field crew uses it. Field consumption is a progress signal, not a cost signal. That rule came from the controller verbatim, and every rollup in the system follows it.
Universal stock audit triggers log every insert and update with who, which field, the old value, the new value and the delta. Bulk edits sit behind a mandatory why-note. A count you cannot explain later is a count nobody will trust.
Stock is never written directly in code or by import, because the flows own the movement. Writing in both places double-counts. The rule is enforced by convention and by the audit log that would show it.
The production forecast parser moved from a fixed cell map to anchor-and-label lookup after one workbook template was found to shift a key cell by one row. Coverage went from 25 orders to 62 to 101.
Start a physical inventory count
412 products selected. Only ticked items on the Products tab are pulled in.
We will demonstrate any of these live, on the real org,.
One ledger is a legacy of the migration and one arrives with the Field Service install. Both are real and both are audited. The documentation says so plainly, because an architecture note that pretends a known duplication does not exist is the thing that costs the next engineer a week.
04Outcome
Inventory value is now answerable at a point in time, with the movement that produced it attached.
Purchase order and kanban totals were confirmed by logging in as the named end users who work those records, not by an administrator query.
Keep reading
Sixteen archive objects populated with zero failures, and two phantom invoices caught and removed before they touched a live record.
Receivables, payables and timesheets sync both ways on a fifteen-minute cycle. Every rule that could round, merge or classify a dollar is written down and refuses to guess.
Tell us what is broken. You get a written read on it within one business day, before any money changes hands.