Before you start
Document the actual frontend adapter, supported capability versions, environment registration and protected refresh configuration. Keep secrets outside public code.
A recognisable example
DYMR publishes an addition beside an overshirt. The source confirms the rule, but the agency also verifies that an eligible customer can see and use it.
Step by step
- Check the specific capability required by the feature. General support for Daymerce does not imply support for every set, gift, alternative or checkout placement.
- Publish through the approved path and confirm the Edge write and source readback. Let the authenticated frontend refresh run for that exact publication.
- Verify the ordinary visitor page and relevant basket behaviour. Check an ineligible case as well as the successful one.
- Review local fallback, configuration validity and revocation behaviour. Prices, stock and discount eligibility must still be validated by the WooCommerce source at the appropriate purchase step.
What you should see
You have evidence that the intended frontend result is visible. A source receipt alone may still mean that the page is updating; uncertain verification is not a completed publication.
If it does not work
Source correct but page stale? Trace the refresh, adapter contract, durable cache and visitor verification. Do not bypass the check by accepting editor HTML as proof or trusting an old cached price.
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.