Before you start
Confirm who is making the request and which organisation, shop and records it concerns. Only authorised people should handle personal data.
A recognisable example
Noor asks DYMR to correct her contact details. The team verifies the request and checks the source record rather than changing a similarly named customer's information.
Step by step
- Record the request through the appropriate customer or shop workflow. Use My account for your own account preferences and data, not as a substitute for a shop customer's request.
- Check which system owns the affected information. Compare the WooCommerce record with relevant Daymerce working data and connected communication preferences.
- Use the supported authorised correction, export or deletion process for that scope. Review retention obligations before deleting business records.
- Check the outcome in the affected systems and tell the requester what actually happened. Store the minimum useful handling record.
What you should see
You have dealt with a defined request. Disconnecting a shop, removing a team member and deleting stored data are different actions; none should be presented as automatically completing the others.
If it does not work
Cannot establish identity, scope or deletion outcome? Pause the change and involve the responsible owner or privacy adviser. Do not send a full customer export through an unsecured channel or promise erasure from systems you did not verify.
Menu names and available actions depend on your app language, permissions and connected shop. Screens show the real Daymerce interface with fictional DYMR data; original screen labels are preserved.