Freight Forwarder Management Software: CargoWise or a Custom Build?
The threshold here is specialisation, not size, and the size rule only tells you when to stop asking.
On this page
The threshold here is specialisation, not size, and the size rule only tells you when to stop asking. If you are a general forwarder under roughly forty staff running conventional ocean and air, implement CargoWise or Magaya properly and put the difference into people who can sell. The build case appears when your differentiator already lives in spreadsheets beside the standard suite: project cargo, perishables, pharmaceutical logistics with validation requirements, or cross border e-commerce where enormous volume at tiny value per shipment inverts every assumption the mass market products are built on. Most forwarders are not that, and for them a first release at $90,000 to $200,000 would be money spent to rebuild what already exists.
When is off the shelf genuinely the right call here?
If you are a general forwarder under roughly forty staff running conventional ocean and air, do not build. Implement CargoWise properly. It is the most complete product in the category and it earns that position, and a first release build will not approach its depth for the same money.
The cost of choosing it is worth stating plainly, because it is a shape rather than a defect. CargoWise is an operating model as much as a system. Implementing it means adopting its way of working, and changes go through its configuration framework, so a forwarder with genuinely unusual processes either conforms or maintains satellite spreadsheets. For a conventional forwarder that is a reasonable trade and most of the market should take it.
Magaya suits small and mid sized forwarders well and gets lighter as consolidation complexity, multi entity accounting and agent share arrangements grow. Descartes offers strong individual capabilities, particularly around customs and network connectivity, assembled from a portfolio built partly by acquisition, so the seams between the pieces are real and worth testing during evaluation. Logitude World and Softlink sit at the accessible end with correspondingly less depth in automation and financial control.
The honest test is whether your file profit question can be answered inside the product you are evaluating. If a demo can show you accruals ageing on an operations queue and a consolidation apportioned the way your business actually apportions it, buy the product.
When does a custom build actually pay off?
Build when you are a specialist and the specialism is the business. Project cargo where every file is an engineering exercise. Perishables where the temperature record is part of the product. Pharmaceutical logistics with validation requirements. Cross border e-commerce, where volume is enormous and value per shipment is tiny, which inverts the economics of every operational assumption these suites make.
In those cases the standard suite forces you to run your differentiator outside the system, and once that is true the comparison is no longer product against build. It is the cost of the workaround against the cost of the software, and the workaround is usually a person.
The second build trigger is structural rather than commercial. Your file profit is accurate for files that closed cleanly and optimistic for everything else, because third party costs arrive on their own timetable and nobody accrued them. A file opens in March, closes in April showing a healthy margin, and in July an agent statement arrives with demurrage, a chassis split and warehouse handling that halves it. If nobody can tell you which of your open files are exposed to that, the accrual discipline is the thing you are buying, and it has to be an operational workflow rather than an accounting field.
The third is agent settlement. A small percentage error repeated across hundreds of files a year is a serious number, and reconciling agent statements is one of the least automated activities in the trade.
How do they compare on the things that matter in this industry?
Consolidation modelling. Apportioning master bill ocean freight across nine house bills by chargeable weight is arithmetic and every product does it. Apportioning a destination terminal charge when one house bill rolled to the next sailing is a business rule you have to decide and encode. If the system cannot express that rule, someone resolves it in a spreadsheet and file profit stops being a fact.
Accrual behaviour. The difference between a standard accrual field and a working accrual engine is ageing and the chase. Accruals older than a threshold with no invoice received are a queue with an owner. Invoices arriving against files with no matching accrual are a different queue, because they usually indicate a cost nobody expected and possibly a charge that should have been passed on.
Unbilled revenue. A remote area delivery surcharge, a pallet exchange, three days of origin storage caused by the shipper. These never appear as a loss anywhere, because unbilled revenue is invisible in a system that only knows what was invoiced. Tying quoted commercial terms to the file so the invoice is assembled from every recorded charge is a design decision, not a feature toggle.
Configuration ceilings. Agent agreements with share percentages varying by direction and lane, and rules about which charge types are shareable, are where packaged configuration usually runs out. So are unusual consolidation models.
Where the products win. Customs connectivity, carrier and terminal networks, multi entity accounting that has already been audited, and thirty years of trade detail you would otherwise rediscover at your own expense.
What does total cost of ownership look like at your scale?
A first release covering the commercial spine, meaning quotation priced from a rate repository, file management with house and master bill structure and consolidation handling, automatic accrual creation with variance surfacing, purchase invoice matching and customer invoicing that sweeps every billable charge, runs $90,000 to $200,000 and ships in 14 to 20 weeks. A worked sixty person forwarder doing ocean and air across two legal entities lands at $200,000 over roughly twenty weeks. Defer air and consolidate to a single entity and the same spine comes in around $130,000.
A full platform adding agent settlement with share rules, direct customs interfaces, milestone tracking from real carrier and terminal data, a customer portal, document extraction and finance integration runs $250,000 to $700,000 phased over 9 to 18 months. The spread between those two ends is decided almost entirely by how many external parties you connect to directly.
Running costs are 15 to 20 per cent of build annually, so $30,000 to $40,000 against a $200,000 spine. Four lines are specific to forwarding: repair work when carrier and agent message formats change, mandatory maintenance for every customs system you file into directly, a human review queue for low confidence document extraction, and an owner with allocated time for rate data quality. The last is unpaid in most budgets and determines whether quoting stays accurate.
Compare that against four lines from your own invoices: the renewal, the expected uplift, the configuration days you buy each year, and the salary cost of work your people do outside the system because it cannot be done inside it. The fourth is usually the largest and always the least visible.
What does the hybrid look like, and when is it the honest answer?
The hybrid in this category is not two products side by side, it is sequencing what you own. Keep filing customs through your brokers everywhere except the country where you file most, keep your existing finance ledger, and build only the commercial spine that answers the margin question.
That is the honest answer for a specialist who cannot justify a full platform yet, and it works because the sequencing is genuinely additive. If the file model, charge structure and party data are built properly in release one, adding a customs interface later is new work rather than rework, so deferring it costs you nothing structurally and takes six figures out of year one.
Direct customs filing is the dominant cost driver and it is not close. Each national system is its own project: specification, accreditation with the authority, a test cycle on their timetable rather than yours, then permanent maintenance because the specification changes and compliance is not optional. One country is a workstream. Three is a programme with its own manager.
The other deliberate deferral is the customer portal, which is counterintuitive and correct. Showing a customer a status is only valuable if the status is accurate, and accuracy depends on milestone work that has not happened yet. Agent settlement and document extraction come first, because both attack money rather than convenience.
Which should you choose, by operator size and stage?
Under forty staff, conventional ocean and air, one country of significance: buy. Implement CargoWise or Magaya properly, resource the implementation seriously, and spend the difference on commercial people.
Forty to a hundred staff, still conventional: buy, then measure one thing. Count the hours a month your operations team spends reconciling agent statements and chasing accruals in spreadsheets. If that is under half a role, keep configuring. If it is over, you are already funding the build through payroll.
Specialists at any size above roughly thirty staff: build the commercial spine. Project cargo, perishables, pharmaceutical logistics and cross border e-commerce are the four profiles where the differentiator has already left the suite, and no amount of configuration brings it back.
Multi entity groups with agent share arrangements: build, and design entity and currency as fields rather than assumptions from the schema up even if you start with one of each. Retrofitting that in year two costs more than building it in.
Anyone about to start: do the rate data work before kickoff. Contract rates, tariffs and surcharges almost always live in spreadsheets with a different structure per trade and per person, and normalising them is the single most common cause of a slipped first release. It is also work your own commercial team can do at their salary cost rather than at a developer's day rate.
When the shortlist is down to two and you need a tiebreaker, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- In PMI's 2014 Pulse of the Profession report on requirements management, inaccurate requirements management is cited as a leading cause of project failure, with 47% of unsuccessful projects failing to meet goals due to poor requirements management. Source: Project Management Institute (PMI) (2014) →
- 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 an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
Frequently asked questions
What does it cost to leave CargoWise if we build our own spine?
Less than most forwarders expect on the data, and more than they expect on the operating model. Your rate repository and file history are extractable, and a build that owns quotation, files, accruals and invoicing already holds the records that matter.
The harder part is that CargoWise is an operating model your team has learned. Budget for retraining and for a parallel period where both run against real files, and expect two to four weeks of live overlap before the spreadsheets go dark. That parallel period is not optional and it is the line most often cut from a proposal.
What happens if our incumbent changes its pricing or module structure?
Run the comparison over three years rather than one, and include the configuration days you buy annually alongside the licence, because those days are how the product bends to your process and their rate is part of your real cost.
Owning the spine changes the shape rather than removing the bill. Subscription and per document costs climb with your shipment volume, while a build's running cost climbs only with your appetite for changes. That difference is what makes a repricing a commercial decision instead of an ultimatum.
How long does a freight forwarding build take, and when can we go live?
Fourteen to twenty weeks for the commercial spine, plus three to four weeks of discovery before it. The full platform phases across 9 to 18 months after that.
The most common schedule surprise is rate data. Contract rates, tariffs and surcharges usually sit in spreadsheets with a different structure per trade lane and per person, and normalising them has to finish before quoting can be automated. Doing that with your own commercial team before kickoff removes the likeliest reason for a slipped date.
Is building cheaper than staying on CargoWise or Magaya?
For a general forwarder running conventional ocean and air, no, and we would say so before quoting. CargoWise is the most complete product in the category and implementing it properly is the right answer for most of the market.
The comparison flips for specialists. If your differentiator is project cargo engineering, perishables temperature records, pharmaceutical validation or cross border e-commerce economics, that differentiator is already living outside the suite in spreadsheets, and the cost of the workaround is what you are really comparing against.
What does direct customs filing add, and can we defer it?
Treat each national system as its own project rather than a feature. You need the message specification, accreditation with the authority, a test cycle that runs on their timetable, and permanent maintenance because the specification changes and compliance is mandatory.
Yes, defer it. Keep filing through your brokers everywhere except the country where you file most. If the file model, charge structure and party data are built properly in release one, adding a customs interface later is additive rather than rework, so deferring it costs nothing structurally and takes six figures out of year one.
What does agent settlement add to the budget, and when should we build it?
It is normally a phase two item and it earns its place because it attacks money directly. The work is modelling the agreement explicitly: share percentage by direction and by lane, which charge types are shareable, how the net is calculated, and what evidence attaches to a disputed line.
Once that exists, reconciling a statement becomes a match with an exception list, so the quarterly conversation with an agent covers twelve disputed lines rather than the whole statement. A small percentage error repeated across hundreds of files a year is a serious number, which is why this usually pays back faster than a portal.
Does document extraction on purchase invoices justify its cost?
In this category, yes, and it is one of the few places automation clearly earns its keep. Purchase invoices and agent statements arrive as documents in hundreds of layouts, and matching them to files by hand is close to a full time role at any real volume.
Budget it as a phase two item with a human review queue rather than a launch feature, because the tuning improves considerably once you have a few thousand of your own real documents to work from. Anyone quoting fully autonomous matching with no review queue has not run this against a live inbox.
What is the cheapest useful version we could build?
The commercial spine with air out of scope and a single legal entity and currency, which brings the same feature set in around $130,000 rather than $200,000 for a forwarder doing both.
Cutting below roughly $90,000 generally means dropping either accruals or consolidation apportionment, and both are the reason the system exists. A system that tracks files and prints invoices without an accrual engine will not answer the margin question, which means you will still be running the spreadsheet you built the software to retire.
What tech stack should a custom ERP be built on?
A boring, hireable one: Digital Heroes most often ships ERPs on PostgreSQL with a Node.js or Python backend and a React frontend, hosted on AWS or Azure. The stack matters far less than the database design, because your ERP schema will outlive every framework choice. Be skeptical of any agency proposing a niche or proprietary framework, since your ability to hire maintainers later is part of the total cost.
Can a custom ERP integrate with the tools we already use, like QuickBooks or Shopify?
Yes, and keeping tools that already work well is usually the right call. The integrations we build most often are QuickBooks or Xero for accounting, Shopify or WooCommerce for orders, ShipStation for fulfillment, and Salesforce or HubSpot for CRM. A typical integration adds $5,000 to $15,000 to the build depending on how much two-way syncing the workflow needs.
Is customizing Odoo cheaper than building an ERP from scratch?
Usually yes in year one, and often no by year three if your workflows sit far from Odoo's assumptions. Odoo's published pricing starts around $25 per user per month and the Community edition is free, but heavy customization means every version upgrade can break your modules and needs paid rework. If you expect to rewrite more than about a third of the core flows, a scratch build with clean ownership tends to cost less over the life of the system.
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.
Is a custom ERP cheaper than NetSuite over five years?
Often yes once you pass roughly 20 to 30 users. NetSuite is commonly quoted at $999 per month for the base platform plus about $99 per user per month, so a 30-user company spends over $200,000 on licenses across five years before paying for implementation. A custom build in the $120,000 to $250,000 range is a one-time cost, and in Digital Heroes projects annual upkeep runs 15 to 20 percent of build cost with no per-seat fees as you hire.
Can I start with one ERP module instead of the full system?
Yes, and it is how most successful custom ERP projects at Digital Heroes begin. We build the single module causing the worst pain first, typically inventory or order management, get it live in 10 to 14 weeks, and let it prove ROI before the next phase gets funded. Starting with one module also derisks data migration because you move one dataset at a time.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Is SAP overkill for a mid-sized company?
For most companies under about 500 employees, yes. SAP S/4HANA is built for multi-entity, multi-country enterprises with implementations measured in years and seven figures, while SAP Business One, the mid-market product, still forces your processes into its mold. If your competitive edge lives in how you operate, a custom ERP scoped to your actual workflows ships faster and costs a fraction of an SAP program.
How do we migrate years of data from our old system without losing anything?
Through a staged migration with a parallel run, never a single cutover weekend. The data gets extracted and cleaned early, loaded into the new ERP while the old system stays live, and both run side by side for two to four weeks so your team can verify counts, balances, and open orders match. In Digital Heroes ERP projects, data cleaning consistently takes longer than the technical transfer, so it starts in week one, not at the end.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP 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 ERP 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 .
