Skip to content
§
§ · hiring guide

How to Hire a Merchandise Allocation and Replenishment Software Development Company

Ask one question before anything else: how would you estimate a size curve for a store with thin history and known stock outs? If the answer is average the last two seasons, they will encode your existing errors and call it a system.

Supply Chain Software workflow illustration for Merchandise Allocation Replenishment Software.
The short answer

Ask one question before anything else: how would you estimate a size curve for a store with thin history and known stock outs? If the answer is average the last two seasons, they will encode your existing errors and call it a system. A focused first release runs $80,000 to $180,000 in 14 to 20 weeks. A full platform runs $220,000 to $550,000 over 8 to 14 months.

Hiring a firm to build allocation software is like hiring the person who decides which containers go on which ship. Nothing looks wrong on the day. You see the consequence six weeks later in a sell through report, and by then the only correction available is markdown. A 12,000 unit buy that went to the wrong doors gets recorded in the season review as a buying error, and the buy was probably fine.

What makes this category hard to buy is that the difficult part is statistical and statistics do not demo. Any competent development firm can build a screen that splits units across 340 stores and looks convincing doing it. Very few can estimate a store level size curve that borrows strength from similar stores and corrects for demand lost during stock outs, or solve pack rounding as a constrained optimisation across the whole estate rather than store by store. Both builds produce an allocation. Only one of them stops stranding extra large in the four stores that were never going to sell it.

What an allocation software development company actually does

The user interface is the smallest part of the work, and the part buyers spend the most time evaluating.

The core is estimation. Size demand varies by store for reasons that persist, and raw history lies, because a store that has not held extra large for two years has taught those customers to shop elsewhere. So the firm builds curves per store and category with strength borrowed across similar stores where a single store's data is thin, and corrects for lost sales during out of stock periods rather than reading a stock out as an absence of demand. Curves must be reviewable, with an allocator able to see why a store differs and override with a recorded reason.

Next is the rounding. You cannot ship 3.7 units, and vendor prepacks arrive in fixed ratios. The correct framing is minimising deviation from each store's target size profile subject to pack integrity and available inventory, across the estate at once. The naive approach of allocating ideal units and rounding store by store accumulates error and typically leaves stock unallocated or over ships the flagships.

Then the rules and the loop: presentation minimums by store grade and fixture with an explicit policy for what happens when the buy cannot fund them everywhere, replenishment with target stock from forecast, lead time and a chosen service level, fair share rationing with a floor when the distribution centre cannot cover total need, exception based review so allocators judge sixty decisions instead of building 340 rows, and integration into purchase orders and warehouse wave picking so the answer becomes work rather than a spreadsheet.

What it really costs in 2026

ScopeCostTimeline
Data assessment and a size curve prototype run against your own history$20,000 to $45,0003 to 5 weeks
First release: store level size curves, pack aware optimisation, minimums, exception review$80,000 to $180,00014 to 20 weeks
Full platform: replenishment and forecasting, fair share, transfers, purchase orders, warehouse waves$220,000 to $550,0008 to 14 months
Support, model retraining and seasonal changes15 to 20 percent of build per yearOngoing

Two costs sit outside almost every proposal.

The first is history remediation. Everything here depends on size level sales history with reliable out of stock flags at store and size, and a great many retailers discover theirs does not exist, or that a hierarchy restatement two years ago was never reconciled. Without stock out flags there is no lost sales correction, and without lost sales correction the curves reproduce the errors that caused the stranding. Fixing that is weeks with your own data team and it will not appear in a software quote unless you ask for it.

The second is warehouse execution. Quotes tend to stop at produces an allocation, after which the distribution centre interprets a file and reintroduces exactly the manual step you paid to remove. Wave picking, carton building and store fulfilment integration is real engineering and belongs in scope rather than in a later phase.

Signals of a strong partner

  • They ask for a sample of your history in the first week. Size level, with stock out flags, because they intend to test whether the data supports what they are proposing.
  • They mention borrowing strength across similar stores. Unprompted, when you ask about thin store history. This is the single clearest competence signal in the category.
  • They frame pack rounding as optimisation. Across the estate, subject to pack integrity, rather than as rounding applied per store.
  • They ask what happens when the buy cannot fund minimums everywhere. And they expect a different answer for fashion than for basics.
  • They describe fair share with a floor. Proportional to need, protecting presentation, rather than filling requests in list order until stock runs out.
  • They can describe an allocator's Monday after go live. With a number of exceptions attached. If they cannot, the team will keep exporting to Excel and you will have bought a report.
  • They insist models and training data live in your accounts. Models built on your own demand history are among the most valuable assets you own.

Red flags

  • Chain average size curves treated as adequate. A chain average is wrong in most stores by construction, and no amount of interface polish corrects it.
  • Stock outs used as demand data. If nothing in the method distinguishes did not sell from was not there, the system will confidently under allocate the sizes you keep running out of.
  • A demonstration built around a chat window. Allocators do not want to converse with a system. They want a size curve per store and a short list of exceptions.
  • Replenishment described as the same logic as allocation. Distributing a finite buy and maintaining a position against ongoing demand are different problems, and merging them starves the stores that sold well.
  • No plan for the warehouse. An allocation that ends in a spreadsheet has moved the error rather than removed it.

Questions to ask on the first call

  1. How would you estimate a size curve for a store with two years of history and long extra large stock outs?
  2. Show me how you decide which whole packs go to a store when the ideal answer is 3.7 units.
  3. Our buy cannot fund presentation minimums in every store. Where does that rule live and who changes it?
  4. How does fair share rationing work in the week a product is selling faster than we can ship?
  5. How many exceptions would an allocator review on a Monday, and what puts an item on that list?
  6. What do you need from our sales history, specifically, and what do you do if the stock out flags are missing?
  7. How does an allocator override a curve, and how is that override evaluated afterwards?
  8. How does the allocation become warehouse work, wave by wave, rather than a file somebody opens?
  9. Where do the trained models live, and what happens to them if we stop working with you?

A simple way to decide

Before you commit to a build, be honest about buying. In grocery and high frequency replenishment, RELEX Solutions does work that would take years to reproduce. If you already run Oracle Retail, native integration carries real value. The reliable tell that a packaged system has failed on fit is that your team still exports to Excel every week to finish the job.

If you are past that point, buy a paid discovery phase rather than choosing from proposals. Require a written specification from each candidate: the estimation method described in plain language, a curve prototype run on your own history, the optimisation formulation, the rule set for minimums and rationing, the data remediation plan with your team's hours, the warehouse integration design and a fixed price for release one. That document is yours to take anywhere.

Digital Heroes works this way as standard, with the requirements document first and the client owning the repository, the cloud accounts and the trained models from the first commit rather than at the end.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
  2. McKinsey estimates that digitizing the supply chain (Supply Chain 4.0) can cut lost sales by up to 75%, reduce inventories by up to 75%, and lower supply chain operational costs by up to 30%, with up to 30% lower transport and warehousing costs. Source: McKinsey & Company (2016) →
  3. 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) →
  4. Gartner estimates RPA can eliminate up to 25,000 hours of avoidable rework caused by human errors in the finance function each year, equating to savings of roughly $878,000 for an organization with 40 full-time accounting staff (based on interviews with more than 150 corporate controllers and chief accounting officers). Source: Gartner (2019) →
FAQ

Frequently asked questions

What does it cost to hire a developer for allocation and replenishment software?

A data assessment with a size curve prototype run against your own history runs $20,000 to $45,000 over three to five weeks. A first release with store level curves, pack aware optimisation, presentation minimums and exception review runs $80,000 to $180,000 in 14 to 20 weeks. A full platform adding replenishment, fair share rationing, transfers and warehouse integration runs $220,000 to $550,000.

What is the single best question to ask an allocation developer?

How would you estimate a size curve for a store with thin history and known stock outs. The right answer mentions borrowing strength from similar stores and correcting for lost sales during out of stock periods. Averaging the last two seasons of sales encodes the errors that stranded your inventory in the first place, because a size that was never in stock looks like a size nobody wanted.

Why does pack rounding need an optimisation rather than simple rounding?

Because vendor prepacks arrive in fixed ratios and rounding store by store accumulates error across the estate, typically leaving units unallocated at the end of a run or over shipping the largest stores. The correct framing minimises deviation from each store's target size profile subject to pack integrity and available inventory, solved across all stores at once rather than one at a time.

Should we buy RELEX or Oracle Retail Allocation instead of building?

Often yes. In grocery and high frequency replenishment, RELEX does forecasting and replenishment at a level that would take years to reproduce. Oracle Retail Allocation carries real value if you already run Oracle Retail. The honest limit on packaged allocation is fit around packs, sizes and your specific constraints, and the tell is simple: if your team still exports to Excel weekly, the fit failed.

Who should own the forecasting models trained on our sales data?

You should, along with the repository and the cloud accounts, agreed in writing before kickoff. Models trained on your own demand history are among the most valuable assets a retailer creates, and they carry information about your customers that no supplier should hold. Ask explicitly what happens to the models if the relationship ends, and refuse any answer that keeps them in a vendor account.

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.

Can we migrate years of data out of our current system into new custom software?

Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.

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.

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 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.

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.

Should I hire a freelancer or an agency to build supply chain software?

For anything past a single-user internal tool, use an agency or an established team, because supply chain systems need backend, frontend, integration, and QA skills that rarely live in one freelancer. A solo developer can build a $10,000 inventory tracker; a system that talks to your ERP, carriers, and warehouse scanners fails badly when its only author is unreachable during a shipping cutoff. In the proposals Digital Heroes sees clients compare, agencies cost 20 to 50 percent more but give you continuity, code review, and someone answerable when order data stops flowing.

How big a development team does a supply chain software project need?

A typical build runs with 4 to 6 people: a project lead or analyst, two or three developers, a QA engineer, and a part-time designer. Digital Heroes staffs most supply chain MVPs this way for 10 to 14 weeks, then drops to 1 or 2 people for maintenance after launch. Bigger is not better here; past 7 or 8 people on a single-product build, coordination overhead usually cancels the added speed.

When is SAP actually a better choice than building custom supply chain software?

Choose SAP when you need a full ERP, operate in a heavily audited industry that expects standard systems, or run global operations where localization, tax, and compliance content matter more than workflow fit. SAP's strength is breadth: finance, manufacturing, and supply chain in one validated suite. Custom wins when your edge lives in a specific workflow, like how you allocate inventory or route orders, that SAP would force you to bend to its standard process. Many Digital Heroes clients keep SAP as the system of record and build custom operational tools around it.

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.

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.

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.

Should we start with an MVP or build the full supply chain platform at once?

Start with an MVP that fixes your single most expensive workflow, prove it in daily operations, then expand module by module. That gets working software onto the warehouse floor in about 12 weeks instead of debating a year-long spec, and real usage always reorders the roadmap; features that felt critical in planning routinely get cut after go-live. Digital Heroes typically scopes phase one at 30 to 40 percent of the total vision and lets measured results justify each next phase.

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.

Keep reading

Published · Last updated .

Online now

Hi there. How can we help you today?

Reply