Required columns and column shifts in product feeds
Technical explanation of structural errors and inspection criteria for CSV/TSV files before submission
Detected Symptoms
When product data sources for Google Merchant Center are created manually or with external tools and submitted, inconsistent header or data-row structures can cause processing errors. Typical symptoms include missing required header columns, missing alternative required header groups, empty required values in rows whose headers exist, mismatches between header and data-row column counts, extra empty columns at row ends, differences in header capitalization or surrounding whitespace, and duplicate header names.
Root Causes
One common cause is the use of spreadsheets or e-commerce cart CSV export features in product data workflows. Editing and saving comma-separated (CSV) files in spreadsheets can unexpectedly shift columns or split rows because of differences in how quotes, line breaks, and text fields containing commas are interpreted.
Google's technical documentation also treats commas as reserved characters within attributes, does not recommend CSV, and recommends tab-delimited TSV files. CSV editing remains common in Japanese cart systems and business workflows; differences in format and editing procedures are a structural source of inconsistencies before submission.
Verification Checklist & Implemented Rules
Feed Seibishi performs deterministic syntax checks locally in the browser using these 10 implemented specification rules.
- MISSING_REQUIRED_HEADER: Checks whether required headers (id, link, price, availability, image_link) exist.
- MISSING_REQUIRED_HEADER_GROUP: Checks whether at least one header exists in each alternative required group (title or structured_title; description or structured_description).
- EMPTY_REQUIRED_VALUE: Checks each row for empty cells corresponding to required headers.
- EMPTY_REQUIRED_VALUE_GROUP: Checks whether a valid data value exists in each required group of columns.
- COLUMN_COUNT_MISMATCH: Checks whether the number of cells in each data row exactly matches the header count.
- TRAILING_EMPTY_COLUMNS: A change-log entry for restoring missing trailing empty cells during safe fixes when a data row has fewer cells than the header. It is not an error-detection rule. The log records the original cell count and header count. Without safe fixes, short rows are reported as COLUMN_COUNT_MISMATCH. After missing trailing empty cells are restored, the mismatch caused by that shortfall disappears from the post-fix diagnosis. This only resolves that row's missing-cell mismatch; rows with too many cells are not restored, and other value errors may remain. The issue table displays the first 100 findings. Check the error and warning counts for the total number detected.
- HEADER_CANONICAL_FORM: A change-log entry recording header normalization when safe fixes are applied; it is not an error-detection rule in the issue table. Ordinary diagnosis trims surrounding whitespace and lowercases header names for inspection, but does not create this log entry. Known aliases are replaced with canonical names only when safe fixes are applied, and those replacements are logged. Download the change log to see individual before/after values. After successful safe fixes, the Changes applied metric and status show the total number of safe fixes, including changes beyond headers.
- DUPLICATE_HEADER: Checks whether a header name occurs more than once.
- VALUE_TOO_LONG: Checks limits such as 50 characters for id, 150 for title, and 5000 for description. Length is counted in Unicode code points. Excess title and description lengths are reported as warnings (Google truncates the excess).
- DUPLICATE_ID_CASE_INSENSITIVE: Warns when IDs in different rows differ only in ASCII letter case (for example, AB1 and ab1). Non-ASCII case differences (for example, Ä1 and ä1) do not trigger this rule. Identical duplicates are reported by DUPLICATE_ID.
Official Google Documentation
For primary data specifications and file-creation requirements, see the following official Google Help documents.