Three Years, Not One Lost Order

US Auto Parts Retailer (NDA)

An established US auto parts retailer selling precision engine components, migrating from Magento 1 to Magento 2 Commerce Cloud.

The Essentials

5 Stellar Soft specialists

January 2019 – December 2021

Enterprise Magento 2 Commerce Cloud

Custom anti-fraud & real-time ERP

Tech Stack

Magento 2 Commerce CloudPHPREST API

When the Platform Becomes the Brake

The Short Version

Not a Single Lost Order

Migration with no significant disruption to the store.

Custom Anti-Fraud System

Catches fraudulent orders before anything ships.

ERP in Real Time

Stock, pricing, and orders — no manual reconciliation.

Changing the Engine Without Stopping the Car

The store outgrew Magento 1, but downtime risked revenue and trust — splitting into three technical problems.

Three Technical Problems

Years of Custom Logic

Custom Magento 1 modules had to be rewritten from scratch for Magento 2's architecture, preserving exact behavior.

Live Integrations

The ERP owns stock, pricing, and order processing — breaking sync would mean selling unavailable parts at outdated prices.

New Frontend, Same UX

The frontend was rebuilt while staying recognizable — zero lost orders and a familiar experience.

Stabilize First, Then Move

Key Architectural Decisions

A custom anti-fraud system that scores orders before they reach fulfillment; deep ERP integration with stock, pricing, and orders synced in real time; and Fastly as CDN and caching layer, with Blackfire for profiling and targeted optimization.

Under the Hood of the Migration

Why We Didn't Start With the Migration

An outside audit shows you the architecture, but not how the system behaves in real life. By taking over support of the live Magento 1 store first, we already had that picture by the time Discovery started — removing the single biggest source of surprises during migration.

The Key Discovery Decision: What Not to Migrate

The central question of this phase wasn't how to migrate. It was what not to migrate at all. A full inventory of the custom functionality sorted it into three buckets: port with the logic intact, rewrite for the new architecture, or drop entirely. The third bucket turned out to be substantial — some of what had accumulated over the years was no longer in use, or duplicated capabilities Magento 2 covers out of the box. Every module that didn't make the trip is migration time saved and future maintenance cost taken off the client's books.

Two Worlds, One Warehouse

The hardest part wasn't rewriting code. It was making the old and new platforms coexist. Magento 1 had to keep selling while Magento 2 filled up with data and logic. The ERP had to work with both, and the client's business processes — taking orders, picking, shipping — weren't supposed to notice anything shifting underneath them. That's why the migration was broken into controlled steps with verification at each one, rather than one big switch.

Why the Anti-Fraud System Had to Be Built From Scratch

Off-the-shelf tools score orders against universal signals that translate poorly to a narrow niche. What looks anomalous for a typical eCommerce store can be perfectly normal behavior for a wholesale buyer of precision engine components — and vice versa. So we built the fraud detection system ourselves, around the patterns of this specific business. Suspicious orders get flagged before the parts head to shipping, at the point where the loss can still be prevented.

ERP: Why Real Time Was Non-Negotiable

Two-way sync over REST API: stock levels and pricing flow from the ERP into the store, order data flows back the other way. Real time isn't a technical indulgence here — it's what the niche demands. A specific part for a specific engine model is often a single unit in the warehouse, and being out of sync by minutes means selling something that's already gone.

Stack

Magento 2 Commerce Cloud, PHP, MySQL, REST API (ERP, anti-fraud system), Fastly (CDN, caching), Blackfire (profiling), SendGrid (transactional email), HTML, CSS, Less.

Same Store. Different Engine.

Pages That Don't Keep Customers Waiting

Before: optimization options were exhausted by Magento 1's architecture. After: Fastly took over static delivery and caching, Blackfire surfaced real bottlenecks instead of guesses. Page load times dropped and Core Web Vitals improved — a metric that moves conversion and organic visibility at the same time.

Fraud That Never Reaches the Warehouse

Before: high exposure to fraudulent orders on expensive, easily resold parts. After: the custom anti-fraud system filters out suspicious orders before shipping, protecting both the inventory and the margin from chargeback costs.

The Warehouse and the Store Finally Speak the Same Language

Before: stock and pricing data lived separately from the storefront. After: stock, pricing, and orders sync in real time — fewer cancellations for parts that aren't actually there.

A Migration Customers Never Noticed

Before: high risk of downtime during the transition. After: the move happened with no significant disruption to the store. Returning customers never noticed the platform had changed — which was exactly the client's definition of success.

A Platform That No Longer Stands in the Way

Before: a system past vendor support, holding the business back. After: a scalable Magento 2 Commerce Cloud on current support, where new functionality is built with native tools instead of workarounds.