COMPATIBILITY
One source.
Know the destination.
Format conversion is one step. Destination onboarding, platform ingestion and live commerce capabilities each have their own requirements.
| Format | What Feedaptor prepares | What still happens separately |
|---|---|---|
| Google Merchant Center feed | Import XML, CSV, TSV or JSON from upload or public HTTPS. Map fields and preserve variant identities. | Check source permissions and mapping. Scheduling needs a public HTTPS URL. |
| ACP discovery | Reviewed discovery feed artifact for the supported schema profile. | OpenAI merchant onboarding, destination account, supported full-snapshot delivery and acceptance. |
| UCP catalog | Catalog snapshot plus deployment preparation. | A business profile, negotiated version/capabilities and hosted Search/Lookup endpoints for live support. Checkout is a separate capability. |
| Google supplemental | Approved supplemental values matched by product identity. | Configure the supplemental source in Merchant Center and verify processing there. |
A successful export is not proof of platform acceptance.
Feedaptor keeps prepared, transferred and accepted states distinct. A manually uploaded receipt is reported evidence, not independent verification.
OFFICIAL SOURCES
Read the rules
at their source.
OpenAI product feed specification OpenAI feed delivery overview UCP catalog capabilities UCP protocol overview
Destination specifications evolve. Check the active profile and current platform requirements before a production release.