COMPLETE ANSWER · MARKETPLACE

How do you connect or reauthorize a solution provider in Walmart Seller Center?

Where the solution provider connection lives in Seller Center, what the OAuth grant covers, yearly renewal, and the end-of-September 2026 Delegated Access cutoff.

By Matt Drake, practicing retail advisor

DIRECT ANSWER

Connect or reauthorize a solution provider in Walmart Seller Center under Apps, then App Listings, then Connect; the OAuth 2.0 grant covers only the scopes on the consent screen and needs yearly renewal under Connected Apps. As of September 2026, Delegated Access keys stop working at the end of September 2026, so a provider still on a key needs Connect now.

You connect or reauthorize a solution provider in Walmart Seller Center from the Apps heading in the left navigation: open App Listings, find the provider, select Connect, log in on the provider’s site, and choose Authorize on the screen that lists the data scopes the provider’s app is asking for. That click is an OAuth 2.0 grant to the provider’s registered app, limited to those scopes, and Walmart requires it to be renewed every year under Apps, then Connected Apps, which is also where Revoke lives. Reauthorizing is the same Connect flow run again. As of September 2026 there is a deadline: the developer portal says the older Delegated Access keys stop working at the end of September 2026, so any provider still running on a key needs the Connect flow before then.

Where does the solution provider connection live in Seller Center?

Under Apps, in the left navigation, on two pages. App Listings is the catalog of approved Solution Providers with apps in the App Store; a provider that has implemented OAuth 2.0 shows a Connect button, and not every approved provider can be connected through the App Store yet. Connected Apps is the list of apps you have authorized, with the two controls for a live connection, Renew and Revoke; Revoke fully removes the provider’s access to your data. The flow is three steps: select the provider under App Listings and choose Connect; create an account or log in on the provider’s website; then, back on the authorization screen, review what the app is asking for, select the privacy-policy checkbox, and choose Authorize to continue or Decline to stop. Your own API keys, generated in the Developer Portal for an integration you run yourself, are not part of this.

What does the OAuth authorization grant, and to whom?

It grants the provider’s registered app, not a person at the provider, a standing permission to call the Marketplace API on your account for the scopes you approved. Walmart issues the app a refresh token tied to your seller ID; the app trades it for fifteen-minute access tokens as it works, and the refresh token itself is good for one year (Token API reference). Your Seller Center password is never shared, and the provider never receives your API keys.

The consent screen draws from a fixed set of nine scopes: Items, Orders, Pricing & Promotions, Inventory, Returns, Account Profile, Analytics, WFS, and Shipping, each mapped to API resources and feed types (Items covers item feeds, Orders covers order retrieval and acknowledgment). A provider asking for scopes it does not need is a provider to question before you click Authorize. The grant does not give the provider a Seller Center login, does not let the app act outside the scopes it asked for (a call outside a granted scope fails as a permission error, not a token error), and does not survive Revoke.

Why does the connection need renewing every year?

Because Walmart requires annual renewal of the OAuth 2.0 authorization for connected apps, in those words on Marketplace Learn. The control is Renew under Connected Apps, which extends the authorization for another year. Underneath, this is the one-year life of the refresh token: when it expires, the provider’s app can no longer mint access tokens for your account, and the connection is dead until you renew or reconnect. Put the anniversary of the day you clicked Authorize on your own calendar, minus thirty days, one entry per provider. Marketplace Learn also recommends a yearly review of connected providers; revoke any that should no longer have access.

How do you tell whether a provider still runs on a Delegated Access key?

Delegated Access was the older method: instead of a consent screen, you created a separate Client ID and Client Secret for a named provider in the Delegated Keys section of the Developer Portal, chose which services it could reach, and handed the pair to the provider. Three tells separate a key-based integration from an OAuth one. First, Connected Apps: an OAuth connection appears there, so a working integration whose provider is not listed is not on an OAuth grant. Second, the App Listings button: a provider whose listing has no Connect button has not implemented OAuth 2.0 for the App Store, so whatever it runs on is a key. Third, the Developer Portal: a Delegated Keys entry for the provider is the live credential. That section is being removed as part of the transition; if it is already gone, ask the provider in writing which method it uses for your account. A fourth possibility is worse than either: the provider holds a copy of your own primary API keys, which means unscoped access to everything your account can do. Move it to a Connect authorization, then rotate your keys.

What breaks when an authorization lapses?

Nothing in Seller Center itself. Walmart keeps running your account as it stands; what stops is every action the provider’s app took on your behalf, and the failure is silent from Walmart’s side.

Feeds (Items, Pricing & Promotions, Inventory). Content updates, price changes, and inventory pushes the provider submits never reach Walmart; there is no feed ID and no error report, because nothing was received. Listings and prices freeze, which matters if the provider was repricing to hold the Buy Box or to stay clear of the pricing rule that can unpublish an item.

Orders. Released orders still land in Seller Center, but the provider stops pulling, acknowledging, and posting tracking for them. The auto-cancel cliff four calendar days past the Expected Ship Date still runs; each auto-cancel refunds the customer and counts against Cancellation Rate, and tracking that never posted counts against Valid Tracking Rate.

Inventory. Walmart keeps selling against the last quantity it received: oversell if the provider was decrementing for other channels, a stuck zero if its last push was a zero ahead of a restock.

Reports. Report pulls, settlement downloads, and insights calls fail, so the provider’s dashboards freeze at the last sync and the payout tie-out lands back on you.

What does a lapsed connection look like in practice?

A hypothetical seller-fulfilled kitchenware seller with 900 SKUs runs listings, inventory, and order flow through one order-management provider. On a Tuesday in early October 2026 the provider’s dashboard shows a last sync of Sunday night and a red Reconnect Walmart banner. Seller Center shows fourteen released orders since Monday, none acknowledged, and Monday’s inventory push never landed. Before any diagnosis, acknowledge the orders, ship what is packed, and post tracking by hand; two carry a Monday Expected Ship Date, so their auto-cancel cliff is Friday. Then set inventory by hand on the fastest movers.

Diagnosis is one page: Apps, then Connected Apps. In the first version of the story the provider is listed; the seller connected in early September 2025, so the one-year authorization has expired. Select Renew, or if Renew is not offered, run Connect again from App Listings, which reruns the consent screen and issues a fresh one-year grant. In the second version the provider is not listed at all, so this integration never ran on OAuth, and the Developer Portal confirms it with a Delegated Keys entry from 2024 that stopped working when September ended. The fix is the same Connect flow, a message to the provider to switch this account to the OAuth connection, then removing the delegated key once the provider confirms. In both versions the last step is a calendar entry one year out, minus thirty days.

What is the status of the Delegated Access retirement as of September 2026?

As of September 6, 2026, the developer portal’s US Marketplace home and its Delegated access authorization page carry the same wording, quoted as it reads today: “The ability for approved Solution Providers to create new Delegated Access keys was retired on July 30, 2026. Existing Delegated Access keys will continue to work until the end of September 2026.” The instruction to providers follows: “Migrate your sellers to OAuth 2.0 by instructing them to reauthorize their app connections using the Connect button in the Walmart App Store.” The page’s FAQ adds that after that date “all Delegated Access keys will stop functioning.”

Three things to read out of that. First, the current wording is “the end of September 2026,” not a day and an hour; an earlier version of the same banner, live in early July, said existing keys “will stop working on October 1, 2026,” so the two readings agree: September 30 is the last working day and October 1 the first dead one. Second, the seller-facing connect guide on Marketplace Learn, last updated February 10, 2026, still says existing providers “can still use delegated access”; the developer portal is newer and explicit, so it wins. Third, the Marketplace Learn release notes carried no entry on the retirement as of September 6, 2026. If your provider has not asked you to reconnect through the App Store, ask it which method your account is on; a provider whose listing still lacks a Connect button at the end of September has no supported way to reach your account in October.

What are the limits of this answer?

This describes the seller side of the connection as of September 2026. What an expired authorization looks like on the Connected Apps page, and whether Renew appears before expiry or only after, is not spelled out publicly; when the control you expect is missing, Connect from App Listings is the reliable path. The token lifetimes come from the developer portal’s OAuth pages and can change without a Marketplace Learn entry. The Delegated Access dates are quoted as they read on September 6, 2026, and Walmart has revised that wording at least once since July, so reread it before relying on the exact day. Retail Reason does not connect to retailer portals, is not an approved Solution Provider, and does not appear in the App Store; it answers questions and checks plans; it does not file disputes or touch your account.

Sources checked

← All complete answersChoose a plan →