The product feed is one output. Product data is the broader set of information and logic used to create that output.
Source product data
This is the raw information coming from ecommerce platforms, PIMs, suppliers, ERP systems, warehouses or files.
Mapped product data
Different source fields are normalised into a consistent internal schema. This is where product_name might become title, stock_status might map to availability and manufacturer_code might map to MPN.
Transformed product data
Rules, joins and enrichment change or supplement the mapped values. The transformation should remain traceable.
Destination feed
The final feed contains the fields and values required by a specific channel, partner or system. Two destination feeds can come from the same transformed catalogue but still differ in field names, taxonomy or delivery format.
Why the distinction matters
When teams treat the feed as a single flat file, every new destination becomes another manual project. A layered data model allows shared fixes to happen once and channel-specific logic to stay isolated.
Feednetic is designed to turn repeatable findings from this kind of audit into mappings, rules, enrichment workflows and validation checks rather than one-off spreadsheet fixes.