Download Lesuto Hub & Seller - Shop and sell on iOS and Android
Download Lesuto Hub & Seller - Shop and sell on iOS and Android
Commerce SDK
You already have the audience. Add a store without rebuilding the site, buying inventory, or standing up checkout. 69 modules from the live registry. Studio on the live page. WordPress merchants install the plugin. Shoppers stay on your domain.
Studio is already on this shop. Open it from Try It or Chrome Toolkit.
Why Merchants Use It
The SDK is for sites that already work: blogs, magazines, publisher pages, gyms, and custom HTML. You are not starting over.
The domain, the SEO, the email list, and the readers stay exactly where they are. Catalog, cart, and checkout mount on the HTML you already ship. You do not migrate to a Shopify theme or rebuild in WooCommerce just to take an order.
Choose products from verified suppliers on Lesuto. They own the stock and ship the order. You curate the aisle and earn commission when a shopper checks out on your page. No container, no warehouse, no returns desk.
Shoppers never bounce to another brand's cart. Stripe, tax, Klarna, Afterpay, and Affirm run through Lesuto. The URL they trust is the URL they pay on, so you keep the customer instead of handing them to a marketplace.
Place search, grid, cart, and checkout on the live page. Pick a Look preset. Save to Command Center. Layout changes do not wait on a developer deploy, a theme rebuild, or a plugin conflict ticket.
What The Traffic Can Do
Published industry figures, plus a conservative attach we use when sizing publisher sites. Not a Lesuto merchant average. Not a guarantee.
38%
Forbes Health kept shopping on the article instead of hopping out to a retailer. Conversion rose 38% vs the affiliate-link control. Earnings per click rose 30%. Same readers. Less friction.
Katalys, Forbes Health case study. six-month split test published on katalys.com/case/forbes-health.
2.26%
Dedicated ecommerce sites convert about 2.26% of sessions. A blog or magazine is not that store yet. Checkout on the same domain is how those visitors start behaving like shoppers instead of bouncing to Amazon.
IRP Commerce market data. July 2026, all ecommerce markets, session conversion.
70%
About 7 in 10 carts never check out. A stranger's checkout, extra accounts, and surprise shipping are why. The SDK keeps tax, Stripe, and BNPL on your URL so the last mile is the page they already trust.
Baymard Institute. 70.22% documented average cart abandonment, updated September 2025.
1 / 5,000
When we size publisher traffic we assume 20% of visitors see a product and 1 in 1,000 of those buy. That is 1 sale per 5,000 monthly visitors. It is a floor for planning, not a promise and not a Lesuto average.
Lesuto publisher model. same 20% see / 0.10% buy attach used on private publisher notes.
Orders on traffic you already have
Conservative column: 1 sale per 5,000 monthly visitors. Store-like column: 20% of visitors see a product, then convert at the IRP July 2026 session rate of 2.26%. Example only. Your mix, AOV, and merchandising decide the real number.
| Monthly visitors | Conservative orders | If shoppers convert like a store |
|---|---|---|
| 10,000 | 2 | 45 |
| 50,000 | 10 | 226 |
| 100,000 | 20 | 452 |
| 500,000 | 100 | 2,260 |
What It Saves
Building it yourself means cart, tax, payments, search, inventory, returns, and crawlers. Lesuto already runs that stack for Hub. The SDK is the same stack on your host, so you sell instead of staffing a storefront team.
A storefront is cart, checkout, tax, payments, search, inventory, returns, and payouts. Building that yourself is a year of engineers, not a weekend widget. The snippet is that stack, already in production on Hub.
You do not buy a container to test a category. Suppliers list once. You curate. They fulfill. Failed SKUs cost you a click to hide, not a pallet you cannot return.
Card data never sits on your host. Tax and BNPL are already wired. Refunds and the return window sit in Command Center. You are not becoming a payments company to sell furniture or home plans.
Faceted catalog search is the same engine Hub uses. The Render Engine (and the WordPress plugin) give matching bots real HTML so product pages can still rank. A homemade React cart is often an empty shell to Google.
Versus Building It
A homemade widget still needs payments, tax, stock, SEO, and a team to keep it alive. The Commerce SDK is the marketplace, already in production, on the site you already run.
| Build It Yourself | Commerce SDK | |
|---|---|---|
| Cart And Checkout | You build, PCI-scope, and patch it forever | Ships in the snippet |
| Catalog Search | You stand up an index and keep it honest | Same search Hub uses |
| Tax And BNPL | You wire Stripe Tax and every lender | Already on |
| Inventory | You buy, store, and eat the leftovers | Suppliers ship |
| Theme Rebuild | Move the whole site to Shopify or Woo | Your host stays the host |
| JavaScript SEO | Crawlers see an empty shell | Render Engine plus WordPress prerender |
| Returns And Payouts | You invent the split and the window | Marketplace rules already run |
| Hub, Boards, Live | Out of scope for a custom widget | Same account, same shopper |
| Updates And Kill Switch | Your next deploy, or the site breaks | CDN. Remote kill switch if you need it |
WordPress
Most stores that already rank are on WordPress. Replacing the theme with WooCommerce or moving to Shopify throws that work away. The official plugin is the Commerce SDK for that host: shortcodes drop the same 69 modules into posts, pages, and builders. One click writes Shop, Cart, Checkout, and Account templates.
Shoppers
Gallery, price, cart, and favorites. The host theme stays in charge. Lesuto mounts the commerce. Trust stays with the URL they already know.
Look Presets
Tap a preset. The rail is live.
Live catalog in Emerald
How It Works
No migration. Visual setup on the host you already have. WordPress uses the plugin. Everyone else uses the snippet.
WordPress, Wix, Squarespace, or HTML.
Drag search, grid, cart, and checkout onto the page.
Emerald, Ocean, Rose, Dark, and the rest from Command Center.
Shoppers check out on your domain. Lesuto runs catalog and payments.
The Snippet
Async from sdk.lesuto.com. Catalog, checkout, and tax stay on the API gateway. Under 40KB gzipped. WordPress loads this same file through the plugin.
69 Modules
69 modules from the live registry. Each module is one element. They inherit your Look. The count is read from the gateway, not baked into this page.
Remote Controls
Change SDK behavior from Command Center. No redeploy of the host.
SDK exits. Host page stays up.
Branded notice on every module.
Toggle features without a code push.
Lock a build, or ride auto-update.
Lesuto Hub
Hearts on your site land in Hub. Followers hear when you go live. One cart across every store they shop. DIY widgets do not get that network.
Explore The HubWhat's new
Release 2026.09.04
Magazine overlay on host sites
Overlay sits on the photo, uses the SDK font, and keeps price on the accent color instead of the host page's text styles.
Storefront module load
Modules on screen hydrate top-down first so the first paint is what the shopper sees.
Studio card-grid slots persist to admin
{chameleon-modules} {chameleon-studio} - Command Center import and publish keep , Size , and layout groups. Live SDK stamps without wiping authored width. Empty Studio placement lists clear the page rule.
Product grid paging
Next and Prev keep the grid size and place on the page. The layout does not jump or collapse while the next page loads.
Sign up, pick products, open Studio, paste one line. WordPress merchants install the plugin instead. Same storefront either way.
Get Started Free