Build vs Buy Humanitarian Relief Logistics Software: Earmarking, Expiry and the Handover Boundary
Buy, or use RITA and disciplined spreadsheets, if you run one country from one warehouse on one or two funding sources.
On this page
Buy, or use RITA and disciplined spreadsheets, if you run one country from one warehouse on one or two funding sources. Build once you hold prepositioned stock across borders for donors with conflicting reporting rules: a first release carrying earmarking to batch level, offline warehouse capture and a pipeline wide expiry view runs $80,000 to $160,000 in fourteen to twenty weeks.
The buy case is stronger than most logistics teams admit
A logistics director who has just spent a fortnight compiling a donor report tends to arrive at the build conversation already convinced. Slow down. There are agencies for whom a custom pipeline system would be a mistake, and it is worth being clear about who they are.
If you operate in one country, from one warehouse, funded by one or two donors, do not build. Use RITA where the logistics cluster is active, keep clean spreadsheets with genuine discipline about batch numbers and expiry dates, and put the money into the response. A system nobody has capacity to maintain is worse than a spreadsheet somebody owns, and in a sector staffed against grant lines, capacity is the constraint that quietly kills software.
Sahana Eden deserves a proper evaluation before you dismiss it. It is a long standing open source disaster management platform with a broad feature set, and if your requirements sit close to what it already does, configuring it is cheaper than commissioning anything. Commercial warehouse management products are also worth a look for a single hub operation with straightforward ownership, because inventory, picking and stock counts are solved problems.
And RITA itself is genuinely valuable during a coordinated response. It was built for common service provision, where the cluster moves items on behalf of organisations, and for that job it works. The catch, which nobody flags at the start, is that cluster support follows the emergency. When a response becomes protracted and the cluster scales down, the shared visibility you had been relying on scales down with it, and your pipeline is suddenly back to email threads at exactly the point the operation gets longer and more complicated.
The four conditions that make ownership worth paying for
Every commercial supply chain product rests on assumptions a relief pipeline breaks. One organisation owns the goods. Lanes are stable. Customs is a routine cost line. Connectivity exists. If you have two hundred blankets in a Dubai warehouse, you have two hundred available.
The first condition is donor earmarking. Those two hundred blankets might be sixty against one grant, ninety against another and fifty unearmarked, and moving the wrong sixty to the wrong response creates a reporting problem that ends in a disallowed cost. Finance systems hold grants. Warehouse systems hold pallets. The join between a grant and a pallet is currently made by a person in a spreadsheet, and that person is the reason your reporting is late.
The second is expiry across a pipeline rather than within a warehouse. A pallet of therapeutic food eleven weeks from expiry in a hub could still be programmed into an ongoing response if anyone knew. Instead it expires and is destroyed, and the destruction is reported to the donor who funded it. That single line costs more credibility than money, and credibility is what the agency actually runs on.
The third is the handover boundary. When goods pass to a partner agency, a broker, a military logistics unit or a government counterpart, the record has to continue. Systems that treat dispatch as the end of the record cannot tell you where anything is once it leaves your custody, which is precisely where consignments disappear.
The fourth is customs. A duty exemption is not a cost line, it is an application against a specific waiver in a specific country requiring a specific document pack. Model the pack per destination and the third shipment into a country moves faster than the first. Do not model it, and every shipment is the first one.
Pricing the two paths honestly
The buy side is rarely priced properly because most of it is not a licence. RITA costs nothing. Sahana Eden costs nothing to download and a configuration project to run, and the pattern many agencies report is that adapting it to their earmarking model, document requirements and offline needs becomes a development project anyway, on a foundation with a smaller pool of people who can maintain it. Commercial warehouse products run per warehouse and per user and will not carry earmarking at all, so you pay the licence and keep the spreadsheet.
The real buy side cost is people and waste: the logistics officers who compile donor reports by hand, the write offs that happen because visibility arrived late, the demurrage accrued while a document pack was assembled from memory, and the consignments reconciled six months after delivery because a waybill sat in a folder in a field office.
A first release runs $80,000 to $160,000 across fourteen to twenty weeks, covering earmarked stock at batch level across multiple warehouses, genuinely offline capture, and the pipeline wide expiry view. Offline is the main reason this sits above a comparable commercial inventory build, because doing it properly is engineering that cannot be shortened. A full platform at $200,000 to $450,000 phased over eight to fourteen months adds waybill handover with partner reconciliation, charter and consignment tracking, customs document packs per destination, cold chain records, last mile distribution capture and donor reporting derived from movements.
Cost rises with the number of donors holding distinct reporting requirements, the number of countries in the pipeline, integration with your finance or enterprise system, multiple languages and scripts in field interfaces, and partner participation, since every counterparty who touches a waybill is an onboarding exercise. Cost falls if the first release covers two hubs, your three largest donors and one country programme.
Costs that hide behind the word integration
Four line items get understated. The first is finance system alignment. The grant structure in your enterprise system has to match the earmarking model in the logistics system, and in most agencies those two structures were designed by different departments in different decades. Reconciling them is a discovery exercise involving finance, not a mapping table, and it belongs in the schedule.
The second is partner onboarding. A waybill only closes the visibility gap if the receiving party confirms receipt. That means the design has to degrade to paper for a counterparty with no smartphone and no access to your system, then reconcile afterwards. Every partner agency, broker and government counterpart you want in the loop is a conversation, a training session and a support relationship.
The third is language and script. Field interfaces in Arabic, French, Spanish or Amharic are not a translation task once numeric inputs, right to left rendering and printed waybills are involved. Test on the devices your warehouses actually use.
The fourth is uncertainty. Consignments spend real time in transit with no telemetry, and a system implying precision the organisation does not have will be distrusted within a month. Modelling last confirmed location and date explicitly costs little and saves the credibility of the whole system.
Then maintenance. Fifteen to twenty percent of build cost annually, named owner, funded from something other than a single grant. Systems agencies build tend to outlive the funding that paid for them, which is a strength only if somebody is keeping them alive.
A one hour test for your logistics director
Here is the test we use on discovery calls. Ask your global logistics director to answer two questions in one hour without phoning three people. Where is the consignment funded by this specific donor right now, and what condition is it in? And what in the pipeline expires in the next ninety days, by location and by donor?
If both answers arrive inside the hour, your current arrangement works and you should keep it. If either requires a round of calls and an evening rebuilding a spreadsheet, the pipeline is being run on memory and the exposure is real.
Then run four checks against the last twelve months. Has an expiry write off appeared in a donor report? Have you handed a consignment to a partner and lost sight of it for more than a month? Do two or more donors funding the same warehouse require different slices of the same movements? Has a shipment accrued demurrage while a customs document pack was assembled?
Two or more yes answers, combined with prepositioned stock across borders, is a build case. One yes is a process fix and probably a better filing convention. None, and the answer is that your team is doing well and the money should go to the response.
If you build, build in this order
Start with earmarking, because it is the model everything else hangs off and because it is the one most likely to be wrong. If your earmarking design does not survive contact with a real donor report, you want to discover that at week twelve, not month nine. Prove it against your three largest donors and two hubs before you widen.
Offline capture comes next, and it has to be genuinely offline: local store, sync queue, an explicit conflict rule, and a visible sync state a warehouse manager can check on a device that has been disconnected for days. Receipts lost to a weak offline design become stock discrepancies that take months and a lot of trust to resolve.
Waybills and customs packs follow, then charter tracking and cold chain. Last mile distribution capture is usually last, because it is the part most likely to need redesign once field teams have used the rest.
When selecting a partner, make them model donor earmarking on a whiteboard against a single pallet split across three grants. Someone who understands this asks what happens during an emergency substitution, who approves it, and how the report reflects it afterwards. Someone who adds a donor field to the stock table has not understood the problem. Ask what offline means in their design, and ask how a waybill works when the receiving party has neither your system nor a smartphone.
Digital Heroes works from a written product requirements document before any code, which here means the earmarking rules and the substitution approval path are agreed on paper with your logistics and finance leads. The team is fifty plus people across more than 2,000 delivered projects, holds Fiverr Vetted Pro status, and publishes to 2.5 million subscribers at Digital Marketing Heroes on YouTube. Contracting runs through an India LLP, a US LLC or a UK LTD, and the client owns the repository from the first commit, including the right to share the work with peer agencies.
If you would rather someone argued with your brief than agreed with it, 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) →
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
- 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) →
- Across ten outpatient clinics the mean no-show rate was 18.8%, and the marginal cost of no-shows reached $14.58 million per year for those clinics, at roughly $196 per missed appointment (2008 figures). Source: BMC Health Services Research / PubMed Central (Kheirkhah et al.) (2015) →
Frequently asked questions
How much does custom humanitarian relief logistics software cost?
A first release with batch level donor earmarking across multiple warehouses, genuinely offline warehouse capture and a pipeline wide expiry view runs $80,000 to $160,000 over fourteen to twenty weeks. A full platform adding waybill handover, charter tracking, customs document packs, cold chain records and donor reporting runs $200,000 to $450,000 phased across eight to fourteen months. Offline capture is what pushes this above a comparable commercial inventory build.
Is RITA enough for an international agency with prepositioned stock?
RITA is valuable during a coordinated response and is often right for common service pipelines run through the logistics cluster. It is not designed to hold your own multi year pipeline across prepositioning hubs, your donor earmarking, or your grant reporting structure. Cluster support also follows the emergency, so shared visibility scales down as a response becomes protracted, which is exactly when the pipeline gets longer and more complicated.
How long does implementation take and what slows it down?
Fourteen to twenty weeks to a first release covering two hubs, your largest donors and one country programme. The usual delay is not engineering, it is agreeing the earmarking model, because the grant structure in your finance system and the stock structure in your warehouse records were designed by different departments. Agencies that can hand over executed grant agreements and current warehouse layouts at kickoff move noticeably faster.
Can this connect to our finance or enterprise resource planning system?
It should, because the grant structure has to match the earmarking model or donor reports will never reconcile. Treat it as a discovery exercise with your finance team rather than a mapping table, since the two structures rarely align out of the box. Start with a one way feed of grant and award data into the logistics system, and add movement level cost postings back only once the earmarking model has survived a real reporting cycle.
Will warehouse staff be able to work without an internet connection?
They must, and offline has to mean a local store, a sync queue, an explicit conflict rule and a visible sync state rather than simple caching. Design for a device disconnected for days, not minutes, because that is the reality in the warehouses that matter most. Receipts lost to a weak offline design become stock discrepancies that take months and considerable trust to resolve with partners and donors.
Who builds logistics software for humanitarian organisations?
A small number of sector specialists and custom development firms with supply chain depth. Digital Heroes fits agencies that need contracting and intellectual property assignment in their own jurisdiction, operating as an India LLP, a US LLC and a UK LTD, with a written product requirements document agreed before code starts. That matters here because the earmarking model has to be settled with logistics and finance together, not discovered during the first donor report.
What separates Digital Heroes from a generic development firm on this?
Ownership terms written for how this sector actually works. The client holds the repository from the first commit, including the right to share the work with peer agencies, which is uncommon and matters because systems built here usually outlive the grant that funded them. The PRD-first process also forces the emergency substitution and approval path to be decided on paper, where it costs nothing to change.
How do we check a development partner is legitimate before releasing funds?
Verify the D-U-N-S registration matches the entity that will sign your contract, then read the public Clutch and Trustpilot profiles for reviews describing comparable delivery rather than the star average. Ask which legal entity signs and under which jurisdiction, since that determines your recourse. Require repository and cloud account access from week one, and ask for a redacted prior agreement showing full intellectual property assignment.
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.
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.
Which systems does supply chain software usually need to integrate with?
The standard set is your accounting or ERP system (QuickBooks, NetSuite, SAP), your sales channels (Shopify, Amazon, or a B2B portal), carriers and 3PLs for rates and tracking (UPS, FedEx, or an aggregator like EasyPost), and warehouse hardware such as barcode scanners and label printers. EDI connections to large retail customers are their own workstream. In Digital Heroes scoping, integration work is commonly 30 to 50 percent of total project effort, so listing every connected system upfront is the single best way to get an accurate quote.
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 much does a custom warehouse management system cost to build?
A custom WMS typically costs $40,000 to $120,000 for a single-warehouse operation, and $120,000 to $300,000 once you add multiple sites, wave picking, and labor tracking. Across Digital Heroes WMS builds, the biggest cost drivers are scanner-based workflows, real-time inventory sync with your ERP, and the number of picking strategies you need. A pilot covering receiving, putaway, and picking for one warehouse is the cheapest credible starting point.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
What happens to our system if the agency shuts down or we part ways?
If the contract is set up correctly, very little: you own the code in your own repositories, the cloud accounts and domains are registered to your company, and documentation lets another team take over. Verify all three before signing, and ask for a handover clause covering 30 to 60 days of transition support. Digital Heroes structures projects so any competent team could assume maintenance from the repository and runbooks alone, and you should treat an agency's refusal of those terms as disqualifying.
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.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
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 .
