Long aisles of warehouse shelving stacked with cartons.

Home · Work · E-commerce

22 custom ERP modules in 37 weeks for a pre-owned electronics retailer

Case study · E-commerce · Custom ERP

A pre-owned electronics retailer past $9 million a year had outgrown spreadsheets and a stalled ERP pilot. Armstrat embedded with the team and led a custom build: 22 modules, 7 weeks ahead of plan.

Client
A pre-owned consumer electronics retailer selling online and on marketplaces, past $9 million in annual revenue
Engagement
Custom ERP strategy, product data redesign and delivery, with 22 modules built over 37 weeks
Result
All 22 modules delivered 7 weeks ahead of a 44-week plan, a 16% shorter timeline
How we worked
Embedded with the client’s new IT team, leading user stories, sprints and governance, with progress judged against the delivery plan

Published . Client name withheld.

22custom ERP modules delivered in 37 weeks against a 44-week plan

The situation

The retailer sells pre-owned consumer electronics online and across marketplaces. It had grown past $9 million a year and was tracking toward roughly $16 million, but it still ran on fragmented spreadsheets, marketplace tools, informal handoffs and departmental workflows that did not connect. Accounting, inventory, procurement, warehouse and customer service data sat in separate systems, and managers had limited visibility across functions.

A packaged ERP pilot was already underway when Armstrat engaged, chosen because it looked cost-effective. It stalled at the warehouse and operations end. The pilot made the real need clear: the business did not just need software. It needed a custom operating backbone for product data, procurement, warehouse work, customer service and reporting.

What made it hard

  • No two products were identical. Condition, compatibility, bundles, accessories and platform-specific listing needs varied item by item, across a catalog of more than 20,000 products whose data was not ready for an ERP.
  • The packaged ERP did not offer the required workflows out of the box, and adapting it risked taking longer than building around how the business actually worked.
  • The system had to be built and rolled out while the business kept running, with no clean window to stop and switch over.
  • Warehouse and operations teams had struggled with earlier system rollouts, largely because of unfriendly interfaces, so adoption risk was high.
  • Teams worked remotely and in silos, which produced inconsistent handoffs and duplicated work. The new system had to win people over, not just function.
An analytics dashboard with charts on a computer screen.

How we worked

Armstrat worked inside the business rather than advising from outside. It led and governed the client’s new IT team, from writing user stories to managing each development cycle, and stayed through rollout module by module. Progress was judged by outcomes, not activity: working modules in the hands of users, measured against a 44-week plan.

  1. 01

    Use the pilot as a diagnostic

    Rather than forcing the stalled packaged ERP pilot to work, Armstrat used it to map where processes were complex, where adoption broke down and which workflows the business required. That evidence supported the move to a custom system built around the retailer’s real operations.

  2. 02

    Rebuild the product data first

    Armstrat redesigned the SKU and product database for more than 20,000 products in about 15 days. It became the foundation for inventory, procurement and reporting, with a structure flexible enough to handle condition, compatibility, bundles and accessories.

  3. 03

    Build modular, release in sprints

    Instead of waiting for a complete waterfall build, the ERP was designed as a set of modules delivered in two-week sprint cycles. Armstrat led the client’s new IT team through user stories, development and rollout, so each module could create value before the full system was finished.

  4. 04

    Design with the end users

    Each module was shaped with input from the department that would use it, with operational control, customer communication and management visibility at the center. Users gave feedback sprint by sprint, making the build a change-management effort aimed at participation and buy-in.

  5. 05

    Tie the system to operations

    Armstrat connected ERP development with a wider redesign of the operating model across warehouse, procurement, customer service and reporting. The aim was cross-functional control and visibility, not just new software.

The results

Measured against the outcomes agreed at the start.

22
  • Delivered 22 custom ERP modules in 37 weeks against a planned 44 weeks, 7 weeks early and a 16% shorter timeline.
  • Redesigned the product and SKU database for more than 20,000 products in about 15 days, creating the data foundation for inventory control, sourcing, reporting and marketplace operations.
  • Replaced spreadsheet-heavy workflows with centralized ERP processes across six to eight core business functions.
  • Cut manual reconciliation by an estimated 40 to 60% and improved cross-functional visibility by an estimated 60 to 75%.
  • Saved an estimated 80 to 120 hours a week in manual coordination, duplicate data entry, spreadsheet upkeep and informal follow-ups.

What leaders can take from it

  • For a growing business with messy operations, ERP is not just a technology project. It is an operating model project, and the processes, handoffs and controls need redesigning alongside the software.
  • Test off-the-shelf ERP against real workflows before paying for expensive customization. A pilot can work as a diagnostic, showing where the package fits and where building around your own operations is faster.
  • Adoption is designed, not announced. Modules built with input from the teams that use them, and released in small increments, create value sooner and earn buy-in that a big-bang launch rarely gets.

Questions about this work

Should a growing retailer build a custom ERP or customize an off-the-shelf one?

Test the off-the-shelf option against real workflows first. If it cannot handle how the business actually runs, customization can become slower than building. For a pre-owned electronics retailer with condition-based products, Armstrat used a stalled packaged ERP pilot as a diagnostic, then led a modular custom build that delivered 22 modules in 37 weeks against a 44-week plan.

How do you get warehouse teams to adopt a new ERP?

Involve warehouse teams in designing it and release it in small pieces. At this retailer, earlier rollouts had struggled largely because of unfriendly interfaces. Armstrat designed each module with input from the department that would use it, released modules in two-week sprints with active user feedback, and treated the implementation as a change-management effort to build participation and buy-in.

Bring us the hard problem.

We agree the outcomes first, then work inside your business until they hold.