How Much Does Air Cargo Software Cost in 2026?
Custom air cargo and freight forwarding software runs $60,000 to $400,000, and the line item that moves the number most is integration count.
On this page
Custom air cargo and freight forwarding software runs $60,000 to $400,000, and the line item that moves the number most is integration count. Every airline is a separate piece of work at one to three weeks each, and customs filing through ABI or ICS2 adds a certification cycle on the authority's calendar rather than yours. A focused first release with the shipment and consolidation model, document extraction and one or two integrations is $60,000 to $130,000 over 12 to 16 weeks. Ten carriers plus customs filing in two jurisdictions is what takes a forwarder to the top of the $150,000 to $400,000 band.
The bands an air cargo software build falls into
The first release band is $60,000 to $130,000 over 12 to 16 weeks. That buys the shipment and consolidation data model, house and master air waybill management, the document extraction pipeline with a review queue, one carrier integration, and then either the rate engine or the customs entry flow. Not both. You pick the one bleeding worse.
The full platform band is $150,000 to $400,000 phased over 6 to 12 months. That adds multi carrier integrations, ABI or ICS2 filing, co-load settlement with profit share, customer notifications and an outbound application programming interface, and accounting integration with job costing and accrual reconciliation.
There is a narrower option worth naming, because it is where the clearest return sits. A document extraction pipeline alone, taking any commercial invoice, packing list or arrival notice as a portable document format file, image or email body and returning a structured shipment object with per field confidence scores and a review queue, runs $30,000 to $55,000 over six to nine weeks. It does not replace your forwarding system. It removes the transcription that currently sits between your documents and your entries.
What drives an air cargo build up
Carrier integration count is the first driver and it is close to linear. Some airlines expose a modern interface. Some give you Cargo-IMP or Cargo-XML messaging over a legacy channel. Some give you a portal and nothing else, which means capture rather than integration. Each carrier is one to three weeks, so ten carriers is a quarter of a serious budget on its own.
Customs filing certification is the second and it behaves differently from everything else. Building to ABI or ICS2 involves a certification process and a test cycle with the authority, and that calendar is not yours. Budget six to 10 weeks of elapsed time per jurisdiction and start it in parallel with the rest of the build, not at the end.
Dangerous goods and pharma add scope that looks small on a wireframe. Making United Nations number, packing group and temperature excursion handling part of the shipment model, enforced at booking rather than checked afterwards, is real work with an audit trail behind it.
Accounting integration is the fourth, and it is where projects quietly overrun. Job costing, accruals against estimated buy rates, and the reconciliation when the airline's invoice arrives weeks later at a different number, connected properly to your ledger, is three to five weeks.
Finally, migration off an incumbent system, because you cannot flip a forwarder overnight without dropping freight.
What keeps the number down
Integrate two carriers, not ten. Pick the two that carry most of your tonnage, prove the pattern, and add the rest as a per carrier line item once the shipment model has settled. Each subsequent carrier is cheaper than the first because the messaging layer already exists.
Choose between the rate engine and the customs flow for release one. Forwarders who scope both discover that each has its own integration surface and its own domain complexity, and the release slips. The rate engine wins when you are losing quotes on response time. The customs flow wins when you are absorbing penalties and re-keying entries.
Keep the incumbent system running for historical shipments rather than migrating everything. Move open shipments, rate tables and customer records. Leave closed history where it is and link to it.
Start the customs certification paperwork before the first line of code if customs is in scope at all. The certification calendar is the constraint, and forwarders who file early get a build that finishes when the code does.
Stabilise your process before you automate it. Building around a workflow that three of your operators disagree about produces a system that all three work around.
A worked example that adds up
A forwarder doing about 1,500 shipments a month across three trade lanes, currently on an off the shelf forwarding system plus spreadsheets, customs handled by an outside broker, one dominant carrier and a long tail of shippers sending documents in every format imaginable.
- Discovery and the shipment and consolidation domain model, including co-load profit share terms: $14,000
- Shipment graph with house and master air waybills, co-load allocations, splits, re-consolidations and onward legs, with margin recomputed at every level: $26,000
- Document extraction pipeline with per field confidence scoring and a review queue showing the highlighted source region: $22,000
- One carrier integration over Cargo-XML, including their test environment cycle: $9,000
- Rate engine with weight breaks, surcharges, validity windows and rapid spot rate capture: $18,000
- Quoting against the rate engine with per customer tier margin applied: $10,000
- Accounting export with job costing and buy rate accrual: $8,000
- Migration of open shipments, rate tables and customer records, plus a parallel run: $14,000
That totals $121,000, near the top of the first release band because both the rate engine and quoting are in scope alongside a real domain model. A forwarder on two lanes with one carrier and no rate engine lands nearer $75,000.
Adding eight more carriers, ABI filing with certification, co-load settlement and customer notifications with an outbound interface takes that forwarder to roughly $260,000 to $340,000 in total across the following two to three quarters.
How the spend phases
Discovery is two to three weeks and around 12 percent of the first release. The deliverable that matters is the domain model on a whiteboard: what a co-load actually is in your business, how profit share settles, and what happens to margin when a house bill moves off tonight's master air waybill.
The shipment graph carries roughly 30 percent across weeks three to nine. Getting this wrong is the failure mode in this category, and it is visible in the first hour of a conversation with a developer. Chargeable weight rules, rate structures with weight breaks, unit load device pivots and a settlement ledger that handles profit share without a human in the loop are the product. Everything else is a view onto it.
Document extraction is around 20 percent, weeks six to twelve, and it runs partly in parallel because it depends on the shipment object rather than the whole system.
Integrations and the rate engine take another 25 percent. Customs certification, when in scope, runs as a parallel track from week one regardless of when the code lands.
The last 15 percent is migration and a parallel run of four to eight weeks where both systems are live and new bookings go into the new one.
The ongoing costs nobody quotes
Infrastructure runs $400 to $1,200 a month for a platform of this shape. Document storage and the extraction workload are the variable parts, and both scale with shipment count rather than user count, which is worth knowing because it is the opposite of how your current licence probably behaves.
Document extraction has a per document inference cost. It is small individually and it is not zero at volume, so model it against your monthly document count rather than treating it as free.
Carrier interfaces change. Airlines revise message formats and endpoints on their own schedule, and each change is a few days of attention. With ten carriers integrated, treat that as a standing maintenance line rather than an incident.
Customs regimes change more than carriers do, and changes carry deadlines set by an authority. Budget for regulatory maintenance separately from feature work, because it is not optional and it is not schedulable.
Support and enhancement typically runs 12 to 18 percent of the build cost annually. Ask specifically about out of hours cover, because freight moves at 03:00 and a forwarding system without an on call arrangement is a system that will fail at the worst possible time.
Comparing a build against your current renewal
Do this on one page before you decide anything. Take your current licence, module and per transaction fees for a full year. Note whether that figure rises with volume, because a volume linked model means growth costs you more forever, which is the opposite of what a system should do.
Then count the transcription. Identify the people whose actual job is moving data between systems: commercial invoice into the customs entry, master air waybill into the forwarding system, arrival notice into the tracking field, carrier status email into a customer update. Multiply by fully loaded cost. In most forwarders of scale that number is larger than the licence, and it is also your throughput ceiling, which is the expensive part.
Then add the losses you do not invoice for: quotes that went out too late to win, penalties from a wrong classification or a missed filing, and demurrage while freight waits on paperwork. You know these numbers. Set the total against a build that stops rising with volume, which is the actual comparison.
When buying beats building
Stay on the off the shelf system if you are under roughly 400 shipments a month, running one or two trade lanes, with customs going through an outside broker. CargoWise at that size is a reasonable deal and your constraint is sales, not software. Building against a business that small is a way to spend six figures automating a process you have not stabilised yet.
Magaya is the right call for a smaller forwarder who wants something usable this quarter and does not have an unusual consolidation model. Descartes gives you strong messaging if that is the specific gap. None of these is a bad product, and rebuilding a competent product is a poor use of capital.
Build when these show up together. Your differentiator is something the system cannot express, such as a co-load model, a vertical service like pharma lane control or aircraft on ground parts, or a partner network with unusual economics. You have three or more people whose job is re-keying. Your licensing plus modules plus per transaction fees are rising with volume and you can see where that lands in three years. Or you have been told that is not how the system works three times about the same workflow, which is the clearest signal of all. The vendor is not wrong, and will not change, because their product is built for the median forwarder and you are not it.
If you would rather someone argued with your brief than agreed with it, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. Nothing about that commits you to the build.
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) →
- Poor software quality cost the US economy an estimated $2.41 trillion in 2022, including roughly $1.52 trillion in accumulated technical debt, driven partly by unsuccessful development projects and low-quality legacy systems. Source: Consortium for Information & Software Quality (CISQ) - Herb Krasner (2022) →
- Criteo's Global Commerce Review found retail apps convert at 18% versus 4% on mobile web (roughly 4.5x), and travel apps convert at 20% versus 6% on mobile web (about 3.3x). Source: Criteo (2017) →
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
Frequently asked questions
What is the total cost of custom freight forwarding software?
A focused first release runs $60,000 to $130,000 over 12 to 16 weeks in our delivery experience, covering the shipment and consolidation model, document extraction with a review queue, one carrier integration and either the rate engine or the customs entry flow. A full platform with multi carrier messaging, ABI or ICS2 filing, co-load settlement, customer notifications and accounting integration runs $150,000 to $400,000 phased over 6 to 12 months.
Integration count is the dominant variable, not shipment volume.
What does it cost to run each year after launch?
Infrastructure sits at $400 to $1,200 a month, with document storage and extraction workload scaling by shipment count rather than user count. Support and enhancement typically runs 12 to 18 percent of the build cost annually, and you should ask specifically about out of hours cover because freight moves overnight.
Budget separately for carrier interface changes, which airlines make on their own schedule, and for customs regime changes, which carry deadlines set by an authority rather than by you.
How long does an air cargo software build take?
Twelve to 16 weeks for a first release, and 6 to 12 months for the full platform. The item that most often controls the calendar is customs certification for ABI or ICS2, which involves a test cycle with the authority and typically takes six to 10 weeks of elapsed time per jurisdiction.
That work has to start in parallel from week one. A developer who scopes it as a two week task at the end will miss, because the authority's calendar is not theirs.
Is CargoWise cheaper than building our own system?
At smaller volumes, yes, and it is the sensible choice under roughly 400 shipments a month on one or two lanes. The comparison changes as you grow, because the licensing model is volume linked by design, so the cost of your success keeps rising while a build does not.
Put both on one page for a three year horizon, including modules and per transaction fees, and add the staff time spent on work the system does not do. That comparison is usually clearer than the feature discussion around it.
How much does each carrier integration add?
One to three weeks each, which lands roughly in the $6,000 to $15,000 range per airline depending on what they expose. A modern interface is at the low end. Cargo-IMP or Cargo-XML over a legacy channel is in the middle. A carrier with only a portal is at the top, because that is capture work rather than integration.
The first carrier costs more than the rest, since it establishes the messaging layer. Integrate two, prove the pattern, then add the others as discrete line items.
Can we build only the document extraction pipeline?
Yes, and it is the clearest single return in this category. A pipeline that reads any commercial invoice, packing list or arrival notice as a document, image or email body and returns a structured shipment object with per field confidence scores and a review queue runs $30,000 to $55,000 over six to nine weeks.
It sits alongside your existing forwarding system rather than replacing it. What it changes is that your operations role becomes exception handling rather than typing.
What does migrating off our current forwarding system cost?
In the worked example, migration plus a parallel run was $14,000, roughly 12 percent of the first release. That covers open shipments, rate tables, customer and partner records and the accounting linkage.
Plan for a parallel period of four to eight weeks rather than a cutover date, with new bookings going into the new system while open shipments finish in the old one. Any developer proposing a single weekend cutover has not migrated a forwarder before.
Why does customs filing cost more than a normal integration?
Because the cost is calendar rather than code. Filing through ABI or ICS2 requires a certification process and a test cycle with the authority, and neither runs to your schedule. Six to 10 weeks of elapsed time per jurisdiction is a reasonable planning assumption, and it multiplies if you file into more than one.
The build itself is manageable. The correct approach is to open the certification track in week one and construct the rest of the system alongside it.
What is the cheapest credible version of this system?
Around $60,000 for a forwarder on two lanes with a straightforward consolidation model, one carrier integration, document extraction and no rate engine or customs flow in release one. That is a working operations core rather than a demonstration.
Be sceptical of anything cheaper that claims to model co-loads. If a developer draws a shipments table with a parent identifier column, they have not built this before, and the domain model is where these projects succeed or fail.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
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.
What security and compliance requirements should supply chain software meet?
At minimum: role-based access control, encryption in transit and at rest, audit logs on inventory and order changes, and tested backups, because the system holds supplier pricing and customer purchase history your competitors would love to see. If enterprise customers connect to it, expect security questionnaires and possibly SOC 2 expectations; food, pharma, and aerospace add traceability rules like FDA lot tracking or ITAR data handling. Raise these in the first scoping call, since retrofitting audit trails onto a live system costs far more than designing them in.
Should I hire a freelancer or an agency to build supply chain software?
For anything past a single-user internal tool, use an agency or an established team, because supply chain systems need backend, frontend, integration, and QA skills that rarely live in one freelancer. A solo developer can build a $10,000 inventory tracker; a system that talks to your ERP, carriers, and warehouse scanners fails badly when its only author is unreachable during a shipping cutoff. In the proposals Digital Heroes sees clients compare, agencies cost 20 to 50 percent more but give you continuity, code review, and someone answerable when order data stops flowing.
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
Published · Last updated .
