Most multi-site retailers pay for technology nobody has added up. The point-of-sale contract sits with IT, the payments processor with finance, the shelf labels with store operations, and the telecom bill with whoever signed it last time.
Each one renews on its own date. Notice dates pass quietly, and the bargaining power goes with them. After an acquisition, the combined business runs two of each for longer than anyone planned. And when the renewal quote arrives, a busy finance team accepts it because nobody has time to challenge it.
The programs behind those contracts fail in predictable ways too, and the failures show up in the spend.
I have walked into stores mid-pilot and watched associates use printed paper cheat sheets to work around a new POS workflow that nobody had tested against actual seasonal traffic. The system was live. The procedure was rejected. The program called that a successful go-live.
Where retail technology programs actually fail
The vendor names change. The platform generations change. The pattern holds.
Pilots run in flagship stores that do not reflect the real estate. A pilot in a well-lit flagship location with a dedicated IT resource on site, a fresh network, and a cooperative store manager produces results that will not survive contact with a strip-mall store running on a ten-year-old switch, staffed by seasonal associates, under a district manager who has not been told the program is happening. Rollout then hits integration failures in stores nobody tested, and nobody can explain why. I wrote about this pattern specifically in the Fail Fast post because I have seen it play out across ESL, POS, and network refresh programs.
Data model assumptions that do not survive acquisition integration. When one retailer acquires another, the two ERPs do not merge, even when the vendor deck says they do. I lived this during a full post-acquisition platform conversion across a large retail network in two countries. The real question was never whether the new system worked. It was which system of record wins for what, and who had the authority to make that call without a three-month escalation.
Vendor selection driven by procurement, not operating model fit. RFP scoring produces a number. The number picks a vendor. The vendor was evaluated against feature checklists and reference calls that the vendor curated. The operating model assumptions embedded in the platform get discovered during implementation, not during selection. By then the contract is signed.
Change management treated as an afterthought. Associate training, store readiness, comms cadence, and the actual adoption curve all sit outside the implementation budget until the week before cutover. At which point the program owner discovers that the people who will use the system every day do not know what it is.
Where the money comes from, in order
- 1Stop paying for what nobody uses. Licences for stores that closed, modules that never went live, the second POS contract an acquisition brought with it. Fixing this costs a notice letter sent on time.
- 2Fix the terms on what you keep. Price escalators, minimum volumes, auto-renewal clauses and per-store fees that made sense at a smaller store count. This is a negotiation, and it has a deadline: the notice date.
- 3Consolidate platforms only where the case holds. Retiring a second ERP or POS saves the most and costs the most. I size it, date it and put it in front of you as a decision.
Most retailers start at step 3, because a vendor brought them a proposal. The Diagnostic starts at step 1.
For each contract behind those steps, the retail technology contract map sets out who usually owns it, the clauses that cost money and what doubles after an acquisition.
How I work with retail operators
I have sat in the technology seat at a large North American retail network, and before that at a cross-border retail group operating in the US and Canada. I run programs. I am not an outside observer.
The work is not a slide deck. It answers one question: which decisions in the next 90 days decide what you pay, and who has the authority to make them?
The engagement pattern starts with the operating model, not the technology. How do stores actually run. Where do corporate and store decisions diverge. What do the seasonal peaks look like. Which operational constraints shape what is deployable. The technology architecture follows from those answers, not the other way around.
Retail-specific capabilities
ERP modernization and migration. I led a full post-acquisition platform conversion across a large retail network in two countries, and advised on roadmaps for others. The hard part of retail ERP is rarely the general ledger. It is pricing, merchandising, inventory, and promotions living across the ERP, POS, commerce platform, and merchandise systems at the same time. The integration design decides whether the migration ships on time, or accumulates two years of data debt before stabilization.
POS and payments modernization. I led a chain-wide POS and payments program with projected payment savings that also materially reduced M&A store onboarding effort. The work was not the POS replacement. It was the payments architecture, card-not-present authentication, the mobile point of sale workflow that associates would actually use in a furniture store aisle, and the rollback plan that nobody budgeted for and everyone needed.
Electronic shelf labels and digital pricing. I led a shelf-edge pricing program at chain scale, validating labor efficiency and pricing-accuracy improvements through a phased pilot before it scaled. ESL looks simple in the demo. In production, the decision that matters is how pricing propagates from ERP to POS to web to shelf edge, and what happens when those systems disagree at 3pm on a promotional weekend.
Omnichannel and commerce platform. SFCC at an apparel manufacturer, order management across physical and digital inventory, and the data-model decisions that decide whether BOPIS, ship-from-store, and endless-aisle actually work or just appear to work during the demo. Inventory truth is a data problem before it is a platform problem.
Store operations technology. Samsung Tab Active devices, VDI, associate experience, and the difference between a hardware-driven problem and an adoption-driven problem. These are usually adoption problems. I have stood in enough stores during go-live weekends to know where the workarounds start.
Data, analytics, and PIM. I have led enterprise platform evaluation and modernization planning covering product information management, worked with Centric PLM in apparel manufacturing, and led master data work that precedes any serious retail analytics investment. The reporting layer is the last and smallest part of the work. Most of it is master data and integration.
Who I work with in retail
I work with multi-site retailers, typically in one of three situations. After an acquisition, when the new parent is paying for two technology estates and needs a plan to retire one. Before a major renewal, when the POS, payments, ERP or ecommerce contract comes up inside the next 12 months and the negotiating window closes on a date. Or when a new CFO or CEO wants a baseline and a defensible first win.
If you have just closed a deal, start with the post-acquisition contract checklist.
The buyer is usually the CFO, then the CEO or owner. In PE-backed retailers the operating partner is often the first call. The person I work with most is the IT director, who gets commercial backing for the negotiations they already want to have, and the credit in the readout. Every engagement runs independent of software vendors and systems integrators.
How I help retailers
I find the money in your technology contracts and systems, then run the program that captures it.
What the five weeks look like in a retailer
Week 1
I meet finance, IT and store operations, and collect the POS, payments, ERP, ecommerce, shelf-label and telecom agreements.
Weeks 2 and 3
I build the renewal calendar and reconcile it to 12 months of accounts payable. You see an interim readout with the notice dates that matter first.
Weeks 4 and 5
Every item is sized, owned and dated. You get negotiation positions for your top five vendors and a 90-day action list.
Your stores are not asked for time unless a contract question needs a store manager's answer.
For CFOs
Technology Spend and Contract Diagnostic
In five weeks you get a renewal calendar, a spend baseline, a risk inventory and a sized list of what is recoverable, for a fixed fee.
You provide the contracts, 12 months of accounts payable data and six to eight interviews.
Learn moreFor CFOs and CEOs
Contract Renegotiation and Systems Consolidation
I lead the negotiations and the system consolidation, and track the savings against your invoices. Includes post-acquisition integration.
Learn moreFor CEOs
Fractional Technology Executive
Senior technology leadership a few days a month, for companies without a CIO or between leaders.
Learn moreCase studies
Two engagements that illustrate how this work lands in practice. Both ran at chain scale and both had measurable business outcomes.
POS and Payments Modernization
Chain-wide rollout, payment savings (projected), and a materially faster M&A store onboarding path.
Case studyM&A Platform Conversion
Two retail estates converted onto a single platform while stores kept trading.
Frequently asked questions
How long is a typical retail engagement?
The Technology Spend and Contract Diagnostic runs five weeks for a fixed fee. If the readout shows money worth going after, the renegotiation and consolidation program runs three to six months. You can stop after the Diagnostic.
Do you work with retailers under $500M in revenue?
Yes. In some ways smaller multi-site retailers benefit more from senior advisory than larger enterprises do. Large enterprises have internal architecture teams and vendor management functions. Mid-market retailers run the same complexity with a fraction of the bench strength, and a few right decisions in the first 90 days of a program materially change the outcome.
Can you support selection of a specific ERP or POS vendor?
Yes. I have evaluated and worked alongside the main retail ERP platforms, including STORIS, SAP, NetSuite, Microsoft Dynamics and Oracle Fusion, in different contexts. No referral fees, no vendor incentives, no implementation partner relationships that shape the recommendation. That independence is rare enough in this category that it is often the reason a retailer calls.
Do you deliver or just advise?
I lead the negotiations and the consolidation decisions, and I hold vendors and integrators to their commitments. I don't configure systems, migrate data or write code. Your integrator does that, and I hold them to it.
Do you need access to my systems?
No. I work from your contracts, order forms, renewal notices and 12 months of accounts payable data. Exports are enough. I do not need a login to your systems. If read-only access speeds things up, that is your call.
How much time does it take from my team?
Six to eight interviews across finance, IT and operations, the time to pull the contracts and the accounts payable export, and an executive at the readout.
Is the savings number a promise?
No. Every item in the register is sized from your contracts and invoices and labelled. A saving is projected until it shows up on an invoice. I do not guarantee savings in a fixed-fee engagement.
Who sees my contracts?
You and me. I sign a confidentiality agreement, yours or mine, before I read anything.
The question is not whether you pay too much for technology. It is whether you find out before your next renewal or after it. Start with a 30-minute call.