Dangerous Goods Compliance Software: Buy Labelmaster DGIS or DGOffice, Licence the Rules, and Build Only the Workflow Around Them
Transport mode count decides this, not shipment volume. One mode, road only, from one or two sites, against a limited set of United Nations (UN) numbers, means buy a validated checking tool and train two people properly.
On this page
Transport mode count decides this, not shipment volume. One mode, road only, from one or two sites, against a limited set of United Nations (UN) numbers, means buy a validated checking tool and train two people properly. Two or more modes, where the same material behaves differently depending on how it travels, means the mapping between your material numbers and the rules has become a person, and that person is the risk. Even then the answer is almost never a full replacement. Licence the regulatory content, keep the checker if it earns its place, and build only the substance master and the determination step inside your own order process.
When is off the shelf genuinely the right call here?
Labelmaster DGIS, Exis Technologies Hazcheck, IATA DG AutoCheck and DGOffice all carry maintained regulatory content and all of them are good at the job they were designed for, which is validating or building a declaration for a consignment presented to them. If that is your actual problem, buy one, train the people who will use it, and spend the rest of the budget on packaging and competence.
Buy, and stop reading here, if this describes you:
- You ship by road only, from one or two sites, against a limited set of UN numbers.
- Volumes are low enough that a trained dangerous goods safety adviser can genuinely check every consignment before it leaves.
- You are a freight forwarder whose role is checking other people's declarations rather than originating them, which is exactly the job these tools were built for.
- Your formulations, concentrations and pack sizes have been stable for years, so the classification data behind each product has not moved.
- No carrier or regulator has raised a finding against your process.
At that shape a validated commercial tool plus proper training is the correct answer, and a build would be indulgent. The safety adviser is genuinely able to hold the picture, the consignments are simple enough that the late check is still an early enough check, and the money is better spent elsewhere.
One rule applies whether you buy or build, and it is the most expensive mistake available in this domain. Do not build the regulatory content. Owning your own copy of the air, sea and road rule sets means owning an annual maintenance obligation forever, with legal consequences when you fall behind, and it will not be cheaper than licensing. The International Air Transport Association (IATA) Dangerous Goods Regulations publish a new edition every year and the International Maritime Dangerous Goods (IMDG) Code amends on its own cycle. Licence that. Build around it.
When does a custom build actually pay off?
The structural limit of every product named above is the same, and it is verifiable rather than a criticism. None of them can own your substance master, because that record is tied to your formulations, your grades, your concentrations and your packaging specifications. So a mapping step exists between your material numbers and their substance data, and that step is a human. That human is why a flammable liquid is still classified against a formulation that changed nine months ago.
The second limit is where the check runs. A checking tool validates a consignment that already exists, which is the right place for a final gate and the wrong place for the only gate. By the time a pallet is built and a truck is booked, the cheap options have gone. A different pack size, a split shipment or a different mode were all available at order entry and none of them are available at four in the afternoon on the dock.
Build when two or more of these are true:
- You ship across more than one mode and the same material behaves differently by mode, so a shipment that is routine by road is prohibited on a passenger aircraft.
- Your substance data does not live with your orders, so somebody translates between the two every day.
- You consolidate mixed loads, where segregation and aggregate quantity thresholds are properties of a combination that only exists when a pallet or container is built.
- Multiple sites apply the rules inconsistently, which usually surfaces as one site being cautious and another being fast.
- A carrier or regulator has already raised a finding, which turns this into a licence to operate question rather than an efficiency question.
How do they compare on the things that matter in this industry?
Ownership of the substance master. A checker holds substance data keyed to its own view of the world. Your material record holds a material number, a description and a weight. The join between them is manual in every packaged arrangement we have seen, and it is where stale classifications survive. A build makes the dangerous goods attributes a versioned part of the material record with an effective date, so a formulation change raises a review task rather than being discovered on a ramp.
Where determination happens. Ask any vendor whether their tool can be called from your order entry screen and return reasons rather than a document. Some can be called. Very few return a decision a salesperson can act on, which is the difference between a check and a gate. The useful output is not pass or fail, it is that this quantity would need a different packing instruction, or that this destination carries an operator variation the chosen carrier does not accept.
Segregation and aggregation. Any tool will tell you whether a single substance is shippable. The combination question lives in your warehouse system, because the combination only exists when the load is built. The failure mode is four consignments each individually under a limit that collectively cross it on one truck.
Edition changes. A licensed content source updates and you inherit it, which is the entire reason to licence. What matters is whether your own logic sits behind an interface you own, so that an edition change is a content update rather than a code change, and so you can move supplier later without rewriting your operation.
Evidence retrieval. After an incident the questions are consistent: who classified this, against which edition, were they trained and current, who signed the declaration. If the answers live across an email chain, a training spreadsheet and a filing cabinet, the finding will be about your system rather than the shipment. Stored determinations with rule edition, inputs, user and timestamp turn that into a query.
What does total cost of ownership look like at your scale?
On the build side, from Digital Heroes delivery experience, a focused first release covering a versioned substance master, mode aware determination surfaced at order entry, an interface to a licensed rules source and declaration output runs $80,000 to $170,000 and ships in 14 to 20 weeks. A full platform adding segregation and load compatibility at pallet and container level, multi leg consignments, label and marking generation, competence binding and a full audit trail runs $200,000 to $500,000 phased over 8 to 14 months.
Priced component by component so you can fund only what you need: the substance master alone runs $45,000 to $75,000 over ten to twelve weeks, segregation and load compatibility adds $50,000 to $90,000, and each additional transport mode adds roughly $35,000 to $70,000 and six to ten weeks, because each brings its own document set, quantity limits and variation handling. The cheapest credible working system is around $80,000 for a single site on one mode with a modest substance master.
Annually after go live, infrastructure sits at $300 to $800 a month, scaling with consignment volume and document storage rather than user count. Support and enhancement runs 12 to 18 percent of build cost. Budget scheduled testing around each new IATA edition and each IMDG amendment, because your own logic around the content has to be exercised even when the content updates itself.
On the buy side, put a full year on one page: the checking tool licence, any per declaration or per consignment charges, the content subscription you already hold, and per site or per user fees. Note which of those rise with shipment volume. Then count the mapping labour, and note how much of it sits with one individual. Then price the failures you have already had, because a missed flight and the production run behind it is a number you know.
What does the hybrid look like, and when is it the honest answer?
For most shippers this is the answer, and it is worth stating plainly even though it is the smaller project. Licence the rules. Keep the checker if your forwarders or your customers expect its output. Build the two pieces that are genuinely yours.
In practice that is:
- A versioned substance master, $45,000 to $75,000. Dangerous goods attributes on the material record with effective dates, review tasks triggered when a formulation changes, and safety data sheet extraction that reads section 14 transport information from supplier documents and raises a difference for a human to approve. It classifies nothing. It notices that a supplier quietly changed something.
- Determination at order entry against a licensed source. A thin call from your order screen that returns reasons, with the rule edition and inputs stored immutably. Keep the dock check as the final gate, because removing both at once doubles the validation burden for no operational gain.
That combination costs a fraction of a platform and it removes the failure mode that actually causes ramp rejects, which is a determination made late against data that expired. Segregation, labelling and competence binding are worth doing, but they are second.
Which should you choose, by operator size and stage?
Find your row and act on it.
- One site, road only, a few dozen UN numbers. Buy a validated checking tool. Train two people to a real standard. Do not build anything.
- Freight forwarder checking other people's declarations. Buy. You will not improve on tools designed for exactly that job.
- Two or three sites, road only, growing substance master. Still buy the checker, but build the substance master at $45,000 to $75,000. Stale classification is your exposure, not document formatting.
- Two modes, one of which you ship less often. This is the decision point, and the exposure usually sits in the mode you ship least, because familiarity with the dominant one is why nobody checks the other. Build the first release at $80,000 to $170,000 and sequence by where your failures actually happen rather than by volume.
- Multi site, multi mode, consolidated mixed loads. Build the full platform, phased. Substance master and determination first, then segregation, then labelling and competence, then multi leg.
- A carrier or regulator finding already on file. Build, and start with the evidence trail, because the next conversation is about whether your process can be shown to work rather than whether it is efficient.
Two conditions apply to every build row. Clean the substance master before development starts, because your safety adviser has to review and sign it off regardless, and doing that during discovery costs nothing while doing it during testing costs a schedule. And end the conversation with any developer who proposes building the rules content.
If you would rather scope this before committing budget, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- In a survey of 579 supply chain professionals (July 31 to October 1, 2024), only 29% had built at least three of the five capabilities Gartner identifies as needed for future competitiveness (agility, resilience, regionalization, integrated ecosystems, and enterprise-wide strategy). Source: Gartner (2025) →
- Senior executives report the highest average compensation among developer roles (e.g., $225K median in the US), and reported salary bands shifted downward year-over-year ($60-75K vs. $70-85K in 2023), underscoring how compensation varies sharply by role and location. Source: Stack Overflow (2024) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
Frequently asked questions
Should we replace Labelmaster DGIS or IATA DG AutoCheck entirely?
Usually not, and this is where shippers most often get the decision wrong. Those tools carry maintained regulatory content and produce declarations competently, and rebuilding either capability adds cost without reducing risk.
The part worth owning is the substance master and the determination step inside your own order process, because both are tied to your formulations, your pack sizes and your commercial commitments. Building above a licensed content source rather than replacing the checker costs a fraction of a platform and removes the failure that actually causes ramp rejects.
What does it cost to switch dangerous goods checking tools or content suppliers?
The licence side is straightforward. The expensive part is that your substance mapping was built for one supplier's data model, so moving means rebuilding the join between your material numbers and their substance records, and that is human work by your safety function rather than an export.
The structural fix is to put the content behind an interface you own before you need it. That costs almost nothing at the start of a build and turns a supplier change into a content update. Ask for it explicitly, because a developer who wires a supplier straight into the application has just made your next decision for you.
What if our content supplier raises its subscription price?
Work out now what that subscription looks like at double your current consignment volume, because several arrangements in this category price per declaration or per consignment and therefore rise exactly as you grow. Do that arithmetic before renewal rather than during it.
The structural response is not to stop licensing. It is to make the supplier replaceable, so the content is a priced commodity you can compare rather than a dependency with nothing to compare it against. You should never own the rules, but you should always be able to change who provides them.
Should we build our own dangerous goods rules database?
No, and it is the most expensive mistake available here. Building your own copy of the air, sea and road rule sets means owning an annual maintenance obligation forever, with legal consequences when you fall behind, and it will not be cheaper than licensing.
The IATA Dangerous Goods Regulations publish a new edition annually and the IMDG Code amends on its own cycle, on top of national road regulations and operator variations. Licence maintained content and build the workflow around it: your substance master, your order entry, your load building and your evidence trail.
How long does a dangerous goods software build take?
Fourteen to 20 weeks for a first release on one or two modes, and 8 to 14 months for a multi mode platform with segregation and labelling, based on Digital Heroes delivery experience. Each additional mode adds six to ten weeks.
The schedule risk is almost never the code. It is the substance master, because most operations discover during discovery that the same commercial product carries different classifications by concentration or pack size and nobody has reconciled that record for years. Only your safety function can do that review, so plan their time explicitly before kickoff.
Can we build only the substance master and keep everything else?
Yes, and for a lot of road only shippers it is the right purchase. Versioned classification attributes on the material record with effective dates, review tasks triggered when a formulation changes, and safety data sheet extraction that flags when a supplier has altered section 14 transport information runs $45,000 to $75,000 over ten to twelve weeks.
It does not classify anything and it does not produce a declaration. What it stops is shipping against a classification that expired nine months ago, which sits behind a large share of dockside surprises.
What does segregation and load compatibility checking add to the build?
Roughly $50,000 to $90,000, because it has to live inside the workflow where pallets and containers are actually built rather than beside it in a compliance tool. Segregation is a property of a combination, and the combination only exists at the moment of load building.
The same engine should evaluate aggregate quantity thresholds, since the common failure is four consignments each individually under a limit that collectively cross it once loaded on one truck. Blocking a bad combination before the pallet is wrapped is far cheaper than discovering it at a terminal.
Does moving determination into order entry mean we can drop the dock check?
No, and trying to do both in release one doubles your validation burden for no operational gain. Keep the final gate where it is. What changes is that the argument happens at ten in the morning with better options available rather than at four in the afternoon with none.
The measurable outcome is not fewer checks, it is fewer expensive ones. A quantity that needs a different packing instruction is a pack size decision when the order is taken and a missed flight when the pallet is already built.
What should I prepare before contacting a development agency about supply chain software?
Bring a written list of your workflows from purchase order to delivery, the systems each step touches, and the 3 to 5 pain points costing you the most hours or errors. Export a sample of your real data, SKUs, orders, and locations, because data shape drives half the design decisions. You do not need a formal spec; Digital Heroes scopes most supply chain projects from a two-page problem description plus screen-share walkthroughs of the current process.
How much does custom supply chain software cost for a small business?
For a small business, a focused custom supply chain tool usually lands between $15,000 and $45,000, covering one core workflow like inventory tracking, purchase orders, or shipment visibility. Across 2,000+ delivered projects, Digital Heroes sees most small distributors and light manufacturers start in the $20,000 to $35,000 range for a first working version. Adding barcode scanning, multi-warehouse support, or carrier integrations pushes budgets toward $50,000 and up.
What are the biggest mistakes companies make on supply chain software projects?
The top three: replacing every system at once instead of one workflow at a time, skipping data cleanup so the new system inherits years of bad SKUs and phantom stock, and designing screens without the warehouse staff who will use them daily. A fourth is underscoping integrations and discovering mid-project that the ERP connection is half the work. Digital Heroes sees more supply chain projects fail from scope and data problems than from any technical cause.
Why do companies replace generic SCM software with custom systems?
The usual trigger is workflow mismatch: generic SCM tools model a standard distributor, so anything unusual, like mixed lot and serial tracking, consignment inventory, or customer-specific routing rules, ends up managed in spreadsheets beside the system. Companies also leave when per-user pricing punishes growth or the vendor's API cannot support needed integrations. In Digital Heroes projects, the number of spreadsheets living around the official system is the most reliable signal a team has outgrown its off-the-shelf tool.
How big a development team does a supply chain software project need?
A typical build runs with 4 to 6 people: a project lead or analyst, two or three developers, a QA engineer, and a part-time designer. Digital Heroes staffs most supply chain MVPs this way for 10 to 14 weeks, then drops to 1 or 2 people for maintenance after launch. Bigger is not better here; past 7 or 8 people on a single-product build, coordination overhead usually cancels the added speed.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
How long does it take to build custom supply chain software?
Plan on 10 to 14 weeks for a first production release covering one or two core workflows, and 6 to 9 months for a full platform spanning procurement, inventory, and fulfillment. Digital Heroes ships most supply chain MVPs in about 12 weeks with a 4 to 6 person team. Integrations are the schedule risk: each ERP, EDI, or carrier connection typically adds 2 to 4 weeks of build and testing.
Who owns the code when an agency builds my supply chain software?
You should own it outright, with full IP assignment on payment written into the contract, and you should walk away from any agency that only licenses the software to you. Insist on the code living in a repository under your own GitHub or GitLab account from day one, not handed over at the end. Digital Heroes contracts assign all custom code, database schemas, and documentation to the client; the only carve-outs should be clearly listed open source libraries.
Is custom supply chain software cheaper than SAP over five years?
For small and mid-size operations it usually is, because SAP costs compound through licensing, implementation partners, and per-user fees, while custom costs are front-loaded. SAP Business One's published list price has run roughly $3,200 per professional user as a perpetual license plus annual maintenance near 20 percent, and the S/4HANA proposals Digital Heroes clients share are typically in the hundreds of thousands before any customization. A $60,000 to $100,000 custom build with 15 to 20 percent annual upkeep often costs less by year three for a 10 to 30 user company, and you stop paying per seat as you hire.
Who can build a custom supply chain software system?
Digital Heroes builds custom supply chain 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 supply chain 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
More from Tara.
React Native Lead · Delhi · 5 posts on the site
Published · Last updated .
