Product feed tools with Google Sheets

Three jobs a Google Sheet does in a product feed

Source. The sheet is the catalog: one row per product, one column per attribute. This is how Merchant Center's own Sheets data source works and how most feed tools import a sheet. It suits small, static catalogs and anything with no store behind it (a wholesaler's line sheet, a service catalog). It does not suit a store whose stock and prices change, because someone has to keep the sheet current.

Merge file. The store is the source and the sheet adds columns the export lacks: GTINs from a supplier, seasonal labels, fitment, a hand-written product highlight. The tool joins the sheet onto the catalog by SKU or id. GoDataFeed calls these merge files; Textfinity calls them merged sources.

Lookup table. The sheet is not joined at all; a rule reads it. A two-column sheet of store category to Google product category, a list of brands allowed on Meta, a map of color names to normalized values. The marketing team edits the sheet and the next rebuild picks it up. Textfinity has three rule types for this: replace from google sheet and extract from google sheet in mapping, and is in google sheet list in filters and conditional mapping rules.

Which product feed tools read Google Sheets, and how

Every tool below publishes Sheets support; the differences are in sharing requirements and roles. Merchant Center starts you from Google's template and syncs every 24 hours by default. DataFeedWatch lists Sheets as a custom source on all four plans. Channable imports a sheet that is shared publicly and asks for it to be updated at the same URL at least daily. GoDataFeed reads a sheet published to the web as a CSV (the URL ends in ?output=csv) as an HTTP primary source or a merge file joined on SKU. Textfinity adds a sheet as a shop source, joins one as a merged source, or reads one from a rule.

Sheet as source: when it is the right call

If there is no store system of record, the sheet is the catalog and that is fine. A wholesaler with 300 lines and monthly price changes, a maker with 40 products, a brand launching before the store exists. Merchant Center's template gives you the column names; a feed tool on top gives you rules (title building, category mapping, filters) and output for channels beyond Google.

Two cautions. First, every tool that reads a sheet by URL needs it reachable: Channable and GoDataFeed require a publicly shared or published sheet, which means anyone with the link can read it; keep cost and supplier columns out of it. Second, a sheet does not know your stock. If you sell from inventory, the store should be the source and the sheet a merge file, or you will advertise sold-out items until someone edits a cell.

Sheet as lookup: the role most tools skip

The highest-value use of a sheet is the one the comparison table shows least support for. Category mapping is the standard case: a store has 80 product types and Google wants its taxonomy ids. Put the pairs in a sheet, point a replace from google sheet rule at it, and the feed's google_product_category fills from the sheet on every rebuild (the rule replaces substrings, so keep column A values specific, or pair it with an is in google sheet list condition for exact matches); add a product type and the merchandiser adds a row, no feed edit needed. The same mechanism handles brand allow-lists for a channel (filter: brand is in google sheet list), color normalization (Navy, navy, NAVY to Navy), size charts, and per-market shipping labels.

Lookups can also stay private. Textfinity reads sheets through your organization's Google service account, so you share the sheet with that account instead of publishing it to the web, which matters when the sheet encodes margins or supplier codes. In Textfinity, we set up the lookups as mapping rules and filters, including is in google sheet list, and share the service account address with you so the sheet never has to be published.