Run a browser-local preflight
Drop source/config files here
or choose multiple text-based files
or
Privacy: file contents, filenames, repository identifiers, merchant IDs, Google Cloud project IDs and source code never leave your browser. Only privacy-safe aggregate activation events are sent when you run the preflight, download a report, or click the commercial-interest link.
What the scanner checks
- Content API v2.1 endpoints, client-library names and common Products / Accounts / Datafeeds / Reports surfaces.
customBatchusage, which has no direct Merchant API equivalent.- Legacy product identifier handling that should move toward Merchant API resource
name/parentpatterns. - Legacy Price objects using
value+currencyinstead ofamountMicros+currencyCode. - Merchant API
v1betareferences that should already be migrated tov1or an appropriate supportedv1alphasurface. - Merchant API usage without an obvious
developerRegistration:registerGcp/registerGcpstep in the scanned material.
Static analysis can produce false positives and cannot prove a migration is complete. Always test against Google's current Merchant API documentation and a development environment before production rollout.
Need a detailed migration pack or recurring compatibility monitoring?
This browser-local software is currently free. No paid offering is attached to this page.
View PAL Pro softwarePAL Pro is a separate self-serve software subscription. The migration preflight remains free.