The operating problem
A shared warehouse can serve several channels, but the same units cannot be promised twice. Looking only at Amazon coverage can produce a transfer that leaves the direct-to-consumer channel short. Looking only at total network stock hides whether the inventory is physically available at the location that must ship it.
What we built
The planning engine keeps separate positions for Amazon and the central warehouse. It evaluates channel demand, committed receipts, and replenishment alternatives before proposing movement. The operator can distinguish a transfer that can leave now from one that depends on later supply.
An Amazon operating view connects product policy, FBA/FBM classification, stock, inbound quantities, coverage, and size gaps. Canonical SKU mapping keeps fulfillment aliases from appearing as extra products. Transfer and direct-purchase recommendations are exposed with their dates and dependencies, while the warehouse position retains the demand it must serve.
What the work enables
The delivered workflow makes allocation decisions explainable across locations and channels. It shows both the Amazon need and the supply that can support it, rather than presenting every shortage as an immediate transfer. The underlying protection thresholds and commercial policy remain private to the business.
A replenishment recommendation needs a source, a destination, an availability date, and an explicit competing-demand constraint.