Building an Ecommerce Store on Spree: From Monolith to Headless

A client asked to add a "buy 3, get the 4th free" promo with order history validation. In Shopify, this would require a third-party app with a separate subscription; in Spree — 50 lines of a decorator. Spree Commerce is an open-source Rails Engine we use for projects requiring deep customization. In this article, we'll show how to set up monolith or headless architecture and cover real examples.

Why Choose Spree: Monolith or Headless?

Spree embeds into a Rails application as an Engine and shares the same database. Starting from version 4.3, headless mode via REST API v2 allows using Spree as a backend for React/Vue frontends. This suits both simple server-rendered stores and complex SPAs. Let's compare.

How to Set Up Spree for Your Project?

Environment setup includes installing required gems and running generators. Standard installation: add gems, run generators, migrate database. Common pitfalls: incorrect database config or gem version conflicts.

# Gemfile
gem 'spree', '~> 4.10'
gem 'spree_auth_devise', '~> 4.6'
gem 'spree_gateway', '~> 3.10'
gem 'spree_backend', '~> 4.10'
gem 'spree_sample', '~> 4.10'   # sample data

# For headless:
gem 'spree_api', '~> 4.10'

bundle install
bin/rails g spree:install
bin/rails g spree:auth:install
bin/rails db:migrate
bin/rails db:seed

After installation, you get:

• /admin — admin panel
• /api/v2/storefront — REST API for frontend
• / — classic storefront (if spree_frontend is installed)

Spree Data Model

Spree's database revolves around key entities: stores (multi-store support), categories (nested via ancestry), products with variants (SKU, price, options), orders with line items, payments and shipments, users.

Spree::Store
├── Spree::Taxon (categories via ancestry)
├── Spree::Product
│   ├── Spree::Variant
│   ├── Spree::Price
│   └── Spree::Image
├── Spree::Order
│   ├── Spree::LineItem
│   ├── Spree::Payment
│   └── Spree::Shipment
└── Spree::User (via spree_auth_devise)

Building a Headless Store with Next.js and Spree API

For headless projects, we use @spree/storefront-api-v2-sdk and work via REST API. In one project, we replaced the monolith storefront with Next.js 14 and ISR, achieving LCP under 0.8 seconds — a significant improvement in Core Web Vitals. React Server Components allow fast server-side rendering of product pages.

// lib/spreeClient.ts
import { makeClient } from "@spree/storefront-api-v2-sdk";
export const client = makeClient({ host: process.env.NEXT_PUBLIC_SPREE_URL! });

// Fetch products
const products = await client.products.list(
  { include: "default_variant,images,taxons", filter: { taxons: taxonId } },
  { sort: "name", page: 1, per_page: 24 }
);

// Create cart
const cart = await client.cart.create();
const orderToken = cart.success().data.attributes.token;
await client.cart.addItem({ orderToken }, { variant_id: variantId, quantity: 1 });

Customizing Business Logic Without Forking

Spree uses the decorator pattern: we add methods and associations in a module that is mixed into the model. This extends functionality without touching the core.

# app/models/spree/product_decorator.rb
module Spree
  module ProductDecorator
    def self.prepended(base)
      base.has_many :bundle_parts, class_name: "Spree::BundlePart", foreign_key: :bundle_product_id
    end
    def bundle?
      bundle_parts.any?
    end
    def effective_price_for(quantity)
      if quantity >= 10 then price * 0.9
      elsif quantity >= 5 then price * 0.95
      else price; end
    end
  end
end
Spree::Product.prepend(Spree::ProductDecorator)

For promotions, use the built-in Spree::Promotion system. For example, a "15% off orders over 2000 rubles" rule:

promotion = Spree::Promotion.create!(
  name: "Summer 15% discount", code: "SUMMER15",
  starts_at: Date.today, expires_at: 3.months.from_now,
  usage_limit: 1000
)
promotion.actions.create!(
  type: "Spree::Promotion::Actions::CreateAdjustment",
  calculator: Spree::Calculator::FlatPercentItemTotal.create!(preferred_flat_percent: 15.0)
)
promotion.rules.create!(
  type: "Spree::Promotion::Rules::ItemTotal",
  preferred_operator: "gte", preferred_amount: 2000.0
)

This flexibility allows complex promos without extra plugins.

What's Included in the Work: Full Development Cycle

We offer turnkey development. Project stages:

The result includes: API documentation, repository and server access, client team training, 30-day warranty on bugs. Our engineers have 10+ commercial Spree projects.

Payment Integration and Multi-Currency

spree_gateway provides ready adapters for Stripe, Braintree, PayPal. For YooKassa or Tinkoff, we write a custom gateway (implementing Spree::Gateway interface). Multi-currency is configured via store attributes: set supported_currencies and supported_locales. Prices are tied to the variant's currency.

Common Mistakes When Starting with Spree

• Not using decorators — editing core Spree directly makes updates impossible.
• Forgetting N+1 queries in API — always include include in requests.
• Ignoring admin panel performance — for large catalogs, Elasticsearch is needed.
• Not setting up caching — Redis is mandatory for production. Without it, the store slows down with 1000+ products.

How to Choose Between Monolith and Headless?

If your team is strong in Rails and you need a typical store, go with monolith — it's faster to start. If you plan a mobile app, complex frontend, or high load, headless offers flexibility but requires more development resources. Order Spree store development — we will contact you within a day. Get a consultation via the form on the website or in messengers.

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.