Duty Drawback Software: Build a Claim Engine, Buy a Trade Platform, or Keep the Contingency Filer?
The threshold is recoverable duty of roughly seven figures a year, and below it almost nobody should build.
On this page
The threshold is recoverable duty of roughly seven figures a year, and below it almost nobody should build. If your recoverable duty is modest and your flows are simple, a contingency drawback specialist recovers more for you than any system would, at no capital risk, and that arithmetic does not lose. If you already run ONESOURCE Global Trade or Descartes with clean mapped data, switch drawback on there. Building is for the minority whose constraint is evidence rather than filing: manufacturing claims that depend on your own part numbering and yields, or a specialist filer whose margin is absorbing messy client data.
When is off the shelf genuinely the right call here?
Two buy answers exist here and most readers land on the first. If your recoverable duty is modest and your flows are simple, meaning you import, export a share of what you imported, and file unused merchandise claims, outsource to a specialist drawback firm on a contingency arrangement. They are good at the work, they carry the effort, and paying a share of a recovery you were not otherwise going to make is a fair trade with no capital at risk. A build cannot beat that arithmetic at low volume and we will not pretend it can.
The second buy answer is packaged trade software. If you already run ONESOURCE Global Trade or Descartes for classification and filing, your import data is clean and mapped, and drawback is a module you can switch on rather than a data reconstruction project, switch it on. Both file drawback competently and both deserve evaluation before anyone commissions custom software. The caution is not about their filing capability, it is about where the work actually sits: they expect clean mapped data about imports, exports and consumption, and getting your data into that state is the real project.
Below roughly $50,000 of spend you are buying a reporting layer that tells you what you already claimed. That is worth having for governance and it recovers nothing, because the leakage in this category is claims never made rather than claims denied.
The test that settles it: can somebody tell you, this week, what proportion of your eligible exports is currently being claimed? If the answer is a confident number, your existing arrangement is working.
When does a custom build actually pay off?
Build when the constraint is evidence rather than filing. That distinction decides the whole question and it is worth being precise about.
Filing is the act of submitting a claim. Every option on this page can file. Evidence is proving that a specific imported line corresponds to a specific exported unit under a rule a reviewer will accept three years from now. That is where recoveries are lost, and it is where a packaged product cannot help you because the difficulty lives inside your own data.
The concrete signals: matching depends on your own part numbering and your actual manufacturing yields rather than on a transaction reference. You know eligible exports are being missed because shipments made under a logistics provider's consignor name never appear in the export file anyone works from. Claims are consistently scoped down to what is easy to prove, which is a quiet decision made by an analyst under time pressure and never reported as a loss. Or you are a specialist filer running claims for multiple clients whose data never arrives the same way twice, and your margin depends on absorbing that mess faster than competitors.
There is one more trigger that finance teams respond to. Run an opportunity analysis across your import and export history and rank what is potentially claimable but currently unevidenced, by value and by how close the statutory window is to closing. Most organisations have never seen that figure. If it is large and ageing, the build case makes itself and you do not need an argument.
How do they compare on the things that matter in this industry?
- Line level fidelity. Claims need duty, classification, quantity and value preserved per import line. Aggregation at intake is the most common irreversible mistake, and it happens easily when a platform is designed around entries rather than lines.
- Manufacturing claims. Unused merchandise is a matching problem. Manufacturing drawback is a modelling problem needing a bill of materials, actual rather than theoretical yield, and a defensible waste treatment. That modelling is specific to your plants and your product families, which is why it is the hardest thing to buy.
- Fungible inventory allocation. The convention that decides which receipt matched which export must be documented in the system, applied consistently and reproducible on demand. If it lives in an analyst's head, the answer to why is a preference rather than a rule.
- Export evidence reconciliation. Export proof is scattered across shipping records, commercial invoices, transport documents and export declarations, using your identifiers rather than the ones a customs authority uses. Mapping those two naming worlds is most of the work and no vendor arrives knowing yours.
- Claim file retention. A reviewer may look years after payment. The package needs the calculation, supporting lines, documents and the rules version applied, stored immutably. Data portability matters here more than in most categories.
- Multi client separation. Specialist filers need tenant isolation and per client matching conventions. Sponsor oriented platforms are not built for that shape.
Every item above is verifiable against your own last claim, which is the right way to test any of these tools.
What does total cost of ownership look like at your scale?
In Digital Heroes delivery experience a first release runs $80,000 to $165,000 and ships in 12 to 18 weeks. That covers import data ingested at line level, export and destruction evidence captured from wherever it actually lives, one claim type worked end to end, and the claim file assembler that produces the immutable package. A full platform adding manufacturing drawback with bill of materials and yield modelling, the allocation engine, opportunity analysis, privileges and accelerated payment tracking, and multi client separation runs $220,000 to $500,000 phased across 6 to 12 months.
Claim type is the largest driver. Adding manufacturing drawback typically adds 50 to 80 per cent to the matching engine and is the difference between the floor and the ceiling of that first band. Source system count is second and importers routinely underestimate it, because imports arriving through several brokers means several formats. Historical data quality is third and it is the one that moves schedules, since claims reach back years and older records are messier.
Running cost sits at 12 to 18 per cent of build value a year. Its specific jobs here are broker format maintenance, because formats change when a broker upgrades their own systems, and classification maintenance, which is business work rather than engineering. Evidence retention is a permanent line: the package has to stay assembled, immutable and readable for years after the money arrived and was spent.
One public fact anchors the return side. In the United States drawback returns up to 99 per cent of duty paid, which makes the business case unusually clean compared with most software spending.
What does the hybrid look like, and when is it the honest answer?
The hybrid is the most under used answer in this category, and it has two shapes.
The first is build the evidence layer, keep the filer. Your contingency specialist continues to file, and you build only the part that finds and evidences what they currently leave alone. Their economics work on flows that are easy to evidence, which is exactly why manufacturing substitution and exports shipped under a logistics provider's name go untouched. Feeding them a clean, evidenced claim on those flows is worth more to both sides than replacing them, and you can negotiate the share on work you prepared.
The second is build the reconciliation layer, keep the platform. If you run ONESOURCE Global Trade or Descartes, let it file and manage classification. Build upstream of it: line level ingestion from your brokers, export evidence reconciliation against your own identifiers, and the allocation convention. That is where the project actually is, and it makes the platform work rather than replacing it.
Both shapes share a virtue. They let you prove the chain on one product family and one claim type before committing to a full platform. The recovery from a single family usually funds the rest of the build, which is a far easier internal conversation than a capital request against a hypothetical.
What should almost never happen is building a filing engine from scratch when a platform you already own files perfectly well. That is rebuilding the easy half.
Which should you choose, by operator size and stage?
Modest importer, simple flows, unused merchandise claims only: outsource on contingency. Do not build, do not buy a platform for this alone, and do not spend another hour reading about it.
Mid sized importer already running a trade platform: switch drawback on and put your effort into data mapping. If claims still come out small after that, the problem is your export evidence, and that is a data project rather than a software purchase.
Manufacturer with seven figure recoverable duty and real yields: build, but scope it to one product family and one claim type first. Price discovery separately at $12,000 to $20,000, and make its output the opportunity figure rather than a specification. That number is the business case.
Manufacturer without plant records at claim granularity: stop and find out before committing. Whether production records were retained at the granularity a manufacturing claim needs is a binary discovery finding that changes the whole project, and no developer can work around a record that was never kept.
Specialist filer running claims for multiple clients: build, and build multi client separation into the architecture from the start rather than bolting it on. Your margin is absorbing messy client data faster than competitors, which is a software problem by definition.
Anyone with a statutory window closing on aged flows: run the opportunity analysis now, whatever you decide afterwards. Value that expires while the decision is pending is the only truly unrecoverable cost on this page.
If you want that decision made properly rather than quickly, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 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) →
- 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) →
- Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
- Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
Frequently asked questions
What does it cost to leave a contingency drawback filer if we build?
The switching cost is mostly knowledge rather than data. Your import and export records are yours, but the matching conventions, the reasoning behind past claims and the working relationship with the filer are not written down anywhere you control.
Ask for the historical claim packages and the allocation conventions applied, in writing, before you give notice. If those are not obtainable, plan a period of parallel running rather than a clean handover, and expect your first self filed claim to take longer than the filer's did.
What if our contingency share or platform licence gets repriced?
A contingency share is a percentage of recovery, so it rises with your success rather than with a vendor decision. The repricing risk that matters is on packaged trade platforms, where module and user pricing scales with your footprint.
Owning the evidence layer changes the negotiation either way. When line level data, export reconciliation and the allocation convention sit in your own system, a filer or a platform becomes a supplier you can replace rather than the only party who understands your claims.
How long before a build produces a filed claim?
Twelve to eighteen weeks to a first release, milestoned on a filed claim rather than on screens, in our delivery experience. The only acceptable definition of done is a claim that went out through your normal route with a complete evidence package behind it.
Manufacturing drawback is a separate phase of 12 to 20 weeks at $70,000 to $160,000, and it depends entirely on what discovery found about plant record granularity. Do not schedule it before that answer exists.
Is ONESOURCE Global Trade enough instead of building?
If your data is already clean and mapped, yes, and you should switch the module on rather than commission anything. It files competently and it is maintained against rule changes you would otherwise track yourself.
The honest caveat is that most drawback projects are upstream of it. It expects mapped data about imports, exports and consumption, and reconstructing your export evidence against your own part numbering is the work regardless of which system eventually files.
Why does manufacturing drawback cost so much more than unused merchandise?
Because it is a modelling problem rather than a matching problem. The exported article contains a proportion of the imported input determined by your bill of materials and your actual yield, and that proportion is the basis of the claim.
Yield has to be modelled per product family, waste has to be treated defensibly, and the whole calculation has to be reproducible from retained records rather than from a percentage applied to a total. That typically adds 50 to 80 per cent to the matching engine.
Can we start with one product family instead of the whole business?
Yes, and it is the approach we recommend. Pick one product family and one claim type and prove the whole chain from import line to filed claim with a complete evidence package.
The recovery from that single family usually funds the rest of the build, which turns a capital request into a self funding programme. It also surfaces the data problems early, on a scope small enough that fixing them is cheap rather than a schedule event.
How do we handle exports shipped under a logistics provider's name?
Treat identifier mapping as a first class part of the build rather than an import step. Shipments made under a third party consignor name are the single most common source of missed eligible exports, because they never appear in the export file anyone is working from.
A developer who has done this will raise identifier mapping unprompted. One who has not will assume the export file is complete, and that assumption quietly caps your recovery at whatever the file happens to contain.
Who owns the claim evidence if an agency builds this?
You should hold the repository, the cloud accounts and the right to hire any other firm, settled before kickoff. At Digital Heroes the client owns the code from the first commit.
It matters more here than in most categories because the system holds evidence behind claims a customs authority may review years after payment. Evidence stored in a supplier's tenancy, on a supplier's retention policy, is a liability rather than an asset.
What does it cost to maintain custom supply chain software each year?
Budget 15 to 20 percent of the original build cost per year, so roughly $9,000 to $12,000 annually on a $60,000 system, covering hosting management, dependency updates, bug fixes, and small enhancements. Across its maintenance contracts, Digital Heroes sees supply chain systems need more upkeep than typical web apps because carrier APIs, EDI specs, and ERP versions keep changing underneath them. Hosting itself is usually minor, often $100 to $500 per month for a mid-size operation.
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 should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
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.
How long does it take to build custom supply chain software?
Plan on 10 to 14 weeks for a first production release covering one or two core workflows, and 6 to 9 months for a full platform spanning procurement, inventory, and fulfillment. Digital Heroes ships most supply chain MVPs in about 12 weeks with a 4 to 6 person team. Integrations are the schedule risk: each ERP, EDI, or carrier connection typically adds 2 to 4 weeks of build and testing.
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.
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.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
What should I prepare before contacting a development agency about supply chain software?
Bring a written list of your workflows from purchase order to delivery, the systems each step touches, and the 3 to 5 pain points costing you the most hours or errors. Export a sample of your real data, SKUs, orders, and locations, because data shape drives half the design decisions. You do not need a formal spec; Digital Heroes scopes most supply chain projects from a two-page problem description plus screen-share walkthroughs of the current process.
Who owns the code when an agency builds my supply chain software?
You should own it outright, with full IP assignment on payment written into the contract, and you should walk away from any agency that only licenses the software to you. Insist on the code living in a repository under your own GitHub or GitLab account from day one, not handed over at the end. Digital Heroes contracts assign all custom code, database schemas, and documentation to the client; the only carve-outs should be clearly listed open source libraries.
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.
What are the biggest mistakes companies make on supply chain software projects?
The top three: replacing every system at once instead of one workflow at a time, skipping data cleanup so the new system inherits years of bad SKUs and phantom stock, and designing screens without the warehouse staff who will use them daily. A fourth is underscoping integrations and discovering mid-project that the ERP connection is half the work. Digital Heroes sees more supply chain projects fail from scope and data problems than from any technical cause.
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 .
