Free 30-minute AI & automation audit with a senior engineer. You keep the notes. Book yours

Use case · Retail & e-commerce

Keeping product options, swatches and SKUs accurate across every channel

Microservices for product options, color swatches and SKUs, with bulk upload, approval workflow and Kafka sync from PIM, pricing and inventory systems.

Client details are kept confidential. This use case describes the problem and what we built.

The brief

The client is a home-furnishings retailer with a large catalog of configurable products sold online and in stores, supported by an established enterprise commerce storefront.

MultiGenesys engineers built and maintained the services behind its product-option and SKU data: the tools merchandisers use to manage options and swatches, and the integrations that keep that data in step with product, pricing and inventory systems.

The challenge

What needed solving

Highly configurable products

Furniture and home products come in many sizes, finishes, fabrics and colors. Each combination needs its own item number, options and swatch so customers order the right thing.

Manual, error-prone updates

Merchandising teams maintained option and SKU data in spreadsheets, which made bulk changes slow and mistakes hard to catch before they reached the storefront.

Many systems of record

Product information, pricing, inventory and content each came from a different system, and the storefront needed all of them to agree.

The solution

What we built

  1. Option and SKU services

    Spring Boot microservices with an OpenAPI-first contract manage item-number options, option types, size options, color-code swatches, product groups, regions, departments, SKU attributes and stocked SKUs.

  2. Bulk upload and download

    CSV and Excel bulk upload, download and bulk delete with sample templates, file metadata on Amazon S3 and processing through Amazon SQS.

  3. Configurable approval workflow

    A workflow engine with configurable transitions moves changes through review states, with user activity logs and reports.

  4. Real-time sync service

    A Kafka consumer service listens to product-information, pricing, inventory and content events and keeps MongoDB up to date, using ShedLock for safe scheduled jobs.

  5. Catalog and colorization APIs

    A catalog service exposes products, SKUs, swatches and restrictions to other channels, and a ClickHouse-backed service serves high-volume colorization data.

  6. Kubernetes delivery

    Each service ships as a Docker image to Kubernetes with per-environment manifests, built through Jenkins with JaCoCo coverage and Prometheus metrics.

The outcome

What changed

Bulk changes without spreadsheets

Merchandisers update options and SKUs through validated uploads and an approval flow instead of hand-edited files.

One consistent product picture

Event-driven sync keeps options, prices, stock and content aligned with the systems that own them.

Independent, deployable services

Separate services for options, sync, catalog and colorization can be scaled and released on their own.

Technology used

  • Java 17
  • Spring Boot
  • OpenAPI
  • MongoDB
  • Mongock
  • Apache Kafka
  • ClickHouse
  • Amazon S3
  • Amazon SQS
  • Resilience4j
  • MapStruct
  • Docker
  • Kubernetes
  • Jenkins
  • Prometheus

Have a similar problem to solve?

Share a few lines about your project. A senior engineer — not a salesperson — replies within one business day.

Free AI audit Let’s talk