Before you start
You need the appropriate publication permissions, a connected shop and the capabilities required by the change.
A recognisable example
DYMR saves a new product description. It is ready in Daymerce, but the owner still checks publication and the ordinary product page.
Step by step
- Review the change and its validation messages. Check the target shop, affected products or pages and any schedule.
- Prepare the publication. Review the proposed action before confirming; a prepared item is not yet an executed change.
- Inspect the publication result and source confirmation. If your shop has a separate frontend, allow its refresh and visitor-page verification to finish too.
- Open the normal customer-facing page, select the relevant variant or basket and confirm the expected result. Keep the publication reference if anything needs investigation.
What you should see
A successful source write and a visible storefront result are different pieces of evidence. Use the reported state; do not call a still-refreshing or uncertain change complete.
If it does not work
Unknown outcome or old page? Check the existing publication and source record before retrying. Ask your agency to inspect the frontend refresh and cache. A browser timeout does not prove that the source write failed.
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.