SuperSync Integrations - Legacy Walmart Documentation
This document describes how the legacy Walmart Marketplace connector behaves and what each configuration field means. Use this as a reference when setting up, troubleshooting, or understanding how your Walmart integration is configured in SuperSync.
Overview
SuperSync connects Walmart Marketplace with NetSuite to keep orders, inventory, pricing, and fulfillment data in sync between the two platforms. Depending on how your flows and mappings are configured, data can move in one or both directions.
| Direction | Typical Use |
|---|---|
| Walmart → NetSuite | Import Seller Fulfilled or Walmart Fulfilled sales orders from Walmart Marketplace into NetSuite |
| NetSuite → Walmart | Push inventory updates, price updates, item fulfillments, and order acknowledgements from NetSuite to Walmart Marketplace |
Authentication uses OAuth 2.0 client credentials. SuperSync obtains a bearer token using your Client ID and Client Secret and caches it for up to one hour, refreshing automatically before expiry. All requests are made to https://marketplace.walmartapis.com.
Credentials
| Field | Required | Description |
|---|---|---|
| Yes | Your Walmart Marketplace API Client ID. Found in Walmart Seller Center under Settings > API Keys. Missing this value will prevent the integration from initialising. |
| Yes | Your Walmart Marketplace API Client Secret. Found alongside the Client ID in Walmart Seller Center. Missing this value will prevent the integration from initialising. |
Walmart → NetSuite
This direction pulls orders from Walmart Marketplace and creates or updates the corresponding records in NetSuite.
Supported Record Types
Set the Record Type field in your flow mapping to one of the following values:
| Record Type Value | What It Syncs |
|---|---|
| Walmart Marketplace orders → NetSuite sales orders |
| Walmart Marketplace cancelled orders → NetSuite |
How It Works
- SuperSync fetches orders from Walmart using a time-based window starting from the last successful sync date (floored by the Live Date config).
- Orders are fetched with a
createdStartDatewindow of up to 180 days in the past. If no window is provided, Walmart defaults to the past 7 days — SuperSync overrides this automatically. - If a Filter Order Status value is configured (e.g.
status=Shipped), SuperSync applies that filter to the API request. - Results are paginated automatically. SuperSync follows Walmart's cursor-based pagination until all pages are retrieved.
- Each order is checked against sync history. Records that have already been successfully synced are skipped to prevent duplicates.
- Orders with an
orderDatebefore the Live Date are skipped. - Each qualifying order is decoded using the Mapping Configuration JSON and sent to NetSuite.
Configuration Fields
Identity and Date Fields
| Field | Default | Description |
|---|---|---|
| | The Walmart field used as the unique record identifier for deduplication and tracking. |
| | The Walmart field stored as the transaction reference in SuperSync. |
| | The Walmart date field used to drive the sync window. |
| | The earliest date from which orders will be synced. Orders before this date are ignored. Also acts as the floor for incremental sync. Format: YYYY-MM-DD. |
Order Filtering
| Field | Default | Description |
|---|---|---|
| | Controls which fulfillment type of orders are fetched from Walmart. If left blank, defaults to SellerFulfilled. Accepted values: SellerFulfilled (merchant ships directly to customer), WFSFulfilled (Walmart Fulfillment Services handles shipping), 3PLFulfilled (a third-party logistics provider handles shipping). You can also pass a comma-separated list to fetch multiple types at once (e.g. SellerFulfilled,WFSFulfilled). |
| (empty) | Optionally filters orders by status. Enter in key=value format (e.g. status=Shipped). When set, SuperSync appends this as a query parameter to the Walmart API request. Accepted values: Created (order placed, awaiting acknowledgement), Acknowledged (receipt confirmed, ready to fulfill), Shipped (tracking submitted), Delivered (carrier confirmed delivery), Cancelled (order line cancelled). |
Mapping Configuration
The Mapping Configuration JSON defines how each Walmart order is transformed into a NetSuite record. This controls what NetSuite receives — field values, nesting, line items, date formatting, and so on.
- The ID, DATE, and REFERENCE fields control which Walmart properties are used for tracking and deduplication; they do not directly affect the NetSuite payload.
- The Mapping Configuration JSON controls what data is written into NetSuite.
NetSuite → Walmart
This direction reads records from NetSuite using a saved search and pushes them to Walmart Marketplace.
Supported Record Types
| Record Type Value | What It Syncs |
|---|---|
| NetSuite inventory records → Walmart Inventory Update |
| NetSuite pricing records → Walmart Price Update |
| NetSuite item fulfillments → Walmart shipping notifications |
| NetSuite order receipts → Walmart Order Acknowledgement |
How It Works
- SuperSync runs the saved search defined in Search Mapping Name to retrieve a list of NetSuite records.
- For
itemfulfillmentflows, records are grouped byinternalidand compiled into order-level records with line items before being sent to Walmart. - Each record is decoded using the Mapping Configuration JSON and sent to the appropriate Walmart API endpoint.
- After a successful sync, SuperSync can optionally write the export result back to the originating NetSuite record (see Write-Back Fields below).
- Records that have already been successfully synced are skipped automatically.
Configuration Fields
Identity and Date Fields
| Field | Default | Description |
|---|---|---|
| | The NetSuite field used as the unique record identifier for deduplication and tracking. |
| (inventory/price), (empty) (itemfulfillment/orderreceipt) | The NetSuite date field used for record validation. |
| (inventory/price),(itemfulfillment), (empty) (orderreceipt) | The NetSuite field stored as the transaction reference in SuperSync. For itemfulfillment flows, this is used to match the record to the correct Walmart order when sending the shipping notification. |
Search Fields
| Field | Default | Description |
|---|---|---|
| (required) | The name of a saved Flow Mapping that defines the NetSuite search used to retrieve records. Must match an existing mapping on the same account exactly. If missing or not found, the sync will throw an error. |
Line Item Fields (Item Fulfillment)
These fields apply to itemfulfillment flows, where NetSuite search result rows must be grouped and compiled into order-level records before sending to Walmart.
| Field | Default | Description |
|---|---|---|
| | The field used to uniquely identify each line item row within a grouped record. |
|
| The set of fields carried over from NetSuite search result rows onto each line item. SuperSync can also infer these automatically from the Mapping Configuration JSON. |
| | The field used to group NetSuite search result rows into single order records before sending to Walmart. |
| | The field used to identify the mainline row in a NetSuite search result. |
| | The value of MAINLINE_PROPERTY that identifies a row as the mainline. |
| (empty) | The set of fields carried over from the mainline row onto the order-level record. |
Walmart Marketplace Header
| Field | Default | Description |
|---|---|---|
| (empty) | When set, this value is passed as the WM_MARKET header on all Walmart API requests, including authentication. Required for some Walmart marketplace configurations. If left blank, the header is omitted. |
Write-Back Fields (NetSuite → Walmart)
After a record is successfully sent to Walmart, SuperSync can write the result back to the originating NetSuite record.
| Field | Default | Description |
|---|---|---|
| for inventory/price | The NetSuite custom field where the Walmart result ID is written after a successful sync. |
| for inventory/price | The NetSuite custom field used to flag a record as successfully exported to Walmart. |
Note: The Don't Update field in NetSuite toggle in the flow mapping UI controls whether SuperSync skips the write-back step entirely. When enabled, no fields are written back to NetSuite after a successful sync.
Mapping Configuration
The Mapping Configuration JSON defines how each NetSuite record is transformed before it is sent to Walmart. For inventory flows, the payload maps item SKU and quantity. For price flows, it maps SKU and pricing details. For itemfulfillment and orderreceipt flows, the JSON defines shipping and acknowledgement data respectively.
Troubleshooting
| Symptom | Likely Cause |
|---|---|
| "Walmart API information missing: no mapping configurations found" | No configuration values have been saved on the flow mapping. Verify credentials and other required fields are entered and saved. |
| "Walmart information missing: Api Client ID" | CLIENT_IDis missing from the flow mapping configuration. |
| "Walmart information missing: Api Client Secret" | CLIENT_SECRETis missing from the flow mapping configuration. |
| "No Search Mapping Provided" | A NetSuite → Walmart flow is missing SEARCH_MAPPING_NAME. |
| "flow mapping 'X' not found" | The value in SEARCH_MAPPING_NAME doesn't match any existing flow mapping on the account — check for typos or confirm the mapping exists. |
| 401 / "Access denied due to invalid key" | CLIENT_ID or CLIENT_SECRET is incorrect. Verify values in Walmart Seller Center under Settings > API Keys. SuperSync will attempt to re-authenticate once before throwing an error. |
| 409 / "This is a duplicate order" | Walmart has received and rejected a duplicate submission. Check whether the record was already successfully synced in SuperSync's sync history. |
| 412 / "Values are Required" | The payload sent to Walmart is missing one or more required fields. Review your Mapping Configuration JSON to ensure all required Walmart fields are populated. |
| Record skipped, no error | The record was already successfully synced (matching transaction ID found in sync history). This is by design to prevent duplicates. |
| Order skipped due to live date | The order's orderDate is before the configured LIVE_DATE. Update the Live Date if older orders need to be synced. |
If you have questions or run into issues not covered here, reach out to supersync@netgain.tech.
