case study · E-commerce

Magento 2 platforms at ICUBE

Backend work on Magento 2 storefronts for enterprise brands: catalog services, multi-store and backorder logic, and GraphQL APIs. GraphQL optimization cut client-side requests by 15%.

Role: Backend Developer at ICUBE by SIRCLO
Timeline: 2021–2023
Type: ICUBE by SIRCLO
Stack: Magento 2 · PHP · GraphQL · Docker · n8n

Client project · code under NDA

// request flow
storefront
→ GraphQL API (Magento 2)
→ custom modules: catalog · PO/backorder · billing

Overview

Two years as a backend developer at ICUBE by SIRCLO, building and launching Magento 2 e-commerce platforms for enterprise brands. The individual client projects are listed below.

The problem

Enterprise brands needed storefronts whose catalog, stock availability and checkout rules match how they actually sell, across several store views.

What I built

Catalog services for category and product pages, with store-view and multi-store rules
Availability logic for READY versus PO/backorder products
GraphQL schema and resolver extensions, with batching to avoid N+1 queries
Backend GraphQL APIs for orders, billing and customers with token-scoped access
Docker for containerized development and n8n workflow automation

Architecture

// Request flow

storefront
GraphQL API (Magento 2)
custom modules: catalog · PO/backorder · billing

Results & what I learned

GraphQL optimization reduced client-side requests by 15%. 3 production releases with zero critical post-launch issues.