Build vs Buy: Markdown Optimization Software for Retail Pricing Teams
Buy if you sit inside an Oracle Retail or Blue Yonder stack, or if your markdown exposure is small relative to turnover. Build when merchants already override most recommendations from an engine you pay for, because that is a trust problem no better model solves.
On this page
Buy if you sit inside an Oracle Retail or Blue Yonder stack, or if your markdown exposure is small relative to turnover. Build when merchants already override most recommendations from an engine you pay for, because that is a trust problem no better model solves. Visible reasoning gets executed. A confidence score does not.
Why buying is right for more retailers than want to hear it
Revionics, Blue Yonder and Oracle Retail Offer Optimization all estimate price response properly. Their mathematics is not the weak point and pretending otherwise would be dishonest. If your planning and pricing data already sits inside one of those stacks, the offer optimisation module is next to the data it needs, and the integration cost of anything else is real money spent reproducing a connection you already have. Impact Analytics stands up faster and prices more accessibly, which suits a mid sized retailer with reasonably clean history who wants an engine this season rather than next year.
Buying is also right when the exposure does not justify a project. If markdown is a small share of turnover, or you clear residual stock through a jobber at a fixed rate where timing barely changes the recovery, then optimising the cadence is optimising a rounding line. Fix the buying instead.
The third case is data. Optimisation needs at least two clean seasons, and crucially the history has to carry the price each unit actually sold at rather than the current list price. Plenty of retailers discover their transaction records hold quantity and revenue but not a reliable per unit selling price after promotions, and reconstructing that is a project in its own right. Under about eighteen months of usable history, any model is a guess with a chart attached, and we will say so rather than take the work.
None of that is a hedge. For a retailer with clean data, a standard assortment and a merchandising team willing to follow a system, a licensed engine is the cheaper path to a better answer.
The conditions where a custom engine earns its place
The tipping point is adoption rather than accuracy. Markdown optimisation only creates value if the recommendations are executed, and they are only executed if merchants believe them. Where deployments fail, they fail like this: recommendations arrive as numbers a merchant did not derive and cannot inspect, so the merchant overrides them, and within two seasons you are paying enterprise licensing for a spreadsheet with better graphics.
Build when these are true.
- Your team already overrides most recommendations from an engine you pay for. That argument is lost, and a newer engine does not win it.
- Store level residual varies enough that chain wide cuts are visibly wrong. The chain view says four thousand units remain, and most of it sits in eleven stores where the item never sold while the four stores that could sell it at full price have none left.
- Your assortment carries broken size and colour curves, and your current tool treats remaining units as interchangeable.
- Execution capacity, meaning re ticketing labour and label technology, is the real limit on how often you can change price, and no vendor model accounts for it.
A separate case entirely: grocery. Your markdown decision is date code driven and happens daily, in store, on chilled, bakery and produce, by a colleague with a label gun. The variables are hours remaining, units on hand, historical clearance at that store at that hour, and the waste cost if it does not sell. Seasonal exit curve optimisation is the wrong product category, and the right build is a small scanning application scoped well below the bands in the next section.
What each route costs
Enterprise pricing here is commonly scaled to revenue rather than usage, with a services heavy onboarding attached. That matters because your bill grows with the business regardless of whether you use the engine more, and because the implementation partner, not the licence, determines whether the thing works. Before signing, ask three questions in writing: what the fee does as revenue grows, what onboarding assumes about your data structure, and what the last three comparable customers actually spent on services against the original estimate.
In Digital Heroes delivery experience, a first custom release covering demand decay estimated from your own history, item and store level residual with exit dates, store group recommendations with inspectable reasoning, and a merchant review and approval screen runs $80,000 to $170,000 and ships in 14 to 18 weeks. A full platform adding transfer versus markdown evaluation, size curve modelling, execution constraints and price change batching, prior price and effective date handling, and post season measurement runs $200,000 to $500,000 phased across 8 to 14 months.
What pushes it up: the number of price zones and whether store group pricing is even possible in your point of sale (POS), since store group recommendations are academic until it is. Then multi channel, because online and store markdowns interact and customers compare. Then history quality, which is the single largest variable. What keeps it down: one division, one season, and the categories carrying the largest markdown spend rather than the most items.
The costs retailers do not budget for
Execution labour is the first and it is routinely ignored. A recommendation to cut price on hundreds of items across ninety stores on a Wednesday means somebody in every store re tickets hundreds of items. If your stores use printed tags, that is hours per store, and it will be done partly, late or not at all. The optimiser reports a margin improvement. The shelf never gets the message. Model a cap on price changes per store per week and batch to your existing re ticketing day, and if some stores run electronic shelf labels while others run paper, the constraint differs per store and the engine has to know that.
Prior price handling is the second, and it is a legal exposure rather than a feature. What you may claim as a previous price, how long the item must have been offered at it and what must appear on the ticket vary by jurisdiction. That interpretation belongs with your counsel, not your vendor. The software's job is to carry prior prices with effective dates as first class data so the ticket, the advertised claim and the pricing decision all come from the same record, and so whatever your counsel decides can be evidenced afterwards.
The third is transfer cost. Cutting price to clear stock that is simply in the wrong stores is the expensive mistake, and evaluating consolidation against markdown as one decision requires knowing what a transfer actually costs to pick, ship and receive. Most retailers have never quantified that per unit, and the number has to come from operations before the model can use it.
Fourth: post season measurement. Without it you cannot tell whether the engine helped, because markdown errors in both directions partly cancel in the reported margin line, which is exactly why uniform cadence survives year after year.
A test to run before the next season
Take last season's worst performing class and answer four questions.
- For a single item, can you produce remaining units by store, the sizes remaining, and how many of those units are genuinely sellable given the size profile that moves in each store.
- What did that item's sell through curve look like at each price point, and can you show it to a merchant on one screen.
- How many price changes did your stores actually execute in the week you asked for them, measured at the shelf rather than in the system.
- Of last season's recommendations from your current tool, what proportion were followed, and can anyone explain the overrides.
Question three is the one that embarrasses most retailers, because nobody measures it. Question four decides the build case: heavy overriding with reasons nobody recorded means your problem is trust and transparency, and that is exactly what a custom engine with visible reasoning fixes.
What to do next
Before commissioning anything, ask your current vendor to show a merchant why a specific recommendation was made, on screen, in the review workflow. If the answer is a score, you have found the boundary. Then price the licensed alternatives against a five year revenue projection rather than this year's fee.
If you build, interview developers on your data before they talk about models. Ask what they will do if sales records do not carry actual selling price, and a team that has done this asks that question in the first meeting rather than the third. Ask how a merchant sees the reasoning: you want the sell through curve, the comparable items used and the projected outcome at each candidate price, in the approval screen, not a number in a queue. Ask how they will model execution limits and prior price effective dates.
Digital Heroes builds these engines where trust is the binding constraint. Every engagement starts with a written product requirements document covering the estimation level, the residual definition, execution constraints and the merchant review flow before any modelling, because in markdown work the specification is a merchandising process document first. Contracting through an India LLP, a US LLC or a UK LTD puts IP assignment under your own law, and we have shipped our own retail products including ShopScore and HeroCheckout, so the commercial mechanics are familiar ground. The team is past 50 people with more than 2,000 projects delivered, and the way we work is public alongside the 2.5 million people subscribed to the Digital Heroes YouTube channel.
Settle ownership before kickoff: repository, cloud accounts, feature data and the trained models. Those models encode your own customers' behaviour rather than any vendor's property. Verify any firm through D-U-N-S registration and its public Clutch and Trustpilot profiles.
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.
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- Analyst estimates place CRM implementation failure rates broadly between roughly 30% and 70% (Johnny Grow cites Forrester at 47%), with low user adoption repeatedly cited as a leading cause of failed CRM projects (this being Johnny Grow's own analysis, not a Forrester attribution). Source: Johnny Grow (industry analysis citing Gartner/Forrester) (2025) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- 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) →
Frequently asked questions
How much does custom markdown optimization software cost?
A first release covering demand decay estimated from your own history, item and store level residual with exit dates, and merchant facing recommendations with visible reasoning runs $80,000 to $170,000 over 14 to 18 weeks in Digital Heroes delivery experience. A full platform adding transfer versus markdown evaluation, size curve modelling, execution constraints and post season measurement runs $200,000 to $500,000 across 8 to 14 months.
How long does it take before the first season is priced by it?
Fourteen to 18 weeks to a first release, which usually means one season of parallel running before merchants rely on it. Expect the early weeks to go into price history rather than modelling. Retailers whose transaction records already carry actual selling price per unit move considerably faster than those who have to reconstruct it, and that difference can be a month on its own.
How much sales history do we need for this to work?
At least two clean seasons, and the history must carry the price each unit actually sold at rather than current list price. If your records hold quantity and revenue but no reliable per unit selling price after promotions, elasticity cannot be estimated until that is reconstructed. Under roughly eighteen months of usable history we would tell you to wait rather than take the work, because the output would be arbitrary.
What does a markdown engine need to integrate with?
Your point of sale for price zones and actual transactions, merchandise planning for exit dates and receipts, inventory for store level residual including in transit, and your labelling or shelf edge system for execution. Ask early whether your point of sale supports store group pricing at all, because store level recommendations are academic until it does, and that constraint should shape the scope.
Who needs to be involved from our side during the build?
One senior merchant with authority over pricing decisions, a planner who understands residual and exit dates, and someone from store operations who can state what re ticketing actually costs in labour. That third person is the one most projects forget, and without them the engine will recommend a volume of price changes your stores cannot physically execute in the week you asked.
Who actually builds markdown optimization software?
Digital Heroes does, for retailers whose merchants have stopped trusting a licensed engine. Buyers choose us for concrete reasons: estimation level, residual definition, execution constraints and the merchant review flow are settled in a written product requirements document before modelling begins, contracting through an India LLP, US LLC or UK LTD puts IP assignment under your own law, and the team is past 50 people with over 2,000 projects delivered.
What makes Digital Heroes different from a generic dev shop here?
We build the merchant review screen as the product rather than as reporting. The recommendation arrives with the sell through curve it came from, the comparable items used and the projected outcome at each candidate price, so a merchant can argue with it on evidence. Generic teams ship a scored queue, which is precisely the artefact that gets overridden, and no amount of model accuracy recovers a decision the merchant does not believe.
How do we verify a development partner before paying?
Confirm D-U-N-S registration against the entity that will sign, then read public Clutch and Trustpilot profiles for reviews describing engagements of similar scope rather than adjectives. Establish which legal entity invoices you and whether it can assign intellectual property in your jurisdiction. Require ownership of the repository, the feature data and the trained models in writing before kickoff, since those models are built on your own selling history.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
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.
What should I have ready before I contact a development agency?
Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
If an agency builds my software, who actually owns the code?
You should own everything, assigned in writing: the contract transfers full IP to you on final payment, the code lives in your GitHub organization, and hosting runs in cloud accounts you control. The red flag is a proposal that mentions the agency's proprietary platform or framework, which usually means you are renting, not buying. Digital Heroes structures every build this way precisely so a client can fire us and lose nothing but the relationship.
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
For validating an idea with real users, yes, and we tell clients that honestly. The walls come later: Bubble apps cannot be exported as code to run anywhere else, performance drops on complex data operations, and usage-based pricing climbs as you grow. A meaningful share of Digital Heroes custom builds are rebuilds of no-code MVPs that proved the business worked, which is the system operating as intended: validate cheap, then build the version that scales.
How do I make sure custom software is secure and compliant with rules like HIPAA?
Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.
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.
Who can build a custom software system?
Digital Heroes builds custom 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 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 .
