1. Contents
  2. Reference
  3. Channels and tasks
  4. CAO-Faktura
  5. Customers Erase

Customers Erase

The action reports that a customer is no longer kept in the ERP system. TRADElube then deletes the customer assigned to that identifier, together with their addresses.

What gets transferred

The ERP system sends nothing but the identifier. What happens afterwards is the same as deleting by hand: the orders are kept in full, with name, address and amounts, because those entries sit on the order itself. What is lost is the link between the two. In full under customers.

Where no customer is found for the identifier, the report is fine all the same. The ERP system gets the answer that there was nothing to delete, and traces carry an entry noting that it was skipped.

How the transfer plan is built

This action has no transfer plan. There is nothing to map, because all that arrives is the identifier of the record meant to disappear. So the channel's Transfer Plans section carries no Erase tab under Customers.

Special features and limits

The connected shop learns nothing. A customer account existing in the shop stays there. What is deleted is the record in TRADElube. So a deletion request under data protection law is not settled by this, but has to be raised in every system involved separately. Which systems those are is visible on the customer in the Channels section.

A customer without an identifier cannot be reached. This action works exclusively through the channel mapping. A customer created in TRADElube who never went to the ERP system cannot be deleted through it.

Further reading