This checklist is for scoping a potential integration. It does not confirm a connector, account setup or supported transfer behavior.
Which system is authoritative?
Record the source of each product-data domain and the team that may change it. Resolve conflicts before mapping begins.
Which records and fields matter?
List objects, identifiers, variants, media, category paths and fields that the intended destination needs. Mark uncertain requirements for review.
Who approves mapping decisions?
Name the people who can approve transformations, defaults and exceptions. Keep mapping decisions separate from transport choices.
What must be confirmed for the account?
Review authentication, permissions, environment, rate limits and supported events with the Vexa team for the actual destination account.
How will outcomes be checked?
Define the expected result, failure owner, retry approach and reconciliation evidence before agreeing implementation scope.
Keep the product record, quality findings, ownership, and next commerce-preparation step in the same operating conversation.