Deploy a complete online shop in one click from our ready-made starter template — or connect an existing site via API — without managing a server or database. Buyers shop on a fast, familiar storefront without signing up for 1💗1, while behind the scenes the rikma manages variants, inventory, orders, task and resource automations, MCP tools, and automatic profit splits by contribution.
An open-source SvelteKit repo (1lev1-shop-starter) that deploys to Vercel or Netlify in one click: catalog, variant picker, cart, checkout or arranged payment, and live order tracking.
Consume the rikma's public REST API from any stack (Next, Astro, SvelteKit, WordPress) or drop in a snippet to report sales automatically after checkout.
12 dedicated shop MCP tools let Claude or any MCP-compatible AI agent check inventory, create products, update stock, and advance orders in natural conversation.
So you never have to build a backend or maintain a separate e-commerce database, we built a complete open-source storefront template wired directly to your rikma in 1💗1.
Open Moach → Sales → Manage Sales. Upload a gallery (up to 12 images per product plus per-variant galleries), define rikma-level option axes (size, color, volume), and generate a SKU variant matrix with per-combination pricing and stock — or an "Unlimited" toggle.
In the "Connections" tab, create a dedicated shop key (orders:create and orders:read) stored only on the shop's server (never in the browser). Pick one or more payment methods: Stripe, PayPal, or arranged payment (phone / WhatsApp).
Clicking the deploy button in the Connections tab pre-fills your rikma's API address and shop key in the Vercel or Netlify form. Within a minute your storefront is live and synced in real time with the rikma.
Enable a single payment path or combine them in the same cart:
The starter's server reprices the cart against the live catalog (so a buyer is never charged a stale price), opens a secure checkout session, and receives a signed webhook that reports a paid order to the rikma.
The lowest barrier to entry for new ventures: no merchant account and no processor fees. The buyer leaves a name and phone number, the order lands in "Awaiting payment" with call and WhatsApp buttons, and clicking "Payment received" records the sales and decrements stock.
You don't have to use the starter template: embed a snippet that reports each sale from your existing checkout, or build your own frontend on top of the rikma's Headless API.
Filter by category and variant axes (?option.size=m&option.color=red), sort by price or recency, with full SSR support before JavaScript loads.
Selecting a size or color immediately updates the gallery, price, and availability ("3 left" or "Available") from a single API response.
The cart stores only IDs and quantities (never prices). Before checkout, the server re-verifies stock and pricing against the catalog and alerts the buyer if anything changed.
Supports shipping to an address (with delivery fee calculation), self-pickup, digital delivery, or coordination, plus preparation lead time display (leadTimeHours).
Buyers get a short, phone-friendly order number (like K7Q4XM) and watch their order progress from recorded → shipped → fulfilled.
Zero lock-in: export all products, variants, and sales in Shopify CSV format for any external tool or spreadsheet.
In an ordinary online store, one admin holds all the keys, and at the end of the month the spreadsheets and arguments begin. When 1💗1 is your backend, partnership rules and mutual consent are built into the engine itself.
Updating stock, reordering galleries, marking an order shipped or fulfilled, and printing packing slips happen immediately for any rikma member. Changing a product's price or adding a variant in a shared rikma changes the partnership's terms — so it automatically opens an edit proposal (editObject) for partner consent (approve · discuss · counter-propose, with silence after the agreed response window counting as consent) while the product keeps selling uninterrupted.
Buyer payments never pass through 1💗1 and we hold no custody or wallet. Money goes directly to the rikma member's Stripe, PayPal, or bank/Bit account, is recorded as a sovereign self-reported sale (holderStatus: 'self'), and immediately enters the amount awaiting distribution under (time + resources) = % of profits. Reporting a sale held by another partner opens a bilateral saleClaim consent.
Once a buyer has paid on your site, the server never throws an error that drops the order because stock ran out a second earlier. The order is recorded, stock goes negative to show the exact unit shortfall, the order is flagged as oversold, and the rikma is notified to produce more or coordinate with the buyer.
Sales in 1💗1 are never deleted from history: cancelling an order zeroes out unsplit sales (preserving the original amount in the note) and restocks unshipped items. Buyer contact details and shipping addresses are visible only to rikma members — never exposed in public DTOs or webhooks.
| Area | Traditional Store (Shopify / WooCommerce) | Shop on 1💗1 Backend |
|---|---|---|
| Pricing & catalog governance | Anyone with admin access can unilaterally change prices or delete products. | Stock and fulfillment are instant; price or variant changes in a shared rikma go through partner consent. |
| Partner revenue splitting | Money lands in one account; partners manually reconcile hours, costs, and splits in spreadsheets. | Every paid order automatically feeds transparent profit distribution based on verified hours and resources. |
| Post-order operations | Generic email notification; manual coordination for who picks, packs, ships, and restocks raw materials. | Fulfillment engine opens heart-card tasks for role holders and deducts raw materials from rikma resources. |
| AI agent management (MCP) | Requires paid third-party plugins and custom integration glue. | 12 built-in MCP tools out of the box to manage products, inventory, and orders in Claude. |
A 1💗1 shop is wired directly into the rikma's missions and resources: every paid order triggers a unified fulfillment engine that turns a purchase into real-world tasks and material consumption — without forcing unconsented obligations on any partner.
In the "Fulfillment" tab, each rikma defines its chain of steps: when a step triggers (every paid order, delivery only, pickup only, or after a previous step), who it targets (an active mission, a rikma role, or a specific member), and whether it opens one task per order or per line item.
A product (or a specific variant, like size L using more fabric than size M) can link to rikma resources so every sale updates physical stock according to how the resource is held:
The same shop handles simple products as well as complex products built from a Bill of Materials (BOM) of multiple missions and resources:
Rikma members can connect Claude or any MCP-compatible AI agent to manage their catalog, stock, and orders in plain language — or build any custom shopping experience over the rikma's REST API and webhooks.
Your agent sees everything shown in the rikma's sales management screens in real time:
listRikmaProducts · getRikmaProduct · getShopInventory (full stock snapshot, low-stock variants, and live unit shortfalls against waiting orders) · listRikmaProductOptions · listRikmaProductVariants · listRikmaOrders · getRikmaOrderEvery write tool is enforced under rikma member permissions and respects partner consent rules:
createRikmaProduct (in an existing rikma, personal home rikma, or brand-new rikma) · setShopStock (set exact count, add incoming stock, or mark unlimited) · updateRikmaOrderStatus (mark shipped/fulfilled or cancel by money holder) · updateRikmaProduct · archiveRikmaProductBuilding a custom storefront in Next.js, SvelteKit, or Astro? Every rikma exposes a canonical API surface with ETag caching, variant filtering, idempotency, and HMAC-signed webhooks:
GET /api/v1/r/:rikma/products · GET /api/v1/r/:rikma/options · POST /api/v1/r/:rikma/orders · GET /api/v1/r/:rikma/orders/:ref · POST /api/v1/r/:rikma/orders/:ref/cancel · Webhooks: order.paid, order.pendingPayment, order.statusChanged, order.oversold, variant.stockChangedNo. Buyers browse your storefront, pick variants, add to cart, and pay as completely anonymous guests — without a 1💗1 account and without leaving your website.
No. 1💗1 holds no wallet and takes no custody of funds. Buyers pay directly into the rikma member's Stripe, PayPal, or bank/Bit account, and the server simply reports the order so sales are recorded for transparent profit splitting among partners.
Yes. In the starter template you can enable "Arranged payment" (phone / WhatsApp) with no Stripe or PayPal keys at all. The buyer leaves a name and phone number, the order appears under "Awaiting payment", you coordinate payment via Bit, transfer, or cash, and click "Payment received".
Operational actions — updating stock, arranging gallery photos, marking orders shipped — take effect immediately. Changing a price or adding a variant on a shared rikma product opens an edit proposal for partner consent while the product continues selling at its current price.
Yes. The sales management screen exports all products and variants in Shopify-compatible CSV format, as well as filtered sales tables by date range and source.
Start a rikma for free, add your first products, and deploy a ready-made storefront in minutes — or book a short personal demo to see the whole flow live.
Back to homepage