Google Sheets synchronization

Google Sheets import and synchronization use the Import module. The sheet supplies shared Collection data; the App continues to read that Collection through its Page Query.

Prepare the sheet

Use one header row, consistent column types, and a stable ID column when you want updates to match existing records. For Region data, use exact SVG region IDs. Avoid changing ID values after the first sync.

Make the sheet accessible in the manner required by the Import source form. A URL to a private editing page is not proof that the WordPress server can fetch the data.

Connect and map

1. Open the destination local Collection in Database.
2. Open Import and select the Google Sheets/remote source option offered by your installation.
3. Enter the source URL and analyze it.
4. Choose the source ID behavior explicitly.
5. Map columns to destination fields and review skips, conversions, and geocoding.
6. Complete an initial import and verify the resulting records.

Do not reuse a column for both an unrelated business value and the record identity. Use a stable id column plus separate fields for category, status, or value.

Enable scheduled updates

Save the remote mapping and synchronization settings only after the first import is correct. Choose an interval appropriate for the sheet and your site. WordPress scheduling must be functioning for recurring imports; loading a map is not a substitute for a healthy scheduled job.

Check import logs after changing the sheet. Unchanged-source checks can skip work, so a successful check does not necessarily mean records were rewritten.

Avoid conflicting ownership

Decide whether the sheet or WordPress is the authoritative editor for these records. A later synchronization can replace local edits according to the saved import policy. Some synchronized Collections can be read-only in the normal record editor.

Changing a one-off CSV import’s mapping does not automatically redefine a saved Google Sheets mapping. Review the remote source settings themselves when moving or renaming columns.

See CSV Import for ID and field-mapping principles.