Feednetic FAQ
What teams usually need to know first.
These answers describe the current product concept and workflow represented by the demo.
The current product model includes CSV, TSV, XML and JSON files, alongside ecommerce connectors, SFTP and API-based sources.
Yes. The platform is designed around a primary catalogue plus supplemental sources joined using a mapped key such as SKU or another shared identifier.
Yes. Shared catalogue rules can run before destination-specific logic, so Google, Meta, TikTok or partner feeds can each have their own output requirements.
No. Product identifiers should come from trusted manufacturer, supplier or product-information sources. Missing identifiers can be flagged, joined from another source or left blank where appropriate rather than fabricated.
AI is positioned as a controlled enrichment layer for descriptive attributes and taxonomy assistance, with review where accuracy or brand tone matters. Deterministic transformations remain rule-based.
The product model includes scheduled hosted feeds, SFTP delivery and API-based output patterns in addition to manual export.
Yes. Feed health is designed to compare source, transformed and destination output quality so teams can measure whether changes improved the feed.
No. Google Shopping is one important use case, but the platform model also supports Meta, TikTok, affiliate feeds, SFTP partners and custom downstream outputs.