> 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/customer-management/synchronize-ship-to-addresses.md).

# Synchronize Ship-to Addresses

Several **ship-to addresses** can be transferred to Shopware for each web customer.

**Procedure**

* During the customer upload, existing ship-to addresses are synchronized automatically as well.
* If you change an address, the customer is flagged as *not synchronized* and updated during the next run.
* Each ship-to address receives its own **Web-ID** and a sync status.

**Fields per ship-to address**

| Field                       | Meaning              |
| --------------------------- | -------------------- |
| Web-ID                      | Shopware address ID  |
| Synchronized / on / Message | Sync status          |
| Origin                      | Source of the record |

{% hint style="info" %}
For imported orders, ship-to addresses that differ from the bill-to address are also taken into account – see [Order Intake from Shopware into BC](/shopware/shopware6_en_us/order-processing/order-intake-from-shopware-into-bc.md).
{% endhint %}

### Frequently Asked Questions

#### Can a customer have several ship-to addresses in the shop?

Yes. Several ship-to addresses can be transferred to Shopware for each web customer. During the customer upload, existing ship-to addresses are synchronized automatically; each address receives its own Web-ID and a sync status.

#### What happens if I change a ship-to address in Business Central?

When an address changes, the customer is flagged as "not synchronized" and automatically updated in Shopware during the next synchronization run. This keeps the addresses consistent between both systems.


---

# 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/customer-management/synchronize-ship-to-addresses.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.