More than a plugin.
A commerce platform.
yStore is a full commerce engine for Craft CMS, built for agencies and developers who want to own the whole build — not fight the framework around it.
Where Craft Commerce gives you a storefront, yStore gives you a storefront, a native automation engine, a customer-segmentation layer, an AI/MCP control surface, and a one-time per-project license instead of a recurring platform fee.
One admin. Five capabilities Commerce doesn't ship.
Five capabilities Commerce leaves out of the box. Scroll to see each one, live, in the panel on the right.
No feature loss when you switch.
The first question every agency asks about a platform change is "what will I lose?" With yStore the baseline is not thinner than Commerce — in several places it is broader, and more of it is native.
- Bundle products (native).
- A parent product composed of N components, its own pricing mode and discount — built on the native Craft Matrix field. Craft Commerce has no built-in multi-product bundle type.
- Advanced pricing.
- Customer-group pricing, tier/quantity pricing, and a dedicated catalog price-rule builder in the CP.
- Order operations built for staff.
- A tabbed order workspace, CP-internal "Admin Cart" order creation, native tax + multi-currency, and native invoicing.
Built to be extended, not forked.
yStore exposes its architecture as extension points rather than hiding it — every one of the ~40 add-ons plugs into the same public event surface you can use yourself.
- A documented event surface.
- Roughly 25 events, documented with code examples, across cart, checkout, orders, gift-card, quote, search, and flow services.
- Pluggable registries.
- Shipping methods, payment methods, and customer-segment types are all registered through events — not hardcoded lists.
- Storefront and integration surface.
- Twig, GraphQL, and REST are exposed for headless and customer-facing use cases alike.
The one thing Commerce can't match.
yStore ships a Model Context Protocol (MCP) server that exposes the store to any MCP-speaking AI agent over JSON-RPC.
- ~35 tools.
- Cart, products, orders, customers, coupons, multi-location inventory, reports, shipping tracking, and GDPR consent/anonymization.
- A three-tier permission system.
- Read-only, write, and destructive tiers, with per-API-key allowlists — granting an agent access is a governed decision, not an all-or-nothing key.
Transparent, one-time.
A one-time, per-project, domain-bound license — not a recurring platform fee. Feature modules are individually licensable and off by default, so a project pays for the surface it actually uses.
- Flow Manager.
- A native, node-based visual automation engine — 99 action classes, 77 trigger classes, 16 condition classes — with versioning/rollback, dry-run, and run history.
- Built for agencies.
- Predictable to quote to a client, doesn't compound as a retainer. Composer/packager access is credential-gated by license.
Same framework, so it stays a scoped project.
- Same framework, same mental model.
- Teams keep Craft, Twig, GraphQL, the element/field system, and their existing Craft skills.
- Familiar authoring surfaces.
- Products, variants, and matrix-style editors map onto patterns Craft developers already know.
- What to scope up front.
- Entity mapping and Craft version compatibility are the concrete questions to answer before the project starts.
One engine runs your whole store.
Nine surfaces, one consistent set of patterns. Wherever you go in the Store Manager, tables filter the same way, columns adapt to you, and every action is one click from where you're looking.
Simple, digital and gift-card types with tier, catalog and customer-group pricing.
Editable orders, custom statuses, invoices, gift cards and shipping labels in one view.
Accounts, address books, wishlists, groups and login-as for real support.
Coupons, gift cards, abandoned-cart recovery, subscribers and catalog rules.
A visual canvas with 99 actions, conditions and logic -- no code required.
24 dashboard widgets and a system report that tells you where to click.
Automate the busywork on a visual canvas.
Drag a trigger, drop in conditions and actions, connect them, and let the Flow Manager run the repetitive work -- status emails, tagging, stock alerts, coupon issuing -- while you sleep.
A dashboard that tells you where to look.
24 modular widgets -- revenue, conversion funnel, top products, cart abandonment, coupon performance, flow health and more -- arranged the way you think. Change the date range and every card moves with you.
- Build the view that fits your role. Switch modules on or off, set the range, and the whole dashboard reflows.
- Understand where people leave. A sessions-to-orders funnel with drop-off at every step.
- A system report that guides you. It shows what's healthy, what's risky and where to click next.
Test payments and read your dashboard before the first order.
Switch on demo data, run payment gateways against ready-made sandbox cards, and send a review or support request straight from the plugin settings.
-
Demo mode
Show generated numbers on a plugin dashboard instead of live data -- useful before the first orders arrive.
-
Sandbox test cards
A copy-to-clipboard list of test cards inside the settings of 24Pay, Barion, GP webpay, SimplePay, Stripe and Tatra pay.
-
Review & Support widget
Rate a plugin or open a support ticket from its settings page, without leaving the Control Panel.
-
Dashboards without gaps
Turn a dashboard module off and the remaining cards grow to fill the row, so the layout never has an empty column.
Recover carts, reward loyalty, sell more
The marketing toolkit that would normally be five separate plugins — coupons, gift cards, abandoned-cart recovery, watchdog alerts and subscribers — all managed from one place and wired into the same automation engine.
Fixed or dynamic codes, priority rules, combine limits and per-product conditions.
Auto-generated designs, balance carryover, watermarks and expiry notifications.
A 3-step recovery sequence, fully configurable timing, with an automatically generated, single-use coupon on any step you choose.
Build static lists or dynamic, rule-based segments from group, status, subscription, address and wishlist data — re-evaluated on every change or on a schedule.
The feature-by-feature edge.
Craft Commerce covers the basics. Everything below it needs a plugin, a manual workaround, or doesn't exist at all — yStore ships all of it out of the box.
| Capability | Craft Commerce | yStore |
|---|---|---|
|
Native Bundle products
First-class field-layout-driven multi-product bundle/kit type — Commerce ships no built-in multi-product bundle type.
|
||
|
MCP server
~35 tools across cart, orders, customers, inventory and reports, gated by a three-tier (read-only/write/destructive) permission system — Commerce has no MCP surface at all.
|
||
|
Flow Manager
99 action / 77 trigger / 16 condition classes, with versioning/rollback and dry-run — Commerce has no native visual automation engine.
|
||
|
Native tax + multi-currency
Customer-group-aware tax rates plus a price-rebase job, built into the core plugin — Commerce needs third-party plugins for multi-currency.
|
Via plugins | |
|
One-time license pricing
A one-time, per-project, domain-bound license fee instead of a recurring platform subscription.
|
Subscription | |
Order operations
CP-internal order creation ("Admin Cart") for phone/in-store orders and discount testing — Commerce has no equivalent staff-facing order builder.
|
Manual |
|
Native invoicing
Invoice/proforma generation built into the core plugin — Commerce requires a separate invoicing plugin.
|
Via plugins |
|
Customer segmentation engine
Rule-based customer segments queryable from Twig, GraphQL, and REST — Commerce has no built-in segmentation engine.
|
||
Documented event surface
~25 events across cart, checkout, orders, gift-card, quote, search and flow services, each documented with a code example.
|
Ad hoc |
|
Checkout agreements over GraphQL
GDPR-ready consent/terms checkboxes exposed to storefront and GraphQL — Commerce requires a custom implementation.
|
||
Shared cart features
Customers can generate a shareable link to their cart. Commerce has no equivalent.
|
||
Marketing watchdog monitoring
Automated health monitoring for marketing and storefront operations, built into core.
|
||
Price history tracking
EU Omnibus-compliant lowest-price lookback tracking, built into core.
|
Manual |
|
Native gift cards
Gift card accounts, codes and transactions out of the box.
|
Via plugins |
|
Wishlist + sharing
Customers can build and share a wishlist without a plugin.
|
Via plugins |
|
Delivery slots & shipping holidays
Per-slot pricing plus configurable shipping holidays and excluded days.
|
Manual |
|
Customer approval workflow
Approve, reject or blacklist customers before they can order.
|
||
Abandoned cart recovery
Native recovery flow for abandoned carts.
|
Via plugins |
|
JSON email schemas
Structured, versionable JSON schemas for account and order emails.
|
Manual |
|
Performance controls
Native x-defer, speculation rules and static-cache toggles for storefront speed.
|
Manual |
yStore is the option for teams that treat commerce as something they build and own, not rent. Native bundles, a real automation engine, a governed AI/MCP control surface, and one-time per-project licensing add up to a platform an agency can standardize on across clients — without a recurring platform tax and without fighting a closed core.