Drupal Commerce 2.x: Setup, Customization, Launch

Imagine an online furniture store with hundreds of SKUs, where each combination of fabric and legs is a separate product with its own price and stock. On WooCommerce, this would require a dozen plugins and workarounds. Drupal Commerce 2.x handles it out of the box. Architecture based on plugins and YAML configs lets you flexibly describe any product hierarchy. Drupal Commerce is not just a shopping cart; it's a framework for complex e-commerce logic.

Problems We Solve

Standard Drupal modules don't always cover complex e-commerce logic. For example, a product with multiple variations (color, size) and different prices. Or multi-level discounts based on order history. Clients often come to us after failed attempts to adapt WooCommerce to Drupal. When 1C integration is required at the order and stock level, Commerce 2.x performs better.

But that's not all. A real case: a client sells furniture with dozens of fabric and leg combinations. Each combination is a separate SKU with price and stock. In Commerce 2.x, this is handled via Product Variation and custom fields via Field API. Another example: you need to consolidate one order from products in different stores (multi-store). Commerce Stores natively supports separate carts and payment profiles. The development savings are clear: no need to write custom modules for each task.

Why Commerce 2.x Is Better Than Commerce 1.x?

Commerce 2.x was completely rewritten for newer Drupal versions and is incompatible with the first version. Key differences:

If your project is still on Drupal 7, you'll either have to use legacy Commerce 1.x or migrate with a full redesign. Our experience shows that migration from Commerce 1.x to 2.x takes 2–4 weeks depending on customizations.

How We Do It: A Concrete Case

We worked with a furniture retailer that had 500+ SKUs and 30 fabric options. Each fabric variant had its own price and stock level. The client needed:

• Custom variation fields (fabric, leg type)
• Integration with 1C for inventory
• A faceted search for product attributes
• A two-step checkout (address + payment)

We built the solution on Drupal 10 and Commerce 2.x. Product variations were created programmatically, and we used the commerce_stock module for multi-warehouse inventory. The checkout flow was customized with two steps: shipping address and payment. The faceted search used Search API with Solr. Result: checkout time reduced from 4 steps to 2, product upload time cut by 60%, and inventory sync errors dropped by 90%.

Migration from Commerce 1.x? Here's What to Do

Migration is not just data transfer; it's a rework of business logic. Commerce 1.x and 2.x are incompatible: modules, hooks, database structure – everything is different. We develop a migration plan that includes: audit of current functionality, export data to CSV/JSON, writing migration scripts on Migrate API, setting up a new store from scratch. After migration, orders and stock are transferred, and custom checkout flows are rewritten for the plugin architecture.

Basic Installation via Composer

composer require drupal/commerce drupal/commerce_price drupal/commerce_store \
    drupal/commerce_product drupal/commerce_order drupal/commerce_cart \
    drupal/commerce_checkout drupal/commerce_payment drupal/commerce_tax
drush en commerce commerce_product commerce_cart commerce_checkout \
    commerce_payment commerce_tax commerce_order -y
drush cr

Store and Product Type Configuration

Create a store at /admin/commerce/config/stores. Set the base currency, default country, and list of countries for shipping.

Products in Commerce are divided into product (card) and variation (SKU with price). Create product types and variation types via the admin. For programmatic creation, use code:

use Drupal\commerce_price\Price;
use Drupal\commerce_product\Entity\Product;
use Drupal\commerce_product\Entity\ProductVariation;

$variation = ProductVariation::create([
    'type'   => 'default',
    'sku'    => 'CHAIR-BLK-L',
    'price'  => new Price('1499.00', 'RUB'),
    'field_color' => ['target_id' => $colorTermId],
    'field_size'  => 'L',
]);
$variation->save();

$product = Product::create([
    'type'       => 'default',
    'title'      => 'Office Chair',
    'stores'     => [$storeId],
    'variations' => [$variation],
]);
$product->save();

For the catalog, use Views. Set up filters by price, attributes, store. For faceted search, connect Search API and Solr.

Customizing the Checkout Flow for Your Business Logic

Commerce 2.x lets you customize the checkout process via Checkout Flows. You can add or remove steps: login, shipping address, payment, confirmation. If you need a non-standard field, like an order note, create a plugin:

/**
 * @CommerceCheckoutPane(
 *   id = "custom_gift_note",
 *   label = @Translation("Gift note"),
 *   default_step = "order_information",
 * )
 */
class GiftNotePane extends CheckoutPaneBase {
  public function buildPaneForm(array $pane_form, FormStateInterface $form_state, array &$complete_form): array {
    $pane_form['gift_note'] = [
      '#type'  => 'textarea',
      '#title' => $this->t('Message to recipient'),
      '#rows'  => 3,
    ];
    return $pane_form;
  }
}

Connect payment gateways: Stripe, PayPal, YooKassa via respective modules. Configuration includes API keys and mode selection (test/live). We guarantee support for the latest Drupal versions.

Inventory Management and Taxes

Commerce does not include inventory out of the box – use the commerce_stock module. It adds a stock level field to variations and supports multiple warehouses.

use Drupal\commerce_stock\StockServiceManagerInterface;

$stockService = \Drupal::service('commerce_stock.service_manager')
  ->getService($productVariation);
$level = $stockService->getStockLevel($productVariation, $locations);
$stockService->createTransaction(
  $productVariation,
  $locationId,
  [],
  100,
  new Price('0', 'RUB'),
  'RUB',
  TRANSACTION_TYPE_IN,
  []
);

Taxes are configured via the commerce_tax module. Create a tax type, set the rate and territories. For example, 20% VAT for Belarus. Commerce automatically applies the rate based on the customer's address.

What's Included in the Work

1. Requirements analysis and technical specification
2. Drupal and Commerce installation on hosting
3. Store configuration, product and variation types
4. Development of custom checkout steps (if needed)
5. Payment gateway and tax setup
6. Inventory integration
7. Catalog setup with search
8. Testing and administrator training
9. System documentation
10. 1-month warranty

Timeline Estimates

A basic working store takes 1.5 to 2 weeks. A complex project with custom logic takes 3 to 5 weeks. Get a preliminary estimate: we'll help you understand which modules are needed and how long development will take. Contact us to discuss details.

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.