Customers Upload
The task creates your customers in the Shopware shop and keeps them current there, with billing and shipping address. It is the opposite direction to the way a customer arrived: in TRADElube they are created by Orders Download or by hand.
What gets transferred
Per customer one customer record goes into the shop, plus their billing address and, where it differs, their shipping address. Both are entered in the shop as that customer's default addresses.
The task does not transfer properties on the customer. Whatever you keep on a customer through properties stays in TRADElube. There is no counterpart in the shop for TRADElube to address.
What goes along is what is new, what has changed and what failed last time. There is no period as with the orders: a customer does not age.
How the transfer plan is built
The task has exactly one plan, so there is no tab bar above the sections. The plan carries four sections:
| Section | What sits in it |
|---|---|
| Selection | Condition, meaning which customers belong in this shop at all, and New Item |
| Common | The customer themselves: Customer Number, salutation and title, company, first and last name, e-mail address, birthday, plus the two fixed values |
| Billing Address | Address, country and phone number for the invoice |
| Shipping Address | The same for the delivery |
Two values are entered as fixed values because Shopware requires them, the Customer Group and the Default Payment Method. Both are pre-filled with their German names, Standard-Kundengruppe and Vorkasse. In a shop with an English system language they are called something else, and until you have adjusted the two values every customer fails. Both are written on creation only. If the customer later changes their payment method in the shop, TRADElube does not overwrite it.
The same holds for the Customer Number: it only goes along when the customer is created in the shop. A number assigned in the shop is thereby preserved.
Shopware requires more mandatory fields than TRADElube does. On the customer, first name, last name and e-mail address are mandatory; on each address, street, postcode, city and country as well. TRADElube does not know that obligation, so a company contact without a first name gets stuck and shows up in the traces as a failed transfer. The remedy sits in TRADElube, not in the shop: add the first name.
The phone number may come from the customer. In both address sections, Phone Number with the note (Customer) is available as a second source beside the address's own field. That is the right setting where you keep the number on the customer and not per address.
Salutation and country come from the mappings, not as text: Mapped Salutation from the channel's Salutation tab and Mapped Country from the Countries tab. A country without a mapping makes the address fail, because in the shop it is mandatory.
Special features and limits
A customer is not deleted in the shop. Where they fall away on your side or drop out of the condition, the execution records that as a skipped transfer and leaves the record standing in the shop. So you remove an account in the shop.
The way back is not a task but an order. There is no Customers Download. Whatever the customer changes about themselves in the shop reaches you the next time they order, see Orders Download.
Where both directions run, the order of the executions decides. A customer created out of the shop by Orders Download carries the same channel mapping as one uploaded by this task. So settle where a customer's master data is maintained.
Further reading
- Shopware: prerequisites, connection, the twelve mappings and the other twelve tasks
- Orders Download (Shopware): the way a customer arrives in TRADElube
- Customers (reference): the detail view of a customer and its sections
- Mappings and channel mappings (concepts): why salutation and country go through a table
- Transfer plan (concepts): plan, section and assignment, plus the three ways to determine a value