> 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/configuration/notes-on-prices.md).

# Notes on Prices

Configure the price settings for synchronization.

The price settings determine how prices are synchronized between Business Central and Shopware.

## 1. Mapping Tables

{% tabs %}
{% tab title="VAT mapping" %}
Map Business Central VAT posting groups to the Shopware tax rates:

1. Open *"Shopware"* <i class="fa-right">:right:</i> *"Mapping"*
2. Select *"VAT Mapping"*
3. Map every VAT product posting group.

For more information, see [Taxes & Tax Mapping](/shopware/shopware6_en_us/configuration/taxes-and-tax-mapping.md).

Example:

FULL <i class="fa-right">:right:</i> standard tax rate (19%), REDUCED <i class="fa-right">:right:</i> reduced tax rate (7%), EXEMPT <i class="fa-right">:right:</i> tax-free (0%)
{% endtab %}

{% tab title="Currencies" %}
If you use several currencies:

1. Open *"Shopware"* <i class="fa-right">:right:</i> *"Mapping"*
2. Select *"Currencies"*
3. Map the BC currency codes to the Shopware currencies
   {% endtab %}
   {% endtabs %}

## 2. Price Types

{% tabs %}
{% tab title="Standard prices" %}
The standard price is used for all customers who are not assigned to a specific price group.
{% endtab %}

{% tab title="Customer prices" %}
Individual prices for specific customers:

1. Open the *"Sales Prices"* in BC.
2. Create prices for specific customers.
3. These are taken into account during synchronization.
   {% endtab %}

{% tab title="Tiered prices" %}
Quantity-dependent prices:

1. Create *"Sales Prices"* with minimum quantities.
2. These are transferred to Shopware as tiered prices.

For more information, see [Tiered Prices](/shopware/shopware6_en_us/price-and-inventory-management/price-updates/tiered-prices.md).
{% endtab %}
{% endtabs %}

## 3. Price Synchronization

{% tabs %}
{% tab title="Automatic synchronization" %}

* Create a *"*[*Job Queue Entry*](/shopware/shopware6_en_us/automation-and-schedules/job-queue-entries.md)*".*
* Select the *"Price Upload"* codeunit.
* Define the interval.
  {% endtab %}

{% tab title="Manual synchronization" %}

* Open the *"Item Card"*
* Click *"Actions"* <i class="fa-right">:right:</i> *"Price to Shopware"*
  {% endtab %}
  {% endtabs %}

## 4. Tips for Day-to-Day Use

{% tabs %}
{% tab title="Price consistency" %}

* Check the prices in both systems regularly.
* Make sure the VAT mapping is correct.
* Document your pricing rules.
  {% endtab %}

{% tab title="Rounding" %}

* Shopware and BC can use different rounding rules.
* Check cent amounts during synchronization.
  {% endtab %}
  {% endtabs %}

{% hint style="warning" %}
Changes to prices made in Shopware are overwritten during the next synchronization.
{% 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/configuration/notes-on-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.