Multichannel Listing & Inventory Hub

The pain

Add a fourth sales channel and the arithmetic turns against you. Each marketplace gets its own connector, its own item mapping, its own idea of what stock is available, and its own overnight sync. Nothing agrees. The same SKU is listed at three prices, a title fix made in NetSuite reaches two channels and not the others, and the moment a large order lands on one marketplace the other three keep selling stock that is already committed. Oversells become cancellations, cancellations become account metrics, and account metrics become suppressed listings.

Meanwhile your NetSuite item record — the thing that should be the master — is not. The real catalog lives in whichever spreadsheet the merchandiser last edited, because no connector was ever built to publish from NetSuite outward.

What ECOSIRE builds

ECOSIRE builds one hub in your NetSuite account rather than a stack of independent connectors. It is delivered as an SDF project / unmanaged bundle you own, built against your item types, your locations and your channel accounts.

One catalog, many channels

NetSuite item records — Inventory Item, Assembly, Matrix parent and child, Kit/Package — remain the master. A channel-listing custom record (customrecord_eco_channel_listing) links each item to each channel it sells on, holding the channel-specific identifier, title, description, category or taxonomy id, price and publication status. Channel-specific overrides live on the listing record, not on the item, so a marketplace that demands a 60-character title does not force you to mangle the title everyone else sees. Matrix items map cleanly: the parent becomes the channel's parent listing and each child SKU becomes a variant with its option values carried across.

Publish and update

A Map/Reduce script builds channel payloads and pushes creates and updates through each marketplace's API. A User Event script on the item record marks a listing dirty when a published field changes, so a price or description edit in NetSuite queues an update rather than waiting for a nightly full sync. Every push writes back the channel's response — accepted, rejected with a reason, pending review — onto the listing record, so a rejected listing is visible in NetSuite instead of silently absent from the marketplace.

Shared available-to-promise

This is the part that stops oversells. The hub computes one ATP figure per item from your NetSuite locations: on hand, less committed, less a safety buffer, optionally less quantity back-ordered, restricted to the locations you designate as sellable for that channel. It then allocates that pool across channels using a strategy you choose during scoping — a percentage split, a fixed cap per channel, a priority order, or simple shared visibility where every channel sees the same number. When an order arrives anywhere, or a Fulfillment or Inventory Adjustment changes stock, the recalculation queues immediately and pushes revised quantities to every affected channel rather than to one.

Order ingestion and writeback

Orders arrive by scheduled pull or by webhook into a RESTlet, are staged on a custom record, then converted into NetSuite Sales Orders with the correct customer, subsidiary, location, shipping method, tax handling and channel-fee line. Staging first means a malformed order never leaves a half-built transaction behind, and a re-delivered webhook is deduplicated on the channel order id. Fulfillments post back to the channel with carrier and tracking number, cancellations and refunds are reflected on both sides, and each order carries its channel and channel order number on custom transaction body fields for reporting.

Operations, not black boxes

A Suitelet console shows, per channel: listings published, listings rejected with reasons, inventory pushes in the last cycle, orders ingested, and any item whose channel state diverges from NetSuite. A SuiteFlow workflow escalates repeated failures. Every API call is logged with its request, response and retry count, because when a marketplace changes a field requirement you need to see what was actually sent.

Multi-subsidiary and multi-location

Under OneWorld each channel account maps to a subsidiary, its own customer defaults, its own item pricing and its own set of fulfilment locations. Custom segments can tag every channel order for margin reporting by channel without polluting your class or department hierarchy.

Who this is for

Sellers listing on four or more channels who are tired of one connector per channel, brands whose merchandising team edits the catalog outside NetSuite because NetSuite cannot publish, and operations teams whose oversell rate is a live risk to their marketplace accounts.

How delivery works

1. Scoping call. We list your channels and their API access, your item structure (matrix, kits, assemblies), your locations, your allocation policy and how orders must land in NetSuite. 2. Fixed quote. A written scope naming every channel in scope, the listing field map per channel, the ATP formula and the allocation strategy, at a fixed price. Adding a channel later is a separately quoted increment. 3. Build. SuiteScript 2.1 Map/Reduce, Scheduled, User Event, RESTlet and Suitelet scripts, plus custom records, custom transaction body fields, custom segments, saved searches and SuiteFlow escalation, assembled as an SDF project. 4. Install in your sandbox. Deployed to sandbox and pointed at each marketplace's sandbox or a small live test set, so you watch real listings publish and real orders land before anything touches production volume. 5. Production. Same bundle deployed to production, then a staged channel-by-channel cutover rather than a big-bang switch. 6. Support window. A defined post-go-live period for defects and marketplace API changes, with all source in your account.

Lead time is typically one working week from signed quote, driven mainly by the number of channels and how different their listing models are from each other.

What we will tell you honestly

Marketplaces differ enormously in what their APIs allow. Some accept full listing creation programmatically; others require category approval, brand registry or manual review before a listing goes live, and no integration can bypass that. During scoping we go channel by channel and tell you which parts are automatable and which will still involve a human in that marketplace's own portal.