PrestaShop Catalogue Management

Bidirectional Google Sheets Sync — Edit prices, stock & titles in a Sheet, auto-sync to PrestaShop (PrestaShop 8 & 9)

Manage your catalog from a Google Sheet. The module handles the rest, both ways.

Edit your product prices, stock levels and titles in a shared Google Sheet, and let the module push them automatically into PrestaShop. A change made in the back office? It flows back into the Sheet on its own. Two-way synchronization, conflict detection, secure cron — without leaving the spreadsheet your whole team already knows.

At a glance
  • Two-way synchronization Google Sheets ⇄ PrestaShop: price, stock quantity, title and active/inactive status
  • Checksum-based change detection: only what actually moved is synced, in the right direction
  • Configurable conflict resolution when a product is edited on both sides (the Sheet wins / the shop wins)
  • Google service account connection (JSON key) — no OAuth to configure, no Composer dependency
  • Token-secured cron for automatic synchronization. Compatible with PrestaShop 8 & 9, multilingual
PrestaShop 8 & 9 Two-way Google Sheets API Secure cron No Composer
  • 30-day refund
  • 12 months updates
  • 24h support
www.datafirefly.com/en/
Two-way Google Sheets Sync — Edit prices, stock & titles in a Sheet, auto-sync to PrestaShop (PrestaShop 8 & 9)
v1.0.0 · updated 2026-07-05
What it does

The short version.

01

One spreadsheet, your catalog

Each product's price, stock quantity, title and active/inactive status are exposed in a six-column Google Sheet. Your whole team edits the catalog in the tool they already master, together, from anywhere — with no access to the PrestaShop back office.

02

Both directions, automatically

A change in the Sheet flows down to PrestaShop; a change in the back office flows back up to the Sheet. The synchronization is truly two-way: the spreadsheet and the shop stay a mirror of each other, with no copy-paste and no manual re-import.

03

Syncs only what changed

The module stores the fingerprint of each product's last synchronized state. On every run, it compares and writes only the rows that actually changed, in the right direction. The result: fast syncs, even on a large catalog, and zero pointless overwrites.

04

Conflicts handled, not suffered

When the same product has been edited both in the Sheet and in the back office since the last sync, the module applies the priority you chose — the Google Sheet wins, or PrestaShop wins. No surprises, no data lost by accident.

05

Near-zero setup friction

You paste the JSON key of a Google service account, you share your Sheet with the service account e-mail, and you're off. No OAuth flow, no consent to approve, no Composer library: the module signs its own calls to the Google Sheets API.

06

Automatic and secure

A token-protected cron endpoint triggers the synchronization every few minutes. In one click you can also run a manual sync from the configuration, or reset the sync state to start over with the shop as the reference.

The long version

Everything you'd want to know before you install.

A detailed look at how Bidirectional Google Sheets Sync — Edit prices, stock & titles in a Sheet, auto-sync to PrestaShop (PrestaShop 8 & 9) works, why we built it the way we did, and the thinking behind the features above.

§ 01

Your PrestaShop catalog, driven from a Google Sheet

Editing a price, adjusting stock or fixing a product title shouldn't force an entire team through the back office. This module exposes your products — title, price excluding tax, stock quantity and active/inactive status — in a shared six-column Google Sheet. Everyone edits in the spreadsheet they already know, many hands at once, and the module takes care of pushing the changes into PrestaShop. The Sheet becomes a real bulk-editing interface, accessible without an administrator account.

§ 02

Truly two-way synchronization

Most connectors only go one way. This one works both ways: a change entered in the Sheet flows down to the shop, and a change made in the PrestaShop back office flows back up into the Sheet automatically. The spreadsheet and the shop stay a permanent reflection of each other, with no manual re-import and no CSV file to regenerate. You work wherever is most convenient at the moment.

§ 03

Smart: it only touches what moved

On every synchronization, the module compares each product's current state to the fingerprint of its last synchronized state, stored in the database. It figures out exactly what changed, and on which side, then writes only those rows — in the right direction. On a catalog of several thousand references, this avoids rewriting everything on each run and keeps syncs fast. Writes to Google are also batched to respect the API quotas.

§ 04

Conflicts, handled cleanly

What happens if the same product has been edited on both sides since the last sync? Nothing is lost at random: you define a priority rule — the Google Sheet wins, or PrestaShop wins — and the module applies it systematically, logging the decision. You keep control over the source of truth, product by product and run by run.

§ 05

Friction-free setup in minutes

No OAuth flow or Google consent screen to get through. You create a service account in the Google Cloud console, paste its JSON key into the module configuration, and share your sheet with the service account e-mail address as an editor. The module signs its own requests to the Google Sheets API (JWT RS256 in native PHP), with no Composer library to install on your server. A status panel shows the connected account, the cron URL and the last synchronization date.

§ 06

Automatic, secure and predictable

A cron endpoint protected by a regenerable token triggers the synchronization every few minutes, via your server scheduler or an external service. You can also run a manual synchronization in one click from the configuration, or reset the sync state to start over with the shop as the reference. Data entered in the Sheet is validated before writing: an empty or invalid name, a negative price, and the offending row is simply skipped and logged — the synchronization of the other products is never interrupted. No core override, clean uninstall: the module meets the standards of a production shop.