Customers Update
The action brings a customer from the ERP system into TRADElube, with their master data and their billing address. It is the route for everyone who keeps their customer master data in CAO-Faktura and needs it in the connected shops.
What gets transferred
Each call is about exactly one customer. TRADElube looks them up through the identifier sent along, and where the ERP system sends none, through the customer number.
Two numbers sit on a customer, and the difference decides the plan's default. Customer Number comes from your number range, Origin Customer Number from the connected system. Out of the box only the second is ticked: TRADElube issues its own number and remembers the ERP system's alongside. If you want to carry the ERP system's number throughout instead, tick Customer Number as well.
The address always goes to the billing address. Where the customer has none yet, TRADElube creates it. This action does not transfer a shipping address.
How the transfer plan is built
The plan sits in the channel, in the Transfer Plans section under Customers and there in the Update tab. It has three sections.
| Section | What sits in it |
|---|---|
| Selection | The single assignment Condition, deciding whether the customer is taken over at all |
| Common | The master data on the customer: the two numbers, Salutation, Gender, Company, name, phone number, email and birthday |
| Address | The same name fields once more, plus Address Line 1, Zip Code, City and Country |
Name and salutation sitting in both sections is not a duplication: the upper block is the customer, the lower one their billing address, and the two keep these fields separately. A customer can be named differently from the recipient on their invoice.
Condition is unticked out of the box, and then every reported customer arrives. You tick it where only part of the customer base is meant to reach TRADElube: the customer's price level and their VAT identification number stand ready as sources, and you write the decision as a script. That is how a customer base can be narrowed down to the resellers, for instance.
Special features and limits
Salutation and country are found through their name, not through a mapping. The salutation has to be named under Settings exactly as the ERP system sends it, and the country arrives as a country code. Whatever cannot be matched stays empty, without the customer failing because of it.
The gender knows three values. The ERP system sends m or f, and everything else arrives as unknown.
Further reading
- CAO-Faktura: login details, configuration, mappings and the other eighteen actions
- Customers Export: the other way round, out of TRADElube into the ERP system
- Customers Erase: what happens when the customer disappears in the ERP system
- Customers (reference): the detail view of a customer, their address blocks and the two numbers
- Number ranges (reference): where the customer number TRADElube issues itself comes from
- Transfer plan (concepts): plan, section and assignment, plus the three ways to determine a value