How Much Does Duty Free and Travel Retail Software Cost in 2026?
$110,000 to $750,000, and the decision that moves the number most is whether you build a till or a regulated layer around the till you already run.
On this page
$110,000 to $750,000, and the decision that moves the number most is whether you build a till or a regulated layer around the till you already run. Keeping Oracle Retail Xstore or Cegid Retail for transactions, promotions and store operations, and building eligibility, bonded stock accounting and concession reporting as your own system alongside it, keeps a first release inside the lower band. Rebuilding the point of sale (POS) as well means taking on payment certification, hardware drivers and cash office reconciliation, which is a materially larger programme and rarely the reason you started looking.
The bands a travel retail build falls into
In our delivery experience a focused first release runs $110,000 to $240,000 and ships in 16 to 24 weeks. That covers boarding pass validation, an eligibility engine holding dated rules by origin and destination, and a bonded stock ledger that reconciles to your customs record. A full platform runs $280,000 to $750,000, phased over 10 to 18 months, adding multi currency tender and cash office, concession fee calculation and declaration, transfers between bonded and duty paid stock, pre order and collection, and loyalty across a travel estate.
The reason this category starts higher than most retail work is that two of its three core objects are legal rather than commercial. Bonded stock is inventory the state has a claim on until a taxable event occurs, so every movement needs a treatment and an immutable record. Eligibility is a decision made in four seconds at a counter that has to be defensible months later in an audit. Neither can be approximated, and both have to be right on day one rather than improved in a later release.
Under $110,000 you are buying a boarding pass scanner bolted to a report. That is worth having and it does not reconcile anything, which means the workbook stays and so does the exposure.
What drives a travel retail build up
The number of jurisdictions is the single largest multiplier. Each one brings its own customs regime, its own declaration format and its own allowance structure, and the second country is close to a second project rather than an increment. If you operate across a land border, a cruise terminal and an airport, treat those as three regimes until proven otherwise.
Whether you build a till or a layer is the second, and it is the decision described above. Taking on the point of sale means payment terminal certification, receipt printers, cash drawers and shift reconciliation, all of which are solved problems you would be re solving.
Offline tolerance is the third, and it is not optional in a terminal. A till that stops trading when the network drops during a departure bank is a till that gets bypassed, and bypassed tills are how bonded stock goes missing. Offline eligibility decisioning with deterministic reconciliation on reconnect is an architecture decision taken at the start, and retrofitting it later is close to a rewrite.
Hardware is the fourth. Scanners that read a phone screen at six in the morning under poor lighting, sealed tamper evident bag printers and label printers each carry integration and testing time that proposals routinely omit.
What keeps the number down
One location and one jurisdiction first. Get the eligibility engine and the bonded ledger correct for a single regime, then treat the second regime as a deliberate second phase with its own budget. Operators who scope three jurisdictions into release one spend the first quarter in rule workshops instead of in code.
Run the new bonded ledger in parallel with the existing workbook for two full declaration periods before it becomes the source of truth. That is not a cost, it is the cheapest insurance available in this category, and it converts go live from a leap into a comparison.
Keep the enterprise point of sale. It handles promotions, transaction structure and store operations well, and the integration between it and your regulated layer is a fraction of what replacing it costs.
Treat rules as data from the start. Allowances and eligibility change on a political timetable rather than a software one, so head office editing dated rule records is the design that keeps your change costs near zero for the life of the system. Hard coding them is how a two week regulatory notice becomes a release queue problem.
A worked example that adds up
An operator with three stores in one airport, one customs jurisdiction, an existing enterprise point of sale that stays in place, and a bonded stock position currently reconciled in a workbook by one person.
- Eligibility engine: boarding pass parsing against the IATA barcode standard, connecting itinerary handling, dated rules per origin and destination pair, and a decision per line item with a reason a supervisor can read: $46,000
- Bonded stock ledger: duty status as an attribute of the unit, append only movement records covering receipt into bond, inter location transfer, eligible sale, removal to duty paid, breakage, sample and destruction, with corrections as reversing entries: $54,000
- Reconciliation reporting comparing system position to declared position, with variances itemised by movement type: $22,000
- Integration with the existing point of sale at transaction and line level, plus the warehouse receiving feed: $32,000
- Offline eligibility decisioning at the till with deterministic reconciliation on reconnect: $28,000
That totals $182,000 and ships in about twenty weeks. Phase two, adding multi currency tender with cash office reconciliation, concession fee calculation and declaration, bonded to duty paid transfers and pre order collection, adds roughly $180,000 to $350,000 and brings the programme toward $400,000 across twelve to eighteen months.
How the spend phases
Four to six weeks of discovery, and most of it is not software work. It is confirming current allowance and eligibility rules with your customs advisers, agreeing the declaration format, and documenting the movement types your bonded position actually uses. Operators who arrive with those confirmed shorten the whole project.
The build runs 16 to 24 weeks. Put a working eligibility decision in front of cashiers early, because the plain instruction they see on screen is the difference between a rule engine that gets used and one that gets overridden.
Then two full declaration periods running in parallel before cutover. That is the schedule item most often compressed and the one that should not be, because the bonded ledger only proves itself against a declaration you have already made by the old method.
Phase two follows, and concession fee calculation is usually the highest value next module because it converts a hand assembled declaration into a query with a trail down to transaction level, on a figure your landlord has audit rights over.
The ongoing costs nobody quotes
Recurring costs in travel retail are heavier than in general retail because the compliance surface never stops moving.
- Rule maintenance. Somebody in head office owns the dated rule records and updates them when a jurisdiction changes an allowance. If the design is right this is administrative time rather than development cost, which is the whole argument for treating rules as data.
- Support and change budget. Plan 15 to 25 per cent of build value per year, so roughly $27,000 to $46,000 on a $182,000 release.
- Hardware refresh. Scanners, sealed bag printers and label printers in a terminal environment wear out on a predictable cycle.
- Point of sale integration maintenance. Each platform upgrade on the retail side needs the integration verified before a peak travel period rather than during one.
- Audit support. Customs reviews and landlord audits take internal time even when the system answers them quickly. Faster is cheaper, not free.
Comparing a build against your current renewal
Build the comparison from four figures in your own accounts. First, what you pay your retail platform partner for extensions and change requests each year, separately from the base licence, because in this category the extensions are the expensive part. Second, the fully loaded cost of the people maintaining the bonded workbook and assembling the concession declaration. Third, any customs discrepancy you have settled or provided for in the last three years. Fourth, concession fee error in either direction, which you can test by recalculating one past period from transaction data and comparing it with what you declared.
Set that against $182,000 plus 15 to 25 per cent per year, remembering that your retail platform licence continues because you are keeping it.
The fourth figure is the one operators most often have never measured, and it is frequently the one that decides the case. Over declaring quietly inflates rent for years without anyone noticing. Under declaring turns into a commercial dispute with the landlord who controls your presence in the terminal. Both are avoidable with a fee calculation that traces to transaction level, and neither is visible from a spreadsheet.
When buying beats building
If you run one small border or ferry shop with a narrow product range and simple eligibility, extend a packaged till and keep a disciplined workbook. The compliance surface is small enough that proportionate manual control is the correct answer, and a six figure build against it is not defensible.
If you are opening in a jurisdiction where a local retail platform is already widely used and supported, buy it and extend. Oracle Retail Xstore is a mature enterprise point of sale with real depth in transaction handling and store operations, and Cegid Retail is similarly capable with strong international localisation. Neither is a bad choice, and both belong in a travel retail estate. The questions to ask a platform partner are practical rather than adversarial: how quickly can an extension change when a destination rule shifts with two weeks of notice, who is permitted to change it, and what a platform upgrade does to your customisations.
Build the regulated layer when any of these are true. You operate in more than one jurisdiction, so no single configuration covers your rules. You have had a customs discrepancy you could not explain from system records. Your concession declaration is assembled by hand and your landlord has audit rights. You hold bonded and duty paid stock of the same product in the same store. Or your allowance rules change faster than your platform partner can deliver a change, which for many operators is the deciding fact rather than any feature gap.
When you are ready to turn this into a specification, 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.
- U.S. retailers lost an average of 1.6% of sales to shrink in FY2022 (up from 1.4% the prior year), equating to $112.1 billion in inventory losses - the benchmark case for POS-integrated loss prevention and inventory accuracy. Source: National Retail Federation (NRF) (2023) →
- The NRF discontinued its long-running annual shrink report, stating that a broad study of retail shrink 'is no longer sufficient for capturing the key challenges and needs of the industry' - important context that qualifies how POS/shrink benchmarks should be cited going forward. Source: Retail Dive (2024) →
- 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) →
- The Standish Group 1995 CHAOS Report found only 16.2% of software projects fully succeeded; success varied sharply by size, with large-company projects succeeding about 9% of the time versus far higher rates for small projects - best treated as an industry survey, not an audited dataset. Source: Standish Group (1995) →
Frequently asked questions
How much does duty free and travel retail software cost in total?
A focused first release covering boarding pass validation, destination eligibility rules and a bonded stock ledger with customs reconciliation runs $110,000 to $240,000 over 16 to 24 weeks in our delivery experience.
A full platform adding multi currency tender and cash office, concession fee reporting, bonded to duty paid transfers and pre order collection runs $280,000 to $750,000 over 10 to 18 months. An operator keeping an existing enterprise till and building only the regulated layer typically lands near $182,000 for release one.
What does it cost to run each year?
Plan 15 to 25 per cent of build value annually, so roughly $27,000 to $46,000 on a $182,000 release. That covers hosting, support, verification of the point of sale integration through each platform upgrade, and a change budget.
Add hardware refresh for scanners and sealed bag printers, and internal time for customs reviews and landlord audits. If your retail platform stays in place, its licence continues alongside and should appear in the business case.
How long does implementation take?
Four to six weeks of discovery, then 16 to 24 weeks to a working release covering one location and one jurisdiction properly rather than several shallowly. Then two full declaration periods running the new bonded ledger in parallel with the existing workbook before cutover.
The schedule risk is rarely the software. It is confirming current allowance and eligibility rules with customs advisers and agreeing the declaration format, which depends on people outside the project team.
Is it cheaper to extend Oracle Retail Xstore than to build?
For a single small shop with simple eligibility, almost certainly. Both Oracle Retail Xstore and Cegid Retail are mature platforms with real depth in transaction handling and store operations, and extending one is proportionate at that scale.
Compare the annual spend on extensions and change requests, separately from the base licence, against a build plus its change budget. The deciding question is usually speed rather than price: how fast an extension can change when a destination rule shifts on two weeks of notice, and who is permitted to change it.
Why does adding a second country nearly double the cost?
Because each jurisdiction brings its own customs regime, declaration format and allowance structure, and those are not parameters on a shared model. The bonded movement types differ, the reporting shape differs, and the eligibility logic for a passenger connecting between the two is its own case.
The cost control is sequencing. Get one regime correct, then treat the second as a phase with its own budget and its own advisers, rather than scoping three regimes into release one and spending a quarter in rule workshops.
What does offline capability add to the price?
On a build of this size, roughly $25,000 to $35,000, covering offline eligibility decisioning, local transaction capture and deterministic reconciliation on reconnect.
It is not an optional line in a terminal. Tills that stop trading during a departure bank get bypassed, and bypassed tills are how bonded stock goes missing. Designed in at the start it is a defined cost. Retrofitted into a system that assumed connectivity it is close to a rewrite.
How much does concession fee reporting cost to build?
Typically $35,000 to $70,000, covering category mapping as dated maintained data, fee calculation as an explicit period object, and a declaration generated from that object with a trail down to transaction level.
Test the payback before you commission it: recalculate one past period from your transaction data and compare it with what you declared. Operators frequently find error in one direction or the other, and the landlord has audit rights over the figure either way.
Can we keep our current point of sale and build only the compliance layer?
Yes, and for most operators it is the right answer. Keeping the enterprise till for retail operations and building eligibility, bonded accounting and concession reporting alongside it avoids re solving payment certification, hardware drivers and cash office reconciliation.
It also keeps the fastest changing part of the operation under your own control, which is the point. The trade is that the platform licence continues, and the integration between the two systems becomes a line you maintain.
What pushes a travel retail project over budget?
Four things. Scoping several jurisdictions into release one. Deciding mid project to replace the point of sale after quoting only the regulated layer. Treating offline behaviour as a later feature. And discovering during the parallel period that the movement types in the existing workbook do not match what the declaration actually requires, which is a discovery problem surfacing late.
Cruise and land border operations add a fifth, because connectivity is worse and rules can change by port.
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.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
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.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
How much does it cost to build a custom POS system for a small business?
A single-location custom POS covering checkout, inventory, receipts, and payment integration typically lands between $30,000 and $70,000, based on Digital Heroes delivery data across 2,000+ projects. Multi-location systems with kitchen displays, franchise reporting, or offline sync usually run $80,000 to $250,000. The biggest cost drivers are custom hardware support and how much of the payment flow you build versus integrate.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
We run multiple restaurant locations on Toast. Would switching to a custom POS actually save money?
Usually only at 8 or more locations, where per-terminal software fees, add-on modules like online ordering and loyalty, and processing markup commonly total $8,000 to $20,000 per location per year in the statements Digital Heroes reviews for restaurant groups. A custom system converts that into a one-time build of $100,000 to $250,000 plus maintenance, which models out to 18 to 30 month payback for most groups. Under five locations, stay on Toast and put the money into operations.
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.
How do I vet a development agency for a POS project specifically?
Ask to see a live POS or payments product they built, then ask exactly how they handled offline mode, receipt printing, and PCI scope, because those three areas expose anyone who has only built ordinary web apps. A competent agency will name the payment SDKs they used, such as Stripe Terminal or Adyen, and describe their terminal certification process without checking notes. If the portfolio is all marketing sites and dashboards, keep looking.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
How many developers does it take to build a POS system?
A typical Digital Heroes POS team is 4 to 6 people: one backend developer, one or two client developers for the register app, a designer through the first half, a QA engineer, and a project lead. That size delivers a single-location system in about 3 to 4 months. Be skeptical of anyone pitching a one-developer POS build, because payments, offline sync, and hardware testing each demand dedicated attention.
Who can build a custom POS software system?
Digital Heroes builds custom POS 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 POS 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 .
