Enterprise commerce platform
Paint Reorder Platform
The Home Depot | Paint systems and homedepot.com integration
I architected and built the paint-side platform capabilities behind online paint reordering. The work migrated legacy data into a modern cloud platform, established ongoing synchronization, and gave the homedepot.com team a stable contract for finding, configuring, ordering, and saving paint.
Cloud data platformGCPPCFAPI architectureData migrationSystem integration
Legacy to cloudData migrated to a modern cloud platform
One contractA facade insulated .com from paint-system complexity
Browse to orderConfiguration, portfolio, and ordering capabilities
Platform architecture
A stable commerce contract across two generations of systems.
PCF services continued to communicate with legacy paint systems while GCP services worked with the new cloud model. An orchestration facade gave homedepot.com one purposeful API surface instead of exposing either platform's internal structure.
Data modernization
Moved the paint domain without losing continuity.
The migration combined one-time loads and repeatable batch processing with ongoing data flows. I helped shape the relationships and data structures needed to support the new paint platform without interrupting existing capabilities.
- Built migration paths with Dataflow, Cloud Functions, Cloud Storage, and batch jobs.
- Handled initial and one-time loads from multiple legacy database systems.
- Architected continuous flows to keep the old and new platforms synchronized.
- Modeled data around paint catalog, configuration, and customer use cases.
API and contract design
Translated paint-domain complexity into commerce capabilities.
I worked directly on the contract between the paint and homedepot.com teams, then designed the internal APIs and orchestration needed to fulfill it across PCF and GCP.
- Exposed paint catalog and color-search capabilities.
- Returned brand, container size, sheen, formula, and display information.
- Supported changes to color and other compatible configuration options.
- Accepted online orders and returned a coherent processing result.
Customer journey enabled
Enough detail to confidently buy the same paint again.
Paint is not a single SKU choice. A reorder depends on the exact combination of color, formula, brand, product, sheen, and container size, plus pricing and fulfillment context.
- 01Find
Search saved colors and paint catalog data.
- 02Configure
Select compatible brand, size, sheen, and formula.
- 03Price
Resolve quantities, cost, and taxes through ordering systems.
- 04Order
Process the request and provide a clear result to .com.
- 05Remember
Add the paint to the customer's portfolio for future use.
Customer-facing examples
From a configured product to a remembered paint purchase.
These public Home Depot examples show the customer-facing endpoints of the platform work: a paint product defined by color, product line, container size, and sheen, and a purchase history experience that lets customers find a previous mix and change its options before reordering.
Order integration
Connected consumer reordering to an established professional ordering system.
The platform integrated with the existing paint ordering capability previously used largely for contractor and professional shipping workflows. We processed orders received from homedepot.com, coordinated amounts, costs, and taxes, recorded the paint in the customer's portfolio, and returned the outcome through the facade.
Public case-study boundary
Paint-platform ownership, responsibly presented.
This work was completed as a Home Depot employee on the paint-platform side. I did not build the homedepot.com user interface. This case study omits proprietary data models, API contracts, source code, infrastructure details, customer data, internal metrics, and operational procedures.