Introduction
In the case the orders are exported to and archived in an external system (e.g., order management system, ERP) or if the data for a specific customer have to be deleted the ICM provides the order deletion feature. On the one hand side you may reduce costs for data storage on the other hand this also takes into account customer requests for data deletion in compliance with GDPR (General Data Protection Regulation).
The Order Deletion feature allows the shop manager to mark orders, e.g., for specific customers that have to be deleted by using the order status import. The system administrator is able to configure the deletion job in the SMC. The following chapters describe the order deletion workflow and also the side effects of the order deletion.
References
- Concept - Order Fulfillment Status Import
- Job - Delete Orders in Reference - Intershop 7.9 Jobs
Feature Overview
Workflow
Following the e-commerce reference process we have to tag the order which has to be deleted in a first step. For setting this flag the order status import is ready-to-use. As a second step you have to run the order deletion job via SMC. We provide a default job via DBINIT. You can use the default job or create your own to match your requirements.
Mark Orders to be Deleted
Order status import schema
<xs:attribute name="toBeDeleted" type="xs:boolean"/>
Order status import example
<order id="" status="" toBeDeleted="true"> <order id="" status="" toBeDeleted="false">
Find concrete example here Order Status Import.
Delete Orders
For the order deletion we introduced the Job - Delete Orders. The job triggers order deletion with all according references.
By default it deletes orders whose toBeDeleted flag is to true and whose status is not PENDING, MANUAL_INTERVENTION_NEEDED or EXPORTFAILED.
The status selection can be overwritten by defining the attribute ExcludedStatuses (data type: String), with comma separated values (e.g., ExcludedStatuses=NEW,EXPORTFAILED). If set to NONE no statuses are excluded.
It is also possible to define the maximum number of orders, which are to be deleted during a run (default 10,000). Larger values are not recommended due to possible database issues/locks. The value can be overwritten by the attribute MaxNumberOfOrders (data type: Integer).
Note
You have to trigger the RunCacheRefresh job after deleting an order via deletion job to update object references like PromotionPO:getPromotionOrderAssignmentPOs.
Side Effects
Orders are linked to some other objects in the Intershop Commerce Management. In the following you find such affected objects. Usual the orders are linked in each table. After a successful order deletion the link will be removed whereas the order number is still present.
Gift Cards & Certificates
For having a transaction overview about gift cards and certificates redeemed in the shop we provide a section in Marketing | Gift Cards & Certificates. Here the shop manager is able to check transactions for each bought gift card and certificate. In the transaction table a link to the related order.
Promotion Code Groups - Promotion Codes
To get an overview about the promotion codes redemption we provide a section in Marketing | Promotion Code Groups | Codes. Here the shop manager is able to check redemption of specific promotion codes. In the given table an order link is present.
Contracts
In a business channel the shop manager is able to create contracts for customers. To check the exceedance of the contract revenue we provide an order overview in Customers | Contracts for each contract. A link to the placed orders is present.
