Defence Logistics Management Software Development Services
Defence logistics management software, built around your supply chain, not a commercial ERP.
Commercial ERP platforms handle procurement and inventory well for commercial supply chains. The mismatch appears when stock is managed by NATO Stock Number rather than a commercial part number, when procurement follows authority structures commercial platforms can't model without heavy customisation, and when demand originates from a maintenance system with no native connection to the logistics system. We build defence logistics management software around your actual supply chain structure.
Spares inventory management by NATO Stock Number with stock level visibility across all depot locations
Procurement workflow from demand signal through purchase order, dispatch confirmation, and goods receipt, with authority-level approval
Inter-depot transfer management for stock rebalancing and urgent demand fulfilment
Demand signal integration with the maintenance system so a spare requirement creates a logistics demand without manual re-entry
Bring the problem, the current workflow, or the existing code. We reply with a practical next step within one business day.
Trusted by
The brief
Start with what is not working.
Good software decisions begin with the constraint, not a list of features or a preferred technology.
Logistics officers manually converting maintenance demand signals into procurement requests because the maintenance system and logistics system have no connection?
Shelf-life-limited stock reaching expiry in the depot because nobody is systematically tracking expiry dates and generating alerts before the stock becomes waste?
Plain answer
RaftLabs builds custom defence logistics management software that manages spares by NATO Stock Number, runs authority-based procurement, and pulls demand straight from the maintenance system. A focused v1 covers spares, procurement, and inter-depot transfers, then grows into shelf-life management, demand-signal integration, and NSN codification.
What to remember
- NSN cross-reference management links manufacturer part numbers and OEM references to the correct NATO Stock Number, so demand expressed in any format resolves to the right item automatically.
- Demand signal integration connects an equipment defect raised in the maintenance system directly to a logistics demand, no manual re-entry, with classification (routine/priority/urgent) driving the processing timeline.
- Shelf-life management applies first-expiry-first-out issuing automatically and quarantines expired stock, preventing issue until a disposition decision is recorded.
- Export-controlled items and controlled technical data are flagged in the item record, and the system deploys to the network your security officer specifies, including segregated or air-gapped hosting.
- A focused v1 covers spares inventory, procurement, and inter-depot transfers, then grows into shelf-life management, demand-signal integration, and NSN codification.
The demand signal that never made it out of the maintenance office.
A maintenance crew raises a defect. The spare it needs sits in a depot two hundred miles away. But the maintenance system and the logistics system don't talk, so a logistics officer reads the demand, retypes it as a procurement request, and hopes the NATO Stock Number matches.
Meanwhile, a pallet of shelf-life-limited stock passes its expiry date on a shelf nobody flagged. It becomes waste, and the demand it could have filled goes to a fresh purchase order instead.
None of that is a people problem. It is a systems problem: two systems that should share a demand signal, and don't.
The platform connects to adjacent systems: logistics automation for carrier and warehouse events, fleet management software for the vehicles moving the stock, inventory management software for depot stock levels, and ERP development when the commercial backbone needs rethinking.
Custom defence logistics management software is built around your specific stock catalogue, depot network, procurement authority levels, and the connection to the maintenance system that keeps logistics informed of operational demand. Commercial ERP platforms handle procurement and inventory well for commercial supply chains. The mismatch shows up in three places. Stock is managed by NATO Stock Number, not a commercial part number. Procurement follows authority structures a commercial platform cannot model without heavy customisation. And demand originates in a maintenance system with no native link to the logistics side.
RaftLabs has been shipping production software since 2015, including for clients in regulated, audit-heavy sectors. The stock model reflects NATO codification standards from day one, not a retrofit onto a commercial ERP, and the cost is fixed before any development starts.
This fits when a commercial ERP keeps falling short of your supply chain.
Everything on the left should already be true for your operation. Even one thing on the right, and an off-the-shelf platform is the smarter first step.
You manage stock by NATO Stock Number across more than one depot, and commercial ERP customisation keeps missing the mark.
Your maintenance system raises demand that a logistics officer currently re-enters into procurement by hand.
Procurement has to follow your authority structure, your shelf-life rules, and your hazardous-material handling, not a commercial default.
A single commercial supply chain that a standard ERP already handles by part number.
No requirement for NATO codification, authority-level procurement, or maintenance-driven demand.
You need an off-the-shelf platform to configure this week, not a system built around your supply chain.
The first decision is not what to build.
It is whether software is the right answer at all. We use four possible recommendations before discussing a development scope.
Buy
Run the build-vs-buy numbersChoose a maintained product when it handles the core defence logistics operations workflow and the remaining gaps can be solved with configuration, a connector, or a small process change. Paying for software you do not have to maintain is often the better trade.
Repair
Keep the existing product when users still get value from it and the code can be understood safely. Start with evidence: where the code lives, how the data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live.
Build
Own the system when defence logistics operations shape margin, customer experience, speed, or a product customers pay for. Start with one complete path and the system connections that path cannot work without.
Wait
Do not turn a changing policy into permanent software. Stabilise the rules, name the workflow owner, and measure the cost of the current process before paying for a product.
Not sure which path is yours? Bring it to a 30-minute call. Leave with the answer in writing.
What we build
What defence logistics management software covers
Spares inventory management
Stock on hand, reserved, and available balance are visible by NSN at every depot, with reorder alerts, condition tracking, and shelf-life stock managed within the same register.
NATO stock numbering and codification
A full NSN catalogue with cross-reference to manufacturer part numbers, interchangeability data for approved substitutes, and a codification workflow for items not yet in the NATO catalogue.
Procurement workflow
Demand signals from maintenance match to an NSN and check against stock before a purchase order is raised, with authority-level approval thresholds and goods receipt updating stock automatically.
Inter-depot transfers
Urgent demands route to alternate depots with available stock, tracked from dispatch to receipt, with transfer authority approval and dangerous goods documentation generated automatically.
Shelf-life management
Expiry dates are recorded at goods receipt, stock rotates first-expiry-first-out, and pre-expiry alerts fire at configurable lead times before items are quarantined automatically at expiry.
Demand signal from maintenance
A defect raised in the maintenance system creates a logistics demand automatically, classified by urgency, and tracked through fulfilment so the maintainer knows when the spare will arrive.
Why sustainment is where this software earns its keep
Buying the equipment is the small part. Keeping it ready is the long, expensive part, and it runs on the logistics system. Operating and support costs, the sustainment tail, can account for up to 70 percent of a weapon system's total life-cycle cost (U.S. Government Accountability Office). A spare that expires unnoticed, a demand that never crosses from the maintenance office, or a requisition that misses its priority all add to that tail. This is the workflow the software is built to protect.
Requisition priority is part of that. A demand from the maintenance system carries its urgency through, so a mission-critical spare is processed ahead of routine replenishment rather than sitting in the same queue. The classification drives the timeline, the alternate-depot search, and the escalation, the way a MILSTRIP-style priority designator would in a manual system.
The regimes a defence logistics system has to answer to
Defence stock is not just parts on a shelf. Spares and their technical data can be export-controlled under ITAR or EAR, so the item record carries the control classification and restricts who can see and move it. Where records sit on a classified network or hold controlled information, the system deploys to the environment your security officer specifies, up to a segregated or air-gapped arrangement, so stock and demand data never leaves its approved boundary.
The defence logistics regime, in short
- of a weapon system's total life-cycle cost goes to operating and support (sustainment)
- Up to 70%
- U.S. Government Accountability Office
- NIST SP 800-171 controls a contractor holding CUI in logistics records must evidence
- 110
- NIST SP 800-171 Rev 2, mandated by DFARS 252.204-7012
- spares, procurement, and maintenance-driven demand on a single air-gappable deployment
- One system
- RaftLabs build approach
Have a defence logistics management project?
Tell us about your supply chain structure: your equipment types, your depot network, your stock catalogue, and where your current logistics process creates fulfilment delays or compliance gaps. We'll scope a system built around your actual requirements.
How it works
From scope to live logistics system
- Week 101
Supply chain structure scoping
We map your equipment types, depot network, and stock catalogue. You leave week 1 with a written scope document and a fixed-price quote.
- Weeks 2-502
NSN and procurement design
We design the codification workflow and procurement authority levels against your governance requirements.
- Weeks 6-1503
Connect inventory, procurement, and maintenance
We connect inventory, procurement, and maintenance in parallel, and test the integration against real stock data.
- Final 2-3 weeks04
Launch and logistics team training
We train logistics officers on the demand and transfer workflow before full rollout.
The nearest work in our portfolio is civilian, not defence. We built a multi-carrier shipping platform for civilian supply chains. Defence logistics adds NATO codification, authority-based procurement, export-control handling, and secure deployment on top of that same supply-chain backbone. If a documented defence logistics reference matters before you commit, we will say plainly where our experience is direct and where it is adjacent.
Where you land in the cost range depends on scope, not negotiation:
- Focused build
- Spares inventory management, procurement workflow, and inter-depot transfers.
- Full build
- Everything in the focused build, plus shelf-life management, demand signal integration, and NSN codification workflow.
What it costs
Spares and logistics software, priced before development starts.
Spares, procurement, and inter-depot transfers, with shelf-life, maintenance-driven demand, and NSN codification added as your scope needs them.
Start with the core spares and procurement workflow. Once it's running across your depots, we scope shelf-life tracking and demand signal integration as the next phase.
Starting investment
Starts at $10000
Shelf-life management and NSN codification scope in as a second phase. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.
No hourly billing
Once we scope your first phase, that price is locked in writing. No hourly billing, no surprise invoices. A scope change is a priced change request, agreed before work begins.
One team
The team that scopes your supply chain builds the solution. No bait-and-switch, no offshore handoff after the contract is signed.
Work with us
Tell us where the work is stuck.
Bring the rough workflow, half-built product, or messy brief. We will map the smallest useful first move, then send scope, timeline, and price in plain English.
- Scope and cost agreed before work starts. No surprises. No obligation.
- Working prototype within 3 weeks of kickoff.
- Pay by milestone. You see progress before each invoice.
- 60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
- All conversations are NDA-protected.
Common questions
Yes. The demand signal integration connects to your existing maintenance management system, whether custom, SAP, or another platform, so defect-driven spare requirements flow into the logistics system automatically. The integration architecture depends on the interface capability of the maintenance system, assessed during scoping.
The codification workflow manages the request from initial item identification through technical data submission to the codification authority and recording of the allocated NSN. Where the organisation has access to the NMCRL, we integrate with the catalogue to pre-populate item records and check for existing NSNs first.
Yes. Hazardous material classification, UN number, hazard class, packing group, is recorded against the stock item, with transfer documentation including the dangerous goods declaration in the required format, and access restricted to authorised personnel.
Items subject to ITAR or EAR are flagged in the stock record with their control classification, so export-controlled spares and their technical data are visible to logistics staff and restricted to authorised users. Transfer and dispatch workflows enforce the handling and documentation your export compliance officer requires before stock leaves a depot.
Yes. The system deploys to the hosting environment your security officer specifies, including segregated, access-logged, or air-gapped arrangements, so stock and demand data never leaves its approved boundary.
Ask whether the vendor holds the facility security clearances your contract needs, and how classified versus unclassified data is separated. Confirm the team is cleared before the project starts, not during it. And ask which security frameworks the system is built to satisfy, with the commitment in writing.
Ask whether the system supports item-level traceability for serially managed assets, and whether it exchanges data with the registries your contracts require. A system that has never been through a defence audit is a feature list, not a compliance position.
The question is not how many spares you hold, it is which spares, in what quantities, stocked where, hit the availability target. Ask whether planners can run demand-planning what-if scenarios without affecting live operations, and confirm NATO codification is built in, not bolted on.
Ask whether the vendor can reference organisations like yours, and whether you get a team through implementation and usage, not just a project manager at kickoff. Confirm air-gapped and classified deployment, and ask how the system handles export-controlled spares, technical data, and hazardous materials in transit.
A focused build covers spares inventory, procurement workflow, and inter-depot transfers. Adding shelf-life management, demand signal integration, and NSN codification workflow adds scope. Every build is priced at a fixed cost agreed before development starts.