Skip to main content

Your shop website

No. Pick a ready-made template, change the logo, colours and texts, and describe bigger changes in words in the AI editor — the AI edits the files, builds a preview, and you click Publish. The code is there for those who want to edit it by hand.
It keeps working unchanged until you migrate. Migration creates a new site project from the bento template and carries over the name, colours, logo, hero and links. Details: Migration.
Yes — as a zip, a folder dragged into the panel, or from the terminal with itemshop deploy. It can be a Vite + React project or plain HTML/CSS/JS. See Custom code and CLI.
No. ItemShop hosts only the static build output — none of your code runs on the server. Your site fetches data (products, checkout, order status, widgets) in the browser from the public Storefront API, with no secrets. On custom sites, redeem a voucher with sf.vouchers.redeem(code, nick).
Yes, under the MIT licence. You can fork them, rework them and use them outside ItemShop. See Templates.
Yes. See Domains.

For developers

TypeScript (the reference one: Node, browser, React and CLI), Python, PHP, Java/Kotlin and Go. Each has a keyless part (Storefront) and a client that uses an API key. The SDKs ship with ItemShop 3.0 — until then plain HTTP works. Start with the TypeScript SDK or API with a key.
Yes — through the hosted MCP server and agent skills.

Payments and fulfillment

Add a payment method to your shop and enter the provider’s credentials. Supported providers and required fields: Payments. A provider outside that list can’t be connected safely — it first needs a verified backend adapter.
It depends on your country, your situation and the provider’s terms. ItemShop doesn’t decide this — check the requirements with the provider and, if in doubt, with an accountant or lawyer.
Usually it’s the plugin or a webhook: a wrong key (it must be a plugin key with orders:write), a serverId from another shop, a misconfigured provider webhook, or wrong or blocked product commands. See Plugin on your server.
Full guide: Plugin on your server. If you’re writing your own plugin, see Plugin protocol.
Place a free order (100% discount) or redeem a voucher and check that the status moves from paid to completed. See Orders.
Upload files in the product form — they’re compressed to WebP and stored in the shop’s storage. API integrations can also pass a public HTTPS URL. See Products.

Next

Quickstart

A shop and your first website in minutes.

Site as code

Templates, the AI editor and custom uploads.