How to prepare a product catalog
Start with a small, representative file
A product feed is a structured inventory of items offered for sale. Each row represents one purchasable product or variant, and each column describes a particular attribute. Begin with a representative selection before processing the full catalog. Use the fictional example to explore missing titles, duplicate identifiers and invalid prices without exposing business data. Keep your original source file unchanged so you can compare every correction. This tool accepts CSV, TSV, XLSX and JSON within the displayed limits. Legacy binary XLS must first be converted to XLSX in your spreadsheet application. Macros and spreadsheet formulas are never executed or treated as authoritative product data.
Map columns without losing identifiers
Review the first imported rows before applying the mapping. Automatic recognition covers common Portuguese, English and Spanish headings, but your company may use different names. Select the corresponding canonical field for each source column and ignore columns that are irrelevant to the destination. You can keep unmatched columns as custom attributes in generic exports. Select the worksheet and header row explicitly when the workbook contains introductory notes. Store SKU, GTIN and postal codes as text in the original spreadsheet. Leading zeros already removed by another application cannot be recovered reliably. Saving a reusable mapping profile requires your permission and stores column choices only.
Choose market and number interpretation
Interface language, product language and target country are separate choices. A seller may work in English while preparing Spanish descriptions for Mexico. Select the source number format before mapping prices: a comma may represent a decimal separator in one locale and a grouping separator in another. Review the correction preview before converting textual prices to technical decimal notation. The tool does not convert exchange rates or change monetary amounts. Market currency differences produce a review warning rather than a claim that cross-border selling is impossible. Confirm taxes, shipping charges, supported currencies and account conversion settings directly with the destination platform before publishing.
Understand local errors and external checks
An error identifies a locally detectable problem that excludes a product from the final feed by default. A warning calls for human review while allowing export. A product valid in the local validator has passed only the implemented static rules. It has not been approved by Google or Meta. URL syntax checks do not download images or inspect product pages. Availability, checkout consistency, image resolution, restricted goods, account eligibility and commercial policies remain unverified. The dashboard counts products separately from individual issues. One product can have several errors. Use the status filter and search to focus on a small batch, then edit the indicated fields.
Identify products and variants accurately
Use stable unique identifiers that remain consistent between updates. A GTIN must have a supported length and a valid check digit, but a mathematically valid number does not establish ownership or assignment. Never generate replacement identifiers to silence an error. If the manufacturer assigned a GTIN, include it. When relevant, check the brand and manufacturer part number against the original packaging. Each variant needs its own product ID while related variants share a group ID. Size, color or another differentiating attribute must distinguish members of the group. Choose the apparel context for clothing and shoes to enable the implemented market-dependent attribute checks.
Review deterministic corrections before applying
Safe corrections trim excess whitespace, normalize Unicode, standardize known availability and condition values, and convert prices using the chosen source number format. The preview lists original and proposed values for each modified field. Applying the batch creates an undo point; it does not delete duplicates or rewrite commercial descriptions. A URL without a scheme is not automatically changed because the intended address may be ambiguous. Invalid GTIN check digits are highlighted for manual correction against a trusted source. Review a few products after applying changes, then inspect any remaining issues. Keep a separate source backup if you need a lasting history beyond this browser session.
Export the right file for the destination
Google exports use technical English attribute names with TSV or RSS XML output. The basic Meta adapter exports CSV or TSV and translates availability values to its catalog notation. Confirm the current Meta account specification: its official reference required authentication or returned a rate limit during the documented review. Generic CSV retains canonical fields; JSON includes a schema version and preserves custom attributes. Spreadsheet audit files have separate product, warning and error worksheets plus export metadata. Formula-like CSV values receive a protective apostrophe, which is an intentional data transformation. Identifiers remain strings in XLSX while usable prices and quantities are numeric cells. Preview the feed before downloading.
Keep an audit and upload manually
Download the PDF summary for a dated overview of product counts, destination, rule version and the most common problems. The full issue list is available in the workbook, and the print action includes the audit details. The empty CSV template helps prepare future batches. Files are generated locally and are not submitted to marketplaces. Upload the selected feed manually in Merchant Center or Commerce Manager, inspect the platform diagnostics and resolve account-specific requirements there. Clear the session when you finish on a shared computer; this also removes the optional mapping profile. Reloading does not restore product data. A successful download confirms file generation, not platform acceptance.
| id | title | price | currency |
|---|---|---|---|
| 00001 | Sample mug | 29.90 | USD |
Google Merchant Center · Google structured data · Google Search Central · Meta Commerce
Frequently asked questions
Are my products uploaded to a server?
Local processing; files are not uploaded. Products are not persisted. Only column profiles can be saved with consent. Clear also removes this profile.
Which formats can I import and export?
CSV, TSV, XLSX or JSON · up to 5 MB, 2,000 products and 60 columns. Binary XLS is unsupported: save as XLSX. Formulas are never executed.
Has a locally valid product been approved by the marketplace?
Not verified: URL accessibility, image quality, policies, account, taxes, shipping and approval. This static validator covers a subset of rules.
Can I fix a GTIN by generating another code?
Check whether an assigned GTIN exists; otherwise supply brand and MPN where applicable. Never invent codes.
Does the country change interface language or convert prices?
Interface language, product language and target country are separate choices. A seller may work in English while preparing Spanish descriptions for Mexico. Select the source number format before mapping prices: a comma may represent a decimal separator in one locale and a grouping separator in another. Review the correction preview before converting textual prices to technical decimal notation. The tool does not convert exchange rates or change monetary amounts. Market currency differences produce a review warning rather than a claim that cross-border selling is impossible. Confirm taxes, shipping charges, supported currencies and account conversion settings directly with the destination platform before publishing.
Inventory Replenishment & Purchase Planner