The Walmart V3 Marketplace integration connects a Walmart Seller account to Logiwa for order fulfillment, product synchronization, inventory updates, and shipment confirmation. The initial connection is designed to be quick and can typically be completed in about 2–3 minutes when you have access to the Walmart account and verification email.
Before You Begin
A Walmart Marketplace Seller account with credentials that can authorize the connection.
Access to the email account or authenticator used by Walmart for verification.
The Logiwa Client and Warehouse that should be associated with the Walmart connection.
The Shipment Order Type and Pack Type to be used for Walmart orders.
Products should be reviewed for SKU and barcode alignment before go-live, especially when Walmart and Logiwa use different SKU values.
⚠️ Seller Fulfilled orders only: Logiwa only supports Seller Fulfilled Walmart orders. WFS (Walmart Fulfilled Services) orders are not pulled into Logiwa by this integration.
Connect Walmart in Logiwa
Log in to Logiwa and open Integrations > Store and Marketplace.
Navigate to Integrations → Store and Marketplace.
2.Locate the Walmart integration card.
3.Click Connect Now.
Select Walmart and click Connect Now.
Connection Configuration
Field | Description |
Client | The Logiwa client that owns the Walmart orders, products, and related integration activity. |
Warehouse | The Logiwa warehouse that will fulfill Walmart orders and serve as the inventory source for this connection. |
Shipment Order Type | The shipment order type that Logiwa will apply to Walmart orders created through the integration. |
Pack Type | The Logiwa pack type that should be used for Walmart product and order quantities. |
Contact Email | Email address that receives integration notifications, status updates, and errors. |
⚠️ Important: Confirm the Client and Warehouse carefully. These values determine where Walmart transactions are created and which inventory is used for synchronization.
Authorize the Walmart Seller Account
After the Logiwa configuration is entered and you continue, a Walmart authorization window opens.
Log in using the Walmart Seller account that should be connected to Logiwa.
Walmart Marketplace login screen.
2. Complete Walmart verification. Walmart emails a one-time verification code to the account contact.
Example Walmart Marketplace verification email.
3. Enter the verification code when prompted.
4. Review and authorize the requested permissions.
5. After authorization, return to Logiwa and confirm that the Walmart connection is active.
💡 Expected setup time: If the Walmart credentials and verification email are available, the authorization portion of setup normally takes only a few minutes.
What the Walmart Integration Does
Order Creation: Downloads eligible Walmart Seller Fulfilled orders and creates shipment orders in Logiwa for fulfillment.
Order Updates: Applies supported Walmart order changes to the corresponding Logiwa shipment order.
Order Cancellations: Supports full-order cancellation scenarios. Partial line-level cancellations are not supported and require operational review.
Product Synchronization: Imports Walmart product information and creates or updates the corresponding Logiwa product relationship.
Product Listings: Stores the Walmart-specific product identity against the linked Logiwa product, including the channel identifier and Walmart Seller SKU.
Inventory Synchronization: Sends available/sellable inventory from Logiwa to Walmart.
Shipment Confirmation: Sends carrier and tracking information back to Walmart after fulfillment.
Order Synchronization
Direction: Walmart → Logiwa
Sync Frequency: Every 10 minutes.
When a new order appears in Walmart with status Created, the integration imports the order into Logiwa. After the order is successfully received by Logiwa, the Walmart order status changes to Acknowledged.
⚠️ Seller Fulfilled only: Logiwa does not pull in WFS (Walmart Fulfilled) orders.
Order Information Transferred:
Customer name and shipping address
Order line SKUs and quantities
Requested shipping method
Order reference number / sales order number
Required Order Data
Requirement | Purpose / Behavior |
Client | Identifies which client in the 3PL Logiwa environment owns the order. If the client cannot be determined, the order cannot be created. |
Order Code | Unique order/reference number, such as the Walmart |
Shipment Order Type | Controls fulfillment rules such as partial shipment, backorder, B2C, B2B, dropship, or other client-specific behavior. |
Shipment Order Date | Indicates when the order was created; used for tracking and scheduling inside Logiwa. |
Currency | Defaults to USD unless another currency is configured during onboarding. |
Order Lines | Contains item-level SKU, quantity, and shipping information. Every item must reference a product that exists in Logiwa or the order will be rejected. |
Warehouse Name | Determines which Logiwa warehouse is associated with the Walmart connection and receives imported orders. Each Walmart workflow is configured for a single Logiwa warehouse — a separate workflow must be configured per warehouse if multiple are required. |
Shipment Confirmation
Direction: Logiwa → Walmart
Sync Frequency: Every 10 minutes.
After an order is shipped or partially shipped in Logiwa, shipment information is sent back to Walmart. When the update succeeds, the corresponding order status is updated in Walmart to Shipped.
Shipment Data | Description |
Order Number | Identifies the Walmart order being updated. |
Order Lines | Identifies shipped SKUs and shipped quantities. |
Carrier Name | The carrier used to fulfill the shipment. |
Tracking Number | The tracking identifier returned to Walmart and the connected sales channel. |
Shipment Date | Date the order or partial shipment was fulfilled. |
Product Synchronization
Direction: Walmart → Logiwa
Sync Frequency: Every 12 hours.
How it works:
Logiwa retrieves products from the Walmart connection.
Each SKU is reviewed against the existing product catalog in Logiwa.
If a product already exists in Logiwa, key details such as name, description, pricing, and packaging are compared and may be updated when differences are found.
If a product does not exist in Logiwa, the integration can create the product automatically.
Product Data Synchronized
Walmart Product Data | Logiwa Behavior / Notes |
SKU | Primary product identifier used to determine whether the product already exists. |
Name | Used to create or update the product name. |
Description | Used to create or update the product description. |
Purchase Price | Synchronized when provided by Walmart. |
Wholesale Price | Synchronized when provided by Walmart. |
Pack Type | Defaults to Each unless another value is requested during onboarding. |
Currency | Defaults to USD unless another currency is requested during onboarding. |
Product Listings and SKU Matching
A Walmart product does not always use the same SKU as the warehouse product in Logiwa. The integration uses Product Listings to preserve the Walmart-side identity while linking it to the correct Logiwa product.
Example: a Logiwa product linked to a Walmart Product Listing. The Product Listing stores the Walmart channel identifier and Seller SKU.
⚠️ Key concept: The Logiwa SKU and Walmart Seller SKU do not need to be identical. When they differ, a Product Listing must ultimately link the Walmart Seller SKU to the Logiwa product used for fulfillment.
During Product Sync, the integration may use a shared UPC/barcode to identify an existing Logiwa product when the Walmart and Logiwa SKUs differ. Once the product relationship is identified, the corresponding Walmart Product Listing can be created or maintained.
🔴 Walmart order data does not provide the UPC used for this product-matching process. Therefore, Order Sync relies on either a direct SKU match or an existing Product Listing — not on UPC/barcode matching. See "Why Product Listings Matter for Order Sync" below.
Matching SKUs
Field | Description |
Walmart Seller SKU | 12345 |
Logiwa SKU | 12345 |
Result | The integration can associate the Walmart listing to the Logiwa product using the matching SKU. No special mapping is normally required. |
Different Walmart and Logiwa SKUs
Walmart Seller SKUs do not have to match the SKU used for the corresponding product in Logiwa.
Example
Field | Example |
Walmart Seller SKU | 12345 |
Walmart Product ID (WPID) | ABC123 |
Walmart UPC | 123456789000 |
Logiwa SKU | ABCDE |
In this scenario, Walmart identifies the item as 12345, while the warehouse continues to receive, store, pick, and ship the product using Logiwa SKU ABCDE. The Walmart Seller SKU must be associated with the correct Logiwa product before Walmart orders can be processed successfully. There are two supported approaches.
Option 1 — Create or Import a Product Listing
Recommended when the Walmart Seller SKU and corresponding Logiwa SKU are already known.
A Product Listing connects the SKU used by Walmart to the existing product that Logiwa uses for warehouse operations. Using the example above:
Product Listing Information | Value |
Channel | Walmart |
Walmart Seller SKU | 12345 |
Logiwa Product | ABCDE |
Once the Product Listing is linked, Walmart can continue sending the item as Seller SKU 12345, while Logiwa resolves the item to product ABCDE for fulfillment.
Example mapping: Walmart: 12345 → Product Listing → Logiwa: ABCDE
This allows Walmart and Logiwa to use different SKU values without requiring a duplicate warehouse product to be created.
Manually importing Product Listings in bulk: For clients with multiple non-matching SKUs, Product Listings can be added or updated in bulk through the Product Listings Excel import. This is typically the preferred approach when a client already has a mapping file containing its Walmart Seller SKUs and corresponding Logiwa SKUs.
General process:
Navigate to Settings > Product Listings in Logiwa.
Export or obtain the Product Listing import template.
Enter the Walmart Seller SKU and the corresponding Logiwa product information.
Import the completed Excel file.
Review the Product Listings after the import.
Confirm that each Walmart Seller SKU is Linked to the intended Logiwa product.
💡 Example: Walmart sends Seller SKU 12345. The imported Product Listing links that Seller SKU to Logiwa SKU ABCDE. The integration can then resolve Walmart SKU 12345 to Logiwa SKU ABCDE when processing orders and inventory.
⚠️ Important: Creating a Product Listing does not create separate inventory for the Walmart SKU. Product Listings represent the channel-specific identity of the product, while inventory remains associated with the underlying Logiwa product — multiple listings can reference one product while that product maintains a single inventory quantity.
Option 2 — Match Using UPC/Barcode
When the Walmart Seller SKU and Logiwa SKU differ, Product Sync may use a shared UPC/barcode to determine that the Walmart product corresponds to an existing Logiwa product.
Example
Field | Value |
Walmart Seller SKU | WalmartSKU-12345 |
Walmart UPC | 811418000000 |
Logiwa SKU | LogiwaSKU-12345 |
Logiwa Barcode | 811418000000 |
Because the UPC/barcode values match, Product Sync can identify LogiwaSKU-12345 as the existing Logiwa product associated with the Walmart item. The resulting Walmart Product Listing should then link:
WalmartSKU-12345 → LogiwaSKU-12345
Future Walmart orders can use that Product Listing to translate the Walmart Seller SKU to the Logiwa SKU used for fulfillment.
🔴 Important: UPC/barcode matching is used to establish the product relationship during Product Sync only. Walmart Order Sync does not receive the UPC on the order line and therefore cannot use UPC as a fallback when processing an order. A Product Listing must exist for the order to resolve correctly — see below.
Why Product Listings Matter for Order Sync
Walmart orders identify each item using the Walmart Seller SKU. The order data does not include the UPC/barcode used by Product Sync for product matching.
When the Walmart Seller SKU and Logiwa SKU are identical, the integration can use the SKU directly.
When the SKUs are different, an existing Product Listing must link the Walmart Seller SKU to the correct Logiwa product.
Example:
Walmart order Seller SKU:
WalmartSKU-12345Product Listing:
WalmartSKU-12345→LogiwaSKU-12345Logiwa order SKU:
LogiwaSKU-12345
⚠️ If no direct SKU match or Product Listing exists, the integration cannot reliably determine which existing Logiwa product should be used for the order. Depending on the integration configuration, the workflow may create the missing Walmart SKU as a new Logiwa product or notify the client for review — before go-live, confirm with Logiwa which behavior applies to your configuration.
💡 Recommended practice: Complete Product Sync and review Product Listings before enabling Order Sync, especially for clients whose Walmart and Logiwa SKUs differ.
Inventory Synchronization
Direction: Logiwa → Walmart
Sync Frequency: Every 10 minutes.
Source Field (Logiwa) | Target Field (Walmart) |
SKU | SKU |
Sellable Quantity | Quantity Available |
Net Kitting Capacity | Quantity Available |
Inventory Calculation Source: For each affected SKU, the integration retrieves inventory data from Logiwa's Available to Promise (ATP) report — Logiwa's authoritative view of inventory eligible to be sold, accounting for operational constraints such as existing orders.
Quantity Sent to Walmart
For standard products
Sellable Quantity = On Hand Quantity − Open Sales Order Quantity
Kit Inventory Synchronization
For Kit to Order products, inventory is calculated differently. Instead of the standard Sellable Quantity, the integration uses the kit's Net Kitting Capacity from Logiwa's Kit Inventory Report — the maximum number of complete kits that can currently be assembled from available component inventory.
Inventory Calculation Source for Kits
Because a kit may contain multiple component SKUs, the available quantity is limited by whichever required component has the lowest available capacity.
💡 Example: Kit SKU MovieBundle requires 1× MovieA (100 available) and 1× MovieB (150 available) per kit. Even though 150 units of MovieB exist, only 100 complete kits can be assembled because MovieA is the limiting component. Net Kitting Capacity = 100, and Walmart receives 100 units of available inventory for MovieBundle.
How Component Inventory Affects the Kit
If MovieA drops to 75 units, Net Kitting Capacity becomes 75.
If MovieA reaches 0, Net Kitting Capacity becomes 0 — even if MovieB still has stock.
This prevents Walmart from advertising more kit inventory than Logiwa can physically assemble.
Quantity Sent to Walmart — By Product Type
Product Type | Inventory Source | Quantity Sent to Walmart |
Standard Product | Available to Promise Report | Sellable Quantity |
Kit to Order Product | Kit Inventory Report | Net Kitting Capacity |
Troubleshooting
Why doesn't the Walmart login window open?
Confirm pop-ups are allowed in the browser and retry the connection from the Walmart integration card.
Why wasn't the verification code received?
Confirm the Walmart account email/contact method and check spam or junk folders before requesting another code.
Why does an order fail because the product can't be found?
If the Walmart and Logiwa SKUs differ and no Product Listing exists, review Product Sync or manually create/import the correct Product Listing before retrying the order.
Why doesn't inventory update as expected?
Confirm the connection points to the correct warehouse and that the product listing is linked to the correct Logiwa product.
Why does shipment confirmation fail?
Verify the order is shipped in Logiwa and that the carrier and tracking data required by Walmart are present.
Why didn't a Walmart Fulfilled (WFS) order come into Logiwa?
This is expected — Logiwa only imports Seller Fulfilled orders. WFS orders are fulfilled by Walmart directly and are out of scope for this integration.
Can partial line-level cancellations be processed automatically?
No — partial line-level cancellations are not supported by the standard workflow and require operational review.
Can UPC/barcode matching be used as a fallback if a Product Listing is missing when an order comes in?
No. UPC/barcode matching only runs during Product Sync to help establish the product relationship. Walmart order data does not include the UPC, so Order Sync cannot fall back to it — a Product Listing (or a direct SKU match) must already exist.
Support Information
When contacting Logiwa Support about a Walmart integration issue, include the Walmart store/connection name, affected order number or SKU, approximate time of the error, and any error message received. This information helps the Support team identify the affected integration event more quickly.