Before you start
The authorised owner should review active tasks, integrations and local modules first. Keep a backup and identify separately issued WooCommerce API keys.
A recognisable example
DYMR stops using the connection. The owner wants normal WooCommerce sales to continue and asks the agency which local features still depend on Edge.
Step by step
- Review active imports and pending publications. Resolve uncertain writes and record the state of any approved local configuration before disconnecting.
- Open the shop's disconnect action in Daymerce. Read the confirmation and verify the intended shop before approving it.
- Check that the connection is absent or revoked. Existing imports stop at a subsequent connection check; already imported data is not automatically deleted.
- Review separate WooCommerce API keys and revoke obsolete ones in WooCommerce. Test the ordinary shop path. Handle data deletion or plugin removal as separately reviewed tasks.
What you should see
Daymerce access through the revoked connection stops. Core WooCommerce data stays in the shop. Local modules depend on their installed code, configuration validity and fallback; not every Daymerce-related feature is guaranteed to continue indefinitely.
If it does not work
Need to remove Edge too? Inventory dependent checkout and local features first and test restoration or replacement. For privacy deletion, follow the appropriate data process instead of treating a successful disconnect as an erasure receipt.
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.