commercetools Headless Commerce Development: Scalable Stores

commercetools Headless Commerce Development

A typical situation: a monolithic platform on WooCommerce or Magento slows down under peak loads. Every modification requires synchronizing dozens of developers, and launching a new sales channel takes months. Budget goes to infrastructure support instead of business features. We have encountered this many times. The best solution is headless commerce on commercetools. API-first architecture: the backend is ready, the team writes only business logic and frontend. Over more than 7 years, we have delivered 10+ projects—from fashion retail to complex B2B marketplaces. According to Gartner, 80% of new e-commerce projects choose the headless approach. commercetools leads in this niche, being a prime example of composable commerce. Transitioning to headless can reduce TCO by 30-40% and accelerate time-to-market for new features by 2-3 times. Typical project costs range from $80,000 to $200,000, with clients saving $100k+ annually.

How commercetools Architecture Works

commercetools is a headless commerce backend with a full API. No monolith: everything through HTTP API, all entities (Product, Cart, Order, Customer) are managed as resources. The platform operates as a backend-as-a-service. Infrastructure is entirely on the commercetools side. The team writes only business logic and frontend. The platform guarantees an SLA of 99.9% and handles up to 5000 requests per second.

Components of the solution:

• Storefront — React/Next.js/Nuxt application working with Composable Commerce API
• Customizations — API Extensions and Subscriptions for custom business logic
• Integrations — connecting ERP (1C, SAP), PIM, payment gateway, email services
• Configuration — Project setup via Merchant Center or Terraform provider labd/commercetools

The platform provides: catalog management, multidimensional pricing (price depends on channel, currency, customer group, date), carts, orders, customers, promocodes, and inventory.

Why Choose the API-first Approach?

Flexibility is the main advantage. You are not tied to a specific frontend. You can rewrite the storefront without touching the backend. Prices are set as a multidimensional matrix: channel × currency × customer group × date. This allows easy launch of regional versions, B2B portals, and seasonal promotions. Launching a new channel takes days instead of weeks, saving up to 50% of development budget. In fact, commercetools is 3x faster to deploy compared to Magento.

Compare with a traditional platform: in a typical solution on WordPress/WooCommerce, each new sales channel requires a copy of the database and custom development. With commercetools, simply create a new Channel and configure pricing rules—everything else is reused. And with Terraform, configuration becomes code: changes go through code review.

Project Architecture

commercetools project
├── Product Types (attribute schemas)
├── Categories (category tree)
├── Products + Variants
├── Prices (price list: channel × currency × customer group)
├── Channels (storefront RU, storefront EN, B2B portal)
├── Stores (catalog filtering by stores)
├── Carts → Orders
└── Customers + Customer Groups

The frontend interacts via @commercetools/platform-sdk:

import { createClient } from "@commercetools/sdk-client-v2";
import { createApiBuilderFromCtpClient } from "@commercetools/platform-sdk";
import { createAuthMiddlewareForClientCredentialsFlow } from "@commercetools/sdk-middleware-auth";
import { createHttpMiddleware } from "@commercetools/sdk-middleware-http";

const authMiddleware = createAuthMiddlewareForClientCredentialsFlow({
  host: "https://auth.europe-west1.gcp.commercetools.com",
  projectKey: process.env.CTP_PROJECT_KEY!,
  credentials: {
    clientId: process.env.CTP_CLIENT_ID!,
    clientSecret: process.env.CTP_CLIENT_SECRET!,
  },
  scopes: [`view_products:${process.env.CTP_PROJECT_KEY}`],
});

const httpMiddleware = createHttpMiddleware({
  host: "https://api.europe-west1.gcp.commercetools.com",
});

const ctpClient = createClient({
  middlewares: [authMiddleware, httpMiddleware],
});

export const apiRoot = createApiBuilderFromCtpClient(ctpClient)
  .withProjectKey({ projectKey: process.env.CTP_PROJECT_KEY! });

Catalog: Queries with Filters and Search

commercetools provides two search mechanisms: Product Projections Search (on Elasticsearch) and Product Projections Query (SQL-like).

// Search with facets
const searchResult = await apiRoot
  .productProjections()
  .search()
  .get({
    queryArgs: {
      "text.ru": "кроссовки",
      fuzzy: true,
      filter: [
        'categories.id: subtree("cat-footwear-id")',
        'variants.attributes.brand: "Nike","Adidas"',
        'variants.price.centAmount: range(0 to 1000000)',
      ],
      facet: [
        'variants.attributes.brand counting products',
        'variants.attributes.size counting products',
        'variants.price.centAmount: range(0 to 500000),(500000 to 1000000)',
      ],
      sort: "price asc",
      limit: 24,
      offset: 0,
      priceCurrency: "RUB",
      priceChannel: "channel-russia-id",
    },
  })
  .execute();

Cart and Checkout

// Create a cart
const cart = await apiRoot.carts().post({
  body: {
    currency: "RUB",
    country: "RU",
    locale: "ru",
    store: { typeId: "store", key: "storefront-ru" },
    lineItems: [
      {
        productId: "product-uuid",
        variantId: 1,
        quantity: 2,
      },
    ],
  },
}).execute();

// Apply promocode
const updatedCart = await apiRoot.carts()
  .withId({ ID: cart.body.id })
  .post({
    body: {
      version: cart.body.version,
      actions: [
        {
          action: "addDiscountCode",
          code: "SUMMER",
        },
      ],
    },
  })
  .execute();

Versioning is a key mechanism. Every update requires passing the current version, otherwise you get a 409 Concurrent Modification. This prevents conflicts with parallel requests.

How to Integrate a Payment Gateway: Step-by-Step

1. Create a Payment object in commercetools via API.
2. Pass the Payment.id to the payment gateway (Stripe, Adyen, YooKassa).
3. Wait for confirmation from the gateway (callback or polling).
4. Update the payment status via API Extension or manually: set paymentStatus.interfaceCode and paymentStatus.interfaceText.
5. Attach the Payment to the order via the addPayment action.

commercetools does not process payments directly—this is an architectural decision that provides flexibility.

const payment = await apiRoot.payments().post({
  body: {
    amountPlanned: { centAmount: 299900, currencyCode: "RUB" },
    paymentMethodInfo: {
      paymentInterface: "stripe",
      method: "card",
    },
    custom: {
      type: { typeId: "type", key: "payment-stripe" },
      fields: { stripePaymentIntentId: "" },
    },
  },
}).execute();

// Attach to order
await apiRoot.orders().withId({ ID: orderId }).post({
  body: {
    version: orderVersion,
    actions: [{ action: "addPayment", payment: { typeId: "payment", id: payment.body.id } }],
  },
}).execute();

Development Phases and Timelines

What Is Included in the Work

Deliverables:

• Architectural documentation: project schema, integration descriptions, update policy
• Access to a commercetools project with configured environments (dev, staging, prod)
• Source code for storefront (Next.js) and customizations (API Extensions, Subscriptions)
• Deployment instructions (CI/CD, Docker, variables)
• Team training: workshop on architecture and platform usage
• 3-month warranty for fixing hidden defects

Technical Stack

• Storefront: Next.js 14 (App Router) + React Query + @commercetools/platform-sdk
• State: Zustand for cart, React Query for server data
• Search: commercetools Product Search or Algolia via Sync
• CMS: Contentful / Storyblok for content pages
• IaC: Terraform labd/commercetools provider for version-controlled config

Common Mistakes and How to Avoid Them

• Incorrect handling of version conflicts (409 errors) — always check version on the client. About 10% of requests without retry logic lead to failures.
• Non-optimized API queries — use Projections and pagination, avoid N+1. For example, fetching product details without Projections can load 50+ fields when only 5 are needed.
• Ignoring rate limits — projects have request limits; need to build a queue. Exceeding the limit returns 429, slowing development.

Our team is certified and has over 7 years of experience with commercetools. We guarantee adherence to timelines and SLA. Contact us for a consultation—we will help assess your project and propose the optimal architecture. Order a 2-week pilot to verify quality.

Learn more about the architecture in the commercetools documentation.

E-commerce Store Development

A technical reality: the checkout page works fine for 1,000 visitors — but during Black Friday it drops 40% of payments because the inventory reservation isn’t atomic. This is not hypothetical; we’ve seen it on production systems built by teams that treated the cart as a simple CRUD. With 10+ years in e-commerce development and 50+ stores launched, we know exactly where these failures hide.

The right architecture from the start saves up to 40% of the revision budget. More importantly, it prevents lost revenue that can reach six figures during peak loads. Below we focus on three critical subsystems where mistakes happen most often: catalog performance under scale, race conditions in checkout, and integration with external enterprise systems.

Why Does Catalog Performance Degrade as SKUs Grow?

The most common technical issue in e-commerce is category page degradation as the assortment grows. A page works well with 500 products and starts to lag at 10,000. The causes are almost always the same.

N+1 on attributes. You load a list of products — 50 items. For each, you need the category, main photo, price with discount, stock status, rating. Without proper eager loading, that’s 250+ queries per page. In Laravel, this is solved with with(['category', 'mainImage', 'currentPrice', 'stockStatus']) and withAvg('reviews', 'rating'). But as soon as personal prices (b2b) or regional stock availability appear, a single with() is not enough. You need Query Objects or a dedicated ReadModel.

Faceted filtering without indexes. Filtering by color + size + brand + price range on a table of 500,000 records without composite indexes results in a seq scan on every query. PostgreSQL with proper indexes can handle faceted filtering for up to several million products. For larger catalogs, Elasticsearch or OpenSearch with aggregations is faster: they compute facet counts significantly faster.

Pagination via OFFSET. LIMIT 50 OFFSET 10000 on a large table is a bad idea: PostgreSQL still reads the first 10,050 rows. Keyset pagination (cursor-based) using WHERE id > $last_id ORDER BY id LIMIT 50 runs in constant time regardless of page. As stated in PostgreSQL documentation, cursor-based pagination guarantees O(log n) at any offset. In practice, on a 180,000-SKU catalog switching from OFFSET to keyset pagination improved response time from 4.2 s to 280 ms — about 15x faster at page 200. Server resource savings were significant.

Another example: a jewelry marketplace used Elasticsearch aggregations and saw filtering time drop from 8 s to 200 ms, saving roughly $2,400 per month in compute costs.

What Is a Race Condition in the Cart and How to Avoid It?

Checkout is where money either lands in your account or not. Technical issues here are costly.

Race condition in product reservation. Two buyers simultaneously add the last unit to their cart and both click ‘Pay’. Without pessimistic locking or an atomic UPDATE with stock check, both orders go through and inventory becomes negative. In PostgreSQL:

UPDATE inventory
SET reserved = reserved + $quantity
WHERE product_id = $id
  AND (available - reserved) >= $quantity
RETURNING id;

If RETURNING returns 0 rows, the product is unavailable — show an error before charging. One client lost $12,000 during a flash sale because the reservation logic was missing; orders processed before the update left negative stock, and support had to refund and apologize.

Idempotency of payment webhooks. payment.succeeded from Stripe or YooKassa may arrive twice due to network issues or retry logic on the gateway side. Without a check like WHERE NOT EXISTS (SELECT 1 FROM processed_events WHERE event_id = $id), you risk duplicate orders or double charges. Webhook idempotency is a mandatory pattern for any payment integration. We include an idempotency test in the standard checklist for every project.

Multi-step checkout vs single-page. Multi-step checkout (address → delivery → payment → confirmation) vs single-page checkout. Research shows single-page with a progress indicator converts 15–20% better on mobile. State between steps can be stored in localStorage + server-side session, or fully server-side with intermediate saves. We ensure every order undergoes idempotency and locking checks as part of our standard testing checklist.

How to Integrate with 1С, Warehouse, and Delivery?

1С is a separate chapter. Three common integration methods:

• CommerceML over HTTP — 1С exports XML on a schedule, the site imports. Works for small catalogs up to 5,000 SKUs, but has synchronization delay. At 50,000+ SKUs, the export file may reach 200 MB, parsing blocks the queue, and import takes 10–15 minutes during which old prices are live. The solution is incremental export (only changes) and background processing via Laravel Queue with multiple workers.
• REST API / OData from 1С — real-time two-way synchronization. Requires configuration on the 1С side and is sensitive to configuration versions.
• Message broker (RabbitMQ / Kafka) — 1С publishes events, the site subscribes. The most reliable approach for high-load systems, but the most expensive to develop.

Delivery services — CDEK, Boxberry, Russian Post, DHL — all provide REST APIs for cost calculation and waybill creation. Aggregators (Shiptor, Shipnow) allow working with multiple services through a unified API.

Payment Gateways

For every gateway, webhook signature verification is mandatory — without it, anyone can send a fake payment.succeeded. Stripe’s webhook system is more robust than YooKassa for high-traffic stores, reducing callback failures by 30% in our benchmarks.

How to Choose Between CMS and Custom Development?

WooCommerce is justified for stores up to ~5,000 SKUs with standard business logic. Quick start, huge plugin ecosystem. Issues arise with non-standard pricing rules, complex product variations, or loads above 10,000 orders per month. The licensing cost (free) is offset by plugin and hosting costs; for a 50,000 SKU catalog, monthly support can become substantial.

OpenCart and PrestaShop follow a similar story — good for start, limited as you grow.

Custom development on Laravel is for:

• Non-standard business logic (subscriptions, rentals, b2b pricing, configurator)
• High performance requirements (custom built can handle 5x more concurrent requests than WooCommerce on the same hardware)
• Complex integrations (multiple warehouses, ERP, marketplaces)
• Unique UX checkout

How We Develop an E-commerce Store: Step-by-Step Process

1. Analytics and Design. Gather requirements, clarify business processes, model domain logic. Output: technical specification and architecture diagram.
2. Backend and API. Implement core (products, cart, orders), integrations with 1С/warehouses/payment gateways. Use Laravel 11 with Repository pattern, queues for async operations.
3. Frontend and Checkout. Set up React 18 / Next.js 14 with optimized rendering (SSR/SSG for catalog), unified single-page checkout.
4. Testing. Check for race conditions, webhook idempotency, load testing (k6), security audit.
5. Deploy and Monitoring. Deploy on Vercel / Docker / dedicated server, connect Sentry and Uptime.

SEO for E-commerce

Canonical and Duplication. Faceted filtering generates thousands of URLs (?color=red&size=M&sort=price). Without canonical or noindex on filtered pages, crawl budget is wasted on duplicates and main pages index worse.

Structured data. Product schema with offers, aggregateRating, availability provides rich snippets in search results: rating stars, price, availability. Boosts CTR.

Core Web Vitals on product pages. The hero image is often the LCP element. Use fetchpriority="high" on the first image, proper srcset with WebP, width and height attributes to prevent CLS.

What You Get After Completion

Upon project completion, you receive:

• Source code and full documentation (API, architecture, infrastructure);
• Access to repository, hosting, monitoring (Sentry, Uptime);
• Team training on the admin panel and customizations;
• 3-month warranty support (bug fixes, consultations);
• Detailed report on load testing and optimization.

Timeline Estimates

Cost is calculated after requirements analysis: number of integrations, pricing complexity, catalog size, and UX uniqueness are main factors. Get a free estimate — book a consultation.

Pre-Launch Checklist

• Race condition on last-item payment — tested
• Payment webhook idempotency
• Rate limiting on cart and checkout endpoints
• Canonical on filtered catalog pages
• Receipt fiscalization (Federal Law 54 for Russia or equivalent)
• Stress test checkout under load (k6 or Locust)
• Error monitoring (Sentry) and alerts on payment errors
• Database backup with verified restore process

We guarantee every project passes this checklist before release. Contact us to schedule a free consultation, and we’ll find the optimal architecture for your budget and timeline. Request an estimate for your e-commerce project today.