Quarry Scale House and Ticketing Software: Custom vs Off-the-Shelf
Buy for one or two pits. A packaged scale ticketing product connected to your accounting system will price loads, print a legal weight ticket and cost less than the discovery phase of a custom project.
On this page
Buy for one or two pits. A packaged scale ticketing product connected to your accounting system will price loads, print a legal weight ticket and cost less than the discovery phase of a custom project. Build at three or more pits with different price books, when royalty terms differ per lease, or when month end regularly turns up loads that nobody invoiced.
What Command Alkon Apex and Libra Systems actually do well
Producers who dismiss these products usually end up commissioning a worse version of them, so be honest about what they already solve.
Command Alkon is the established name across aggregates and ready mix, and Apex is a mature ticketing product with real depth in dispatch and in the connections between pit and concrete operations. If you run both sides of that business and want one supplier across them, that argument is strong and the product is good. Libra Systems has long roots in scale house automation and unattended weighing hardware, and shops that need the physical side handled properly have relied on it for years. Creative Information Systems and TAC Insight both serve smaller producers well at a price a single-pit operation can justify.
What all of them give you is the part that is genuinely hard to build from nothing: a ticket that prints reliably at the scale, an interface to a scale indicator, customer and material setup, and an export your bookkeeper can post.
Most operations should buy. One pit, a short material list, a stable customer base and an attendant who has run that scale house for a decade is not a software problem. Buy a packaged product, connect it to your accounting, and spend the money on the yard. We tell producers this in scoping calls and it costs us work, which is exactly why it is worth writing down.
Where they stop: the royalty per lease and the ticket written on a pad
The gap is not weighing. It is everything attached to the weight.
Start with pricing. A general product prices an item. It does not natively know that this material at this pit for this customer on this job carries one rate, that the same material for the same customer at the pit forty miles away carries another, that the price is per ton if the customer is set up by weight and per yard if by volume, and that a third rate applies when you haul it into a specific freight zone with your own trucks. So a second price list appears in a spreadsheet, and the errors surface five weeks later when a contractor's accounts payable clerk queries an invoice worth a few hundred dollars that costs both sides an hour.
Then royalties. Tonnage leaving a pit creates an obligation to a landowner on terms specific to that lease: a rate per ton, sometimes tiered, sometimes with a minimum, sometimes only on certain materials. Producers reconstruct that quarterly from sales reports, and the reconstruction rarely matches what the tickets actually said. When the landowner asks, the disagreement is uncomfortable and you are the party holding the records.
Then connectivity. Pits sit in valleys and behind hills, and the link drops for twenty minutes twice a day. During those twenty minutes the scale must still weigh, the ticket must still print with a valid unbroken number, and the transaction must reconcile without duplication when the link returns. Any design that queues a request to a cloud service and waits sends trucks away or pushes the attendant back to a paper pad, and the pad is where the unbilled loads come from, because a pad sheet leaves no gap when it goes missing.
Last, the ticket is not only an invoice line. It is a weight record from a device certified for commercial use under NIST Handbook 44 and carrying a Certificate of Conformance from the National Type Evaluation Program, and it may be the document a state transportation department wants for material supplied to a public job. Scale identity, calibration date and operator belong on it.
The arithmetic: cost per site and per ticket against a one-time build
Reduce this to two numbers you can get in an afternoon.
First, cost per site. Packaged ticketing is normally licensed per scale house or per site with annual support, so multiply your quoted figure by the number of pits and by five years. A producer at four sites paying $6,000 per site per year is at $120,000 across five. Use your own quote, because per-site pricing varies widely and unattended hardware is often quoted separately.
Second, cost per ticket unbilled. Take last year's ticket count, then take your best estimate of loads that left without a ticket or with the wrong rate. Even one load a day at an average ticket value across four pits is a five figure annual number, and it is the figure nobody puts on a proposal because no vendor can measure it for you.
Against that, a custom first release runs $60,000 to $130,000 with support at 15 to 20 percent a year, so a $95,000 build costs roughly $176,000 across five years.
The crossover sits at sites multiplied by pricing complexity. At one or two pits with a short price list, buy, and it is not close. At three or more pits with different price books, or any number of sites where royalty terms differ per lease, the combination of pricing errors, royalty reconstruction and unbilled loads typically passes the build inside three years. The cheapest diagnostic costs nothing: ask your controller how many invoice corrections were issued last quarter and how long the quarterly royalty reconciliation took.
What a custom build actually costs
A first release covering one central price book applied at every scale house, ticket capture with the weight read from the indicator rather than typed, stored tares with drift alerts, customer credit status shown before the truck loads, gapless numbering per site, full offline operation and an accounting export runs $60,000 to $130,000 in 10 to 16 weeks. A full platform adding unattended kiosk weighing with driver credentials, haul zone freight, landowner royalty accrual, stockpile inventory and a customer portal runs $150,000 to $350,000 across 6 to 11 months.
Then the lines nobody quotes. Migration runs 10 to 25 percent of build cost, and it sits mid-band here because customer and material setup is straightforward while lease terms and stored tares are not. Every tare has to be reweighed and confirmed rather than imported on trust, since a stale tare set when a truck carried a different body puts every load that truck hauls out by several hundred pounds in somebody's favour. Year two onward runs 15 to 20 percent of build cost annually, covering hosting, indicator firmware changes and the price book work that follows every contract season.
What moves the number: the count of sites; unattended hardware at multiple pits, since loop detection, cameras and kiosk printers are a physical project as well as a software one; inbound recycled material with tipping fees, which turns the ticket into a two direction transaction; and scale indicator integration, because Rice Lake, Cardinal, Mettler Toledo and Avery Weigh-Tronix each expose their own protocol and reading a stable weight rather than a fluctuating one is specific work per make.
The four situations where building wins
- Regulatory fit. A certified weight record with scale identity, calibration date and operator on every ticket, retained where you can produce it, plus the material certification a state transportation department asks for on public work. Operations under Mine Safety and Health Administration Part 46 training rules often want that currency visible at the same gate.
- Scale economics. At three or more pits, per-site licensing plus the cost of pricing errors and quarterly royalty reconstruction passes the build inside three years. Count last quarter's invoice corrections before you renew anything.
- A workflow that is your competitive advantage. Contractors notice tickets that arrive in real time rather than at month end, and a portal where their own accounts payable clerk pulls documents without phoning your office. It is one of the few places in this business where software is visible to the person signing your cheque.
- Integration sprawl across three or more systems. The accounting ledger, the scale indicators, the dispatch or haulage system, and increasingly the customer's project management platform expecting data in its own format. Four interfaces each needing a vendor change request is the point where packaged licensing stops being cheap.
One signal on its own is rarely decisive. Two together usually is, and the pairing we see most often is multiple pits plus royalty terms that differ per lease.
How to decide in a week
Do not write a specification yet. Spend one morning at your busiest scale house between five thirty and eight, and count three things: how many trucks were ticketed on a pad rather than in the system, how many times the attendant had to pick between two versions of the same customer, and how long each truck spent on the scale.
Then spend an afternoon with your controller. Pull the last quarterly royalty calculation and try to tie it back to tickets rather than to a sales report. If those two numbers disagree, you have the business case, and it is one your owner will understand immediately.
Third, ask every vendor and every developer on your shortlist the same three questions. What happens when the internet drops mid weigh, where the only acceptable answer is that the scale house weighs, numbers and prints entirely locally and syncs in a way that cannot double bill. Which scale indicators have you read, by make and protocol, and how did you handle motion detection and stable weight capture. And how does your price book handle a customer with a negotiated rate at one pit, list price at another, and a job with its own freight zone. Anyone who needs a week on the third question will build a pile of conditional statements you cannot maintain.
Then buy a paid discovery phase that ends with a written specification you own: the price book model, the offline and reconciliation design, the indicator integration per make, the royalty terms per lease, and acceptance criteria measured at the scale rather than in a meeting room. Take it to every other firm on your list. That is what turns four quotes into four prices for the same scope.
Digital Heroes will not write code without a signed product requirements document. We contract through India LLP, US LLC and UK LTD entities so intellectual property assigns under law your own counsel already reads, and you own the repository, the cloud accounts and every stored ticket from the first commit. Over fifty specialists, more than 2,000 projects, and a named team you meet before signing, checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
We are the wrong firm for a single pit with a short price list and a long-serving attendant. We are also wrong if you want the scale, the indicator, the kiosk hardware and the software from one supplier under one purchase order, which is a legitimate way to buy and not one we can serve.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The average documented online shopping cart abandonment rate is 70.22% (based on 50 studies), and large ecommerce sites can achieve a 35.26% increase in conversion rate through better checkout design. Source: Baymard Institute (2024) →
- Based on responses from 39 retailers with a combined turnover in excess of EUR 1 trillion, ECR Retail Loss researchers estimated that self-checkout increases loss by an average of 22% in the year after implementation, with losses running 33% higher in stores with self-checkout than in comparable stores without it. Source: ECR Retail Loss / University of Leicester (Prof. Matt Hopkins) (2026) →
- SMS reminders that stated the specific cost of the appointment to the health system reduced missed appointments in Trial One, with the DNA (did-not-attend) rate falling from 11.1% (control) to 8.4% (specific-costs message) - an odds ratio of 0.74 (95% CI 0.61-0.89), i.e. roughly a 24-26% relative reduction - at no additional cost. (Trial Two replicated this at an 8.2% DNA rate.). Source: PLOS ONE (Hallsworth et al.) (2015) →
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
Frequently asked questions
How much does scale house ticketing software cost per site?
Packaged products are normally licensed per scale house or per site with annual support, so multiply your quote by the number of pits and then by five years, and check whether unattended hardware is quoted separately. A custom first release runs $60,000 to $130,000 in Digital Heroes delivery experience, with 15 to 20 percent annually thereafter and no additional licence when you open another pit.
How long does it take to roll a ticketing system out across several pits?
The first release ships in 10 to 16 weeks and should go live at your two busiest pits first, because those surface every pricing and workflow edge case. Additional sites then become a repeatable deployment measured in days rather than a project each, provided the hardware is consistent. Run the new system alongside the old one for one full billing cycle before switching anything off.
Who owns the ticket history if an outside firm builds the system?
You should own the repository, the cloud accounts and every stored ticket, written into the contract before kickoff. At Digital Heroes the client owns all of it from the first commit. Ticket history is a certified weight record used in weights and measures questions, the basis of royalty obligations, and a document public agencies may ask about, so it has to outlast any software relationship.
What happens if the network drops while a truck is on the scale?
In a properly designed system, nothing visible. The scale house weighs, prices, numbers and prints entirely locally from its own allocated number range, then synchronises when the link returns, with reconciliation written so a slow sync cannot bill a customer twice. Any design that queues a request to a cloud service and waits will send trucks away or push your attendant back to a paper pad.
Can we keep our accounting system and build only the ticketing layer?
Yes, and that is the usual shape. The accounting ledger stays authoritative for receivables and the ticketing system feeds it, rather than trying to replace it. Agree the export format and the posting rules with your bookkeeper during discovery rather than after, because reconciling a mismatched export at month end is exactly the manual work the project was supposed to remove.
Should unattended weighing come before or after the core ticketing system?
After. Unattended weighing changes the economics of a small pit because the site can sell material without an attendant, but it also removes the human who catches a wrong customer or a wrong material, so it depends on a clean central price book being in place first. Build the price book and staffed ticketing, run a season, then add kiosks at the sites that justify them.
What is the difference between scale ticketing and a point of sale system?
A point of sale system prices an item and takes payment. Scale ticketing produces a legal weight record from a certified device, applies a rate that depends on customer, material, pit, job, unit of measure and haul zone, checks credit before the truck loads, and creates an obligation to a landowner at the same time. The weighing is the easy part.
Can the same system calculate landowner royalties?
It should, and computing royalty from the same tickets that produce the invoice is the whole point. Rates per ton by lease, tier breaks, minimums and material specific terms accrue as loads leave, so what you owe the landowner and what you billed the customer come from one record. Producers who rebuild royalty quarterly from sales reports almost always find the two versions disagree.
We run one pit with a short material list. Should we build anything?
No. Buy a packaged ticketing product, connect it to your accounting system and put the money into the yard. The build case starts at three or more pits with different price books, when royalty terms differ per lease, when month end regularly finds unbilled loads, or when you want unattended weighing at a site that cannot support an attendant.
What happens if a customer disputes a weight months later?
You produce the ticket with the scale identity, the calibration date, the operator and the stored tare that applied on the day, which is why those fields belong on every ticket rather than in a maintenance file. If you have cameras at an unattended lane, the image of the plate and the load settles most disputes in minutes. Retention policy should be set before go-live, not after the first argument.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
Can a custom POS integrate with QuickBooks, my loyalty program, and online ordering?
Yes, and integrations are often the strongest reason to go custom, since you control the sync logic instead of waiting on an app marketplace. QuickBooks and Xero have stable public APIs, and a daily sales journal sync is a 1 to 2 week build item in most Digital Heroes POS projects; loyalty and online ordering connections typically run 2 to 4 weeks each depending on the vendor's API. List every integration in the initial scope, because each one added mid-project reopens the data model.
How do I calculate the payback period on a custom POS?
Add up what you pay per year today: subscription fees per terminal, add-on modules, and the gap between your effective processing rate and an interchange-plus rate, then divide the build cost by that total. A retail group paying $60,000 a year in fees and processing markup against a $150,000 build pays back in 2.5 years, before counting labor saved by workflows designed for your operation. Digital Heroes models 2 to 4 year payback for most multi-location operators and advises against building when the model shows longer.
Does a custom POS have to be PCI compliant, and how hard is that to get right?
Any system that touches card payments falls under PCI DSS, but the practical burden depends entirely on architecture. If your POS uses certified terminals from Stripe, Adyen, or a similar processor so card data never reaches your servers, most of the compliance scope shifts to the processor and you typically complete only a short self-assessment questionnaire. Building your own card capture puts you in full PCI DSS audit territory, which is why Digital Heroes has never recommended it in a POS engagement.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
Who can build a custom POS software system?
Digital Heroes builds custom POS software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other POS software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .