> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/blog/advanced-and-premium-version.md).

# Advanced and premium version

PremsBlog comes in three tiers: **Basic**, **Advanced** and **Premium**. Without an active licence the plugin runs in **Basic** mode — fully functional, but with quantity limits. The two premium tiers unlock higher limits and additional features.

## Feature overview

| Feature                                   | Basic | Advanced | Premium   |
| ----------------------------------------- | ----- | -------- | --------- |
| **Number of articles**                    | 5     | 20       | unlimited |
| **Number of authors**                     | 1     | 5        | unlimited |
| **Number of categories**                  | 1     | 5        | unlimited |
| **Number of tags**                        | 1     | 5        | unlimited |
| **Review system**                         | —     | —        | ✓         |
| **Auto-publish** via start and end date   | —     | —        | ✓         |
| **Visual content editor**                 | ✓     | ✓        | ✓         |
| **Multilingual**                          | ✓     | ✓        | ✓         |
| **SEO, rich snippets, RSS feed**          | ✓     | ✓        | ✓         |
| **Headless / app integration**            | ✓     | ✓        | ✓         |
| **Blog elements in Shopping Experiences** | ✓     | ✓        | ✓         |
| **Sales-channel activation**              | ✓     | ✓        | ✓         |

> Articles, authors, categories or tags that exist **above the limit** remain in the database — they simply aren't surfaced in the shop. An upgrade re-enables them immediately. A later downgrade therefore loses nothing.

## Inspect the active plan

In the administration the active plan is shown under **Content → Blog → Plans**. The page lists every feature and lets you jump straight to the matching store entry for an upgrade.

As soon as you get close to a limit a subtle inline note appears in the respective list view (articles, authors, categories or tags).

## Premium features in detail

### Reviews

Full review system with star rating, comments, admin moderation and star snippets in Google search results. More in [Reviews](/en/plugins/blog/create-and-edit-blog-posts/reviews.md).

### Auto-publish

You plan articles with a **start date** (when they become visible) and optionally an **end date** (when they disappear again). The plugin automatically flips the article online and offline at the chosen moment — no click required.

In the Basic and Advanced plan you set the status manually.

## What happens on a downgrade?

If you move from Premium to Advanced:

* **Existing reviews** stay in the database but are no longer shown in the shop.
* **Auto-publish pauses.** Articles keep their last status; you re-activate them manually.
* Articles, authors, categories or tags above the Advanced limit stay untouched in the database but disappear from the shop.

Re-upgrading reactivates everything instantly.

## Buying a licence

The extension is distributed via the **Shopware Store**. Licences can be bought directly in the Shopware Account and are auto-activated in the plugin.

For questions about licensing, volume pricing or custom extensions reach out to [PremSoft](mailto:info@premsoft.de) any time.


---

# 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:

```
GET https://docs.premsoft.de/en/plugins/blog/advanced-and-premium-version.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.