Multi-Brand Automotive Parts Distributor ยท Distribution & Ecommerce
Two systems of record. Thirteen storefronts. One order in two broke.
A fifty-year family of automotive restoration parts brands, owned by a private equity sponsor and built by acquisition, had grown into thirteen web storefronts, roughly 400,000 items, a 200-seat call center and a few thousand orders a day, on a stack nobody had designed. An ERP replacement begun years earlier was never finished, so the business ran on the half-implemented new system and the unsupported old one at the same time, and the two did not agree. David Day was lead consultant and technology lead, running the program.
What David walked into
- Two systems of record that disagreed. Orders flowed from the web into the newer ERP, then into the legacy system for fulfillment, and nothing flowed back. Change an order in the old system and its shipping dropped off.
- Thirteen storefronts, thirteen code bases. Every brand ran its own outdated site. Two produced over half of web revenue; eight produced under 5% each.
- A warehouse on paper. Paper pick sheets, no scanners, and receiving looked up part numbers on the public website.
- Money leaking in the gaps. Backorders lost their card authorization after seven days, and parts shipped anyway when re-authorization failed. A price-variance account ran $30,000 to $40,000 a month.
- An IT team on fire. One manager was also the developer for all three systems. Pick runs and morning reports failed on a recurring basis, on a single internet circuit.
The insight
The problem was not which ERP the company had chosen. It was that nobody had decided which system was the system, so every department had chosen for itself. The goal David wrote on the whiteboard on the first day was one line: get people using one system for order entry. Everything else, the platform selections, the sequencing, the interim compromises, followed from that.
The roadmap david built
Front end
Thirteen storefronts onto one enterprise commerce instance with shared catalog, checkout and order management. Largest brands first.
Enterprise resource planning
A cloud ERP chosen on price and fit, in three phases: purchasing and finance, then inventory and warehouse, then reporting.
Customer service
A service platform for the call center, so 90% of what an agent did in a day happened on one screen.
The fires
First, a hundred-day plan: daily standups, a help desk, a second internet circuit, contract developers, and roles to hire.
Staggered and parallel on purpose: each stream its own vendor and phases, so no single go-live could take the business down.
Three decisions that mattered
None of these were the obvious move. All three protected money the company had already spent.
He rebooted the web vendor instead of firing it
The agency had a signed master agreement and a proposal to rebuild on the old edition. David ran a gap analysis of everything the proposal missed, forced a re-scope to the enterprise edition with order management and ERP integration, and had the statement of work rewritten. It was signed at $680,005 with $54,000 in credits for work already done.
He used the flawed system as the bridge
The half-finished ERP was not the destination, but it was the fastest way off the legacy system for order entry. Phase 1 moved order entry into it deliberately and reduced the old system to warehouse work. An interim answer chosen with eyes open beats a big bang.
He priced un-signing a contract
Weeks after an order-management contract was signed, a new executive team asked whether it was needed. David put both paths side by side: cancelling was $181,000 cheaper now and $139,000 more expensive later, with integration code thrown away. The decision was theirs. The numbers were his.
What was delivered
- Technology strategy: three work streams, budgets, timelines, and a cost model showing run-rate parity by the third year
- 240 written requirements and selection matrices for front end, ERP and customer service, through demos and reference checks
- A signed storefront build contract, ERP licenses purchased, and five storefront design cycles approved
- A company help desk live within six weeks; pick-run failures cut from daily crises to two a day within two weeks
- A hundred-day IT plan, change and incident processes, and job descriptions for the leaders the company needed to hire
The record runs February to November 2018. David left before the new systems went live. The company, a private equity portfolio company, was later acquired by a larger e-commerce retailer. Lead consultant and technology lead: David Day, prior to founding Elevate Tech. Client, brand, sponsor and vendor names withheld by policy.
What this means for your company
- Distributors and ecommerce If an order can be changed in one system and shipped from another, you have a decision nobody made.
- Private equity A stalled ERP inside a portfolio company is a second system of record, and the next buyer prices it.
Related service: Independent ERP and system selection.
Not sure where to start?
Take a free three-minute score. If a conversation makes sense, it will offer one.