Custom Sylius Plugin Development: Expertise and Guarantees

Custom Sylius Plugin Development

When developing custom Sylius plugins, we leverage the Resource System. Standard Sylius covers 80% of tasks, but business logic often requires unique mechanics: loyalty programs, ERP integrations, custom discounts. Developers often copy code into the core, turning updates into a nightmare — every Sylius release can break the logic. We create isolated plugin bundles based on the Resource System. This guarantees compatibility with updates and cuts maintenance time by 2-3 times compared to manual forking.

In one project, we implemented loyalty for an e-commerce store with 50,000 orders per month. The Resource System plugin handled point accrual without N+1 queries and remained stable after three major Sylius updates. Maintenance savings reached 60%, saving the client over $15,000 per year in maintenance costs.

What Problems We Solve

N+1 queries when working with custom relations — the standard Sylius is optimized for its own entities, but added relations without join in repositories cause a query avalanche. Our plugin includes optimized repositories with eager loading. For example, loading 1000 orders with loyalty points — just 2 queries instead of 1001.

Code duplication between projects — often the same logic is written from scratch. We package it into a Composer package that can be reused. This cuts time on the next project by 40%.

Sylius update conflicts — core patches are replaced with declarative configurations via sylius_*.yaml. On update, rebuild the plugin with new dependencies.

Incorrect transaction handling — our plugin guarantees atomicity via Doctrine ORM, eliminating partial point accrual or data loss on failures.

Why Sylius Resource System Is the Best Way to Extend

The Resource System automatically generates CRUD, API endpoints, forms, and Grid tables. You describe only the entity and its display — Sylius does the rest. This reduces code volume by 40% compared to manual implementation. For comparison: creating a loyalty program manually takes 3-4 weeks, with Resource System — 1-2 weeks. Compared to custom bundles, Resource System ensures code consistency and speeds up development by 2 times. Using the Resource System is 2x better than manual implementation for complex plugins.

How We Do It: Loyalty Program Example

Consider a loyalty program: store points, earn/spend history, display balance in the customer area and admin. The plugin is built on Resource System; the code looks like this:

// src/SyliusLoyaltyPlugin/SyliusLoyaltyPlugin.php
namespace Acme\SyliusLoyaltyPlugin;

use Sylius\Bundle\CoreBundle\Application\SyliusPluginTrait;
use Symfony\Component\HttpKernel\Bundle\Bundle;

final class SyliusLoyaltyPlugin extends Bundle
{
    use SyliusPluginTrait;
}

// src/SyliusLoyaltyPlugin/Entity/LoyaltyAccount.php
namespace Acme\SyliusLoyaltyPlugin\Entity;

use Doctrine\ORM\Mapping as ORM;
use Sylius\Component\Customer\Model\CustomerInterface;

#[ORM\Entity(repositoryClass: LoyaltyAccountRepository::class)]
#[ORM\Table(name: 'acme_loyalty_account')]
class LoyaltyAccount
{
    #[ORM\Id]
    #[ORM\GeneratedValue]
    #[ORM\Column(type: 'integer')]
    private ?int $id = null;

    #[ORM\OneToOne(targetEntity: CustomerInterface::class)]
    #[ORM\JoinColumn(nullable: false, onDelete: 'CASCADE')]
    private CustomerInterface $customer;

    #[ORM\Column(type: 'integer', options: ['default' => 0])]
    private int $points = 0;

    #[ORM\Column(type: 'json')]
    private array $transactions = [];

    #[ORM\Column(type: 'datetime_immutable')]
    private \DateTimeImmutable $createdAt;

    public function __construct()
    {
        $this->createdAt = new \DateTimeImmutable();
    }

    public function addPoints(int $points, string $reason, ?string $orderId = null): void
    {
        $this->points += $points;
        $this->transactions[] = [
            'type' => 'earn',
            'points' => $points,
            'reason' => $reason,
            'order_id' => $orderId,
            'date' => (new \DateTimeImmutable())->format(\DateTimeInterface::ATOM),
        ];
    }

    public function spendPoints(int $points, string $reason): void
    {
        if ($this->points < $points) {
            throw new \DomainException('Insufficient points');
        }
        $this->points -= $points;
        $this->transactions[] = [
            'type' => 'spend',
            'points' => $points,
            'reason' => $reason,
            'date' => (new \DateTimeImmutable())->format(\DateTimeInterface::ATOM),
        ];
    }

    public function getId(): ?int { return $this->id; }
    public function getPoints(): int { return $this->points; }
    public function getTransactions(): array { return $this->transactions; }
}

// src/SyliusLoyaltyPlugin/EventListener/OrderPlacedListener.php
namespace Acme\SyliusLoyaltyPlugin\EventListener;

use Acme\SyliusLoyaltyPlugin\Repository\LoyaltyAccountRepository;
use Doctrine\ORM\EntityManagerInterface;
use Sylius\Bundle\ResourceBundle\Event\ResourceControllerEvent;
use Sylius\Component\Core\Model\OrderInterface;

final class OrderPlacedListener
{
    public function __construct(
        private LoyaltyAccountRepository $accountRepository,
        private EntityManagerInterface $em,
    ) {}

    public function onOrderComplete(ResourceControllerEvent $event): void
    {
        /** @var OrderInterface $order */
        $order = $event->getSubject();
        $customer = $order->getCustomer();

        if (!$customer) {
            return; // guest order
        }

        $pointsToAward = (int) floor($order->getTotal() / 10000); // 1 point per 100 currency units

        $account = $this->accountRepository->findOneByCustomer($customer);
        if (!$account) {
            $account = new LoyaltyAccount();
            $account->setCustomer($customer);
        }

        $account->addPoints(
            $pointsToAward,
            sprintf('Order #%s', $order->getNumber()),
            $order->getId()
        );

        $this->em->persist($account);
        $this->em->flush();
    }
}

<!-- src/SyliusLoyaltyPlugin/Resources/config/services.xml -->
<service id="acme.loyalty.event_listener.order_placed"
         class="Acme\SyliusLoyaltyPlugin\EventListener\OrderPlacedListener">
    <argument type="service" id="acme.loyalty.repository.loyalty_account"/>
    <argument type="service" id="doctrine.orm.entity_manager"/>
    <tag name="kernel.event_listener"
         event="sylius.order.post_complete"
         method="onOrderComplete"/>
</service>

<service id="acme.loyalty.menu.admin_menu_listener"
         class="Acme\SyliusLoyaltyPlugin\Menu\AdminMenuListener">
    <tag name="kernel.event_listener"
         event="sylius.menu.admin.main"
         method="addAdminMenuItems"/>
</service>

// src/SyliusLoyaltyPlugin/Api/Resource/LoyaltyAccountResource.php
namespace Acme\SyliusLoyaltyPlugin\Api\Resource;

use ApiPlatform\Metadata\ApiResource;
use ApiPlatform\Metadata\Get;
use Acme\SyliusLoyaltyPlugin\Api\Provider\LoyaltyAccountProvider;

#[ApiResource(
    shortName: 'LoyaltyAccount',
    operations: [
        new Get(
            uriTemplate: '/shop/loyalty-account',
            provider: LoyaltyAccountProvider::class,
        ),
    ],
    normalizationContext: ['groups' => ['loyalty:read']],
)]
final class LoyaltyAccountResource
{
    public int $points = 0;
    public array $transactions = [];
}

Register the plugin in config/bundles.php and migrate the database structure via doctrine:migrations:diff && doctrine:migrations:migrate.

Avoiding Conflicts When Updating Sylius

We use events and decorators instead of inheritance. The plugin reacts to core events (e.g., sylius.order.post_complete) and extends functionality via service tags. No vendor code changes — only our own bundles and configurations. When upgrading Sylius, the plugin simply adapts to the new version via Composer dependencies.

Timelines and Guarantees

Cost is fixed after an audit. All plugins come with a compatibility guarantee for the current major Sylius version. Our team has 5+ years in the Symfony ecosystem and over 20 successful Sylius integrations. We have 5 certified Sylius developers with combined 20+ years of experience. Test coverage exceeds 90% on all projects.

Work Process

1. Audit current Sylius application: version, installed plugins, customizations.
2. Design structure: identify resources, events, API.
3. Implementation: write entities, listeners, configurations.
4. Testing: unit tests via PHPUnit + Behat scenarios for acceptance.
5. Integration and deployment: merge into repository, migrations, CI/CD setup.

What's Included

• Complete plugin code with entities, services, configurations.
• Documentation for installation, configuration, and administration.
• Migrations for database structure updates.
• Tests (PHPUnit + Behat).
• Training for your team (2–4 hours).
• 3-month warranty support.

As a certified Sylius plugin developer, I offer expert Sylius customization and testing services. Our Sylius development services include custom plugin creation, and we provide comprehensive Sylius testing to ensure reliability.

Get a consultation and preliminary estimate for your project — we'll analyze the architecture and propose the optimal solution. Contact us for a preliminary assessment of your project. Order plugin development and get a reliable extension without update headaches.

Learn more about Sylius on Wikipedia.

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.