How to Hire a Duty Drawback Software Development Company
Shortlist three firms that have defended a drawback claim, not merely filed one. Give each the same brief and judge them on how they handle fungible inventory allocation, broker entry data at line level, and evidence retention.
On this page
Shortlist three firms that have defended a drawback claim, not merely filed one. Give each the same brief and judge them on how they handle fungible inventory allocation, broker entry data at line level, and evidence retention. Expect $150,000 to $300,000 for a core matching and claim file platform. Buy a paid discovery phase first so the written specification belongs to you.
Commissioning duty drawback software is closer to hiring a forensic accountant than a software shop. Nobody is asking for a new process. They are asking someone to reconstruct one that already happened, across import entries filed by a broker, exports booked by a forwarder, and consumption recorded by a plant that stopped tracking material origin the moment goods crossed the receiving dock.
That is what makes the category hard to buy. The deliverable is not a screen. It is an evidence package that has to hold when a customs officer reviews a claim years after the refund was paid and spent. You cannot judge that in a demo, because a demo shows a claim being filed and the risk lives in the claim being defended. Every vendor will show you the filing. Very few will show you the file.
What a duty drawback software development company actually does
The visible build is a claim workspace: pick the entries, pick the exports, produce a number. That is perhaps a fifth of the engagement.
The rest is the work nobody demos. Normalising import entry data from every broker who files for you, at line level rather than entry level, with duty, classification, quantity and value preserved per line. Mapping your part numbers, plant codes and customer references onto the identifiers customs uses, which is most of the effort and never quite finishes. Designing an allocation convention for fungible inventory and writing it into the system rather than into a senior analyst's memory. Modelling actual manufacturing yield and waste treatment so a substitution claim can be substantiated per unit instead of as a percentage applied to a total. Building a claim file assembler that stores the calculation, the supporting lines, the documents and the version of the rules applied, immutably, for the full retention period. And building the opportunity analysis that shows finance what looks claimable but is currently unevidenced, which is usually what gets the project funded.
What it really costs in 2026
| Project tier | Cost | Timeline |
|---|---|---|
| Unused merchandise claims, one broker feed, one claim type end to end | $70,000 to $140,000 | 10 to 16 weeks |
| Core platform: import line ingestion, export evidence capture, matching engine, claim file assembler | $150,000 to $300,000 | 5 to 8 months |
| Manufacturing drawback with bill of materials and yield modelling, allocation engine, opportunity analysis, multi client separation | $320,000 to $600,000 | 9 to 14 months |
| Maintenance, rule changes and support | 18 to 22% of build per year | Retainer |
Two line items go missing from almost every quote in this category.
The first is historical data remediation. Claims reach backwards, so the data you need most is the oldest and the messiest: a broker who changed file layout, a product family reclassified two years ago that nobody restated, a period where eligible exports moved through a third party logistics provider under its own consignor name. Assume weeks of that work and price it in the contract rather than discovering it in week five.
The second is a parallel run. You should not cut over to a system that files money claims until it has produced the same or a better result than the people it replaces, across at least two claim cycles. Vendors omit it because it reads like padding. It is the cheapest insurance in the project.
Signals of a strong partner
- They raise fungible inventory before they raise screens. An allocation convention is a customs decision with a software consequence, and anyone who has defended a claim asks about it in the first hour.
- They want entry data at line level. Aggregating to the entry at intake is the one irreversible mistake here, because the claim needs the line and you cannot recover it afterwards.
- They treat classification as dated data. Substitution eligibility turns on classification, so a family reclassified two years ago has to be carried as history rather than corrected in place.
- They ask which brokers file for you, by name. Each one is a separate format, a separate relationship and a separate failure mode when a layout changes without notice.
- They separate matching from transmission. Building the evidence layer while continuing to file through established channels is the sensible architecture. A partner who offers to replace your filing route is selling scope.
- They can describe the claim package three years out. The right answer covers the calculation, the supporting lines, the documents and the rule version applied, stored so it cannot be edited.
- They plan the parallel run themselves. Two claim cycles alongside your current process before the system becomes the source of truth.
Red flags
- The demo opens on the filing screen. Filing is the straightforward part. If nobody shows you an evidence package, nobody has built one that survived a review.
- They say the export file, singular. Exports arrive from several systems and some eligible shipments moved under a logistics provider's own consignor name. A partner who assumes one clean file will under claim and never notice.
- Manufacturing drawback priced at the same rate as unused merchandise. Yield modelling, waste treatment and per unit substantiation are materially harder, so a flat rate means one of the two numbers is wrong.
- No retention story. Ask where the evidence lives in year five and who can read it. The application database plus a backup policy is not an archive.
- They want to host it and file on your behalf under their own licence. That is a filer relationship dressed as a build, and it puts your evidence inside someone else's tenancy.
Questions to ask on the first call
- Our inventory is fungible. What allocation convention would you propose, and where does it live in the system so a reviewer can see it?
- Which broker entry data formats have you parsed, and what happens the month one of them changes layout without telling us?
- How do you carry classification at line level, and what happens to a claim spanning a historical reclassification?
- Walk me through the claim package a customs reviewer sees three years after payment.
- How would you reconcile exports shipped by a third party logistics provider under its own consignor name?
- For manufacturing claims, do you model theoretical yield or actual production records, and how do you treat waste?
- How does the system refuse to generate a claim it cannot evidence?
- If we file for several clients, how is client data isolated and how are per client conventions stored?
- Who owns the repository, the cloud accounts and the evidence archive from day one?
A simple way to decide
Do not choose between three proposals written from three different readings of your business. Buy a paid discovery phase from your leading candidate, two to four weeks, at a price you would not mind losing. The output is a written specification you own outright: the source systems and their formats, the allocation convention with its reasoning, the claim types you will support, the evidence package definition and its retention period, and an opportunity analysis ranking what appears claimable but unevidenced by value and by how close the window is to closing.
That document does two useful things. It makes the remaining quotes comparable, because every firm is finally pricing the same build. And if it convinces you that a specialist filer on contingency is the better answer, you spent a small sum to avoid a large one. Digital Heroes works specification first for that reason, contracts through an India LLP, a US LLC or a UK LTD so the IP assigns under your own law, and can be checked against D-U-N-S, Clutch and Trustpilot before you commit to anything.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 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) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- Only 16% of respondents said their organizations' digital transformations had successfully improved performance and equipped them to sustain gains over the long term; even in digitally savvy industries such as high tech, media, and telecom, self-reported success rates did not exceed 26%. Source: McKinsey & Company (2018) →
Frequently asked questions
How much does it cost to hire a duty drawback software development company?
A single claim type running end to end from one broker feed costs $70,000 to $140,000 over 10 to 16 weeks. A core platform with line level import ingestion, export evidence capture, a matching engine and a claim file assembler runs $150,000 to $300,000. Manufacturing drawback with yield modelling and multi client separation reaches $320,000 to $600,000. Budget 18 to 22 percent of the build each year for maintenance.
What is the one thing to verify before signing with a drawback developer?
That they have built a claim which survived a post payment review, not just one that was accepted at filing. Ask them to describe the evidence package a customs officer opens three years later. A partner who answers with the calculation, the supporting import and export lines, the documents and the rule version applied has done this. One who talks about the filing screen has not.
Should we hire a developer or use a specialist filer on contingency?
Use a filer if your recoverable duty is modest, your flows are simple and you file a handful of unused merchandise claims a year. Contingency puts no capital at risk. Hire a developer when the constraint is evidence rather than filing: matching depends on your own part numbering and manufacturing yields, claims keep getting scoped down to what is easy to prove, or you file for multiple clients yourself.
Why do quotes for drawback software move so much after kickoff?
Because two costs are usually left out. Historical data remediation is the first, since claims reach back years and the oldest broker files, reclassified product families and exports shipped under a logistics provider's consignor name all need untangling. The second is a parallel run across two claim cycles before the system becomes the source of truth. Put both in the contract and the quote stops moving.
Who owns the code and the claim evidence if an agency builds this?
You should own the repository, the cloud infrastructure accounts and the evidence archive from the first commit, written into the contract before kickoff. This matters more here than in most categories because the archive holds the substantiation behind claims a customs authority may examine long after payment. That evidence has to stay readable and explainable regardless of whether you are still working with the firm that built it.
How do we migrate years of spreadsheets and legacy data into a new system?
Migration runs as its own workstream: extract and profile the data, clean duplicates and dead SKUs, map fields to the new schema, then do trial loads and a final cutover during a weekend or slow period. Expect 2 to 6 weeks depending on how many sources you have and how dirty they are. Digital Heroes runs old and new systems in parallel for 2 to 4 weeks on most supply chain cutovers so inventory counts and open orders can be reconciled before the legacy system is retired.
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.
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.
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.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
How 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.
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 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.
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.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
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.
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 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 .
