Inventory & Orders

Stock you can promise. Orders you can see.

Keep on-hand, reserved and available-to-promise distinct, then bring order exceptions into a worklist operators can act on.

The record

Three numbers, kept apart on purpose.

On-hand is what is on the shelf. Reserved is what is already promised. Available-to-promise is the only one a channel should ever be told about — and the only one worth arguing over at month end.

Availability · reservations · worklist
AvailabilitySKU CFT-6C-INOX
LocationOn handReservedAvailable
Marbella · main1 240861 154
Bucharest · 3PL512144368
Warsaw · overflow96096
Worklist
  • ORD-2026-004182HeldReservation expired before payment cleared
  • ORD-2026-004190ExceptionLine SKU not in the product master
On-hand, reserved and available-to-promise, per location — three numbers kept apart.

The arithmetic

Available to promise, written out.

LocationOn handReservedAvailableWarehouse ES340− 62= 278Warehouse RO118− 40= 783PL DE56− 9= 47Available to promise403Channelone number
Available-to-promise is on-hand minus reserved, per location, and the channel is only ever told the total.

Operational workflow

Availability and orders on the same records.

Availability and reservations

core workflow

On-hand per location, reserved, available-to-promise — three numbers, kept apart, because collapsing them into one is what oversells a listing. A reservation is held while an order is decided and released with the order's state, rather than by a nightly job.

Order intake and worklists

core workflow

Orders land in a queue. Anything that cannot proceed becomes a worklist item with an owner, a note and a resolution, and a command centre shows what is stuck and why — which is the difference between an operations tool and a dashboard.

Fulfilment status

Order state is visible end to end, from intake to dispatch. Couriers are an integration class here, in the same directory as the marketplaces.

Versus the alternatives

Everything else knows about one place.

Where stock lives today, and what each option can see.
Shop's native stockA marketplace's inventorySpreadsheetWMSZuduno
Sees every channelnonomanuallynoyes
Reservations while an order is decidedpartialnonowarehouse-sideyes
Per-location availabilityrarelynomanuallyyesyes
Joined to the product masterone shopone marketplacenonoyes
Stays current without a personyes, one channelyes, one channelnoyesyes, across channels
Where stock lives today, and what each option can see.

FAQ

Questions people actually ask

Does it sync stock to Amazon, eMAG or Kaufland today?

Integration scope is assessed channel by channel. Zuduno separates source imports, read-only data flow and controlled write-back so each step can be validated before it affects a live channel.

Multiple warehouses?

Locations are first-class. On-hand, reserved and available-to-promise are computed per location and rolled up, so a 3PL and your own shelf are the same kind of thing to the system.

Does it generate AWBs and labels?

Couriers are an integration class — DPD, GLS, DHL, InPost, Sameday, Fan Courier and regional 3PLs are in the integrations directory.

Does it replace my WMS?

No, and it should not. A WMS is warehouse-side: bins, picking, packing. Zuduno is channel-side, and it reads what the warehouse says rather than telling it how to work.

What changes for you

What one availability number changes.

  1. Stock you have promised to somebody else stops being counted as stock you can sell.

    Operations and customer service

    Availability, reservations and order intake

  2. An order from any channel lands in the same worklist, in the same shape, whoever it came from.

    Order desk

    Availability, reservations and order intake

Review your availability and order flow.

Bring a representative product and order export so the evaluation reflects the systems and exceptions your team handles.