Fishbowl thinks your stock lives in one country, but a Belfast warehouse feeds two customs regimes at once

Most builds run £30,000 to £80,000. Core inventory with dual-currency valuation sits at the lower end, while adding cross-border customs documentation and full ERP and warehouse integration reaches higher. The border logic is the main cost driver and the main reason to build.

They track quantity and location well but do not natively hold the commodity codes, origin data and destination logic that decide how a unit must be documented when it ships to GB versus the EU. That intelligence ends up in spreadsheets, which is exactly the gap custom software closes.

Each item carries the data needed to document either path, so when stock dispatches the system generates the correct customs and VAT paperwork for a Great Britain or an EU destination automatically. Your team stops reconciling stock against border reality by hand.

Between three and six months depending on scope. Core inventory with dual-currency valuation is quickest, while cross-border customs documentation and full integration take longer. Many Belfast firms ship the core first, then add customs automation.

Yes. Dual-currency valuation means stock destined for the Republic of Ireland reflects true euro value while GB stock stays in sterling, so your margin and reporting are accurate rather than distorted by a single base currency.

Yes. A custom inventory system shares one source of truth with your ERP, accounting software and warehouse management system, so stock, finance and dispatch stay aligned rather than each holding a slightly different version.

Yes. Batch and serial traceability follows components through inbound, work-in-progress and dispatch, which matters for Belfast's aerospace and advanced manufacturing firms where part history and recall traceability are non-negotiable.

You own the code and data, with no per-location licence tax as your Belfast operation grows. Any competent developer can maintain it, and you control where your stock and customs data live.

Budget a monthly retainer to keep customs and VAT rules current and apply updates. Because cross-border rules can change, that stewardship is the value of owning border logic rather than depending on a vendor to prioritise Northern Ireland trade.

A deliberately boring one: PostgreSQL for the stock ledger, a mainstream backend such as Node.js, Python, or .NET, a web dashboard, and a mobile app or mobile web interface for scanning. The data model matters far more than the language; an append-only movement log with atomic stock updates prevents overselling in any stack. Reject anything exotic that only the original developer can maintain.

A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.

Most of the build can run remotely, but if you operate a physical warehouse in Belfast, plan at least one on-site visit, because watching a real pick-and-pack surfaces workflow details no video call catches. A hybrid model, local discovery with a remote build team, usually gives the best cost-to-quality ratio. Inventory-specific track record matters far more than where the agency sits.

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.

Start with a minimum viable product covering the single most painful workflow, usually receiving, movements, and scanning for one location, then extend in phases. In Digital Heroes delivery experience, phased builds put a working system on the warehouse floor in 8 to 12 weeks and let real feedback shape phase two, while big-bang builds routinely ship features nobody uses. Phasing also spreads the budget across quarters instead of demanding it all up front.

You should, in full, with intellectual property assignment written into the contract before any payment is made. Insist on the code transferring to a repository you control no later than final payment, plus hosting and domain accounts in your own name. If an agency offers to license you their platform instead of assigning the code, you are buying another Cin7 with fewer features.

In quotes Digital Heroes reviews alongside clients, local agencies in Belfast typically bill $100 to $200 per hour, while hybrid teams pairing local project leadership with remote engineering land around $40 to $75 per hour. On a 600-hour inventory build, that rate gap separates a roughly $30,000 project from a $90,000 one for comparable output. Compare vendors on shipped inventory systems first and rate second.

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.

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.

Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.

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.

Digital Heroes builds custom inventory management software systems for operators who have outgrown the off-the-shelf tools in their category. The work is delivered remotely: our engineers work from Delhi and Lucknow, leadership is in New York, and some team members live in London and Sydney and work remotely from there. We have no office in Belfast. You can chat with the team directly, and every form gets an email reply within 24 hours.