> For the complete documentation index, see [llms.txt](https://docs.blockbolt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockbolt.io/blockbolt-demo/online-store-website.md).

# 🛒 Online Store - Website

**Build. Sell. Get Paid in Crypto — No Code Needed.**

BlockBolt offers a simplified eCommerce platform that empowers vendors to create and manage their online stores without any technical skills. Inspired by the ease of Shopify, this no-code dashboard enables product management, storefront customization, and crypto payment integration — all in one place.

The current version is a demo designed to showcase core functionality and the potential of crypto-native commerce.

***

🎥 **Experience the BlockBolt Storefront in Action**\
See how easy it is to create and manage a crypto-powered online store with BlockBolt — no coding required.

{% embed url="<https://www.youtube.com/watch?v=9k3e20eetWY>" %}

> **👉 Demo Website:** [**https://store.blockbolt.io/mocha**](https://store.blockbolt.io/mocha)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.blockbolt.io/blockbolt-demo/online-store-website.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.