Before you start
Identify the authoritative WooCommerce shop and a small set of known records. Keep production and test references separate.
A recognisable example
DYMR changes stock directly in WooCommerce. The agency compares the source variant with the Daymerce working view before diagnosing a missing update.
Step by step
- Check the selected shop and connection state. Note any import, source or freshness warning rather than treating the absence of an error as proof of completeness.
- Compare one known order, product and customer against their source records. Check identifiers and times, not just similar names.
- For a write, inspect the action receipt and readback. A completed request without a matching source result needs investigation before retry.
- Refresh through the supported interface and inspect progress. Keep large work in bounded batches and preserve useful job references for diagnosis.
What you should see
You know which data was confirmed and which is still delayed or unknown. Do not describe synchronisation as an instant full mirror or assume that a partial list proves no other records exist.
If it does not work
Repeated delay? Check source availability, credentials, permissions and background work. After a timeout, inspect the existing action outcome before replaying it; otherwise an apparently failed request can create duplicate work.
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.