Stay organized with collections
Save and categorize content based on your preferences.
The v1 inventory is a hierarchical structure of feed entities in JSON-LD format. This schema
allowed early access-program partners to use the schema to integrate with Ordering End-to-End. The
v1 inventory schema is now deprecated.
The latest version of the data feed specification, v2 inventory, has a flat structure and uses a
relational schema model. This allows partners to extract and transform entities from their
relational database in a more straightforward manner to create the data feeds. The v2 inventory is
in NDJSON, which is a newline delimited JSON format.
Why you should migrate from v1 to v2
Although we continue to provide maintenance support to partners with Ordering End-to-End v1
inventory schema integrations, all new partner integrations must use the v2 inventory.
New features in the v2 inventory might not be available in the v1 inventory. For an example, see
Deal.
Migration steps
The use of v2 inventory requires a separate Ordering End-to-End project and a new integration. The
following process explains how to migrate a v1 inventory to a v2 inventory.
To prevent serving both your v1 and v2 inventory schema to end users, undeploy the
production release from your v1 project. Your v1 project inventory stops serving in production
within minutes after this step.
Create a production release for your v2 project and notify your Google consultant.
Rollback steps
If you want to rollback to v1 after deployment of your v2 project in production, you can undeploy
the production release in your v2 project and then redeploy your v1 project’s production release.
Impact on partner data and provider ranking
The following are potential impacts to partner data and provider ranking.
Transaction logs and analytics data from your v1 project don't transfer to your v2 project.
Performance metrics, such as conversion rates and API metrics from your v1 project, aren't
ported to the v2 project. This resets your provider ranking in Ordering End-to-End.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-31 UTC."],[[["The v1 inventory schema for Ordering End-to-End is deprecated and being replaced by the v2 inventory schema."],["The v2 inventory uses a relational schema model in NDJSON format, offering easier integration for partners."],["All new Ordering End-to-End integrations must utilize the v2 inventory schema, while existing v1 integrations will receive maintenance support."],["Migrating to v2 involves creating a new project, implementing the relational schema, and potentially reusing existing fulfillment endpoints."],["Partners migrating to v2 should be aware that transaction logs, analytics data, and performance metrics will not transfer from v1, potentially affecting provider ranking."]]],["The v1 inventory schema, a hierarchical JSON-LD format, is deprecated in favor of the v2 inventory, which uses a flat, relational NDJSON structure. Migration to v2 requires a new project and integration, using the relational inventory schema. Steps involve creating a v2 project, implementing data feeds, and undeploying the v1 production release before deploying v2. Rollback to v1 is possible by reversing the deployment process. Note that transaction logs, analytics, and performance data do not transfer from v1 to v2, impacting provider ranking.\n"]]