A product can be perfectly described in your store and still arrive at a shopping channel with the wrong price, missing attributes or yesterday’s inventory. A product feed is the handoff between your catalog and a destination’s rules. The job is not simply to export rows. Teams map fields, normalize values, validate records, schedule updates and trace errors without corrupting the source catalog. This guide separates the file or connection from the destination’s processing and approval decisions. Follow the terms in order: build the data contract, keep updates moving, then diagnose what failed.
🧭 Jump to a term
Shape the data: Product feed · Channel mapping · Feed rule · Attribute mapping · Destination schema · Field normalization
Keep updates moving: Full feed · Delta feed · Feed refresh · Feed schedule · Product exclusion
Validate and diagnose: Feed validation · Price mismatch · Availability mismatch · Feed error · Feed diagnostics
⭐ Know these first
Start with Product feed, Attribute mapping, Feed validation, Delta feed, Availability mismatch. Then follow the grouped learning order below.
📎 How to read this page
What it means gives the precise meaning. Operator translation gives the version you might hear in a real ecommerce meeting. In real life shows an illustrative example. Watch out and the confusion boxes show where a familiar term can mislead.
📈 Read the relationships first
These combinations are diagnostic hypotheses, not proof of causality. Compare the same period and scope, then investigate the mechanism.
🔵 Full feed vs delta feed
Usually means: A full feed provides a current snapshot while a delta carries only changes. Check next: the destination deletion behavior, last successful baseline and recovery path before relying on incremental updates.
🟡 Price mismatch + availability mismatch
Usually means: The destination and offer page may disagree about the same item. Check next: variant, market, currency, location and update time before changing the source or campaign.
🟢 Validation passes + item errors remain
Usually means: The file may meet basic format rules while individual products still fail later checks. Check next: processing status, policy issues and the affected item list separately.
Shape the data
01 · 🟢 Core
Product feed
🧠 What it means
A product feed is a structured export of catalog records for one or more sales or discovery destinations. It carries identifiers and fields such as title, image, price and availability; its format and required fields depend on the destination.
💬 OPERATOR TRANSLATION
“The catalog’s passport. Every channel asks for different stamps.”
🛍️ In real life
A candle seller exports SKU CND-8 with its title, image, $24 price and current stock to a shopping destination.
⚠️ Watch out
A feed is a data delivery, not proof that a destination accepted or displayed every item.
🔗 Related: Channel mapping · Feed rule · Attribute mapping · ↑ all terms
02 · 🔵 Operations
Channel mapping
🧠 What it means
Channel mapping connects source catalog fields and values to a destination’s required fields and vocabulary. It can include renaming, translating or transforming data for each channel.
💬 OPERATOR TRANSLATION
“One product, several dialects; the spreadsheet is the translator.”
🛍️ In real life
The store maps its internal stock field available_qty to a destination’s availability field and converts 3 units to in stock.
🔗 Related: Product feed · Feed rule · Attribute mapping · ↑ all terms
03 · 🔵 Operations
Feed rule
🧠 What it means
A feed rule applies a defined condition or transformation to product data before export, such as adding a prefix or excluding items without images. Rules may be account or destination specific.
💬 OPERATOR TRANSLATION
“A tiny policy that keeps one weird SKU from becoming a company-wide incident.”
🛍️ In real life
If shipping weight is missing, a rule routes that SKU to an error queue instead of inventing a value.
⚠️ Watch out
A rule can mask a source-data problem or affect thousands of SKUs; keep its conditions visible and test a sample.
🔗 Related: Product feed · Channel mapping · Attribute mapping · ↑ all terms
04 · 🟢 Core
Attribute mapping
🧠 What it means
Attribute mapping assigns each source value to the corresponding destination attribute and formats it to that destination’s specification. It is more specific than merely sending a product record.
💬 OPERATOR TRANSLATION
“Blue-ish is not a data strategy when the channel expects blue.”
🛍️ In real life
An apparel source field shade=navy is mapped to the destination’s accepted color attribute blue only where that conversion is valid.
💡 Why it matters
Correct attributes help the destination interpret and match the item; unsupported guesses can make the listing inaccurate.
🔗 Related: Product feed · Channel mapping · Feed rule · ↑ all terms
05 · 🔵 Operations
Destination schema
🧠 What it means
A destination schema is the receiving system’s expected structure: fields, data types, allowed values and relationships. It describes what the destination can parse, not the merchant’s entire product model.
💬 OPERATOR TRANSLATION
“The receiving channel’s form, with fields it insists are required.”
🛍️ In real life
One marketplace schema requires a condition value while the source catalog stores condition as a free-text note.
💡 Why it matters
Keep the destination contract separate from the source model so changes do not corrupt master data.
🔗 Related: Product feed · Channel mapping · Feed rule · ↑ all terms
06 · 🔵 Operations
Field normalization
🧠 What it means
Field normalization converts equivalent source values into a consistent format before mapping or comparison. It can standardize whitespace, units, casing or accepted synonyms without changing the underlying product truth.
💬 OPERATOR TRANSLATION
“Make US, United States and U.S. stop pretending to be three countries.”
🛍️ In real life
The connector standardizes Large and large before matching a size value, while keeping the actual size meaning intact.
⚠️ Watch out
Normalization is not permission to erase meaningful distinctions such as pack size or material.
🔗 Related: Product feed · Channel mapping · Feed rule · ↑ all terms
Keep updates moving
07 · 🔵 Operations
Full feed
🧠 What it means
A full feed is a complete snapshot of the records intended for a destination at that moment. A destination may interpret omitted items differently, so confirm its update and deletion behavior.
💬 OPERATOR TRANSLATION
“The whole inventory report, because apparently nothing changed was too optimistic.”
🛍️ In real life
At midnight a merchant sends all 8,000 active catalog records, not just the 43 updated since yesterday.
💡 Why it matters
Full exports are easier to reason about, but may take longer or replace destination state depending on its rules.
🔗 Related: Delta feed · Feed refresh · Feed schedule · ↑ all terms
08 · 🟢 Core
Delta feed
🧠 What it means
A delta feed sends only records or fields that changed since a prior successful state. It depends on reliable change tracking and destination support for incremental updates.
💬 OPERATOR TRANSLATION
“The update memo instead of reshipping the entire filing cabinet.”
🛍️ In real life
A connector sends the 43 products whose price or stock changed, after recording a successful previous sync.
⚠️ Watch out
A missed change marker can leave stale data behind; the delta’s baseline and recovery path matter.
🔗 Related: Full feed · Feed refresh · Feed schedule · ↑ all terms
09 · 🔵 Operations
Feed refresh
🧠 What it means
A feed refresh is the process or cadence by which a source is re-read and its data is regenerated or resubmitted. A refresh can be scheduled, triggered or manual; its timing is not the same as destination processing time.
💬 OPERATOR TRANSLATION
“We uploaded it and the channel has it are different calendar events.”
🛍️ In real life
The store refreshes stock every 30 minutes, while the destination may still need time to process the update.
💡 Why it matters
Faster refreshes reduce stale windows only if the source and destination can keep up.
🔗 Related: Full feed · Delta feed · Feed schedule · ↑ all terms
10 · 🔵 Operations
Feed schedule
🧠 What it means
A feed schedule defines when a file or data source is fetched, generated or submitted. It may be independent from destination processing and from the store’s inventory update cadence.
💬 OPERATOR TRANSLATION
“An alarm clock for catalog data; not a teleportation device.”
🛍️ In real life
A nightly export starts at 02:00, but the destination processes the file later and reports results separately.
⚠️ Watch out
Confirm timezone, daylight-saving behavior, fetch windows and failure alerts.
🔗 Related: Full feed · Delta feed · Feed refresh · ↑ all terms
11 · 🔵 Operations
Product exclusion
🧠 What it means
A product exclusion prevents selected items or destinations from receiving a product record. The method may be a rule, destination setting or explicit exclusion field, depending on the platform.
💬 OPERATOR TRANSLATION
“A controlled “not this channel” sign, not a product deletion.”
🛍️ In real life
A restricted-size product remains in the store catalog but is excluded from a destination where it cannot be sold.
⚠️ Watch out
Excluding from one destination should not accidentally remove the item from the source catalog or other channels.
🔗 Related: Full feed · Delta feed · Feed refresh · ↑ all terms
Validate and diagnose
12 · 🟢 Core
Feed validation
🧠 What it means
Feed validation checks whether records meet a destination’s syntax, required-field and value rules before or during submission. Passing validation does not guarantee approval, ranking or display.
💬 OPERATOR TRANSLATION
“The bouncer checks your paperwork. The club still decides if you get in.”
🛍️ In real life
A preflight catches a missing product image and invalid currency code before 2,000 records are uploaded.
⚠️ Watch out
Technical acceptance and policy approval are separate checks.
🔗 Related: Price mismatch · Availability mismatch · Feed error · ↑ all terms
13 · 🔵 Operations
Price mismatch
🧠 What it means
A price mismatch occurs when a destination’s observed price differs from the value supplied by the merchant or expected from the landing page. Diagnose currency, tax, sale timing, variants and update lag before changing bids.
💬 OPERATOR TRANSLATION
“Your feed and your product page have started quoting different prices.”
🛍️ In real life
A feed sends €39.00 while the page defaults to a selected 2-pack at €54.00; the destination flags the difference.
⚠️ Watch out
Compare the same variant, market, currency and sale window before calling it a feed bug.
🔗 Related: Feed validation · Availability mismatch · Feed error · ↑ all terms
14 · 🟢 Core
Availability mismatch
🧠 What it means
An availability mismatch is a difference between reported stock status and the destination or landing page’s availability for the same offer. Inventory timing, location, variant selection and caches can all contribute.
💬 OPERATOR TRANSLATION
“The feed says in stock; the warehouse has entered its witness-protection era.”
🛍️ In real life
A channel still says available after the last unit sold because the inventory update has not completed.
⚠️ Watch out
Distinguish product-level stock from store-level or variant-level availability.
🔗 Related: Feed validation · Price mismatch · Feed error · ↑ all terms
15 · 🔵 Operations
Feed error
🧠 What it means
A feed error is a reported issue that prevents a record or data source from being read, matched or processed as intended. The exact cause and severity come from the receiving platform’s diagnostics.
💬 OPERATOR TRANSLATION
“The channel has returned your spreadsheet with red pen marks.”
🛍️ In real life
A rejected item report identifies an invalid identifier on 12 of 600 products; the rest may remain eligible.
💡 Why it matters
Separate account-level failures from item-level errors before pausing a whole catalog.
🔗 Related: Feed validation · Price mismatch · Availability mismatch · ↑ all terms
16 · 🔵 Operations
Feed diagnostics
🧠 What it means
Feed diagnostics are reports and tools that identify data-source, item, mapping or processing problems. Read the scope, timestamp and affected records before deciding what to repair.
💬 OPERATOR TRANSLATION
“The dashboard’s something is wrong message, translated into an actual to-do list.”
🛍️ In real life
A report shows that 4% of items have missing images and separates those from a failed file fetch.
💡 Why it matters
Prioritize by reach and severity; one account error and one bad SKU need different owners.
🔗 Related: Feed validation · Price mismatch · Availability mismatch · ↑ all terms
🔀 PIM vs product feed vs Merchant Center
A PIM governs product information; a feed translates or delivers selected data for a destination; Merchant Center is Google’s named product-data environment. One layer does not replace the others.
🔀 Feed validation vs product approval
Validation checks whether data follows stated format and field rules. A destination can still review eligibility, policy and display after a record is accepted.
🔀 SKU vs GTIN vs marketplace IDs
A seller SKU is an internal identifier. GTINs identify trade items under standards such as UPC or EAN. Marketplace identifiers such as ASIN or FNSKU serve platform-specific purposes. Do not substitute them.
🤔 Still confused?
Follow this thread: Product feed → Full feed → Feed validation. That sequence moves from the basic object or relationship to the decisions and checks it supports.
Sources and scope
Primary documentation checked on 27 September 2026. Platform features and eligibility can change; examples and cartoon situations are illustrative.
