Selected Engineering Project

Multi-Supplier E-commerce
System

A supplier integration system built for a commercial e-commerce website running on a custom CMS.

The system automated product imports, category mapping, price updates and inventory synchronization from multiple independent suppliers.

Project

Supplier-driven e-commerce catalog

Role

Backend development, import logic and CMS integration

Focus

Supplier imports, category mapping and stock synchronization

Business Challenge

Why the system was needed

The client needed to publish all available products from its suppliers on the website without manually creating and updating every catalog item.

Supplier data arrived through different sources and structures. The main challenge was not simply reading files, but turning inconsistent external product data into a predictable catalog structure inside the CMS.

Architecture Overview

High-Level System Flow

Supplier Sources

Supplier API
Supplier XML
Supplier YML

Import Layer

Collects data from multiple supplier sources in different formats and schedules.

Category Mapping

Matches supplier categories with the internal category structure.

Product Transformation

Normalizes and enriches product data to fit the internal product model and business rules.

Price and Stock Update

Calculates prices and margins, updates availability and stock levels in real time.

Custom CMS

Manages content, categories and product information through a unified administration system.

E-Commerce Website

Displays products, prices and availability to customers on the storefront.

Key Engineering Decisions

Practical design choices

Shared Import Workflow

Suppliers delivered data through different formats, including XML, YML and APIs.

Rather than developing completely independent import solutions for every supplier, the project adopted a shared processing workflow wherever possible.

This reduced duplicated logic and made future supplier integrations easier to maintain.

Category Mapping

Supplier categories did not match the website structure directly. A supplier taxonomy could be too broad, too narrow or simply organized differently.

The system needed a mapping layer that translated supplier categories into the website catalog structure before products were saved into the CMS.

Working With an Existing Platform

The objective was to extend an established commercial CMS rather than replace it.

Introducing a separate product management system would have increased complexity without providing additional value for the project's requirements.

The solution focused on integrating supplier automation while preserving the client's existing administration workflows.

Inventory Expiration Strategy

Products disappearing from a supplier feed are not always permanently unavailable. A feed may be incomplete, delayed or temporarily broken.

Instead of setting stock to zero immediately, the system marks products as unavailable only after they remain absent from supplier data for a defined period.

Technology Stack

Implementation

Backend and CMS

PHP · MySQL · custom CMS · product catalog logic

Supplier data

XML · YML · API · scheduled imports · automated stock updates

Confidentiality

Commercial Confidentiality

This overview intentionally omits client-specific business information, individual website names, implementation details and proprietary logic. Its purpose is to demonstrate the engineering approach behind a long-running CMS while respecting commercial confidentiality.

Contact

Let's discuss your project

Get in touch