Project Dossier

Served as Software Architect and Systems Technical Partner, designing an e-commerce engine and backend data synchronization pipeline for Bouri Center. The architecture integrated a web-facing retail catalog with an existing corporate ERP legacy system serving a multi-location brick-and-mortar retail chain.

To manage third-party system constraints, the platform decoupled the e-commerce storage layer from the live ERP nodes, structuring the web application database to function as an isolated physical store branch node.

//Core Architecture & System Engineering

• ->Legacy ERP Integration: Designed middleware abstraction layers to decouple multi-location inventory updates from frontend rendering. Treating the web database as an independent branch node allowed the architecture to handle retail stock updates without dependency on real-time third-party API availability.
• ->Data Sanitization Pipelines: Engineered a human-in-the-loop ingestion portal to normalize and sanitize inconsistent vendor data streams. This gateway validated unformatted product listings prior to live production database insertion.
• ->Catalog Indexing: Optimized the relational schema within a customized Drupal architecture to enforce categorical indexing and relational taxonomy trees, ensuring consistent page-load speeds across home and kitchen appliance inventories.

//Engineering Notes / Edge Cases

Conducted system forensics to reverse-engineer required data synchronization formats due to limited documentation from the external ERP vendor. Built schema-validation layers to preserve the transactional integrity of the online catalog over a multi-year deployment lifecycle.

Use Case Case Study: Bouri Center (E-commerce Isolation & Legacy Integration)

//1. Objective & Scope

Architect a retail e-commerce platform integrated with a legacy corporate ERP backend, insulating user-facing systems from inventory state synchronization latency.

//2. Technical Decisions & Implementation

• ->The Branch Node Database Abstraction: Rather than executing synchronous queries against the external ERP system, the web database layer was modeled as an isolated retail store endpoint. Stock balances were batched, verified, and mapped to a local transactional cache schema, mitigating external system latency.
• ->Boundary Ingestion Validation: Implemented a validation schema to evaluate incoming inventory payloads. Data anomalies or duplicate entity definitions were isolated in a staging environment for administrative review before updating core production database tables.
• ->System Modularization: Organized application workflows into independent service modules. Front-end display logic, taxonomy generation pipelines, and backend data processing utilities were decoupled to ensure modifications to consumer interfaces did not affect background synchronization scripts.