Deterministic Merchant API insert check

Catch a wrong feed ID before it reaches Google.

Before your store sends a product insert, compare the feed ID Google reports for that product with the feed ID the next insert will use. Exact matches pass. Mismatches and missing product evidence stop.

Check the first 10 insertsSee the exact rule →

For Merchant API developers and feed agencies · deterministic, no AI · runs locally with input files kept in-browser

Migration timing

Google lists August 18, 2026 as the standard Content API for Shopping cutoff. An extended-access application exists, so a merchant's applicable date may differ.

Check Google's current guidance ↗

Free local preview · first 10 planned writes

Compare Google’s feed ID with your next insert.

Input files stay local · anonymous event count only

Load the example or supply a timestamped snapshot and planned update file.

One narrow v1 rule

A repeatable check, not an AI opinion.

This version covers only migrations from Content API products.insert to Merchant API productInputs.insert. It reads the exact evidence you provide and returns the same result for the same files.

  1. 01
    Capture Google's product evidence

    Merge every accounts.products.list page and record when it was captured. The check reads each output-only Product.dataSource.

  2. 02
    Load the planned update file

    Supply the primary ProductInput fields the next productInputs.insert calls will use.

  3. 03
    Compare exact product identity and feed ID

    Account, local-product flag, language, feed label, offer ID, and data source must match. A missing product becomes NOT_VERIFIED.

  4. 04
    Optionally verify the feed definition

    A complete accounts.dataSources.list response can also check API input type, primary role, language, and label scope.

One-time versioned offline license

Turn the check into a pipeline gate.

The free preview checks the first 10 planned inserts locally. The paid kit adds the snapshot-verified productInputs.insert request skeletons, clearly marked source-correction suggestions for mismatches, a deterministic correction diff, and local CLI/CI execution with a blocking exit code.

Built for developers and feed agencies

A pre-deploy check a pipeline can run without a reviewer.

Evidence

Caller-supplied, timestamped products.list snapshot

Plan

Exact planned update file for primary productInputs.insert calls

Rule

Strict identity and feed-ID equality; no AI or inference

Optional

dataSources.list checks API type, primary role, and scope

Output

Verified skeletons, review-required corrections, ledger, and guard

CI

Deterministic exit status for feed-ID conflicts or missing snapshot evidence

Exact evidence, narrow claim.

A match means only that the planned feed ID exactly equals the Product.dataSource in your captured snapshot. The tool does not connect to Google, infer a missing feed, make writes, validate supplemental inputs, or claim that a product is live, approved, correct, or safe. A product absent from the snapshot is NOT_VERIFIED and blocks. Processed Product data can lag recent writes, so choose the snapshot time accordingly.