Server-side engine

The Platform

A server-side CMS, standard HTML pages, TagCode plugins, a JSON API for your own pages and your site files over WebDAV.

HTML Templates CMS Engine Plugin System Collections Multi-Touchpoint
01 — CMS ENGINE

Server-side rendering.

The Shoppi Cloud engine receives the HTTP request, finds the right template through the routing system, reads the header configuration block, loads the plugins, replaces the localized variables and serves the final HTML, all on the server.

It is not a single-page app and not a statically generated site. It is a CMS that knows the visitor’s language and session when it builds the page.

Smart RoutingURL → template automatically
Native Localization6 languages, zero config
Standard HTMLPlain HTML plus TagCode placeholders
Composite TemplatesIncludes & constants
— Request flow —
HTTP Request /en/products
Router → page/en_US/products.html
HeaderParser → $_PLUGINS, $_TITLE
LangEngine → %_KEY% = "Value"
PluginLoader → cart, search injected
HTML Response → browser
02 — TAGCODE SYSTEM

Standard HTML. Plugins where you need them.

TagCodes are server-side placeholders you can put in any HTML file. The engine replaces them while it renders the page: a cart drawer, the title and price of a product, structured data for search engines.

Everything around them stays plain HTML and CSS, so any editor, any developer and any AI coding tool can work on your pages.

A plugin in one tag
{cart:act=drawer}
Product fields inside your own HTML
<div class="card">
  <img src="{photo}" alt="{title}">
  <h3>{title}</h3>
  <span>{price}</span>
</div>
{cart:act=drawer}

The full cart drawer, connected to Stripe Checkout.

{search:nout=true}

Starts search on your collections, by text, category or distance.

{offers:act=seo}

JSON-LD structured data for your product offers.

{cookieconsent}

A cookie consent banner, in one tag.

03 — JSON API

A JSON API for your own pages.

Pages on your own Shoppi domain read your catalog and orders as JSON, through the same API the app uses. The Shoppi SDK adds a cart on that domain and sends the buyer to Stripe Checkout. There is no API key: on your own Shoppi domain the API works out which store the page belongs to.

What it is not: the API is not built for third-party sites, there are no API keys to give an ERP or a CRM, and Shoppi does not send outgoing webhooks.

read products read categories read search read pages cart add, update checkout Stripe
On a page of your own domain
// the page loads /shoppi/shoppi-sdk.js

const list = await Shoppi.catalog.products({ limit: 12 });
// { items: [{ id, title, price, photo, quantity }],
//   count, hasMore }

Shoppi.cart.add(10034, 1, { title, price, image });
await Shoppi.checkout.start();
// redirects to Stripe Checkout
04 — COLLECTIONS + AI

Structured data, with an AI writing assistant

Collections are structured JSON records with dynamic fields per type, attached media and coordinates for location search. An AI writing assistant helps you with the text; you decide what to keep.

Geo-Awareness

Items carry coordinates, so search can rank results by distance or filter them by city.

"loc": [9.18, 45.46]

AI writing assistant

Improve, shorten or expand product and post text, and get a suggested title or category.

improve · shorten · expand · title · categorize

Dynamic Fields

Products, services, files, news: every type has its own fields. Fields can hold text, media, links, structured data and inline HTML.

"sections": [...], "cta": {...}
05 — MULTI-TOUCHPOINT

One account. A touchpoint for every place you sell.

A touchpoint is one place you sell: a website, a shop counter, a QR menu, a payment link. Each one has its own web address, catalog, orders and its own Stripe account under Stripe Connect. With the Shared Catalogue add-on on Business, product details and prices are copied across linked touchpoints every 10 minutes, and stock stays per touchpoint.

Web store

A store on brand.shoppi.site from the $29 Starter plan, or on your own domain with Business. HTML templates and TagCode.

Shoppi marketplace

Products of merchants on paid plans are listed on the Shoppi marketplace, with a 10% revenue share only on the orders it brings.

QR menus and stores

Customers scan a QR code at the table or the counter and order from their own phones.

Shoppi POS app

Tap to Pay on Android or a Bluetooth Stripe reader. Each counter is its own touchpoint.

Payment links

A Stripe Checkout link you can share in a chat, an email or a social profile.

Your files

Storefront pages are standard HTML on your own WebDAV drive. Copy them whenever you want.

No API keys on your own domain

Your storefront code needs no API key: on your own Shoppi domain the API works out which store the page belongs to.

No API Keys Same API as the app

What this means for integrations

The API is built for your own Shoppi pages. There are no API keys to give a third-party site, an ERP or a CRM, and no outgoing webhooks.

Keeping another website? Link to Shoppi payment links and product checkout pages from it, and embed the Booking Calendar widget (an add-on) with one script tag.

Your site files over WebDAV, for Claude Code or Codex

AI coding tools like Claude Code and Codex work best on plain files. Shoppi Cloud gives you your site’s files over WebDAV: standard HTML and CSS, no build step, no framework. Database credentials stay hidden from the drive. Prefer not to use your own tools? The built-in AI site editor proposes page changes and you approve them, from the $29 plan.

1
Get your WebDAV access

Copy the server address and your credentials from the Shoppi Cloud console.

2
Mount the folder

Use any WebDAV client or Shoppi Go, then point Claude Code or Codex at the folder.

3
Edit and save

The AI edits your HTML, CSS and TagCodes. Each save goes live on your domain.

One platform, standard web files.

Standard HTML, a JSON API for your own pages, an AI writing assistant and an AI site editor you approve. Monthly, no contract.