Editorial evidence

Sources and Verification

We check official sources to explain what you need to do and when no action is needed.

What we include

A change must affect your deadline, permissions, available tools, costs, next action, or how to interpret store data.

What we leave out

We leave out launch promotions, unsourced predictions, repeated coverage, developer changes that do not affect merchants, and numbers that answer no merchant question.

How we check an Answer

  1. Read the original changelog, specification, policy, help page, or filing.
  2. Record the check date.
  3. Explain when the Answer applies and when it does not.
  4. Give the official page, Steps, finish condition, and reasons to stop. Explain what the result cannot prove.
  5. Explain when paid help is useful and what is already free.
  6. Keep source links so you can check the claims.

Who publishes

Automation collects evidence and drafts. A person checks the sources, reviews each draft, and publishes English and Traditional Chinese together. Automation cannot publish.

When we review sources

Every Answer shows a Source Check date. Platform Changes need a review within 30 calendar days; Decisions and Steps within 90. Outdated or future-dated checks block publication. Both languages must match in identifiers, dates, Areas, Steps, and sources.

How lists are ordered

The Guide uses original publication dates. Platform Updates use the date the change took effect, so an older change cannot appear new because we wrote about it later.

Registered sources

Other sources can flag a change. We check its primary source. Our sources and review plans are: