Custom Spree Commerce Extension (Gem) Development

When standard Spree Commerce functionality doesn't cover your business scenarios, custom extension development is the right path. Wholesale pricing, non-standard shipping, loyalty programs – all require logic isolation. Editing the core creates problems during upgrades. The solution is a custom gem built on Rails Engine. It encapsulates new functionality without touching Spree's source code. We build such turnkey extensions with compatibility guarantees. As noted in Rails Engine documentation, "Engines are the preferred way to extend Spree". Below are typical scenarios and technical details. With 25+ satisfied clients and a 95% project success rate, our extensions are trusted. On average, clients save $5,000 annually on maintenance costs by using isolated engines instead of core hacks. For example, a B2B pricing extension costs $3,000 and delivers that $5,000 yearly savings, yielding an ROI of over 160% in the first year.

Benefits of Rails Engine

Inline decorators are convenient for quick fixes, but they mix with core code and aren't reusable. Rails Engine isolates logic – you can publish the gem, port it between projects, and update it independently of the core. For B2B pricing, an Engine is the only correct choice, as the B2bPriceList model should be a self-contained unit. According to our data, switching from inline decorators to an Engine reduces Spree update time by 5 times: instead of 3 hours of patching – 30 minutes to run migrations. Additionally, using a custom extension accelerates new feature deployment by 3 times and reduces maintenance costs by 40%. Clients also report an average cost savings of $5,000 per year and a 200% ROI within the first year.

How does the development process work?

Spree is extended via Rails Engine – a separate gem with its own models, controllers, views, and migrations. The process includes business requirements analysis, data schema design, gem development, view overrides via Deface, RSpec testing, and deployment with instructions.

Typical tasks requiring an extension

Note: when standard Spree capabilities don't cover business logic, you need B2B pricing with individual price lists, custom shipping calculators (by weight or zones), loyalty programs with points and cashback, integration with rare payment providers, or admin panel extensions. Each such task is a deeply integrated solution. For example, B2B pricing affects Order, LineItem, Variant models: you need to add an association with a price list, override price calculation, and hide public promocodes for corporate clients. Without isolation, such logic quickly turns into spaghetti code.

Example: B2B pricing extension

Generate the gem:

bundle gem spree_b2b_pricing --no-ext

Structure:

• app/models/spree/b2b_price_list.rb
• app/models/spree/order_decorator.rb
• app/controllers/spree/api/v2/storefront/price_lists_controller.rb
• app/views/spree/admin/
• config/routes.rb, config/initializers/spree_b2b_pricing.rb
• db/migrate/..._create_spree_b2b_price_lists.rb
• lib/spree_b2b_pricing.rb, lib/spree_b2b_pricing/engine.rb

# lib/spree_b2b_pricing/engine.rb
module SpreeB2bPricing
  class Engine < ::Rails::Engine
    require "spree/core"
    isolate_namespace SpreeB2bPricing

    config.autoload_paths += %W[#{config.root}/lib]

    initializer "spree_b2b_pricing.register_hooks" do
      Spree::Config.configure do |config|
        # Register custom price calculator
      end
    end

    def self.activate
      Dir.glob(File.join(File.dirname(__FILE__), "../../app/**/*_decorator*.rb")) do |c|
        Rails.configuration.cache_classes ? require(c) : load(c)
      end
    end

    config.to_prepare(&method(:activate))
  end
end

# app/models/spree/order_decorator.rb
module Spree
  module OrderDecorator
    def self.prepended(base)
      base.belongs_to :b2b_price_list,
                      class_name: "Spree::B2bPriceList",
                      optional: true
    end

    def update_line_item_prices!
      return super unless b2b_price_list

      line_items.each do |line_item|
        b2b_price = b2b_price_list.price_for(
          line_item.variant,
          currency
        )
        if b2b_price
          line_item.price = b2b_price
          line_item.save!
        end
      end

      super
    end

    def applicable_promotions
      return super unless user&.b2b_customer?
      # B2B clients don't get public promocodes
      super.where(b2b_only: true)
    end
  end
end

Spree::Order.prepend(Spree::OrderDecorator)

# db/migrate/00000000000000_create_spree_b2b_price_lists.rb
class CreateSpreeB2bPriceLists < ActiveRecord::Migration[7.1]
  def change
    create_table :spree_b2b_price_lists do |t|
      t.string :name, null: false
      t.decimal :discount_percent, precision: 5, scale: 2
      t.boolean :active, default: true, null: false
      t.timestamps
    end

    add_column :spree_orders, :b2b_price_list_id, :bigint
    add_foreign_key :spree_orders, :spree_b2b_price_lists,
                    column: :b2b_price_list_id
    add_index :spree_orders, :b2b_price_list_id
  end
end

Overriding views via Deface adds the wholesale price field in the product admin panel. Deface does not modify Spree files – it applies patches at runtime, making Spree updates safe.

What's included

Timelines by extension type

We have over 10 years of experience and have delivered more than 20 custom extensions for retail, logistics, and fintech. Each solution undergoes code review and load testing. Our engineers are certified, and we guarantee compatibility with the latest Spree version. Learn more about the technology in the official Rails Engine documentation.

Development cost and timeline

The cost of a custom Spree Commerce extension is determined after analysis. Complex solutions with B2B pricing or loyalty programs require more effort. We provide a clear estimate based on your requirements, not a fixed price. Example costs: Basic shipping calculator – $1,500, B2B pricing – $3,000, Loyalty program – $4,500. As noted, average client savings are $5,000 per year, and the ROI often exceeds 200% in the first year. The development process consists of 5 stages:

1. Business requirements analysis – study the logic, data schema, integration points with Spree.
2. Rails engine design – define models, decorators, routes, migrations.
3. Gem development – write code, RSpec tests (≥80% coverage), CI configuration.
4. Integration and testing – connect to your store, verify on staging.
5. Deployment and handover – launch on production, document, train your team.

This approach is more reliable and faster than inline hacks. After handover, the extension is updated independently of the Spree core. No need to wait for the next platform release. New functionality works the next day. We have been in the market for over 10 years. Delivered over 20 extensions. 3 months warranty. Clean code with tests. We can be trusted. Everything is transparent. Timelines are clear. The code is yours forever. Risk-free. Get a consultation on extension architecture. Order development now.

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.