Bring your devices online
Weighbridge indicators, GPS trackers, balers, shredders, environmental sensors - all streaming straight into the scrap-yard workflow. No transcription, no portals to switch between.
Live device telemetry, health monitoring, calibration audit log.
Why hardware integration is the highest-ROI thing you can do
Hardware already exists at the yard. The cost of NOT integrating it is the transcription error, the bypass, the calibration drift nobody noticed.
You bought a $40,000 weighbridge that prints a sticker. The operator types the weight into the scrap-yard software. Two transcription errors a week, undetected.
The indicator streams gross and tare directly into the ticket. Operator confirms, not transcribes. Two transcription errors a week become zero.
Insurance audit asks for the GPS trail of last week's loads. Your fleet GPS lives in one vendor portal, your dispatch lives in another, the two never talked.
The platform ingests GPS pings from your existing trackers and binds them to dispatch jobs. The GPS trail per load is two clicks - geocoded, timestamped, exportable.
Baler controller knows exactly how many bales were produced and what they weighed. The information lives on the controller's LCD and dies there. Production reports are guessed.
The baler PLC pushes telemetry to the work order. Bale count, individual bale weights, machine downtime - all captured live and rolled into the production yield report.
Inside the IoT layer
Every protocol scrap yards actually use
Most weighbridge indicators speak serial (RS-232 or RS-485) with a vendor-specific framing. Some newer setups speak TCP, MQTT or a REST endpoint. The platform supports all four with vendor-specific parsers for Avery Weigh-Tronix, Mettler Toledo, Rice Lake, Cardinal, Fairbanks, Sartorius and others. Adding a new vendor is a one-day parser, not a 6-month project.
Edge gateway for sites with bad connectivity
A small Linux daemon (or even a Raspberry Pi) sits at the scale, reads the indicator, and posts to Scraplytics. When connectivity drops, the gateway buffers locally and uploads when the connection returns. Operators see no difference; the office sees a small delay rather than missing data. Production-tested across remote yards.
Device health that surfaces problems before they hurt
Every connected device is monitored: last-heartbeat, last-reading, drift vs calibration, error rate. A scale that has not reported in 10 minutes triggers an alert before anyone tries to use it. A drift from calibration shows on the device dashboard. Maintenance becomes scheduled, not reactive.
What you get
Frequently asked questions
Will it work with my existing weighbridge?+
Almost certainly yes. The platform supports 50+ commercial indicator brands. If yours is not on the list, our team will write the parser during onboarding at no extra cost - it is typically a 1-2 day exercise for an unfamiliar protocol.
Do I need to buy specific hardware?+
No. Most yards reuse the PC already running at the scale plus a USB-to-serial adapter ($25). For remote sites we recommend a small Linux gateway (Raspberry Pi or a cheap mini-PC) but it is not required if you already have a Windows or Linux machine at the scale.
Can I integrate non-scale devices like cameras or GPS?+
Yes. The IoT pipeline is generic - any device that can POST a JSON payload (most cameras, GPS trackers, environmental sensors and PLCs can) can be ingested. Vendor-specific parsers live in the same pipeline as the weighbridge ones.
What happens if a device sends a bad reading?+
Each device has plausibility rules (weight in expected range, change vs last reading within X%, etc.). Out-of-range readings are flagged at the cashier rather than silently posted. The audit log preserves the original reading so calibration drift can be diagnosed.
Let your hardware do the data entry
Start your free trial. Our team will integrate your weighbridge during onboarding at no extra cost.
Start Free Trial