The Ticket-First Principle

A scrap yard has one irreversible moment: material crosses the weighbridge, a number is agreed, and money changes hands. After that, every other record - inventory, payables, tax, the audit trail, margin analysis - is a derivation of what the ticket said.

This has three consequences, and they are the reason Scraplytics is built the way it is.

One: capture completeness beats downstream reporting

A ticket missing its deduction reason cannot be reconstructed later. No amount of business intelligence recovers information that was never recorded. This is why the ticket asks for the reason at the moment of the deduction rather than offering a report that flags missing reasons afterwards.

Two: the ticket must be immutable once approved

If a ticket can be edited after the fact, then inventory, tax and margin all rest on something that can move. The record stops being evidence and becomes an opinion. Scraplytics writes every approval, price change and pre-approval edit to an append-only log, so what a load weighed and what was paid for it cannot be quietly rewritten.

Three: valuation follows the ticket, not the other way round

Weighted average cost is computed from what was actually paid. Where the ticket is wrong, the valuation is wrong, and the error compounds silently through every subsequent movement - consumption, processing, sale. A yard that discovers a costing problem is usually discovering a capture problem from three months ago.

How Scraplytics implements this