Contents7 sections ↓
Why multichannel product feeds break on NetSuite
Selling on Amazon, Walmart, eBay, Google Shopping, and your own SuiteCommerce site sounds like growth strategy until you're managing six different versions of the same product catalog. Each channel wants a slightly different feed format. Each channel has different category taxonomies. Each channel needs near-real-time inventory updates or you start overselling.
NetSuite is the source of truth for items, pricing, and inventory. GoDataFeed is the multichannel feed orchestrator — it pulls from NetSuite, transforms per-channel, and pushes optimized feeds to 200+ marketplaces and ad platforms. The integration sounds simple. In practice, what breaks is:
- Inventory drift: Marketplaces show 5 in stock when NetSuite says 0. Customer orders. You can't ship. You eat the cancellation fee and the listing penalty.
- Variation matching: SKU child items in NetSuite don't map cleanly to Amazon's variation theme. Listings get rejected or merged incorrectly.
- Bundle/kit logic: NetSuite kits have member items. Marketplaces want a single SKU with a single price. Mapping requires real business logic.
- Currency and multi-country: Selling on Amazon.com, Amazon.ca, and Amazon.com.mx from one NetSuite OneWorld instance needs per-market pricing and tax handling.
This page covers how to do the GoDataFeed + NetSuite integration so it actually works for a multichannel operation, not just for a demo.
What flows where
| Data | NetSuite → GoDataFeed | GoDataFeed → Channels | Direction |
|---|---|---|---|
| Item master (title, description, images) | Hourly or real-time | Per channel mapping | One-way out |
| Pricing | Real-time on item save | Channel-specific markup applied | One-way out |
| Inventory levels | 5-min near real-time | Pushed to all channels | One-way out |
| Variations (matrix items) | Item structure synced | Mapped to Amazon variation themes | One-way out |
| Kits/bundles | Member items + bundle price | Single bundle SKU per channel | One-way out |
| Orders from channels | — | Channel → GoDataFeed → NetSuite | One-way in |
| Order shipment status | NetSuite Item Fulfillment | Pushed back to channel | One-way out |
The implementation pattern
1. Item attribute mapping (the boring critical piece)
NetSuite item records have ~50 fields. Marketplaces want 20-30 channel-specific fields. Mapping is where most integrations fail: someone maps "description" to Amazon's bullet points and ends up with a wall of HTML in a listing that gets rejected.
We define the mapping per channel:
- Title → Title (length capped per channel: Amazon 200 char, Google 150)
- Description → Long description (HTML stripped or kept depending on channel)
- Bullets → Custom item record field with marketing copy, channel-specific
- Category → Channel taxonomy node (Google product category, Amazon browse node)
- Brand → Manufacturer or brand custom field
- GTIN/UPC/EAN → Item barcode field (required for most marketplaces)
- Images → Item image URLs, ordered, optimized (some channels reject images under 500px)
- Attributes → Item record custom fields (color, size, material, etc.)
2. Inventory sync: the timing problem
Amazon will penalize sellers who show in-stock for items they can't ship. GoDataFeed pulls inventory from NetSuite, but the lag matters:
- NetSuite → GoDataFeed: 5-minute polling for inventory levels (or real-time webhook on inventory change)
- GoDataFeed → channels: each channel has its own update frequency (Amazon 15 min, Walmart 30 min, eBay 15 min, Google Shopping 24h)
Total worst case: a sale on SuiteCommerce can drain inventory and Amazon won't reflect it for 30+ minutes. Most clients are fine with that. Companies running tight inventory (high-velocity SKUs with under 10 on-hand) need real-time webhook firing instead of polling — we build that.
3. Bundles and kits
NetSuite kits are a parent SKU made of member items. Marketplaces want a single SKU with a single price. The mapping:
- Kit SKU → channel listing SKU
- Sum of member item prices (or kit's override price) → channel price
- Min available across member items → channel inventory level
The last point is critical. A kit with 5 member items shows available inventory = min(member items). If one member item has 2 in stock, the kit has 2 in stock. We build this calculation in SuiteScript and feed the result to GoDataFeed.
4. Multi-currency and multi-marketplace
Selling on Amazon.com (USD), Amazon.ca (CAD), and Amazon.com.mx (MXN) from one NetSuite OneWorld instance: each marketplace gets its own price book based on subsidiary or item pricing schedule. GoDataFeed handles the per-channel routing. We configure NetSuite to expose:
- Base price (USD) for Amazon.com
- CAD price for Amazon.ca (manual override or auto-calculated via FX)
- MXN price for Amazon.com.mx (same approach)
Tax handling stays in the marketplace (Amazon collects sales tax in most US states automatically). NetSuite records the sale at the gross amount.
5. Order routing back into NetSuite
Channel orders flow back through GoDataFeed → NetSuite as Sales Orders:
- Channel maps to NetSuite customer record ("Amazon Customers", "Walmart Customers")
- Order line items match by SKU
- Channel-specific custom fields capture order ID, channel commission, shipping method
- NetSuite fulfills, ships, and the tracking number flows back to the channel
Common problems we fix when teams call us
"We oversold 15 units on Amazon last weekend."
Inventory polling is set to 1-hour intervals. For high-velocity SKUs, switch to webhook-fired inventory updates from NetSuite — each item save triggers an immediate GoDataFeed push.
"Amazon keeps rejecting our listings for missing GTINs."
Item records have UPC stored in a custom field, not the standard barcode field. Map it correctly or apply for GTIN exemption with Amazon for private-label items.
"Our prices on Walmart are 5% lower than they should be."
Channel-specific markup isn't being applied. Add a custom item field "Walmart price multiplier" and have the integration apply it before sending the feed.
"Bundle orders from Amazon don't break down into member item revenue in NetSuite."
Sales Order is created with the kit SKU. NetSuite recognizes kits and breaks revenue out automatically — but only if the channel order maps to the kit SKU, not to a synthetic bundle SKU.
"We can't tell which channel is most profitable."
Order classification isn't capturing channel + commission. Add a Sales Order custom field "Channel" populated from GoDataFeed and another field "Channel commission" for Amazon FBA fees / Walmart commission. Then build channel P&L in saved searches.
Implementation timeline and cost
Timeline: 3-6 weeks
- Week 1-2: Discovery, item attribute mapping, channel taxonomy mapping
- Week 2-3: GoDataFeed connector configuration, item feed testing
- Week 3-4: Inventory sync, bundle handling, multi-currency setup
- Week 4-5: Order routing back into NetSuite, fulfillment loop
- Week 5-6: Multi-channel listing review, go-live, monitoring
Cost: $15,000-$40,000
- Single-channel (just Google Shopping) with basic catalog: $15K-$20K
- 3-channel (Amazon + Walmart + Google) with variations and bundles: $25K-$32K
- 5+ channels with multi-currency and complex item logic: $35K-$40K
Ongoing: $400-$1,000/month for channel monitoring, listing health, and category mapping updates.
When this integration is worth doing
Worth it if:
- You sell on 2+ external channels beyond your own SuiteCommerce site
- Your catalog has 500+ active SKUs
- You're running inventory tight enough that oversell risk is real
- You want NetSuite as single source of truth (not channel-specific item maintenance)
Skip if:
- You only sell on your own site (no multichannel)
- Catalog is under 100 SKUs (manual channel uploads are cheaper)
- You're testing a new channel (start manual, automate once revenue justifies)
What clients ask before signing
Related
- NetSuite SuiteCommerce services — broader ecommerce + ERP scope
- Shopify + NetSuite integration — alternative if you're consolidating on Shopify
- SuiteCommerce performance optimization — keep your own SuiteCommerce site competitive
Need GoDataFeed + NetSuite?
Tell us about your setup — typical GoDataFeed integrations go live in 2-6 weeks.
Get StartedKey Capabilities
- Multichannel feeds
- Inventory sync
- Pricing automation
- Bundle support



