Open-source commerce / The Winkdom family
One storefront for everything you sell.
Turn a WordPress site into a shop, a booking desk, or a marketplace. Give customers a fast Vue storefront inside Winkdom, with native ShopiChain commerce or WooCommerce behind it.
Find your setup ↓Build around what your customer buys.
Products & subscriptions
Give shoppers a catalog, cart, checkout, and order history. Use native ShopiChain commerce or connect an existing store engine. For recurring purchases, customers can review their subscriptions in their account.
Bookings
A workshop seat or studio session needs a time as well as a price. ShopiChain Bookings connects bookable services and availability to the purchase journey.
Marketplaces
Let vendors list products under one storefront. Marketplace Engine connects each listing to its seller and records how a sale or refund affects the vendor’s balance.
Software licenses
Sell access to a digital product and connect the license to the purchase. Local-first licensing lets merchants manage entitlements, activation limits, and renewals.
Live shopping
Turn a product demo or vendor Q&A into a shopping event. Link products to a session and keep replay references so viewers can find what they saw.
Campaigns & wishlists
Set sales-tier pricing for native products with Campaigns, or add Wishlists to a supported storefront so shoppers can save items and return to them.
Explore the rest of the plugin family
Payments. Stripe connects supported native orders to card checkout and refunds. Onchain Payments provides a separate Solana checkout option.
Sales channels. FluentCommunity presents commerce inside a community. AppSumo and WPBay integrations connect eligible external purchases to license fulfillment. Agent Tasks explores a marketplace for work with human review.
Store connections. The WooCommerce and FluentCart adapters connect existing engines. Ecosystem Bridge supports connections with Winkdom and Cointacted. Offload moves selected jobs to a compatible worker.
On the roadmap. Course and community sales, branded marketplace developer kits, and richer live offers build on these modules. Availability will depend on the plugin and host.
Choose where your store runs.
WordPress · Open-source core
A Vue storefront inside your site
Start with free, GPL-licensed ShopiChain Core. Its Vue single-page storefront updates supported views and cart actions without reloading the whole page. Inside Winkdom, shoppers can move between content and commerce in the same interface.
Already using WooCommerce? Keep its catalog, stock, checkout, shipping rules, and payment gateways. ShopiChain presents products and updates the cart through WooCommerce’s Store API, then hands the order to WooCommerce checkout. FluentCart has its own adapter.
EmDash · Plugin by plugin
Bringing ShopiChain to EmDash
A native licensing integration is in development for EmDash. Broader storefront, booking, marketplace, and live-shopping support is a staged effort. Choose the host according to the workflows your store needs today.
Standalone · In development
A serverless shop built with Go and PostgreSQL
Our planned standalone platform is designed to add Go service instances as demand grows, while PostgreSQL keeps durable order and payment records. Go and PostgreSQL prototypes already exercise order persistence and recovery.
The intended migration starts with the ShopiChain WordPress plugin and moves supported store data into that independent platform. Production migration, feature coverage, and measured scaling limits are still in development.
Your store data. Your infrastructure choices.
On WordPress, the commerce engine you select manages the store records. With WooCommerce, orders stay in WooCommerce. Payment and fulfillment providers receive the information their services need.
Offloading is optional. For example, a compatible worker can build a search index away from your site server. You choose which supported jobs to delegate and can run the worker yourself.
For the standalone platform, we’re designing around merchant choice: where store records are hosted, which services can access them, and which optional sharing to enable. These controls are a design goal for that platform.