Scrap Yard Management Software

Scrap yard software for every ticket weighed, priced, and ready for inspection.

Tickets are written by hand, weights are read off a display, prices are set by the morning guess, and the compliance file is a drawer of paper. We turn that scattered yard workflow into one owned system that follows each load from the scale to the payout, and each record to the inspector.

See our work

Bring one stuck yard workflow. Leave with a buy, repair, or wait recommendation.

Trusted by

Perceptional logoMusgrave GroupUrShipper logoBrux Dental SolutionsBella Skin Institute LogoEnergia RewardsDraftly logoTuneClub LogoSekou LMS logoLogo of food order management app gulaSnelwegDealsGrubly logoPSi logoInstantor Rewards logologo of Mobile app for events, membership clubs, and communitiesAldiFest retail campaign logoVidmattic logoEMS Connect logoWorx Squad logologo of Online Web App For Making Intrologo of Referral and Viral Marketing PlatformConcurrences logoGE logoTicketstop logo

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

The weight is read off a display and typed by hand, and the ticket is the only copy.

02

A seller arrives with no ID on file and the queue stops while the office sorts it out.

03

Prices move with the market every day, but the price sheet on the wall is from last week.

Plain answer

Scrap yard software runs a yard from the scale to the payout in one place. It reads the weight straight from the scale, puts an ID scan and a photo on every ticket, prices each grade against the market, and keeps the records an inspector asks for. It fits a yard that has outgrown paper tickets, cash envelopes, and spreadsheets.

What to remember

  • Use this when scale tickets, seller records, pricing, and inventory live apart and the gaps cost margin or compliance evidence.
  • The first release should complete one load from scale to payout, not collect disconnected features.
  • A ticket is evidence, not a receipt: weight, seller, photos, grade, and price belong on the same record.
  • Quote the team's own screens as their own scope: scale ticketing, compliance, pricing, inventory, payouts, and the record of who did what are a second product, not a single admin-panel line.
  • Hire freelancers for one small, well-defined task; use one accountable agency party when the work needs coordination across scales, sellers, grades, and payouts.

The first decision is not what to build.

It is whether software is the right answer at all. We use four possible recommendations before discussing a development scope.

  • 01

    Buy

    Choose a maintained product when it handles the core workflow and the remaining gaps can be solved with configuration, a connector, or a small process change. ScrapRight, Scrap Dragon, and the AMCS recycling suite cover scale ticketing, compliance, and inventory for most yards, and CRGG Scrap covers Illinois compliance ticketing. Compare them against your real yard flow, your scale, and your state's rules before paying for anything custom.

    Run the build-vs-buy numbers

  • 02

    Repair

    Keep the existing product when users still get value from it and the code can be understood safely. Start with evidence: where the code lives, how your data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live.

  • 03

    Build

    Own the system when the way you buy, price, and prove shapes margin, compliance, and trade loyalty. Start with one load path that runs from scale to payout, and the system connections that path cannot work without.

  • 04

    Wait

    Do not turn a changing policy into permanent software. Stabilise the rules, name the workflow owner, and measure the cost of the current process before paying for a product.

Not sure which path is yours? Bring it to a 30-minute call. Leave with the answer in writing.

Fit

Scrap yard software should earn its maintenance burden.

A feature request is not enough. The case is real when the same constraint shows up in time, errors, margin, or compliance risk.

A fit

Scale tickets, seller records, pricing, and inventory live apart, and the gaps cost margin or evidence.

A yard running more than one scale or station can name a workflow owner and what 'done' looks like for the first release.

Pricing, grading, or compliance rules differ by state or by buyer and no maintained product holds them cleanly.

Not a fit

A maintained product fits with reasonable configuration and process change.

The team wants software to settle an unresolved operating policy.

The brief is a feature list with no load, seller, or business result attached.

Not sure which side you are on? Use the first call to make that decision. A useful answer may be to buy, connect, repair, or wait.

Start with the load, not the software.

A scrap yard problem usually starts as an operating problem. A truck pulls onto the scale and the weight is read off a display and typed by hand. The seller has no ID on file, so the queue stops while the office sorts it out. The price is set by the sheet on the wall, which is from last week, while the market moved yesterday. The ticket is printed once, and the only other copy is a drawer of paper that an inspector may ask for at any time.

The cost is easy to miss because it is spread across the yard. A weight typed by hand is a mistake waiting to happen, and the whole margin rests on accurate, certified weighing. Every price set from an old sheet is money given away or a supplier who walks to the yard down the road. A compliance record that cannot be pulled up in seconds is a licence at risk, and a licence at risk is a loan at risk.

A second product hides inside the first. Sellers see one ticket; your team lives in another: scale ticketing, compliance, pricing, inventory, payouts, and a record of who did what. Quotes that squeeze all of that into an "admin panel" line item are where budgets most often break. On a real platform, your team's screens are routinely the most underestimated part of the build, so we quote them as their own job, with their own users, from the start.

Scrap yard software makes sense when one owned system can remove that constraint better than a product, connector, or process change. The first release should take one load from scale to payout. It should not replace every tool at once.

We start where it hurts.

The interface is only one part of the job. The real scope includes the rules, the data, the connections to your other systems, what happens when things fail, who can see and change what, and who runs it after release.

A ticket that starts at the scale

Weights come straight from your certified scale, with motion lock on the reading. Gross, tare, and net are calculated on the ticket, not typed from a display, and the ticket is saved and searchable in seconds.

ID, photo, and plate on every purchase

The ticket cannot be finished without the seller's ID on file, a photo of the seller, and a photo of the material on the scale. The compliance record is built as the work happens, not reconstructed when an officer asks.

Prices that follow the market, not the morning guess

A price matrix by grade, tied to the market index, with contamination deductions and volume bonuses applied by rule. The supplier sees an itemised ticket with a price they can check against the market, and the yard keeps its margin.

Inventory that knows what the pile is worth

Every load lands in a grade, and every grade lands in a pile with a weight and a value. Outbound sales to mills draw from the same inventory, so the yard knows what it holds, what it is worth, and what is ready to ship.

Your team's screens, quoted as their own job

Scale ticketing, compliance, pricing, inventory, payouts, and the record of who did what are a second product, not one line buried in the quote. We quote them as their own scope, with their own users, from the start.

Which one is yours?

Bring it to a 30-minute call. Leave with a buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

Workflows

One record from scale to payout.

Some of this work only exists in one corner of the business. The same rules apply: configure first, build only the part the maintained products cannot cover, and start with one complete path.

Public peddler buying

The walk-in trade: a seller, a load, a scale ticket, an ID scan, and a payout. The queue moves fast because the ticket, the compliance, and the payment are one flow, not three.

Industrial and demolition accounts

Trade accounts won on relationships, reliable payment, and a fair, transparent price sheet. Each account carries its own pricing, its own containers, and its own invoice, separate from the public queue.

Catalytic converters and high-value non-ferrous

The material that brings the strictest rules: vehicle identification numbers, proof of ownership, and payment holds where the law requires them. The converter is tracked by serial and by source, not by the pile.

Outbound sales to mills

Sorted, baled, and shredded material sold onward to mills and smelters. The outbound load draws from graded inventory, and the sale, the weight, and the price sit on the same record as the buying tickets that filled it.

Proof

The fifth attempt became a product customers could keep using.

UrShipper had already worked with four development vendors. Its founder describes the communication and decisions during the recovery.

The case study documents a 14-week recovery, five carrier connections, a Shopify fulfilment workflow, and client-reported results. It is one comparable project, not a promise that every inherited codebase can follow the same plan.

Read the UrShipper case study

Which load is costing you the most right now?

Bring it to a 30-minute call. Leave with a buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

How it works

Close one expensive risk before opening the next.

Each stage answers a buyer question and leaves behind a decision you can inspect. The next stage only opens when the expensive uncertainty in the current one is small enough to accept.

  1. 01
    Understand

    Trace the real yard workflow

    Where is the cost or failure actually coming from?

    Follow one load and one seller from the scale to the payout. Include the workarounds, manual judgement, duplicate entry, waiting, and failure paths that a tidy process diagram usually misses.

    Decision produced

    A map of the yard workflow, exceptions, owners, systems, and the baseline cost or delay worth changing.

    Risk closed

    Paying to automate the visible symptom while the expensive constraint remains.
  2. 02
    Shape

    Choose the first useful release

    What needs to exist together for one useful result to work?

    Choose the shape from the way the work happens, not from a preferred technology. Name the user, the device, the data, the system connections, who can access what, the exceptions, and the result the first release must complete.

    Decision produced

    The right mix of web, mobile, desktop, browser extension, connected device, wearable, or behind-the-scenes connection work, with the first-release boundary and a clear definition of done.

    Risk closed

    A small-looking feature list that quietly depends on several interfaces, systems, and owners.
  3. 03
    Prove

    Review working software

    Will it hold up outside a controlled demo?

    Review the product against the agreed workflow, not a tour of finished screens. Record changed assumptions and test what happens when data is missing, access is wrong, or a connected system fails.

    Decision produced

    Working checkpoints tested with realistic data, real user types, system connections, recovery plans, and the people who will use or run the system.

    Risk closed

    Discovering the important gaps during migration or after customers depend on the release.
  4. 04
    Transfer

    Release, measure, and hand over

    Did the new workflow improve the original constraint, and can another capable team operate it?

    Move a controlled set of loads or stations first. Compare time, errors, completion, or another agreed measure with the starting point before adding the next workflow.

    Decision produced

    A controlled release, comparison with the baseline, operating notes, account ownership map, and a recommendation for what should happen next.

    Risk closed

    Measuring development activity instead of the business result, or depending on the original vendor to keep the system running.

What stays out of the black box

These are operating conditions to put in the engagement, not claims to take on faith.

The scope names the whole yard

The user, the trigger, the decisions, the data, the exceptions, and what 'done' looks like. A screen list is not enough.

Progress is visible in working software

Reviews against the product at agreed checkpoints, while there is still time to act. You see the yard workflow working, not a slide deck about it.

A scope change has a price before it has code

A new workflow or system connection shows its effect on cost and timing before anyone approves it.

Ownership exists throughout, not only at handover

Code, cloud, data, and provider access stay visible and under your control from day one.

You can judge the work without being technical

Checkpoints are working software you use yourself, reported in plain language. If a step fails, you see it fail in the product, not in a status report.

Scrap yard software by related service.

Start from the surface or the system behind it. Each area below is a working practice with shipped products behind it.

What it costs

Every project starts at $10000.

The first phase turns the costliest patched yard workflow into a scoped build with written acceptance criteria.

Starting investment

Starts at $10000

Workflow complexity, systems to connect, data migration, and user roles set the scope. After a 30-minute call, you get a written buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.

Buy or own

Buy a maintained productOwn custom software
Best fitHandles your yard workflow with reasonable setup, and its pricing makes senseThe way you buy, price, and prove is itself the advantage
Manual workConfiguration and process changes can remove the constraintRepeated manual work has a measurable cost
ConnectionsExisting connections work with reasonable setupA critical connection to your scale, accounting, or law-enforcement reporting cannot be done cleanly any other way
Platform routeConfigure a maintained product when its ticket, compliance, and inventory model fitsOwn custom software only when the differentiating process, pricing rules, or cost of constraint justifies build and support

Work with us

Bring one stuck yard workflow. Leave with a decision.

In a 30-minute call, we will help you decide whether to buy, connect, repair, build, or wait. If custom software is not the sensible next move, that is still a useful answer.

  • One named workflow owner and one yard path scoped for the first phase.
  • Scope, price, what 'done' looks like, and exclusions agreed before paid work starts.
  • Code, cloud, data, and provider access remain under your control.
  • Post-launch warranty cover for defects in the agreed scope.

Common questions

Scrap yard software runs a yard from the scale to the payout in one place. It reads the weight straight from the certified scale, puts an ID scan and a photo on every ticket, prices each grade against the market, and keeps the records an inspector asks for. It covers public peddler buying, industrial and demolition accounts, high-value non-ferrous, and outbound sales to mills.

It fits three buyers with the same scattered workflow. A public yard buying from walk-in sellers needs fast scale tickets, ID capture, and payouts on one flow. A yard running trade accounts needs per-account pricing, containers, and invoicing separate from the public queue. A multi-yard operator needs the same ticket, compliance, and inventory shape across every station. A one-scale yard writing a handful of tickets a day can usually stay on paper until the compliance file, not the volume, is the problem.

A truck drives onto the certified scale loaded, and the software reads the gross weight from the scale indicator, with motion lock on the reading. The truck dumps the material and re-weighs empty for the tare, and the ticket subtracts tare from gross to get the payable net weight. Grade deductions and contamination are applied on the ticket, and the ticket is printed and saved in one step.

The ticket cannot be finished without the seller's government photo ID on file, a photo of the seller, a photo of the material on the scale, and the vehicle plate where the rules require it. The records are kept for the period the local law requires, and they can be pulled up for a law-enforcement inspection in seconds. Illinois, for example, requires an ID scan on every purchase and keeps purchase records for three years. The yard stays responsible for its own compliance; the software makes the records exist.

A price matrix by grade, tied to the market index, with contamination deductions and volume bonuses applied by rule instead of by memory. Ferrous and non-ferrous grades each carry their own price, and high-value material such as copper and catalytic converters is priced separately with its own checks. The supplier sees an itemised ticket with a price they can check against the market, which is what wins trade loyalty.

Catalytic converter theft has brought the strictest rules in the yard: the vehicle identification number and proof of vehicle ownership are recorded, and payments are held for the waiting period the law requires. Each converter is tracked by serial and by source, and the records can be sent to law-enforcement registries. A converter in the pile without a source is a risk, not inventory.

The payout follows the ticket: net weight, grade, price, and any deductions, in one calculation the seller can read. Where the law bans cash, as in the UK and parts of Australia, payment goes by cheque or bank transfer with the records kept for three years. Where cash is allowed, the payout voucher can go to an automated cash dispenser, so the cashier never holds the float.

Every load lands in a grade, and every grade lands in a pile with a weight and a value that follows the market. Unprocessed material is tracked through sorting, baling, and shredding into outbound mill commodities, so the yard knows what it holds, what it is worth, and what is ready to ship. The outbound sale draws from the same inventory as the buying tickets that filled it.

It should connect to the hardware and systems the yard already runs. Certified scale indicators from Rice Lake, Cardinal, and Mettler Toledo feed weights straight into the ticket, invoices and payouts reach your accounting without retyping, and daily transaction logs can go to law-enforcement portals such as LeadsOnline where the state requires it. Name the exact scale, accounting, and reporting systems in the first call, and confirm each connection before it is promised in scope.

Buy a maintained product when it handles your workflow with reasonable setup and its pricing makes sense. ScrapRight, Scrap Dragon, and the AMCS recycling suite cover scale ticketing, compliance, and inventory for most yards, and CRGG Scrap covers Illinois compliance ticketing. Own custom software when your pricing, grading, or compliance rules do not fit any maintained product, or when the way you buy and prove is itself the advantage. If the rules of the operation are still changing every week, wait and settle them first.

For a small, well-defined task with someone technical managing it, freelancers are often cheaper. The pattern that goes wrong is a non-technical buyer coordinating several freelancers becoming the project manager, the tester, and the person who discovers the pieces do not fit. A scrap yard software company earns its fee when the work needs coordination across scales, sellers, grades, and payouts: one accountable party, one phase price, and checkpoints against the whole workflow. If your need is one screen or one fix, hire the freelancer.

The first paid phase may cover a bounded audit, a proof of concept, a recovery plan, or a small first release. The final price depends on how deep the workflow goes, how many kinds of users it serves, what it needs to connect to, whether data needs moving over, whether phones or tablets are involved, any compliance requirements, and the condition of existing code. The agreed phase is priced in writing before it starts.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the workflow agreed at the start. Progress is reported in plain language: what changed, what is next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads. Our job is to make the work checkable; your job is to check it against your business.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

Every launch includes post-launch warranty cover for defects in the agreed scope, release support, and small screen corrections. After that, work can continue as another fixed phase or an ongoing product engagement. The code and accounts stay under your control either way.