Store Fulfillment Software: Custom Build Versus Manhattan, Fluent and NewStore
Buy if you run under about 40 stores with similar layouts, and buy anyway if you are replacing your order management system at the same time. Manhattan Active Omni and Fluent Commerce are better than anything you would write in that situation.
On this page
Buy if you run under about 40 stores with similar layouts, and buy anyway if you are replacing your order management system at the same time. Manhattan Active Omni and Fluent Commerce are better than anything you would write in that situation. Build the associate picking layer once you pass roughly 80 stores and cancel rates differ between them for reasons nobody can explain.
What the off-the-shelf products actually do well
Ship from store made every location a fulfilment node without giving it any of the tooling a distribution centre takes for granted. The products that grew up to fix that are genuinely good, and three of them are better than a first attempt at a build.
Manhattan Active Omni is the most capable product in this category and we say so plainly. Its distributed order management depth is real: sourcing logic, inventory availability across nodes, appeasements, returns against a store fulfilled order, and a store fulfilment module that works. Fluent Commerce gives you an order management rules engine that is a pleasure to change, which matters because sourcing rules change more often than anyone plans for. NewStore is opinionated and strong if you are adopting its point of sale (POS) as well, though that is a much larger decision than store picking. Deposco carries warehouse heritage that shows in the store experience, which cuts both ways.
What all of them bring is the boring correctness underneath. Carrier rate shopping with fallbacks, label rendering in ZPL for the Zebra printer at the pack bench, address validation, GS1-128 shipping labels, and payment handling that keeps your point of sale inside PCI DSS 4.0 scope where it belongs. Nobody should rebuild that layer.
If you run under about 40 stores with near identical layouts, modest volumes and no in-house engineering, buy one of them, configure it well and stop. A build at that size is a distraction from the merchandising decisions that actually move your margin.
Where they stop: the short pick and the store floor
Two things no vendor can give you, and one of them is the entire economics of the channel.
A short pick is not an error. It is the normal outcome of picking against inventory a shopper may have moved, hidden or carried into a fitting room. The question is never how to avoid short picks. It is what happens in the forty seconds afterwards. Most implementations mark the line not found, bounce the whole order back to the sourcing engine, and start again from zero somewhere else. That discards the six lines already picked and hands the customer a delay measured in days. Two shorted lines route to another store, short again the next morning, and thirty six hours after paying the customer gets a cancellation email. Nobody in head office can reconstruct that without opening three systems.
The second gap is your floor. Picking efficiency in a distribution centre comes from sequence, because the software knows the bin. The store equivalent is which fixture holds which category, where footwear overflow lives in the stockroom, that the sale rail moves every fortnight, and that store 214 has two floors with the lift at the back. Almost nobody holds that as data. Merchandising has planograms for some fixtures, store operations has a floor plan from the last refit, and the truth lives with the store manager.
No vendor can know your floor, and that is not a criticism of them. Pick sequence has to be derived from location data you own and maintain, which means the part that produces the saving is yours to build regardless of which product you buy.
The arithmetic: per store per month against a one-time build
Take the per store figure from your own quote. Order management platforms in this category are priced per store per month, per order, or as a blend, and the blend is where comparisons go wrong, so separate the store fulfilment line from the order management line before you do anything else.
Suppose the store fulfilment module is $250 a store a month. Two hundred stores is $600,000 a year. A picking layer built once at $140,000 with $25,000 a year of support is $240,000 across five years, or $48,000 a year. On licence alone the crossover is about 16 stores, and if the vendor prices by order instead at 12 cents, it is roughly 400,000 store fulfilled orders a year.
Now the correction that matters, and it is the part vendors and agencies both leave out. Licence is not the comparison. Training 400 stores is a programme with its own budget, its own regional leads and its own attrition problem, and it lands on the build side of the ledger while a packaged rollout carries a vendor enablement team. Once you include rollout, device testing across an ageing handheld estate, and the support load in the first peak, the honest crossover moves to somewhere near 80 stores.
Below 80 stores, buy. Above it, the arithmetic and the operational case both point the same way, and the operational case is larger: cancel rate is a margin number and a customer retention number at the same time.
What a custom build actually costs
A first release runs $90,000 to $190,000 and ships in 12 to 18 weeks, piloted in a handful of stores rather than rolled out cold. That covers the associate picking application with zone based pick paths, batching, structured short pick handling and in-store carrier label printing.
A full platform adding collect, curbside and locker handoff, labour measurement per order, sourcing feedback based on store capability and integration across your order management and point of sale estate runs $250,000 to $600,000 over 6 to 12 months.
Data migration is 10 to 25 percent of the build, and in retail it is not a database export. It is capturing store location data that has never existed as data. Zone level is enough to start and zone level sequencing beats no sequencing by a wide margin, but capturing zones store by store is a real workstream with store manager time in it. Budget it as migration, because that is what it is.
Year two runs 15 to 20 percent of the build annually: new carriers, a device refresh, a point of sale upgrade, seasonal changes to the collect flow, and the handful of store specific rules that always appear after the first peak.
What pushes the number up: device estate, because supporting old handhelds alongside newer phones doubles the testing surface. Carrier count and whether you rate shop live. Point of sale integration, since taking a collect payment or a return against a store fulfilled order touches the till software, and till software is the most defended system in the building.
The four situations where building wins
Regulatory fit. Payment touchpoints in a collect or curbside flow drag the till into scope, and PCI DSS 4.0 requirements became mandatory in March 2025. A build lets you keep the picking layer entirely outside cardholder data scope, handing payment back to the point of sale, which is cheaper to assess every year than a product that wants its own payment path.
Scale economics. Past roughly 80 stores including rollout and training, or 400,000 store fulfilled orders a year on a per-order licence, the numbers have turned.
A workflow that is your advantage. Short pick handling is the honest example. Confirm not found on the device, then immediately offer substitution where the merchant allows it, partial ship of the found lines, or a real time re-source of only the missing lines while the picked lines continue. The customer gets one honest notification instead of a cancellation two days later. Feed every short pick back as an inventory adjustment event with location context, because a line shorted three times in one store is a stock accuracy problem with an aisle attached.
Integration sprawl across three or more systems. Store fulfilment touches order management, point of sale, inventory, carrier APIs and your customer notification stack. Owning the picking layer means the joins are yours, and the joins are where the day breaks.
How to decide in a week
Do not run this from head office. Send someone to three stores: your best, your worst, and one in the middle.
Have them pick ten real orders on the current tooling and time each one, then record every interruption. Separately, pull last quarter's cancelled lines by store, and for each cancellation trace whether the item was genuinely absent or simply not found by someone who had four minutes. Then ask the store manager to draw their stockroom on paper and see how long it takes.
- If pick times are consistent across all three stores, buy. Your variance is not a floor problem.
- If the worst store takes more than double the best, build the zone model and the pick path first.
- If most cancellations were items that existed but were not found, your first project is short pick handling, not a new platform.
- If the store manager draws the stockroom in five minutes, your location data is capturable and cheaper than you feared.
Then commission a paid discovery phase rather than accepting a proposal. At Digital Heroes that is two to three weeks producing a signed product requirements document covering the zone model, the short pick decision tree, the carrier and label path and the acceptance criteria, before a line of code exists. You own it whether or not you hire us, and it makes three quotes comparable for the first time.
Who we are wrong for: a retailer replacing its order management system this year. Buy Manhattan or Fluent, take the store module that comes with it, and revisit the picking layer in two years. We are more than fifty specialists with over 2,000 projects delivered, verifiable on Clutch, Trustpilot, Fiverr Vetted Pro and by D-U-N-S number. Our own products, ShopScore and HeroCheckout, are retail commerce tools and Section Vault is a documentation product, so we know this stack from both sides. Our India LLP, US LLC and UK LTD entities mean intellectual property assigns under your own law rather than ours. You meet the named engineers before signing.
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.
- 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) →
- 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) →
- The performance gap between digital and AI leaders and laggards is widening: McKinsey reports leaders pull ahead on shareholder returns, and the average maturity spread between top and bottom performers jumped ~60% (from 10 points in 2016-19 to 16 points in 2020-22), reinforcing that the returns to transformation concentrate among top performers. Source: McKinsey & Company (2023) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
Frequently asked questions
How much does custom store fulfillment software cost?
A first release covering the associate picking application with zone based pick paths, batching, structured short pick handling and in-store carrier label printing runs $90,000 to $190,000 over 12 to 18 weeks. A full platform adding collect, curbside and locker handoff, labour measurement and estate wide integration runs $250,000 to $600,000 across 6 to 12 months. Location data capture adds 10 to 25 percent.
How long does a rollout across several hundred stores take?
The software is the short part. A pilot in six stores runs 12 to 18 weeks including build, and the estate rollout that follows is usually two to four stores a day once training materials settle, so 400 stores is a quarter of calendar time with regional leads doing the work. Retailers who compress that below two weeks a region see the support load spike through their first peak.
Who owns the code and the store location data we capture?
You should own both from the first commit, and the location data matters more than people expect. Zone definitions per store are the asset that makes pick paths work, they take real store manager time to capture, and they are the one part no vendor can hand you. Keep them in your own database with an export you can test, whoever builds the application on top.
What happens when a carrier API times out mid shift?
Label generation should queue locally so an outage delays a print rather than stopping the whole queue, and rate shopping should fall back to a default service rather than blocking the pack bench. This is a design decision rather than a vendor feature, and it is worth asking about specifically, because a store that cannot print for twenty minutes on a Saturday stops picking altogether and the queue never recovers that day.
Can we keep our order management system and build only the picking app?
Yes, and for most retailers past 80 stores that is the right shape. The order management system keeps sourcing, inventory availability, payments and customer notification. The build owns the associate experience: zone based pick paths, batching, the short pick decision, and the handoff workflow with a physical hold location model. The interface is narrower than it sounds, mostly work in and outcomes out.
Should a chain with 25 stores build its own picking application?
No. Under about 40 stores with similar layouts, the licence saving does not cover rollout and training, and a packaged store module plus disciplined process will serve you. Spend the money on stock accuracy instead, since most cancellations at that size trace to inventory that was wrong rather than to picking that was slow. Revisit the question when store count or layout variety grows.
What is the difference between store fulfillment and distributed order management?
Distributed order management decides which node should fulfil an order, holds availability across the network, and manages the order lifecycle including payment and returns. Store fulfilment is what happens inside the four walls afterwards: the pick path, the batch, the short pick decision, the pack bench and the customer handoff. Products bundle both, and separating the two lines on a quote is the first step to comparing quotes honestly.
How do we cut cancel rates without replacing anything?
Three changes help before any build. Stop bouncing whole orders back to sourcing when one line shorts, because the picked lines are the customer relationship. Record every short pick as an inventory adjustment with a location attached, so repeat offenders surface. And hand out collect orders due within the hour before ship orders due tomorrow, which most tooling does not distinguish and which costs you the most visible failures.
Can associates use their own phones instead of handhelds?
Often yes, and it changes the cost picture materially, because supporting an ageing handheld estate alongside newer devices doubles the testing surface. The constraint is scanning quality in poor stockroom lighting and whether your device management policy permits it. Build the application so state lives on the server rather than in the session, and any associate can resume any batch from any device mid shift.
What are the alternatives if the budget is not there this year?
Capture zone level location data for your twenty busiest stores, which costs store manager time rather than software and makes any later build cheaper. Change the short pick policy so partial shipment is the default. And publish cancel rate by store weekly to store managers, since the variance you cannot currently explain usually explains itself once the people responsible can see it.
What does it cost to maintain a custom WMS after launch?
Budget 15 to 20 percent of the build cost per year, so a $120,000 system runs $18,000 to $24,000 annually for bug fixes, dependency updates, carrier API changes, and small feature requests; that figure comes from Digital Heroes retainers across 2,000+ projects. Hosting for a single-warehouse system adds roughly $200 to $600 per month on AWS or Azure. Weigh that against subscription fees that grow every time you hire another picker.
How many people does it take to build a custom WMS?
Five is the typical Digital Heroes WMS team: a project lead, two backend developers, one developer on the scanner app and dashboard, and a QA engineer, with DevOps involved part-time. EDI-heavy or multi-warehouse scopes add a dedicated integrations developer. On your side, assign one operations person who can answer process questions within a day, because their availability moves the timeline more than adding developers does.
What should the first version of a custom WMS include?
Four flows that touch every order: barcode receiving, location-based putaway, directed picking, and shipment confirmation, plus a live inventory view for the office. Digital Heroes ships that scope in 12 to 16 weeks and pushes wave picking, automated cycle counts, and labor analytics to phase two. Pilot it in one zone or product category before the whole floor, because go-live problems found on 10 percent of your SKUs are annoyances while the same problems on 100 percent are a shutdown.
Should I hire a freelancer or an agency to build our WMS?
An agency, for anything that will run a live warehouse. A WMS needs backend, scanner app, integration, and QA work happening in parallel, plus someone reachable when receiving stops at 6 a.m., and a solo freelancer is a single point of failure on a system your shipping depends on. Freelancers are the right call for a bolt-on report, a one-off integration script, or maintaining a system that already works.
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.
What integrations does a custom WMS usually need?
Four categories cover most builds: the ERP or accounting system for purchase orders and invoices, sales channels like Shopify or EDI feeds from retail customers, shipping carriers through UPS, FedEx, or a multi-carrier API like EasyPost, and hardware such as label printers and scales. Each ERP connection typically adds 2 to 4 weeks of work in Digital Heroes builds, and EDI with a big-box retailer adds more. List every integration before asking for quotes, because integrations are the most common source of budget overrun in Digital Heroes projects.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
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 can build a custom warehouse management software system?
Digital Heroes builds custom warehouse management 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 warehouse management 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 Sophie.
Account Manager · UK Retail & Fashion · London · 4 posts on the site
Published · Last updated .
