Scrap is where warehouse inventory quietly stops being inventory. Material goes into a container, paperwork moves it off the customer's books, a truck takes it away. Every step is a place where the paperwork and the physical reality can drift apart.
An estimated $2,782 a year in labour time saved, by the site's own tracker. Where the figure comes from
$2,782 a year, estimated
The site's efficiency-savings tracker timed two tasks by hand and again with the software. The labour time saved comes to an estimated $2,782 a year.
| Task | Saved a year |
|---|---|
| Closing a scrap container | $2,025 |
| Opening a scrap container | $757 |
| Total | $2,782 |
Estimated by the site's own efficiency-savings tracker: each task timed by hand and again with the software, the time saved valued at a fully loaded labour rate over a 252-day working year. Labour time only, to the whole dollar.
Built for the scrap and recycling operation of a contract-logistics site, moving end-of-life material from the floor to third-party recyclers.
Freeze each container's contents when it closes, then keep comparing. In this build, closing a scrap container takes a per-item snapshot; a background job re-reads live inventory, alerts whenever anything was added after the transfer paperwork was filed, then re-arms its baseline. At the gate, any pallet assigned to the load but not scanned onto the truck blocks submission.
The chain ran on people remembering. A supervisor guessed which container was free. An analyst queried inventory and hand-typed a transfer document — the paperwork that moves material off the customer's books — then uploaded it manually to their portal. A placard was hand-written. A truck was audited at the gate against whatever was written down.
The gap that mattered had no owner at all: nothing stopped material being dropped into a container after its transfer paperwork was already filed. That inventory physically leaves the site and never appears on any document: shrink with nobody's name on it.
The full chain, automated and instrumented — container allocation verified against live inventory rather than guessed, transfer paperwork generated from actual on-hand quantities, automatic upload to the customer portal with the failure called out in red when it doesn't succeed, and placards printed on the ZPL label printers on the warehouse floor, carrying a scannable container code, load and pallet number, and captured weight. The customer portal offers no API, so the upload drives its screens, the second half of APIs over legacy systems, or screen access where there is none.
Then the control that didn't exist before.
| Step | Before | After |
|---|---|---|
| Choosing a container | A supervisor guessed which one was free | Allocation verified against live inventory |
| Transfer paperwork | Hand-typed from an inventory query, uploaded by hand | Generated from on-hand quantities, uploaded automatically, failures shown in red |
| Placards | Hand-written | Printed with a scannable container code, load and pallet number, and captured weight |
| The truck audit | Checked against whatever was written down | Blocks submission on any assigned pallet not scanned onto the truck |
| Material added after filing | Left the site on no document | Raises an alert |
The truck audit is a hard stop. If any pallet assigned to the load wasn't physically scanned onto the truck, submission is blocked and leadership is emailed — checked in the browser, re-checked on the server, and alerted independently, so bypassing the interface still produces both a block and a notification.
Two asset trackers must be logged on specified pallets before a pickup can be confirmed, and the rule is enforced identically in every path that can confirm one. The system also holds three separate records of driver, truck, trailer and plate — what was ordered, what the vendor's confirmation said, and what was verified at the gate — for no reason other than to catch the mismatch.
Weight is captured once, at placard printing, and carried forward automatically. Where a single order spans several pallets, weight resolves by container rather than by order, because keying on the order number collapses every pallet to whichever placard was printed last.
Status is derived from what actually happened — each milestone is a timestamp, and the stage is computed from them — so there is no status field to drift out of sync with reality. Stamping a milestone twice is harmless, which matters when several people work the same load.
The operation gained a control it had never had: material that leaves the building without appearing on the paperwork now generates an alert instead of a discrepancy someone finds later. That is reconciliation as a control, not a report.
So that going around the screen changes nothing. If any pallet assigned to the load was not physically scanned onto the truck, the browser blocks submission, the server re-checks and blocks it again, and leadership is emailed by an independent alert. Bypassing the interface still produces both a block and a notification.
Because a stored status can drift out of step with what actually happened. Each milestone is a timestamp, and the stage is computed from them, so there is no status field to disagree with reality. Stamping a milestone twice is harmless, which matters when several people work the same load.
Because one order can span several pallets. Weight is captured once, when the placard is printed, and carried forward automatically. Keying it on the order number would collapse every pallet in a multi-pallet order to whichever placard was printed last; keying it on the container keeps each pallet's own weight.
Client, location, system names and volumes are withheld deliberately; the savings above are the tracker's dollar estimates, with the minutes, rates and headcount behind them left out. We're happy to go deeper on architecture and approach on a call.
Squeeze more throughput out of the hardware and licenses you already pay for.
See Workload Optimization →Connect aging systems to modern APIs, data platforms, and SaaS tools.
See System Integration →Customer-facing quality audits ran on paper and a survey tool. We built a configurable audit platform with scheduling, escalation, approvals — and a gate that blocks sign-off when the scan doesn't match.
Read the story →Powered industrial trucks were signed out on a clipboard, and the fall-protection harness that some of them require was a separate honour system. We built a badge kiosk where the truck you pick decides the inspection you must pass — and which refuses to release anything that fails.
Read the story →Access was a boolean column on the user record, so every new screen was a schema change. We replaced it with roles that map to screens, credential checks that verify a second person without elevating the first, and a suspension path that fails closed.
Read the story →Walk us through one load, from the container to the truck, and where the paperwork comes from. Free assessment.
Call 832-598-8234 or email msco@stoneagesoftware.com. Houston, Texas — serving Houston, The Woodlands, Conroe, Sugar Land, Katy, Pearland, and the Greater Houston metro.
We read your message, an engineer replies with questions or a straight answer, and if a call would help, we book one. From the first reply on, you're talking to the people who'd do the work.
