Multichannel Inventory and Order Hub

Selling on four or more channels with a point connector behind each one produces a predictable set of problems. Every connector holds its own idea of how many units are available, and each publishes that number on its own schedule, so the same physical unit is sold twice and somebody spends Monday morning writing apology emails and cancelling orders. Bundles make it worse: a kit sold as a single code on one channel silently consumes components that another channel is still advertising. And at the end of the month the settlement deposit that lands in the bank is net of commission, shipping and advertising deductions, so it matches no invoice in Zoho Books and gets parked in a suspense account until someone reconciles it by hand.

None of this is a limitation of Zoho Inventory. It is the absence of a layer above the connectors that owns one number and decides who gets to sell it. That layer is what this engagement builds.

This is a build-to-order project, not a downloadable app. Nothing is pre-packaged and there is no instant install. ECOSIRE studies your actual channels, item structure, warehouses and fee schedules, builds the hub for that reality, installs it in a test organization first, runs it in parallel with your current setup until the numbers agree, and only then lets it take control of published availability. Typical lead time is two to four weeks from an accepted quote.

What ECOSIRE builds

One stock pool, per-channel buffers

The authoritative quantity lives once, in Zoho Inventory Items across your Warehouses. Every channel reads an available-to-sell figure the hub calculates rather than a raw on-hand count: physical stock, minus open reservations, minus committed picks, minus the buffer for that channel. Buffers are rules, not a single global percentage. You can hold back units on a fast-moving line where a stockout is expensive, publish a long-tail line at full depth, and set different behaviour per item group, warehouse or channel. Rules are held as configuration you can edit, not as constants buried in code.

Order intake and normalisation

Orders arrive through Zoho Inventory and Zoho Books webhooks where the channel supports them, and through scheduled Deluge fetches where it does not. Everything is normalised into one internal order shape — buyer identity, ship-to, line items, channel-specific codes, taxes, promised delivery date — before a single record is created downstream. Normalising first is what makes the rest of the hub channel-agnostic: adding a fifth channel later means writing one adapter, not touching allocation, returns or reconciliation logic.

Bundle and kit explosion

Where you sell kits, the hub explodes Composite Items at intake, so the reservation is taken against component items rather than against a phantom parent quantity. A shared component consumed by three different bundles is decremented once per unit sold, across all of them, which removes the most common cause of a multichannel oversell that no single connector can see.

Reservation and allocation

Stock is reserved at order acknowledgement, not at pick time. That single change closes the window in which two channels can both sell the last unit. Allocation rules then pick the fulfilling warehouse by destination, channel priority and available depth, creating the Zoho Inventory Sales Order, Package and Shipment against the chosen location. When the allocator finds the stock is in the wrong place, it raises a Transfer Order suggestion and takes reorder levels and incoming Purchase Order quantities into account before recommending it.

Returns, refunds and cancellations

Cancellations release the reservation immediately so the unit goes back on sale rather than sitting invisible until someone notices. Returns are processed end to end as Sales Returns and Credit Notes in Zoho Inventory and Zoho Books, with stock returned to the correct warehouse or routed to a quarantine location where inspection is required. Refund values flow through to the accounts so the channel margin figure stays honest.

Payout reconciliation into Zoho Books

When a settlement arrives, the hub matches its lines to the underlying invoices, posts commission, shipping and advertising deductions as Expenses against the accounts you nominate, and records the net figure as a Zoho Books Deposit that clears cleanly in bank reconciliation. The result is that the channel deposit on the bank statement matches a real transaction rather than becoming a monthly manual exercise, and margin after fees becomes a reportable number instead of an estimate.

Control tower and exception console

A control application in Zoho Creator gives operations one screen: current availability by item and channel, active buffers, open reservations, unfulfilled ageing, and an exception queue. Every failed or held record appears there with the API error, the payload that caused it and a retry action once the underlying master data is fixed. A widget built with Zoho's extension framework surfaces the same per-channel availability inside Zoho Inventory and Zoho CRM record pages, so nobody has to switch applications to answer a stock question. Zoho Analytics dashboards cover oversell near-misses, channel margin after fees and stock cover by warehouse.

Who this is for

Sellers running four or more channels on one inventory, especially where kits or bundles are part of the range, where more than one warehouse or a third-party fulfilment location is involved, or where channel deductions have made true margin unclear. It suits an operations lead who currently reconciles stock across systems manually, and a finance team that has stopped trusting the channel revenue figure because the deposits never tie.

How delivery works

Scoping call. We map your channels, item and bundle structure, warehouses, current connectors, order volume shape and fee schedules, and confirm which Zoho plan features the design depends on.

Fixed quote. A written scope naming the channels, the rule types, the reconciliation behaviour and a price. No hourly billing, and no build work before you accept.

Build. The Creator control application, Deluge functions, Zoho Flow orchestrations and the embedded widget are built against your real item and channel data.

Install in test. Everything goes into a test organization first and then runs in parallel with your existing setup, calculating availability without publishing it, until its numbers match reality.

Production cutover. The hub takes control of published availability channel by channel rather than all at once, so a problem is contained to one channel.

After go-live

You get a support and tuning window, because buffers are always wrong on day one and need adjusting against real sell-through. You also get an operating runbook and training for the inventory and finance teams. Everything runs inside your own Zoho organization with no licence key and no dependency on us to keep functioning.