How to Hire an Air Cargo Software Development Company
Hire the vendor who can model a co-load on a whiteboard in the first hour. The shipment graph, not the screens, decides whether the system survives.
On this page
Hire the vendor who can model a co-load on a whiteboard in the first hour. The shipment graph, not the screens, decides whether the system survives. Expect $60,000 to $130,000 for a first release over 12 to 16 weeks and $150,000 to $400,000 for a full platform. Start customs certification in parallel with the build, never at the end.
Choosing a company to build your forwarding system feels a lot like handing a consolidation to a partner agent you have only ever met over email. You get a booking confirmation, then silence, and the truth arrives weeks later as a settlement statement that either reconciles to your numbers or starts an argument. By the time you know which, the freight has moved and the money is committed.
What makes this category hard to buy is that the thing you are actually purchasing is a data model, and data models do not demo. Every vendor can show you an air waybill screen and a tracking map. Very few can express a co-load where three house bills came from a partner in Chicago, the master was bought from an airline, the consol splits at the hub, two pieces are Class 9 lithium batteries and the profit share runs net net on the buy rate. If the system cannot hold that shape, your operators will keep running the business in a spreadsheet next to it, which is precisely the situation you were paying to end.
What an air cargo software development company actually does
The operations screens are the visible tenth. The work that decides the outcome sits behind them.
- The shipment graph. House bills, masters, co-load allocations, splits, re-consolidations and onward legs modelled as relationships rather than a parent column, so margin recomputes per house bill, per consol, per lane and per partner when an operator moves a piece off tonight's flight.
- Chargeable weight and rate structure. Dim factors, IATA weight breaks, spot rates captured while the ops manager is still on the phone with the airline, and validity windows that stop a stale tariff quoting Q1 pricing in July.
- Document extraction. Commercial invoices, packing lists and safety data sheets arriving as PDFs, photographs and email bodies, read rather than template matched, with a confidence score per field and a review queue for anything below your threshold.
- Carrier messaging. Cargo-XML, legacy Cargo-IMP and REST, plus the airlines that offer nothing but a portal, each with its own quirks between test and production.
- Customs as a first class object. The entry living beside the shipment with a full audit trail of who classified what, on which description, against which document, so a request for information nine months later is a lookup rather than a lost afternoon.
- Accounting linkage. Job costing and accrual against estimated buy rates, then the reconciliation when the airline invoices a different number three weeks later.
What it really costs in 2026
| Scope | Cost | Timeline |
|---|---|---|
| First release: shipment and consol model, air waybill management, document extraction with review queue, one carrier integration, plus either the rate engine or the customs flow | $60,000 to $130,000 | 12 to 16 weeks |
| Full platform: adds multi carrier messaging, filing to ABI or ICS2, co-load settlement, customer notifications and API, accounting integration | $150,000 to $400,000 | 6 to 12 months |
| Multi jurisdiction filing across two or more customs authorities | $400,000 and up | 12 months and beyond |
| Support, hosting and enhancement retainer | 15% to 20% of build per year | Ongoing |
Two line items are routinely absent from quotes in this category, and both are calendar risks rather than engineering risks.
Customs filing certification. Building to ABI in the United States or ICS2 in the European Union is not an integration sprint. There is a registration and test cycle with the authority, on their schedule, and it runs six to ten weeks of calendar time per jurisdiction that no development team can compress. A quote that lists customs filing as a two week task at the end of the plan is a quote that will slip, because the long pole is not code.
Freight accounting reconciliation. Every quote covers connecting to NetSuite, Sage or QuickBooks. Very few cover what happens when the carrier invoice lands weeks after you accrued the estimated buy rate at a different figure, across a consol whose costs were allocated to eight house bills. That reconciliation logic is three to five weeks of work and it is where forwarding projects quietly overrun.
Signals of a strong partner
- They draw the co-load before they draw the screens. Ask for a whiteboard in the first meeting. A vendor who has built this reaches for relationships and allocations. One who has not reaches for a shipments table.
- They name the carriers and the standards. Not integrations experience in general, but which airline, which message standard, and what broke between the test environment and production.
- They schedule certification in parallel. ABI or ICS2 registration starts in week one while the rest of the system is built alongside it.
- They propose a parallel run rather than a cutover date. New bookings enter the new system while open shipments finish in the old one, usually across four to eight weeks. Nobody flips a forwarder over a weekend without dropping freight.
- They put confidence thresholds in the extraction design. Straight through processing above a line you set, review queue below it, with the source region highlighted so an operator confirms in one keystroke.
- They agree to full code and infrastructure ownership in writing. Repository, cloud accounts and deployment pipeline, before kickoff.
Red flags
- A shipments table with a parent identifier. This model cannot express a split consol or a partner profit share, and it is visible within an hour if you ask.
- Template based document capture sold as automation. Templates handle your top ten shippers and fail on the long tail, which is most of your document volume and all of your data entry pain.
- Fixed price before seeing your rate sources. Half your buy rates arrive as partner tariff PDFs and phone calls. Anyone pricing a rate engine without looking at that mess is guessing.
- Denied party screening described as a nightly report. A screen that runs after the freight is airborne is a report, not a control, and it will not help you when it matters.
- Silence on migration from the incumbent system. Open shipments, rate tables, partner records and the accounting linkage all have to come across cleanly, and a vendor who has never done it will call it straightforward.
Questions to ask on the first call
- Model this on the whiteboard now: my four house bills plus three from a partner, one master, split at the hub, dangerous goods in the mix, profit share on the buy rate. Where does margin live?
- Which airlines have you integrated with, over which standard, and what differed between their test environment and production?
- How would you sequence ABI or ICS2 certification against the rest of the build, and what is your assumption about the authority's calendar?
- How does the system compute chargeable weight, and where do dim factors and weight breaks get configured rather than coded?
- Show me how a spot rate gets captured while the ops manager is still on the phone with the airline.
- How do you handle the long tail of shipper document formats without templates, and what confidence threshold routing do you propose?
- When a request for information arrives nine months after clearance, what exactly does the audit trail show about the classification decision?
- How do you accrue against estimated buy rates and reconcile when the carrier invoice arrives at a different number?
- What is your parallel run plan out of our current system, and who owns the repository and cloud accounts from day one?
A simple way to decide
Stop comparing proposals written from a two page brief. Buy a paid discovery phase from your two best candidates, four to six weeks, quoted separately from the build, and require a written specification as the deliverable: the shipment and consol data model, the rate and chargeable weight rules, the carrier and customs integration list with certification timelines named, the migration and parallel run plan, and a phased estimate any competent shop could execute. If the discovery is strong, continue with that team. If not, you keep the specification.
Digital Heroes delivers PRD first, with a 50 plus team and 2,000 plus projects behind it, contracting through an India LLP, a US LLC or a UK LTD so intellectual property assigns under your own law. We are a Fiverr Vetted Pro, verifiable through D-U-N-S, Clutch and Trustpilot. Send us one real consolidation and we will model it.
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.
- 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) →
- McKinsey reports that autonomous supply-chain planning can raise revenue up to 4%, reduce inventory up to 20%, and cut supply-chain costs up to 10% while maintaining service levels (the wider 20-30% inventory-reduction figure comes from McKinsey's separate distribution-operations research, not this page). Source: McKinsey & Company (2020) →
- Sensor Tower's State of Mobile 2026 reports that global users spent 5.3 trillion hours in iOS and Google Play apps in 2025 (+3.8% YoY), roughly 3.6 hours per day per mobile user. (Note: the page does not itself contrast app time vs. mobile-browser time, so the 'overwhelming majority of time in apps vs browsers' framing is not directly supported by this source.). Source: Sensor Tower (2026) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
Frequently asked questions
How much does it cost to hire an air cargo software development company?
A first release covering the shipment and consolidation data model, air waybill management, document extraction with a review queue and one carrier integration runs $60,000 to $130,000 over 12 to 16 weeks. A full platform adding multi carrier messaging, customs filing, co-load settlement, customer notifications and accounting integration runs $150,000 to $400,000 phased over 6 to 12 months. Filing across two jurisdictions pushes past that.
What single test separates a real air cargo developer from a general agency?
Ask them to model a co-load on the whiteboard in the first meeting: your house bills plus a partner's, one master air waybill, a split at the hub, dangerous goods in the load, and profit share on the buy rate. A team that has built this reaches for allocations and relationships. A team that has not draws a shipments table with a parent identifier, and that model cannot express your business.
Why does customs filing add so much time to the schedule?
Filing to ABI in the United States or ICS2 in the European Union requires registration and a test cycle with the authority, and that cycle runs on their calendar rather than your sprint plan. Budget six to ten weeks of elapsed time per jurisdiction. The correct approach is to begin certification in week one and build the rest of the platform alongside it, which is why sequencing tells you more than headline price.
Can we switch off our current forwarding system on a single weekend?
No, and any vendor proposing it has not migrated a forwarder before. Plan a parallel run of roughly four to eight weeks where new bookings enter the new system while open shipments finish in the old one. The migration itself covers open shipments, rate tables, customer and partner records and the accounting linkage, and it usually takes three to six weeks inside the overall build.
What gets left out of most freight forwarding software quotes?
Customs certification calendar time and freight accounting reconciliation. The second is the quieter one. Quotes cover connecting to your accounting package but not the logic for accruing against estimated buy rates and then reconciling when the carrier invoices a different figure weeks later across a consol allocated to several house bills. Price that as its own three to five week item before you compare bids.
We are a growing distributor. Should we pick SAP Business One or go custom?
If you need full accounting, purchasing, and inventory in one system today, SAP Business One is the faster path; if your pain is operational workflows the ERP handles badly, custom is usually the better spend. Business One gives you a proven ledger and stock control, but changing its workflows means paying certified consultants, and the customization quotes Digital Heroes clients share commonly run $150 to $250 per hour for changes you never own. A pattern Digital Heroes builds often is Business One or QuickBooks as the financial core with a custom order, warehouse, or logistics layer on top.
Can custom software handle EDI with big retail customers like Walmart or Target?
Yes, and this is one of the most common reasons distributors go custom, because retailer scorecards penalize late or malformed documents. The typical build covers EDI 850 purchase orders in, 855 acknowledgments, 856 advance ship notices, and 810 invoices out, usually through a network like SPS Commerce or TrueCommerce rather than raw AS2. In Digital Heroes builds, onboarding your first major retailer adds 4 to 8 weeks and $10,000 to $25,000, with each additional trading partner far cheaper once the pipeline exists.
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.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
When is SAP actually a better choice than building custom supply chain software?
Choose SAP when you need a full ERP, operate in a heavily audited industry that expects standard systems, or run global operations where localization, tax, and compliance content matter more than workflow fit. SAP's strength is breadth: finance, manufacturing, and supply chain in one validated suite. Custom wins when your edge lives in a specific workflow, like how you allocate inventory or route orders, that SAP would force you to bend to its standard process. Many Digital Heroes clients keep SAP as the system of record and build custom operational tools around it.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
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.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
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.
What tech stack is best for custom supply chain software?
Boring and mainstream wins: a typed backend such as Node with TypeScript, Python, or C#, PostgreSQL for transactional inventory data, a React web frontend, and hosting on AWS, Azure, or GCP. Real-time needs like scanner feeds or live shipment tracking add a message queue such as Redis or RabbitMQ. Be wary of any agency pitching an exotic stack; in Digital Heroes handover work, systems built on niche frameworks are consistently the hardest and most expensive for a new team to take over.
Will custom software scale as we add warehouses, SKUs, and order volume?
Yes, if multi-location support and your target volumes are stated requirements at design time, because a schema built for one warehouse is expensive to retrofit for ten. A well-built system on PostgreSQL comfortably handles millions of SKUs and tens of thousands of orders per day on modest cloud hardware, so scaling cost shows up in hosting bills rather than rewrites. Give your agency the 3-year growth picture upfront even if phase one covers a single site.
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 .