> For the complete documentation index, see [llms.txt](https://docs.b2b-sellers.com/b2b-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2b-sellers.com/b2b-platform/product-tour/test-the-plugin-in-our-demo-shops.md).
# Test the plugin in our demo shops
## Public demo shop
Explore our LUXON Demo Store to see a seamless integration of a Corporate Website, B2B Shop, Customer Portal, and Sales Portal in action. Test-drive advanced B2B features firsthand, including our deep Sales Agent integration.
Explore the Live Demo:
## Spare-Parts demo shop
A closed spare parts store where you can add models and spare parts. A search for spare parts via the model number or even exploded views and multi-dimensional accessory groups are part of the spare parts store. A suitable B2BShopTheme completes the offer.
Get in touch:
## Highlast demo shop
For load testing we have a special demo shop with 100.000 products, 500.000 customers and employees as well as 1 million customer individual prices.\
\
Get in touch:
## Get Your Own B2B Demo shop
Want to test every feature extensively? We provide individual demo stores that give you full access to both the storefront and the Shopware administration.
* Fully Featured: All B2B functions are activated by default.
* Unrestricted Testing: Install plugins and test workflows as long as you need.
* Personalized: We can add your branding and use your custom domain.
Claim your instance: [Fill out the request form](https://www.b2b-sellers.com/en/book-a-demo/) and we’ll have it ready in minutes.
### Partner & Agency Support
Are you an agency looking to showcase B2B capabilities to your clients? We provide dedicated, regularly updated demo environments for our partners. Contact us to set up your agency instance!
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.b2b-sellers.com/b2b-platform/product-tour/test-the-plugin-in-our-demo-shops.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.