Google Sheets / Practical data checks / Open-source experiment

Compare two Google Sheets tabs before you update hundreds of rows.

A missing SKU, a duplicate key or a blank price can be easy to miss when an export looks correct. Before applying a bulk change, compare the original and proposed versions inside the spreadsheet, with a list of differences worth investigating.

Current status: original source-tested Google Sheets editor prototype; not a published, installed or approved Marketplace app. No paid customer results.

A worked example with fictional stock records

Imagine a small shop with two Google Sheets tabs, Original and Proposed. Both use an exact SKU header to identify rows. This is a fictional comparison, not data from a real shop.

TabSKUPriceTitle
OriginalA10Tea
OriginalB20Book
ProposedA(blank)Tea
ProposedC30Cup

A conservative comparison returns three observations, each with a different action:

  1. Possible clear: row A's displayed Price changed from 10 to blank. Check whether the future import would erase or ignore this blank.
  2. Missing from proposal: row B is absent. A missing row is not evidence that the destination will delete it.
  3. New proposed row: C is not in the original. Check the destination's append and conflict rules before assuming it will create an item.

What must a safe comparison distinguish?

ObservationWhy it mattersNext step
Duplicate keyMore than one row could matchReview all repeated row numbers before comparing values; the checker omits raw keys
Missing keyA row cannot be matched reliablyCheck source IDs, rather than guessing
Blank proposed valueA field could be clearedVerify the importer's actual blank behavior
Changed displayed valueTwo field values disagreeInspect units, rounding, and intended changes
Missing/new columnTwo exports use different schemasReview mapping separately; don't infer deletion
Unmatched rowA key appears in only one tabCheck insert, update and deletion policy

Try a comparison right here — no login

Paste two tiny tab-separated tables from a spreadsheet, or choose the fictional example. This preview executes entirely in your browser. It does not upload cell contents, store a report, edit a spreadsheet, or invoke the Google Sheets add-on.

Use the fictional example to see the expected three risk categories.

Limits: 500 data rows and 32 columns per tab. Only unquoted tab-separated cells are supported in this web preview; embedded tabs/newlines in quoted fields are rejected. It compares displayed text, not formulas or any importer's behavior. Avoid sensitive records when experimenting.

Try the Google Sheets editor prototype

Moruneva's Sheet Change Preview v0.1 runs as a sidebar inside an Apps Script-enabled spreadsheet. It reads two tab selections and compares displayed values. It reports classifications, sheet row numbers and field names. It does not display or return source identifiers or the original values, modify cells, send client files to Moruneva, or call external APIs.

  1. Create a new Google spreadsheet with entirely fictional data. Use tabs named Original and Proposed with headers SKU, Price, and Title.
  2. From the spreadsheet choose Extensions → Apps Script. Copy the exact Core.gs, Code.gs, and Sidebar.html project files from the public source folder; use the included manifest if appropriate.
  3. Save and reopen the spreadsheet. From Moruneva · Change Preview choose Compare two tabs, then select both tabs and enter the exact key header SKU.
  4. Confirm the three expected differences in the example. You have not changed anything in either tab or simulated an external import.

Open the complete source, setup instructions and automated tests →

Evidence boundary: The exact analysis core passed nine isolated JavaScript checks on November 10, 2026, including duplicate keys, row reordering, blank risks, input limits and omitting original customer values. The Google Sheets editor sidebar itself has not been tested in a real authorized Google Workspace session. These results do not certify production data imports or predict Shopify, CRM or ERP side effects.

When free Google Sheets formulas are enough

Start with the strongest free alternative. Use COUNTIF to flag duplicate keys, XLOOKUP or exact-match VLOOKUP to align rows by key, and conditional formatting or filters to inspect differences. For example, if Proposed column A holds an SKU and column B its proposed price, while Original columns A:B hold the earlier values:

=IFERROR(IF(B2=XLOOKUP(A2,Original!A:A,Original!B:B),"SAME","REVIEW"),"UNMATCHED")

This is a teaching formula, not an import guarantee. It does not detect duplicate keys by itself or distinguish missing columns. Blank handling, locale, formulas and numeric formatting can mislead comparisons. If these built-in steps are enough and faster, a paid add-on offers no proven benefit.

Compare strong free alternatives first. SheetDiff advertises a free Google Sheets add-on for five comparisons per day. Feemag offers free local file comparisons without an account. We have not independently tested their runtime results. If your current formulas or these free tools solve the job, there is no demonstrated reason to pay for a similar Moruneva product. Our experiment remains free and focuses on row-level risks with no source values in findings.

Why try an editor add-on?

A genuinely useful add-on should eliminate switching between apps, stay inside the user's editing context, require minimal permission, and make the next safe review obvious. A website tool repackaged as a plugin without a native advantage has no meaningful business case. This experiment is intended to test the native interaction, not claim that a Marketplace listing exists.

The prototype is intentionally limited to 500 data rows and 32 columns per tab, comparisons of displayed values, and read-only reports. No formula semantics, hidden rows, import policy simulation, external integrations, certified privacy testing or customer acceptance are included. Google Workspace Marketplace publication would require additional developer/account authorization, platform review, and independent editor tests.

If you are preparing a Shopify product CSV rather than just comparing two tables, use the Shopify-specific import risk preflight and official-source checklist. A generic sheet diff does not model variant identities or importer overwrite settings.

Six checks before any bulk update

  1. Keep a dated and authorized original export.
  2. Confirm the key is unique and stable on both tabs.
  3. Separate new, missing, blank and changed values.
  4. Examine formulas and display formatting before trusting apparent equality.
  5. Read the destination platform's official behavior for missing columns and empty fields.
  6. Run a small, reversible destination-side test before importing the full batch.

References and next steps

Have a recurring change-comparison problem? Tell Moruneva what you currently compare and what the free method misses. Do not email credentials or private customer spreadsheets.