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

Products Erase

The action reports that an article is no longer kept in the ERP system. TRADElube then deletes the product assigned to that identifier, and the connected shops strike it out as well on the next execution.

What gets transferred

The ERP system sends nothing but the identifier. What happens afterwards is the same as deleting by hand: the article disappears together with its texts, prices, stock and properties. Its images stay in the media directory, because what sits there is the file and not the link. Orders stay untouched as well: their positions keep quantity, price and description and merely lose the reference to the product. In full under products.

Where no product 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 Products.

Special features and limits

A parent article takes its variants along. Where the ERP system reports the parent product for deletion, the versions hanging below it disappear as well, even where the ERP system keeps them individually.

Taking it out of the range is often the better move. An article no longer sold but which a customer is meant to see in their order history is better switched off in the Active field than deleted. Products Update does that. Deleted is deleted, and an article reported again later is created afresh, with a new channel mapping.

Further reading