> 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/magento-2-api-connector/magento2_en_us/customer-management/customer-and-address-mapping.md).

# Customer and Address Mapping

During document creation, the setup determines whether an existing/default customer or a newly created customer is used.

### Decision Logic

* Existing Magento customer mapping → assigned BC customer
* Unknown + Create Unknown Customer → new record from template
* Guest → Default Guest Customer
* Logged-in without creation → Default Login Customer

### Addresses

Bill-to and ship-to addresses are transferred separately. Verify company name, first/last name, street lines, post code, city, region, country, phone, and email.

{% hint style="warning" %}
In version 27.10.0.16, the first name may be used twice in the Sell-to Customer Name. Verify and correct the name before posting.
{% endhint %}

### Test Cases

Guest, registered individual, company, alternate ship-to address, special characters, long fields, and missing region.


---

# 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/magento-2-api-connector/magento2_en_us/customer-management/customer-and-address-mapping.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.
