Articles in this section

Migrate the Walmart - NetSuite integration app to OAuth

Saikumar Rachamalla
Updated

Walmart moved its APIs to OAuth authentication and required all integrations to use it by September 30, 2026. The Walmart - NetSuite integration app supports this with a new Walmart OAuth Connection and with replacement flows for its wrapper-based Order, Fulfillment, Inventory, and Pricing flows. Flows that still use the legacy wrapper connection may fail to authenticate with Walmart, which stops order, fulfillment, inventory, or pricing syncs. This article walks integration app administrators through the one-time migration. The migration doesn't change what the flows do, and existing mappings, schedules, and configurations are preserved.

What changes

  • Authentication: Instead of a Client ID and Client Secret, you authorize access by signing in through a Walmart login pop-up.
  • Connections: A new connection named Walmart OAuth Connection is added to the integration app automatically.
  • Flows: Each wrapper-based flow has a replacement flow in the same flow group. The original flows are labeled (Deprecating on Sep 30, 2026).
  • Order flows: The separate customer, order, and acknowledgment flows are consolidated into one flow, Walmart order to NetSuite order Add. For how it works, see Sync Walmart orders to NetSuite.
  • WFS and transfer order flows: The Order (WFS) and Shipments (TO) flows switch to the OAuth connection through a one-time setting.
  • Mappings: All flow mappings are upgraded to Mapper 2.0.

Prerequisites:

  • Make sure you have your Walmart Seller Center credentials.
  • Make sure you have permission to edit connections, flows, and settings in integrator.io.

Authorize the Walmart OAuth Connection

  1. Open the Walmart - NetSuite integration app, and go to Connections.
  2. Open Walmart OAuth Connection. It shows Offline until you authorize it.
  3. Sign in through the Walmart login pop-up to authorize access.
  4. Confirm that the connection status changes to Online.

Other Walmart connections, such as Walmart Connection (wrapper) and Walmart Http Connection, can still appear on the list. Only the Walmart OAuth Connection needs to be authorized for the migration.

Turn on the replacement flows

The replacement flows are already in your account.

  1. In the integration app, go to Flows.
  2. In each of the Order, Fulfillment, Inventory, and Pricing flow groups, turn on the replacement flow for each flow labeled (Deprecating on Sep 30, 2026).

Only one flow of each pair can be on at a time. When you turn on a replacement flow, its original flow is turned off automatically, and turning the original flow back on turns off the replacement flow.

Migrate the WFS and transfer order flows

Complete this step only if you use the Order (WFS) or Shipments (TO) flows.

  1. Make sure the Walmart OAuth Connection is Online.
  2. In the integration app, go to Settings > General > General.
  3. Select Migrate WFS and Transfer order flows to OAuth connection, and then select Save.

This is a one-time, permanent action. After you save, the setting is disabled, and the Order (WFS) and Shipments (TO) flows use the Walmart OAuth Connection.

Validate your mappings

The migration keeps your mapping logic, but review it before you rely on the new flows:

  1. Open each flow you turned on, and review its mappings in Mapper 2.0.
  2. Confirm that the required fields are mapped.
  3. Run a small test, such as a single order or record.