Build vs Buy: Merchandise Allocation and Replenishment Software
Buy first. If you run grocery replenishment or already sit on Oracle Retail, packaged allocation is hard to beat on price or depth. Build when vendor prepacks, store level size curves and fair share rationing push your allocators back into Excel every Monday.
On this page
Buy first. If you run grocery replenishment or already sit on Oracle Retail, packaged allocation is hard to beat on price or depth. Build when vendor prepacks, store level size curves and fair share rationing push your allocators back into Excel every Monday. A focused custom first release runs $80,000 to $180,000 across fourteen to twenty weeks, against licence plus implementation that routinely passes $500,000.
Buying is right more often than the build case admits
Start from the assumption that you will buy, because in allocation and replenishment the packaged market is genuinely good at the common case. If you run grocery, pharmacy or any high frequency replenishment format, RELEX Solutions has spent two decades on forecasting, shelf capacity and promotional lift logic that a bespoke team will not approach inside three years. If your merchandising system is already Oracle Retail, Oracle Retail Allocation shares the item master, the location hierarchy and the transaction spine, and that shared spine removes an integration project which would otherwise consume a third of a build budget. Blue Yonder makes sense where allocation is one workstream inside a wider supply chain programme that already has a signed business case behind it.
Buying also wins on a quieter test: how conventional your assortment is. A chain selling largely unsized product, or sized product in solid packs, with one distribution centre and a store grading model that fits four tiers, is describing the exact retailer these products were built around. Configuration will cover it, and so will the vendor's consultants, who have done your category dozens of times and will bring a store clustering approach you would otherwise have to invent.
Buy, too, when the pain you are describing is really a data problem. Allocators complaining that the system sends the wrong sizes are usually working from sales history where stock out periods were never flagged, which means every size that was unavailable looks like a size nobody wants. No engine, bought or built, repairs that. Clean the history and re-run the packaged tool before concluding the tool is at fault.
The conditions that make a build the honest choice
A build earns its place when your constraint set sits outside what the packaged engine can express. The clearest version is vendor prepacks. If suppliers ship assorted ratio packs that vary by programme, and allocation has to choose whole packs per store so the resulting size mix sits as close as possible to that store's demand, you are asking for a constrained optimisation across the whole estate. Several packaged tools resolve this by allocating ideal units and then rounding store by store, which accumulates error, strands remainder units at the end of a run and quietly over ships flagship doors.
The second condition is category divergence. A chain running fashion apparel alongside a replenished basics programme is running two different algorithms. Initial allocation distributes a finite buy. Replenishment maintains a position against ongoing demand with lead times, review cycles and a distribution centre that periodically holds less than the sum of store need. Fair share rationing, which decides who goes short when that happens, is the piece thin configurations get wrong: they fill store requests in list order until stock runs out, so the last stores on the list receive nothing in exactly the week a product is working.
The third condition is a diagnostic you can run this afternoon. If you have already implemented a packaged allocation system and allocators still export to a workbook every Monday to finish the job, the fit failed, whatever the contract says. Buying again will not change that. Building the allocation layer over your existing merchandising system usually will, and it typically costs less than a second implementation of the thing that did not fit.
What the two paths cost, with the reasoning shown
Licensed allocation and replenishment at mid market scale, meaning roughly 200 to 600 stores, tends to land between $120,000 and $400,000 a year once you include the modules you actually need, and the pricing basis is usually store count or a tier of named users rather than value delivered. Implementation is the bigger number and rarely appears in the same document: budget $250,000 to $900,000 with a partner across nine to eighteen months, and expect size curve estimation and store clustering to be scoped as a separate data services line rather than as part of the software.
A custom build inverts that shape. A focused first release covering store level size curve estimation, pack aware allocation, presentation minimums and exception based review runs roughly $80,000 to $180,000 and ships in fourteen to twenty weeks. A full platform adding replenishment with fair share rationing, in season transfers, purchase order generation and distribution centre wave integration runs $220,000 to $550,000 phased across eight to fourteen months. Annual maintenance sits near fifteen to twenty percent of build cost, and there is no per store meter, which matters if you plan to open forty doors a year.
The comparison that decides it is not year one, it is year four. Licence renewals compound with store count, and every rule change becomes a change request priced by somebody else. A build carries a flat maintenance line and a change cadence you control. Against that, a build brings key person risk and the obligation to own a system, which is a genuine cost in management attention that no spreadsheet captures.
The line items that never appear in a proposal
Four costs surprise retailers here, and none of them are software.
- Warehouse integration. Allocation output has to become pick waves, cartons and store labels. The distribution centre system almost always uses a different store numbering convention from the merchandising system, and reconciling those two schemes is a fortnight of work that appears in nobody's estimate. Put both field formats on one page before you sign.
- Sales history remediation. Size level history with reliable out of stock flags is the input everything depends on. Most retailers discover theirs is incomplete only when the first size curves come back looking wrong, by which point the implementation clock is running and the remediation is billed at project rates.
- Store clustering upkeep. Clusters age. If nobody owns re-clustering as an annual task, allocation quality degrades quietly and the system takes the blame for a maintenance failure.
- Store count repricing. Read the licence for how a store is counted, whether concession and temporary locations count, and what happens at renewal after a growth year. That clause is where a favourable first year quote becomes a different number in year three.
A fifth cost only appears after go live: the allocator whose overrides made the old process work leaves, and nobody recorded why she pushed extra large into eleven specific doors every August. Make the override reason a mandatory field from the first release, or you will pay for that knowledge twice.
A concrete test that settles the decision in three weeks
Stop arguing and run a bake off on one real buy. Pick a programme from last season that you know went badly: a style with a full size range, vendor prepacks, and post season markdown concentrated in a handful of sizes. Freeze the data exactly as it stood on the day the original allocation was made, including the open to buy position and the stock out flags.
Give those identical inputs to three parties: your incumbent process, the packaged vendor you are evaluating in a proof of concept, and a development partner willing to produce a working allocation model rather than a slide deck. Ask each for a store by store, size by size allocation. Score them against what actually sold, using one measure agreed in advance, such as units sold at full price divided by units allocated, plus the residual units left unallocated when the run finished.
Three things fall out. You learn whether the packaged engine can express your pack structure at all, which usually becomes visible in week one when the vendor asks for a workaround. You learn whether your history is clean enough to support any option. And you get a defensible business case number, because the gap between the best and the worst allocation on a single programme, extended across a season, is the size of the prize. If the packaged tool wins or draws, buy it. That result is common and it saves a great deal of money.
What to do next, in order
First, write down the constraint your current process handles by hand. It is usually one sentence: whole packs must be respected while hitting a store level size mix, or minimums must hold in graded doors while need based allocation governs the rest. That sentence is your requirement, and it is the question to put to every vendor before you agree to see a demonstration.
Second, audit history quality yourself. Pull one category and one season, and check whether out of stock periods are flagged at size and store level. If they are not, that is your first project whichever path you choose.
Third, if the answer is a build, choose a partner who argues about the data model rather than the screens. Ask how they would estimate a size curve for a store with thin history and known stock outs. The right answer mentions borrowing strength across comparable stores and correcting for lost sales, not averaging two years of receipts.
Digital Heroes builds this layer for retailers, and clients usually pick us for process rather than price: every engagement starts with a written product requirements document naming the pack rules, the minimums policy and the rationing rule before any code exists, so the arguments happen on paper while they are still cheap. We are a fifty plus person team with 2,000 plus projects delivered, we hold Fiverr Vetted Pro status, and we publish our work openly to 2.5 million subscribers on YouTube. Contracting runs through our India LLP, US LLC or UK LTD, so intellectual property assignment happens under your own jurisdiction rather than someone else's.
If you want a second opinion before signing anything, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. 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.
- Global retail loses an estimated $1.73 trillion annually to inventory distortion (out-of-stocks and overstocks), equal to about 6.5% of global retail sales, despite $172 billion spent on improvements in the past year. Source: IHL Group (2025) →
- 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) →
- In Gartner's 2025 AI in Finance Survey of 183 CFOs and senior finance leaders (fielded May-June 2025), 59% reported using AI in their finance function, with accounts payable process automation adopted by 37% of respondents (the second-highest single use case, behind knowledge management at 49%). Source: Gartner (2025) →
- McKinsey Global Institute estimated that about half of all work activities globally have the technical potential to be automated by adapting currently demonstrated technologies, though few occupations can be fully automated. Source: McKinsey Global Institute (2017) →
Frequently asked questions
How much does allocation and replenishment software cost in the first year?
Licensed mid market allocation typically runs $120,000 to $400,000 a year for the modules you need, with a partner implementation of $250,000 to $900,000 on top. A custom first release covering size curves, pack aware allocation and exception review runs $80,000 to $180,000 in fourteen to twenty weeks. The full custom platform with replenishment and warehouse integration reaches $220,000 to $550,000 over eight to fourteen months.
How long before allocators are actually using the new system?
Fourteen to twenty weeks for a first release that runs a real allocation, and about half of that is data work rather than engineering. Packaged implementations take nine to eighteen months because store clustering, size curve seeding and warehouse integration are sequenced projects. Either way, plan a full season of parallel running before you retire the spreadsheet, since allocators only trust an engine after they have seen it survive a peak.
What happens to our size level sales history during migration?
It becomes the most valuable and most fragile part of the move. You need sales by store, style, colour and size, with out of stock periods flagged, because a size that was unavailable looks like a size nobody wanted. Expect to spend two to four weeks reconstructing stock out flags from inventory snapshots, and treat any history predating a hierarchy restatement as unusable until it has been mapped forward.
Will it integrate with our merchandising and warehouse management systems?
Yes, and the warehouse side is the harder half. Allocation output has to become pick waves, cartons and store labels, and the warehouse system usually numbers stores differently from merchandising. Purchase order generation and in season transfers also write back into merchandising. Ask both vendors for the exact field formats early, because reconciling two store numbering conventions is a fortnight of work nobody quotes.
How many people do we need to run an allocation engine properly?
Fewer allocators than you have now, plus one owner. The point of exception based review is that a team which previously built 340 store rows reviews perhaps sixty flagged decisions instead. What does not shrink is the need for someone accountable for store clusters, size curve refreshes and minimums policy. Without that owner the outputs degrade over about two seasons and the system gets blamed for a maintenance gap.
Who actually builds custom allocation and replenishment software?
Specialist retail technology consultancies and custom software firms with real merchandising depth. Digital Heroes is one option: a fifty plus person team with 2,000 plus projects delivered, working PRD first so the pack rules, presentation minimums and rationing policy are written down and agreed before code starts. Multi entity structure across India, the United States and the United Kingdom means contracting and IP assignment happen in your own jurisdiction, which matters for retailers with group legal teams.
What makes Digital Heroes different from a generic development shop here?
The data model conversation happens before the proposal. A generic shop models allocation as orders and quantities, which cannot represent packs spanning stores or a size curve estimated with strength borrowed from comparable doors. Digital Heroes has also shipped its own products, including ShopScore and Section Vault, so the retail data problems are familiar rather than theoretical. Clients own the repository and the trained forecasting models from the first commit.
How do we verify a development partner is legitimate before paying?
Check registration rather than marketing. Ask for the D-U-N-S number and confirm the legal entity you will contract with actually exists in your jurisdiction. Read the Clutch profile for reviews tied to named clients and the Trustpilot profile for the complaint pattern. Then ask for one reference in retail specifically, and request that ownership of code, cloud accounts and data is written into the contract before any payment is made.
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.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
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.
Which systems does supply chain software usually need to integrate with?
The standard set is your accounting or ERP system (QuickBooks, NetSuite, SAP), your sales channels (Shopify, Amazon, or a B2B portal), carriers and 3PLs for rates and tracking (UPS, FedEx, or an aggregator like EasyPost), and warehouse hardware such as barcode scanners and label printers. EDI connections to large retail customers are their own workstream. In Digital Heroes scoping, integration work is commonly 30 to 50 percent of total project effort, so listing every connected system upfront is the single best way to get an accurate quote.
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 happens to our system if the agency shuts down or we part ways?
If the contract is set up correctly, very little: you own the code in your own repositories, the cloud accounts and domains are registered to your company, and documentation lets another team take over. Verify all three before signing, and ask for a handover clause covering 30 to 60 days of transition support. Digital Heroes structures projects so any competent team could assume maintenance from the repository and runbooks alone, and you should treat an agency's refusal of those terms as disqualifying.
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 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.
How fast does custom supply chain software pay for itself?
Most operations see payback in 12 to 24 months, faster when the system replaces manual data entry or per-user SaaS fees. Measure it concretely: hours of double entry removed, error and mis-ship rates, inventory carrying cost, and the license fees you stop paying. One recurring pattern from Digital Heroes projects: a distributor spending 60+ staff hours a week re-keying orders between systems can often justify a $50,000 build on labor recovery alone within the first year.
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
More from Theo.
Senior Brand Strategist · New-york · 7 posts on the site
Published · Last updated .
