Articles in this section

Migrate to OAuth–based HTTP Connections

Saikumar Rachamalla
Updated

Overview

As Walmart deprecates its existing authentication mechanism effective May 01, 2026, and moves to an OAuth-based authentication model, we have updated the Walmart – NetSuite integration app to support Walmart OAuth authentication and introduced updated flows to ensure continued compatibility.

This migration ensures continued compatibility with Walmart APIs and does not change functional behavior from a business perspective. However, you must complete a few one-time configuration steps to transition successfully.

Authentication change (Walmart-side)

  • Before: Authentication relied on credentials such as Client ID and Client Secret
  • Now: Authentication uses OAuth, where you sign in through a Walmart login pop-up to authorize access

Integration app changes

  • A new connection named Walmart OAuth Connection has been added
  • Wrapper-based flows are replaced with updated flows
  • Order processing flows are consolidated
  • WFS and Transfer Order flows require a one-time migration setting
  • Flow mappings are upgraded to Mapper 2.0

Before you begin

  • Ensure you have access to Walmart Seller Center credentials
  • Ensure you have permission to edit Connections, Flows, and Settings in integrator.io
  • Plan to validate mappings after migration

Migration Steps

Step 1: Bring the Walmart OAuth Connection online

With this upgrade, you’ll see a new connection named Walmart OAuth Connection is automatically added.

To authorize the connection

  1. Go to Connections in the integration app.
  2. Locate Walmart OAuth Connection (it may initially appear Offline).
  3. Open the connection.
  4. Complete the OAuth authorization using the Walmart login pop-up.
  5. Confirm the connection status changes to Online.
Connections_1st.png

Important

  • You may see other Walmart connections, such as Walmart Connection (Wrapper) or Walmart Http Connection.
  • For this migration, only the Walmart OAuth Connection must be authorized.
Step 2: Enable replacement flows for wrapper-based sections

Several existing flows were originally built using wrapper-based connections. These flows now have replacement flows built using HTTP-based handling.

The following are the affected flow sections:

  • Order
  • Fulfillment
  • Inventory
  • Pricing

Important

  • Existing flows marked as Deprecating on May 01, 2026
  • New replacement flows are available in the same flow section

To enable replacement flows:

  1. Go to Flows.

  2. Open each wrapper-based flow section:

    1. Order
    2. Fulfillment
    3. Inventory
    4. Pricing
  3. Enable the replacement flow.

Important

  • When you enable the new flow, the older flow is automatically disabled
  • When you enable the old flow, the new flow is automatically disabled
  • At any time, only one flow (old or new) can be enabled
Orders flow migration (consolidation)

Previously, order processing was handled by multiple flows, such as:

  • Customer creation/update
  • Order import into NetSuite
  • Order acknowledgment back to Walmart

With this upgrade, these steps are consolidated into a single order flow.

  • A new flow, such as:

    Walmart Order to NetSuite Order Add 

  • Older flows labeled with a message:

    (Deprecating on May 01, 2026) 

Flows_2nd.png

Note

This is a structural change only. The functional outcome remains the same.

Step 3 (Only if applicable): Migrate Order (WFS) and Shipments (TO) flows to OAuth connection

If you are using Order (WFS) or Shipments (TO) flows, complete this step.

This one-time setting migrates existing Order (WFS) or Shipments (TO) flows to use the Walmart OAuth Connection.

To migrate:

  1. Go to Settings > General.
  2. Select the Migrate WFS and Transfer order flows to OAuth connection settingcheckbox.
  3. Click Save.
Settings_3rd.png

Important

  • Ensure the Walmart OAuth Connection is Online before clicking Save
  • This is a one-time action
  • After a successful migration, the setting becomes disabled (greyed out)
  • Order (WFS) or Shipments (TO) flows automatically switch to the OAuth connection
Step 4: Validate mappings (Mapper 2.0)

As part of this migration, all mappings are now on Mapper 2.0.

Recommended validation
  • Open enabled flows and review mappings
  • Confirm required fields are mapped correctly

  • Run a small test (for example, a single order or record)

    Note

    Mapping logic is preserved, but validation is recommended as a best practice.

What happens after migration
  • Walmart OAuth authentication is active
  • Legacy wrapper-based flows are replaced with OAuth-based flows
  • WFS/Transfer Order flows (if used) are migrated
  • Mappings are validated and ready for use