Before you start
Have an authorised plugin package, a current backup, WordPress administrator access and a representative test environment. Check the package's requirements and supported versions.
A recognisable example
An agency prepares DYMR's connection on a test shop first. Installing the package is only the beginning; the agency also checks permissions, synchronisation and storefront behaviour.
Step by step
- Record the existing WordPress, WooCommerce, PHP, theme and plugin versions. Back up files and database and confirm how restoration would work.
- Install the approved Edge package through the normal WordPress plugin workflow. Activate it and check reported prerequisites and capabilities before authorising the intended environment.
- Connect the shop through Daymerce and verify a small read path: a known product, order and customer record. Grant writes only to authorised people and supported workflows.
- Test one reversible approved change with readback and storefront verification. Record the environment, package version and actual results before a production rollout.
What you should see
You have evidence of an installed and functioning connection for the tested scope. Plugin activation alone does not establish compatibility with every theme, extension or custom checkout.
If it does not work
Activation or checks fail? Read the specific error, verify requirements and use the agreed restoration procedure if needed. Never patch production by disabling unrelated safeguards or exposing credentials in browser code.
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.