How Amazon's Passkey Requirement Affects Your Webgility Desktop Connection
If you have received Amazon's email saying passkeys will soon be required to sign in to Seller Central, you can keep using Webgility Desktop exactly as you do today. Webgility connects to Amazon through a one-time authorization you approved when you first added your store, so changing how you personally sign in to Seller Central does not touch that connection.
If you have received Amazon's email saying passkeys will soon be required to sign in to Seller Central, you can keep using Webgility Desktop exactly as you do today. Webgility connects to Amazon through a one-time authorization you approved when you first added your store, so changing how you personally sign in to Seller Central does not touch that connection.
How the Webgility connection to Amazon works: When you first connected your Amazon store, you were sent to Amazon's Seller Central page and signed in once to grant Webgility permission to read your orders, settlements, and inventory. Amazon then issued Webgility a secure authorization token. From that moment on, Webgility uses the token to talk to Amazon on your behalf. Your Seller Central username, your password, and now your passkey are never shared with Webgility and never travel through the Webgility Desktop app.
You do not need to change any Webgility setting, re-enter credentials, or run any update to prepare for the passkey rollout. Your scheduled downloads, settlement posting, and inventory sync continue to run on their normal schedule.
The one time the passkey could come into play is if you ever decide to disconnect and re-add your Amazon store in Webgility Desktop — for example, if you revoke Webgility's access from the Amazon side, or you move to a brand-new Amazon seller account. In that case the reconnection flow is unchanged: Webgility sends you to Seller Central, you sign in with your passkey the same way you now sign in to Amazon directly, and Webgility receives a fresh authorization token.
Note: Set up your Seller Central passkey on at least two devices so you still have a way in if one device is unavailable. Passkeys do not sync across different manufacturers' ecosystems, so a passkey saved on an iPhone cannot be used from a Windows computer unless you also enroll a passkey on that Windows computer.
If you ever do need to reconnect your Amazon store in Webgility Desktop after setting up a passkey, follow these steps.
- Open Webgility Desktop and go to Connections > Sales Channels > Manage Sales Channel, then click the Action pencil beside your Amazon store and open Sales Channel Settings. The settings panel for your Amazon store opens.
- Click Connect to Amazon. Webgility opens your browser and sends you to Amazon's Seller Central sign-in page. For a full walk-through of this screen, see Connect Your Amazon Store in Webgility Desktop.
- Sign in to Seller Central with your passkey, approve Webgility's access when Amazon prompts you, and wait for the browser to return you to Webgility Desktop. Webgility shows a success message once the new authorization token is stored. If the browser returns an error instead of a success message, see reconnect your Amazon store if the authorization is revoked for the recovery flow.
Everything that comes after — order downloads, posting, settlement reconciliation — picks up where it left off, because only the authorization token was refreshed and all your existing Webgility settings stay in place.
If you are not sure whether your Amazon connection is still active, open Connections > Sales Channels, click the Action pencil beside your Amazon store, open Sales Channel Settings, and click Test Connection. A green confirmation message tells you the token is still valid. If you see a sign-in prompt instead, the connection has been revoked on the Amazon side (not by the passkey change) and you can follow the three steps above to reconnect.
If you still have questions about how the passkey rollout interacts with your specific Amazon setup, contact Webgility Support with your Subscriber ID and the exact message you are seeing in Seller Central.