{"section":"known-issues","requestedLocale":"en","requestedSlug":"seller-account-created-with-incorrect-editionsponsor-during-onboarding","locale":"en","slug":"seller-account-created-with-incorrect-editionsponsor-during-onboarding","path":"docs/en/known-issues/Apps/seller-account-created-with-incorrect-editionsponsor-during-onboarding.md","branch":"main","content":"## Summary\n\n\nDuring the onboarding process of new sellers through the Seller Portal, some accounts are being created with the incorrect edition and/or sponsor. The expected behavior is that the account should be provisioned with the \"edition-seller\" edition sponsored by the sponsor account. However, in certain cases, the account is created using the default VTEX edition/sponso.\n\nInvestigation indicates that this issue originates from failures or retry events during the IO provisioning process. The payload sent for account creation contains the correct information, but if there is an internal retry within IO, the edition/sponsor may not be correctly applied, leading to an inconsistent seller environment.\n\n\n#### Simulation\n\n\n\n- Initiate the onboarding flow for a new seller on the platform via Seller Portal.\n- The seller will receive an invitation and accept it, triggering internal provisioning actions (Onboarding.Web, OnboardingBO, Billing).\n- Monitor onboarding and account creation logs (especially vendor_onboarding, onboarding-api calls, account creation in Billing).\n- If an internal IO error or retry happens during the edition/sponsor setup, the account may be created with an incorrect edition and/or sponsor.\n- The affected seller will not have the correct environment, impacting features and permissions.\n\n\n#### Workaround\n\n\nN/A"}