> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/shopware/shopware6_en_us/price-and-inventory-management/delete-and-clean-up-prices.md).

# Delete & Clean Up Prices

To make sure that no outdated prices remain in the shop, the connector offers several cleanup functions.

**Automatic cleanup**

* **Expired** price lines are removed.
* Lines with a deletion flag (**Marked Delete**) are deleted.
* Lines with a **future starting date** are not transferred until they become valid.
* If a price line is deleted in BC, the corresponding Shopware price is removed as well.

**Deleting orphaned prices**

The **Delete Orphan Prices** action removes Shopware prices that are no longer assigned to any item.

**Resetting all prices**

For a complete rebuild, **Delete all Shopware prices** is available. Afterwards you can trigger a full re-upload using *Mark all prices as unsynchronized*.

{% hint style="warning" %}
Deleting prices in Shopware cannot be undone. Whenever possible, perform larger cleanups outside business hours and check the [Price List Overview & Sync Status](/shopware/shopware6_en_us/price-and-inventory-management/price-list-overview-and-sync-status.md) afterwards.
{% endhint %}


---

# 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.solutioo.de/shopware/shopware6_en_us/price-and-inventory-management/delete-and-clean-up-prices.md?ask=<question>&goal=<user_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.