Before you start
Have approved business details, contact choices and the WordPress pages you intend customers to read. Have policy wording reviewed for your situation.
A recognisable example
DYMR changes its return instructions. The owner updates the published source and checks the help answer instead of leaving a second contradictory version.
Step by step
- Open Manage, then Shop information. Review the business identity, public contact information and relevant service facts.
- Link each document role to the intended published WordPress page. Check that the page really contains the information its role suggests.
- Open Help & FAQ and review the answers against those confirmed facts. Leave an explicit fallback for a question whose answer has not been established.
- After changing a source document, review its approval again and check the normal customer-facing help and links.
What you should see
Customers receive help based on the information you approved. Editing a linked page can invalidate an approval; an old check is not proof that the changed text is still correct.
If it does not work
A help answer or document is missing? Check publication, the assigned page and its current approval. Do not fill a legal or delivery fact with an AI guess. A stored contact request is also not proof that an email reached your team.
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.