GDPR Suite Anonymization Data Retention | Erase customer data on time
In-App Purchases
Subscriptions
Description
Highlights
- Your revenue figures stay correct, only names and addresses disappear
- Nothing happens without a dry run and your explicit release
- Handle Art. 17 and 18 GDPR requests in a few clicks
- Complete evidence for audits, with no personal data in the log
- Periods and rules controlled separately per sales channel
Features
- Anonymize orders after the retention period, amounts, taxes and line items stay intact
- Optional second stage: delete orders completely after a longer period
- Delete inactive customer accounts after a period you choose, default 1095 days
- Remove guest accounts once all their orders are anonymized
- Delete stored document files after the period, number and order reference remain
- Clean up customer comments, review authors and the mail log after the period
- Dry run with key figures and a sample without names or email addresses
- Release per rule and sales channel, confirmed warnings are recorded
- Erasure request page: delete or restrict (Art. 17, 18 GDPR), restricted orders stay protected
- Run log and release journal, each with CSV export, kept for up to 180 days
- Covers PayPal, Shopware Commercial and the Migration Assistant
- Four permission levels, deleting orders requires its own permission
- Daily run in batches, large backlogs can also be run from the command line
- In-app purchase Data subject rights: Privacy account page, deadlines, access as PDF, JSON, CSV
- In-app purchase Four-eyes principle: orders are only deleted once a second person confirms
About the Extension
Your shop has been running for years. The database holds thousands of old orders with names, addresses and phone numbers, plus customer accounts nobody has logged into for ages. You can't just delete the invoices. But you can't keep the personal data forever either.
The problem
The GDPR says you may only keep personal data for as long as you need it. Tax and commercial law say you must keep accounting records for years. Out of the box, Shopware has no retention periods for orders. So everything stays where it is, or someone deletes things by hand and hopes the books still add up afterwards. Both are risky, and in neither case can you prove what happened and when.
The solution
The GDPR Suite reconciles the two obligations. It removes personal data only once the period has ended, and it leaves the amounts, taxes and line items of your orders untouched. You set the periods, check every rule in a dry run and release it explicitly. From then on a daily task processes the due records. Every release is recorded permanently.
What's in it for you
Your figures stay correct. Anonymization overwrites names, addresses and contact data only. Amounts, taxes, line items, dates and states remain, and so do your revenue reports.
Nothing happens until you've seen it. All rules are switched off by default. Each rule first counts in a dry run what would be due, without changing any data. Only your release makes it live. Change a period later and the release is lifted automatically.
Erasure requests in a few clicks. A customer emails you asking to be deleted. You open her customer page and click GDPR action. The preview shows which orders would be restricted, anonymized or deleted. Orders still inside their retention period are only restricted, never deleted.
Evidence that holds up when someone asks. Who checked and released which periods, and when? The Releases & confirmations list answers that. Its entries cannot be changed and are stored for up to 180 days; with the CSV export you keep them longer. The run log contains numbers only, no personal data.
Less room for mistakes. Deleting orders requires a permission of its own and an explicit confirmation. Restricted orders are protected against deletion until their period ends, including via APIs and imports.
How the plugin works
The suite knows five rules: anonymize orders (optionally followed by deletion as a second stage), delete document files, remove guest accounts with orders, delete inactive customer accounts and clean up business letters. Business letters cover customer comments, review author names and mail log entries. The stars and text of your reviews stay.
You enter the periods in the plugin configuration, with different values per sales channel if you like. Under Customers → GDPR suite you see per channel which rule is switched on and released, how much was due last time and when something last ran. Restricted and skipped records appear under Restrictions & exceptions, with reason and restriction date.
Besides the Shopware data, the suite covers Shopware's own extensions PayPal, Shopware Commercial and the Migration Assistant raw data when they are installed. It does not touch tables of other plugins; their data is up to the respective plugin.
Optional in-app purchases
The base plugin works fully without any add-on. Two monthly add-ons are available: Data subject rights at €7.90 and Four-eyes principle at €4.90 per month, both net.
Data subject rights. Logged-in customers file requests on the Privacy page in their account: access, erasure, rectification, objection or portability, with the types chosen per sales channel. Requests by letter or email you record under Customers → Privacy requests after checking their identity. The plugin tracks the one-month deadline, allows one two-month extension and reminds you daily, optionally by email, without personal data. Rejections need a reason; erasure uses the familiar erasure request page. The access report comes as a readable PDF (Art. 15) and as JSON and CSV (Art. 20), across every data source the suite knows.
Four-eyes principle. A release or erasure request that deletes orders becomes an approval request. It only takes effect once a different user with the permission "Confirm deletion release" confirms it, never the requester. Requests expire after 7 days and become void when the settings change. They appear under Approval requests, every step lands in the journal and the CSV export. Switchable per sales channel.
Typical use cases
The first clean-up after years. Your shop has orders going back to 2012. You set your retention period, check the number of due orders in the dry run along with a sample showing order number and total, release the rule and let the backlog be worked off in small portions.
The erasure request by email. A customer asks for his account to be deleted. You verify his identity, open the Erasure request page and delete the account. His invoices from last year stay restricted until the period ends. After that the order rule anonymizes them automatically.
One shop, several countries. You run a German storefront and a UK storefront in the same Shopware. The defaults follow German periods. For the UK sales channel you store the periods your accountant gives you, and releases always apply per rule and channel.
B2B and B2C with different periods. In your trade channel you keep customer accounts longer, in your consumer shop the default of 1095 days applies.
Technical facts for your IT team
- Shopware 6.7, PHP 8.2 or later.
- Own tables for runs, restrictions, releases and the journal, plus privacy and approval requests with the in-app purchases. Shopware's tables get no additional columns. Once you release them, the rules overwrite and delete personal data in orders, customer accounts and other Shopware data, which is their purpose.
- The plugin does not send any data to external servers.
- No storefront output, no impact on your customers' page load times. Exception: the Privacy account page from Data subject rights, in your theme's account layout.
- Processing via the message queue in batches of 50 to 500 records (default 200). An interrupted run picks up where it stopped.
- Requires a running message queue worker and the scheduled task runner. Large runs can be started from the command line, but releasing only works in the Administration.
- Four permission levels via Administration roles. The in-app purchases add three roles for privacy requests and the additional permission "Confirm deletion release".
- Uninstallation: choose to keep the data and run log, restrictions and journal remain. Otherwise the plugin tables are removed.
Notes
Which retention periods apply to your shop is for you to decide with your tax advisor and your data protection officer, and the GDPR Suite puts that decision into practice. Try the suite on a copy of your shop first and take your time with the dry run to see what would be due.
Legal notice
We accept no liability for legal requirements. Please check the use of this plugin with a qualified legal advisor.
Your shop has been running for years. The database holds thousands of old orders with names, addresses and phone numbers, plus customer accounts nobody has logged into for ages. You can't just delete the invoices. But you can't keep the personal data forever either.
The problem
The GDPR says you may only keep personal data for as long as you need it. Tax and commercial law say you must keep accounting records for years. Out of the box, Shopware has no retention periods for orders. So everything stays where it is, or someone deletes things by hand and hopes the books still add up afterwards. Both are risky, and in neither case can you prove what happened and when.
The solution
The GDPR Suite reconciles the two obligations. It removes personal data only once the period has ended, and it leaves the amounts, taxes and line items of your orders untouched. You set the periods, check every rule in a dry run and release it explicitly. From then on a daily task processes the due records. Every release is recorded permanently.
What's in it for you
Your figures stay correct. Anonymization overwrites names, addresses and contact data only. Amounts, taxes, line items, dates and states remain, and so do your revenue reports.
Nothing happens until you've seen it. All rules are switched off by default. Each rule first counts in a dry run what would be due, without changing any data. Only your release makes it live. Change a period later and the release is lifted automatically.
Erasure requests in a few clicks. A customer emails you asking to be deleted. You open her customer page and click GDPR action. The preview shows which orders would be restricted, anonymized or deleted. Orders still inside their retention period are only restricted, never deleted.
Evidence that holds up when someone asks. Who checked and released which periods, and when? The Releases & confirmations list answers that. Its entries cannot be changed and are stored for up to 180 days; with the CSV export you keep them longer. The run log contains numbers only, no personal data.
Less room for mistakes. Deleting orders requires a permission of its own and an explicit confirmation. Restricted orders are protected against deletion until their period ends, including via APIs and imports.
How the plugin works
The suite knows five rules: anonymize orders (optionally followed by deletion as a second stage), delete document files, remove guest accounts with orders, delete inactive customer accounts and clean up business letters. Business letters cover customer comments, review author names and mail log entries. The stars and text of your reviews stay.
You enter the periods in the plugin configuration, with different values per sales channel if you like. Under Customers → GDPR suite you see per channel which rule is switched on and released, how much was due last time and when something last ran. Restricted and skipped records appear under Restrictions & exceptions, with reason and restriction date.
Besides the Shopware data, the suite covers Shopware's own extensions PayPal, Shopware Commercial and the Migration Assistant raw data when they are installed. It does not touch tables of other plugins; their data is up to the respective plugin.
Optional in-app purchases
The base plugin works fully without any add-on. Two monthly add-ons are available: Data subject rights at €7.90 and Four-eyes principle at €4.90 per month, both net.
Data subject rights. Logged-in customers file requests on the Privacy page in their account: access, erasure, rectification, objection or portability, with the types chosen per sales channel. Requests by letter or email you record under Customers → Privacy requests after checking their identity. The plugin tracks the one-month deadline, allows one two-month extension and reminds you daily, optionally by email, without personal data. Rejections need a reason; erasure uses the familiar erasure request page. The access report comes as a readable PDF (Art. 15) and as JSON and CSV (Art. 20), across every data source the suite knows.
Four-eyes principle. A release or erasure request that deletes orders becomes an approval request. It only takes effect once a different user with the permission "Confirm deletion release" confirms it, never the requester. Requests expire after 7 days and become void when the settings change. They appear under Approval requests, every step lands in the journal and the CSV export. Switchable per sales channel.
Typical use cases
The first clean-up after years. Your shop has orders going back to 2012. You set your retention period, check the number of due orders in the dry run along with a sample showing order number and total, release the rule and let the backlog be worked off in small portions.
The erasure request by email. A customer asks for his account to be deleted. You verify his identity, open the Erasure request page and delete the account. His invoices from last year stay restricted until the period ends. After that the order rule anonymizes them automatically.
One shop, several countries. You run a German storefront and a UK storefront in the same Shopware. The defaults follow German periods. For the UK sales channel you store the periods your accountant gives you, and releases always apply per rule and channel.
B2B and B2C with different periods. In your trade channel you keep customer accounts longer, in your consumer shop the default of 1095 days applies.
Technical facts for your IT team
- Shopware 6.7, PHP 8.2 or later.
- Own tables for runs, restrictions, releases and the journal, plus privacy and approval requests with the in-app purchases. Shopware's tables get no additional columns. Once you release them, the rules overwrite and delete personal data in orders, customer accounts and other Shopware data, which is their purpose.
- The plugin does not send any data to external servers.
- No storefront output, no impact on your customers' page load times. Exception: the Privacy account page from Data subject rights, in your theme's account layout.
- Processing via the message queue in batches of 50 to 500 records (default 200). An interrupted run picks up where it stopped.
- Requires a running message queue worker and the scheduled task runner. Large runs can be started from the command line, but releasing only works in the Administration.
- Four permission levels via Administration roles. The in-app purchases add three roles for privacy requests and the additional permission "Confirm deletion release".
- Uninstallation: choose to keep the data and run log, restrictions and journal remain. Otherwise the plugin tables are removed.
Notes
Which retention periods apply to your shop is for you to decide with your tax advisor and your data protection officer, and the GDPR Suite puts that decision into practice. Try the suite on a copy of your shop first and take your time with the dry run to see what would be due.
Legal notice
We accept no liability for legal requirements. Please check the use of this plugin with a qualified legal advisor.
Details
- Available: English, German
- Latest update: 18 November 2026
- Publication date: 18 November 2026
- Version: 6.7.1
- Category: Checkout / Cart process
Resources
Reviews (0)
About the Extension Partner
BuI Hinsche GmbH
Partner Status
-
Shopware
Bronze Partner -
Shopware
Premium Extension Partner
Details
-
Ø-Rating:
4.3
Average rating of 4.3 out of 5 stars
- Partner since: 2014
- Extensions: 115
- Certifications: 2
Support
- Based in: Germany
- Speaks: German, English
- Response time: Very quickly
6.7.1 6.7.0.0 - 6.7.16.1
- Shopware Commercial: customers and start orders of a subscription that is not cancelled (paused included) are skipped and listed under "Restrictions & exceptions" with the reason, so renewals keep working; the dry run counts them.
- Shopware Commercial: a business partner with employee accounts is not deleted even when the extension is switched off for the sales channel; customers with quotes or shopping lists show as blocked in the dry run and the erasure preview; addresses of pending B2B approval orders are exported and anonymized through the order.
- Fix: abandoned draft versions of an order are found and deleted also after Shopware's 30-day cleanup; tables of Shopware extensions are anonymized in the document versions of an order as well.
- Anonymization: in tables of Shopware extensions, department, additional address lines and customer number count as personal data; for the Migration Assistant (version 16 and later), values corrected by administrators are deleted too.
- Fix: if the fallback anonymization after a refused deletion fails, the record is still marked skipped and the run continues; the plugin log names the error; batches already completed stay counted in the run. Deactivating and uninstalling delete queued files with system rights.
- Administration: date-only fields show the same day in every time zone; the failure notice of a request follows its latest run; the export on the customer page drops a response once another customer is open; every run detail has a label; "Restrictions & exceptions" names a running subscription or a business partner with employee accounts as the reason.
- Fix: if marking a failed record throws, the records already processed in the same batch are still counted in the run log and reported; deactivating the plugin first deletes the files still queued for deletion, so an uninstall without keeping data leaves none behind. Storefront: the German privacy page in the customer account uses the formal address like the storefront.
- Administration: the deletion summary of the dry run and of the release shows the order dates and the revenue formatted in the language of the administration; the cutoff date of the dry run, of the release and of the run appears as a date as well, without time, and stays the same day in every time zone; the mail log warning uses singular and plural; the dry run counts the same sales channels blocking the mail log as its warning, without the sales channel being released.
- Scope: the plugin processes Shopware tables and the tables of the Shopware extensions PayPal, Shopware Commercial and Migration Assistant, and only through their own DAL definition.
- Fix: if the database refuses to delete a customer account because of a table of another plugin, the account stays with its reason and blocking table; due orders of the customer are anonymized anyway, orders in retention are restricted. A request under Art. 17 stays open and its detail page shows the failure count of the run. A refused order deletion anonymizes the order, counts it in the run and shows it under "Restrictions & exceptions".
- Fix: document files are deleted only after the batch succeeded; a rolled back batch can no longer remove a file on an external message transport (for example Redis, RabbitMQ).
- Fix: anonymizing or deleting an order that started a subscription (Shopware Commercial) no longer fails; required data fields in tables of Shopware extensions are emptied instead of set to null, and IP addresses there are replaced by 0.0.0.0.
- Fix: carts of expired customer sessions are deleted with the account (Shopware 6.7.0.0 to 6.7.2.2).
- Fix: a sales channel setting of the periods made via system:config:set is checked against the stored values of that channel.
- Fix: deleting an order also removes the status history of its captures and refunds.
- Performance: guest accounts ready for deletion are selected in one query; the clean-up of the change log runs once at a time, deletes its queue in batches and continues an interrupted pass.
- Administration: the "Save " button of the export disappears when another customer or request is opened.
- Technical: shop and extension data goes through Shopware's Data Abstraction Layer (DAL), including draft and document versions, the change log and the tables of Shopware extensions. These tables are only processed while the extension is active.
- Uninstall: Shopware removes the plugin's scheduled tasks itself; the plugin no longer touches the task list for this.
- Fix: anonymizing an order also clears the internal comments of status changes of the order, its deliveries and payments (available from Shopware 6.7.x); deleting an order removes its status history.
- Administration: exports (access report, run log, release journal) are no longer downloaded automatically; after the export a "Save " button appears.
- Access report: the raw data of the Migration Assistant no longer contains credentials of the source shop (password, encoder, session ID and other secrets, also nested).
- Fix: anonymizing an order clears the internal comment together with the customer comment; staff notes can hold personal data.
- Fix: the marker of a restricted order can no longer be deleted through the API, not even by administrators; before, this lifted the restriction and the order could then be deleted. The permission "Release the deletion of orders" no longer includes deleting markers.
- Fix: the save check of the deletion period treats a 0 in a sales channel like an empty field and checks the value of "All sales channels", as the help text describes.
- Fix: the console command gdpr:retention:run --sync (systems without message worker) no longer runs out of memory on large data sets. Between two batches it resets the services like the message worker does; close to the PHP memory limit (80 %) it ends the run cleanly and says so, a new start continues at once. Before, the process aborted after about 60,000 orders with 2 GB and the run stayed blocked for two hours.
- Clarification: orders of deleted accounts stay restricted until the end of the period currently configured. If the period is shortened, the next run anonymizes them, or deletes them once the deletion period has passed; manual deletion stays blocked as long as the restriction exists.
- Fix: users with only the permission "Manage extensions" can install, update and uninstall the plugin; the mail template of the deadline reminder is written with system rights.
- Fix: a deletion confirmed under the four-eyes principle also runs through the message queue with system rights; the confirming person needs no deletion permissions of their own.
- Fix: the four-eyes principle applies to the single action as soon as any sales channel whose orders are deleted has it switched on, not only the customer's own channel.
- Fix: the clean-up of the change log (version_commit_data) only removes the queue entries it has processed; entries added while it runs are processed in the next pass.
- Fix: scheduled tasks are only registered when the plugin is active and are removed on uninstallation.
- Access report: tables of Shopware extensions that are linked to the customer's orders are included, with every column; extensions switched off under "Disabled Shopware extensions" are included as well.
- Run log: entries can no longer be deleted via the API; they are removed by the log retention only.
- Administration: a request is marked as exported only after the export succeeded; a failed export shows the reason; "Open run" only for users of the retention module; the empty state of the releases only appears without releases; purchase fields stay greyed out under Shopware 6.7.0 to 6.7.4.
- Account page "Privacy": line breaks count as one character, a message up to the field limit is no longer refused.
- Four-eyes principle for the single action: the request is bound to the configuration of every sales channel the customer ordered in; a change in any of them discards it.
- Access report: binary content is included as a complete copy (Base64); a row linked to the customer and to one of the orders appears once.
- In-app purchase "Data subject rights" (Swpgdpr_compliance_rights): customer account page "Privacy" and store API route /store-api/account/swp-gdpr/privacy-requests for access, erasure, rectification, objection and data portability requests of logged-in customers; switchable per sales channel with selectable request types.
- Privacy requests in the administration (Customers → Privacy requests): list, detail and recording of requests received by letter or e-mail with verified identity; one-month deadline with one extension by two months, status handling with mandatory reason for a rejection, erasure requests answered through the existing single erasure action (restriction under Art. 18 kept), new ACL roles view, edit/export and record. The detail page names the involved users instead of their ids and hides empty fields.
- Data access report: complete copy as JSON and CSV (Art. 20) and readable PDF (Art. 15) over all data sources, including every order, address, delivery, payment, line item and document. Daily deadline reminder as admin notification and optional digest mail per sales channel (mail template "GDPR: privacy request deadline reminder"), without personal data. After the purchase ended, existing requests stay editable and keep reminder and export; closed requests lose their free text after 180 days and are deleted after three years.
- In-app purchase "Four-eyes principle" (Swpgdpr_compliance_four_eyes), switchable per sales channel: a release or erasure request that deletes orders becomes an approval request (admin API answers 202) and takes effect only after a different user with the new additional permission "Confirm deletion release" confirmed it; nobody confirms their own request, administrators confirm those of others, integrations neither request nor confirm. Requests expire after 7 days (daily task) and become void when the settings change; releases made before the switch stay valid and are marked in the overview. New view "Approval requests"; every step (request, confirmation, rejection, withdrawal, end) is a journal entry with its approval request id, also in the CSV export. Without the purchase the single-person procedure applies; open requests stay readable.
- Configuration: a period below 8 years for anonymizing orders shows a warning right below the field (§ 147 AO; shorter only if the accounting records are kept in another system such as the ERP). The period remains freely adjustable from 1 year.
- Configuration: the settings of both in-app purchases are at the end of the page and greyed out until the purchase is active; the privacy page in the customer account is off by default and is switched on after the purchase.
- Fix: deleting orders (second stage) no longer books the quantities of deleted orders back into product stock and no longer aborts on product line items without a product reference (migrated data).
- Fix: uninstalling no longer fails with HTTP 400 when a sales channel only overrides the deletion period; removing the plugin configuration is never rejected by the period check.
- Fix: the accessible (HTML) copy of a document is found through the document on every Shopware 6.7 patch; on 6.7.0 to 6.7.2 the document purge and the order deletion no longer leave it behind.
- Fix: orders with cancellation invoices or credit notes are deleted without a write error on Shopware below 6.7.9 (reference to the invoice is cleared first).
- Fix: account rules delete orders of another sales channel only if that channel has a valid release of the same rule including the deletion stage; otherwise these orders are anonymized only.
- Fix: documents whose file was purged are marked static, so Shopware no longer renders the file again on the next download.
- Fix: Shopware Commercial subscriptions: addresses (subscription_address) and the order snapshot (subscription.converted_order) are cleaned with account deletion and order anonymization.
- Fix: VAT ids (vat_id, vat_ids) in tables of Shopware extensions are recognized as personal data.
- Fix: account deletion removes newsletter subscriptions in every sales channel of the customer, not only in the account's own one.
- Fix: every error of a batch counts towards the failure limit, so a run no longer stays in "running" (e.g. missing permission, restrict violation); runs stuck in queued/running without activity for the run log period are aborted and removed by the daily cleanup, including the customer id of an erasure.
- Performance: audit-log rows (version_commit_data) are removed in one pass after the run instead of a full table scan per batch.
- Configuration: help texts state that in a sales channel both an empty field and 0 take the value of "All sales channels" (deletion period, batches per run); to delete orders in some sales channels only, keep 0 under "All sales channels" and enter the period in those channels. Disabled Shopware extensions: no selection inherits.
- Security: the complete copy of the access report leaves out credential columns of tables of Shopware extensions (password, *_hash, token, secret, API keys and similar).
- Fix: every setting that moves a cutoff voids the release and requires a new dry run: the order period for documents with their own period and the reference date for business letters.
- Fix: the mail log without sales channel is cleaned up to the cutoff of the most conservative sales channel (longest period with its own reference date).
- Fix: documents whose file is still referenced (document files from Shopware 6.7.10) are skipped once per run instead of being selected again in every batch.
- Access report: the child tables of Shopware Commercial subscriptions are included.
- Access report (PDF): dates are shown in the format of the language, the reference date as text and a deletion period of 0 as "never".
- Store API: an invalid request type (e.g. a list) is answered with 400 instead of 500.
- Configuration: the default placeholder for review authors is "Anonymous".
- Administration: changing the customer in the single action discards the approval request of the previous customer and ignores late previews; the selection of the dry run is locked while it runs; the journal names the permissions "Confirm deletion release", administrator and system; order and customer links in the restriction list only for users who may open them.
- Administration: the viewer role no longer contains the unused privileges system_config:read and scheduled_task:read; the documentation button no longer causes a 403 notification for users without plugin:read; the deletion period check and the greyed-out purchase fields also work on Shopware 6.7.0 to 6.7.11; the releases tab is paginated, each list loads once per page change and the inactive "Edit" action is gone.
6.7.0 6.7.0.0 - 6.7.16.1
- First release of the GDPR suite for Shopware 6.7.
- Retention rules per sales channel: inactive customer accounts, guest accounts with orders, orders (default 8 years, start at order date or end of the calendar year), document files and business letters (default 6 years).
- Orders are anonymized instead of deleted: amounts, taxes, line items, dates and states stay identical, names, addresses, contact data, comments, tracking codes and payment custom fields are overwritten with deterministic placeholders; draft versions and audit-log entries are cleaned as well.
- Restriction of processing (Art. 18 GDPR): orders of deleted accounts stay locked until their retention period ends and cannot be deleted.
- Dry run (administration and CLI) with numbers, sample without personal data, list of tables that are not covered and custom field keys; live runs only after a release per rule and sales channel that is bound to the reviewed settings; the overview names every switched-on rule without a valid release together with the reason in plain text.
- Processing in batches through the message queue, resumable, idempotent and isolating faulty records; CLI commands gdpr:retention:run, gdpr:retention:status and gdpr:fk-scan.
- Single erasure request (Art. 17 GDPR) for one customer with retention check per order.
- Extension point for tables of other plugins with providers for Shopware Commercial, PayPal, NetInventors Access Manager, ChannelPilot, Coolbax external orders, Mollie subscriptions, Migration Assistant raw data and FroshMailArchive (archived mails of an anonymized order are only removed once they are past the business letter period of the sales channel, younger ones follow the business letter rule); redeemed individual promotion codes lose the customer name on anonymization.
- Run log without personal data with CSV export, own log channel, ACL roles viewer, editor and executor.
- Every retention period is set per sales channel (orders, documents, business letters, inactive accounts); defaults are the German standard values, only a technical minimum of one day or year applies.
- Orders in two stages per sales channel: anonymize after X years (default 8) and, optionally, delete after Y years (empty or 0 = never; only effective when Y is longer than X, otherwise the deletion stage stays locked and the overview, dry run and release dialog warn). Deletion also covers anonymized orders and removes the order with documents, files (including the accessible file), every version and the audit log, never while an order is restricted; orders referenced by restricting tables of other plugins are anonymized instead and reported. Coolbax external orders follow the same stages. The dry run shows both stages separately with count, period and gross revenue per currency of the orders to delete.
- Warnings that must be confirmed one by one before a rule is released or an erasure request deletes orders: deletion stage and every period below its standard value. The release API refuses missing confirmations.
- Deleting orders needs its own permission "Release the deletion of orders" (in addition to release and execute): releasing or starting a rule with deletion stage, confirming the deletion warning and an erasure request that deletes orders. The journal records the permission each entry was made under: release or execute (deletion permission for a confirmed deletion), dry run for a revocation.
- Guest accounts whose orders were deleted are marked and removed by the guest rule once nothing is open; guests that never ordered stay with Shopware's own cleanup task.
- Append-only journal of releases, revocations and confirmations (warnings with text version and hash, language, periods, configuration hash, admin user with name snapshot); live runs, the run log and the CSV export name the confirmation they are based on. New view "Releases & confirmations" with filters by type and rule and its own CSV export (releases, revocations and subject erasures, without customer data; admin API GET /api/_action/swp-gdpr/confirmations/export), so the journal can be saved before the retention period removes it.
- Orders with several customer rows (migrated data) are anonymized completely; anonymized orders that still hold personal data are cleaned by the next run, at most one batch size per batch; an account deletion waits until every order of the customer is clean. The document date of a document counts for the retention period, the creation date only as fallback.
- New provider ShopStudio Blog (comments of deleted accounts get placeholders); Coolbax external orders are anonymized or deleted with their Shopware order, external orders without Shopware order follow their own period. Tables that only cascade and hold no personal data are shown as information instead of a warning.
- The dry run counts exactly what a run processes, for every rule; the guest rule selects ready guests with one indexed query per batch.
- Daily cleanup per sales channel with a retention period of 1 to 180 days (default 180) for live runs, dry runs and the journal of releases and confirmations; dry runs go after 90 days unless a release refers to them. A release stays effective after its dry run and confirmation have been deleted; order markers are kept. The overview shows size and rows of the plugin tables, the retention period per sales channel and the next cleanup.
- Notice with the statutory retention periods (§ 147 AO, § 257 HGB, start at the end of the calendar year) in the configuration; every period field refers to it.
- The deletion period must be greater than the anonymization period: the administration reports a conflicting value before saving, API and CLI reject it with HTTP 400 without saving anything; inherited values of every sales channel are taken into account.