Walmart Marketplace Connector

The problem

Selling on Walmart Marketplace puts a fulfillment clock on every order. Acknowledgement windows, expected ship dates and carrier tracking are scored, and the data that satisfies those requirements — quantity on hand, item identifiers, shipping carrier and tracking number, ship-from location — already lives in NetSuite. What is usually missing is the wiring between the two.

So teams do it by hand. Someone downloads an order report from Seller Center, keys Sales Orders into NetSuite, re-keys tracking numbers back into Walmart after the Item Fulfillment is created, and updates a spreadsheet of available quantity twice a day. Every one of those steps is a place where a late acknowledgement, a wrong tracking number, or an oversell against stock that was sold on another channel an hour ago becomes a real cost. The manual process also does not scale: it holds up while volume is low and breaks in the exact week that volume spikes.

What ECOSIRE builds

This is a build-to-order NetSuite customization. Nothing here is a shrink-wrapped product you download — ECOSIRE writes the connector against your NetSuite account, your item catalogue and your Walmart seller account, and hands you the source.

Order ingestion and acknowledgement

A Scheduled Script polls the Walmart Marketplace orders API on an interval you choose and creates NetSuite Sales Order records. Each Walmart purchase order number, customer order number, order line number and ship method are stored in custom body and column fields so every downstream record traces back to the source. Acknowledgement is sent back to Walmart as part of the same governance-aware job, so an order is not left unacknowledged because a nightly batch failed silently. Duplicate protection is done with a saved search lookup on the Walmart purchase order number before any record is created.

Inventory and item publishing

A Map/Reduce script computes available quantity per item — either from Inventory Item quantity available, a location-filtered saved search, or a custom availability formula you define during scoping — and pushes it to Walmart. In a OneWorld account, availability can be restricted to the subsidiaries and Locations that actually serve the Walmart channel, so warehouse stock reserved for wholesale is never advertised on the marketplace. Item content (price, attributes, identifiers) can be published from Inventory Item, Assembly Item, Kit/Package or Matrix item records using a field mapping stored on a custom record so your team can change it without a code change.

Fulfillment, tracking and returns

A User Event script on the Item Fulfillment record sends shipment notice to Walmart the moment fulfillment is approved: carrier, method, tracking number and shipped quantity per line. Because it is triggered by the record rather than a batch, tracking lands inside the expected window instead of at the next polling cycle. Returns and cancellations are pulled back into NetSuite as Return Authorizations or order line cancellations, with reason codes mapped to your existing NetSuite lists.

Walmart Fulfillment Services

If you use WFS, the connector treats it as a separate supply source. WFS stock is tracked against a dedicated NetSuite Location so that a WFS order does not decrement your own warehouse, and inbound shipment plans can be represented as Transfer Orders. This keeps your NetSuite inventory valuation honest instead of forcing a manual adjustment every month.

Custom records, roles and monitoring

Every moving part is inspectable. A custom record stores the connection configuration and field mappings; another logs every API call with request, response, HTTP status and the NetSuite record it touched, so a support question is answered by opening a saved search rather than by guessing. A RESTlet is deployed for inbound webhooks and for your own tooling. A dedicated integration Role is created with only the permissions the scripts need, and a custom segment can be added to tag transactions with their sales channel for reporting.

Who this is for

US wholesalers and brands already running NetSuite who are adding Walmart Marketplace as a growth channel, and existing Walmart sellers whose current process is spreadsheets and manual re-keying. It suits companies with real SKU complexity — matrix items, kits, multiple fulfillment locations, OneWorld subsidiaries — where a generic mapping is not enough.

How delivery works

1. Scoping call. We walk your NetSuite account and your Walmart setup: item types in use, locations and subsidiaries, how availability should be calculated, which order types you sell, whether WFS is in play, and what your current manual process looks like.

2. Fixed quote. You receive a written scope with the record and field mappings, the scripts to be built, the assumptions, and a fixed price. Nothing is built before you approve it.

3. Build. ECOSIRE develops the SuiteScript 2.1 scripts, custom records, saved searches and role as an SDF project. Typical lead time is two to four weeks depending on scope.

4. Install in your sandbox. The bundle is deployed to your sandbox or a Release Preview account first and tested against your real item data and a Walmart test setup. You review, we adjust.

5. Production. After your sign-off, the same tested artifact is deployed to production with you present, and initial catalogue and inventory syncs are run under supervision.

6. Support. A support window follows go-live for defect fixes and configuration adjustments. You hold the source code and the SDF project throughout — the customization is yours, not licensed back to you.