> 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/frequently-asked-questions-faq/faq-customers-and-b2b.md).

# FAQ – Customers & B2B

### How is a customer assigned to an order?

The connector first matches via the **Web ID** and then via the **email address**. If no matching customer is found, the rules for guest and default customers apply. See [Guest Customers & Default Customers](/shopware/shopware6_en_us/customer-management/guest-customers-and-default-customers.md).

### Can I upload customers from BC to Shopware?

Yes. The customer must be marked as a **web customer** and have the mandatory information: salutation, customer group, sales channel, and country/region. After the upload, it receives a Web ID. See [Customer Upload (BC to Shopware)](/shopware/shopware6_en_us/customer-management/customer-upload-bc-to-shopware.md).

### What are B2B users and which roles are available?

B2B users are contact persons of a corporate customer who can sign in. There are three roles: **View** (view only), **Buyer** (view and order), and **Approval** (view, order, and approve). See [B2B Roles & Approval Process](/shopware/shopware6_en_us/customer-management/b2b-roles-and-approval-process.md).

### How are the customer and the contact related in B2B?

The **customer** is the company account in Shopware, and the **contacts** of this customer become the B2B users who can sign in. The assignment is made via the customer ID of the customer, or alternatively via the email address. See [B2B Users from Contacts](/shopware/shopware6_en_us/customer-management/b2b-users-from-contacts.md).

### What happens if a contact has no email address?

In that case, the connector builds a substitute address following the pattern `{ContactNo}@{CustomerNo}.{fallback-domain}`. This requires a configured **B2B Email Fallback Domain**.

### How do I set up customer group-specific prices?

Via a BC price list of the **Customer Price Group** type, which is uploaded as a Shopware price rule. See [Customer Group Prices (Rules)](/shopware/shopware6_en_us/price-and-inventory-management/customer-group-prices-rules.md) and [Set Up a B2B Shop](/shopware/shopware6_en_us/onboarding-and-best-practices/set-up-a-b2b-shop.md).

### Are a customer's ship-to addresses synchronized?

Yes. During the customer upload, existing ship-to addresses are transferred automatically and updated when they change. See [Synchronize Ship-to Addresses](/shopware/shopware6_en_us/customer-management/synchronize-ship-to-addresses.md).

### What is a default or guest customer?

A fixed customer to which orders without a (synchronized) customer account are posted – guest orders, for example. This keeps the customer list lean. See [Guest Customers & Default Customers](/shopware/shopware6_en_us/customer-management/guest-customers-and-default-customers.md).

### How do I create B2B users for the Shopware shop?

B2B users are created from Business Central contacts. The connector creates login accounts in Shopware for the contacts and assigns them to the respective company. This allows your business customers to sign in to the B2B shop with their own users. For details, see [B2B Users from Contacts](/shopware/shopware6_en_us/customer-management/b2b-users-from-contacts.md).

### How do roles and approval processes work in the B2B shop?

Using B2B roles, you control which users are allowed to perform which actions, and with approval processes you can make orders subject to approval. The connector supports the assignment of roles and company structures. For details, see [B2B Roles & Approval Process](/shopware/shopware6_en_us/customer-management/b2b-roles-and-approval-process.md).

### What is the difference between B2B and B2C customers in the connector?

B2C customers are private customers with a single account; B2B customers are corporate customers, possibly with several users, price groups, and approval processes. The connector can synchronize both types and distinguishes them via the customer or contact assignment. For details, see [Specifics for B2B/B2C Customers](/shopware/shopware6_en_us/customer-management/specifics-for-b2b-b2c-customers.md).

### How are several ship-to addresses per customer synchronized?

The connector synchronizes several addresses per customer between Shopware and Business Central, so that different ship-to and bill-to addresses are available for B2B customers. For details, see [Synchronize Ship-to Addresses](/shopware/shopware6_en_us/customer-management/synchronize-ship-to-addresses.md).

### Can I upload customers from Business Central to the shop?

Yes. Using the customer upload, customer accounts, addresses, and customer groups are transferred from Business Central to Shopware – useful for enabling existing customers for the shop. For details, see [Customer Upload (BC to Shopware)](/shopware/shopware6_en_us/customer-management/customer-upload-bc-to-shopware.md).


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.solutioo.de/shopware/shopware6_en_us/frequently-asked-questions-faq/faq-customers-and-b2b.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
