For the complete documentation index, see llms.txt. This page is also available as Markdown.

Customer Upload (BC to Shopware)

Customers can be transferred from Business Central to Shopware, for example to provide B2B accounts with stored terms and conditions there.

Prerequisite

The customer must be flagged as a web customer (SOUSHW Web Customer = Ja). Only then is the upload available.

Mandatory information (checked before upload)

Before the upload, the connector checks the following, among other things:

  • Email address and name

  • Customer group (GroupId)

  • Salutation (SalutationId)

  • Sales channel

  • Country/region mapping

Procedure

1

Prepare the customer

Set Web Customer = Yes and maintain the customer group, salutation, and sales channel.

2

Upload

Open the Customer Card and choose Upload Customer. Once successful, the Web-ID is filled in.

3

Follow-up synchronization

The ship-to addresses and, if applicable, the customer price list are then synchronized automatically.

Fields on the Customer Card

Field
Meaning

Web-ID

Shopware customer ID (after upload)

Web Customer

Flagged for upload

Sales Channel / Salutation / Customer Group

Mapping values

Account Type

Business or Private

Synchronized / on / Message

Sync status

If a customer is changed, it is automatically flagged as not synchronized and transferred again during the next run.

Frequently Asked Questions

Which endpoint is used to transfer customers and addresses?

Customers are created (POST) or updated (PATCH) via customer, and ship-to addresses via customer-address. After a successful upload, the "SOUSHW Web ID" is set on the customer and – if one exists – the customer price list is synchronized afterwards automatically.

Which information must be maintained before the customer upload?

Before the upload, the connector checks the email address and name as well as the mappings for customer group (GroupId), salutation (SalutationId), sales channel, and country/region. If any of this information is missing, the upload is canceled with a message – maintain the corresponding mappings first.