The question this page answers
Which moves between my own warehouses are drafted or in flight, and which moves does Tightly propose because one warehouse will run short before it can be restocked while another holds more than it needs?
What you see
Transfer orders has two views under one head: Orders, and Proposed moves. The old address for proposed moves lands on the second view; there is no separate page. The head carries Stock by location and Draft transfers.
In the Orders view a row of figures counts the transfer orders On the book, and, when Tightly has proposed moves, how many Proposed moves and the Sales at risk they would protect. The basis line reads Units · warehouse to warehouse. The columns are Transfer, From, To, Created, Expected, Status and Units. A drafted transfer's Expected reads Agreed on confirmation; a transfer behind its date reads its day with the word late and carries the attention dot. Absences are words: No source, No date. Completed transfers stay out of the table until you ask for them.
In the Proposed moves view the figures read Moves, Units to move and, where the engine could not assess some variant and warehouse pairs, Pairs not assessed, with how many had no stock count and how many no forecast. A chart gathers the sales at risk by the warehouse each move would go to. The basis line reads Units · retail · {n} days, the served cover horizon, and the as-of names when the engine ranked.
The columns are Product, Move, Units, Sales at risk, Cover at destination, Cover at source and Spare at source; on a narrow screen the source columns fold away first. Move names the two warehouses, with the engine's own reason on hover, and under it the transit: a number of days, with estimated where it was not declared, different countries where the move crosses a border, and timing uncertain where both are true. Estimated transit comes from a rule on the two countries, never from your supplier lead time. Sales at risk reads No retail price on hover where the variant has none. Cover reads before and after the move; a bound prints as the horizon with a plus. A destination whose cover is zero now carries the hover word Out of stock now. The table is in the engine's rank order, and the footer counts the moves shown. Filters are location, variant, location type and cluster, which is also how you obey the scope refusal below.
In the retailer chair this page is Store transfers.
If the source-stock check confirms that nothing was drafted, Review latest refreshes the recommendation before you try again. An unconfirmed create still requires checking the transfer orders; refreshing does not make that uncertain write safe to repeat.
What to do
Review transfer, on a proposed row, opens a review of that one move with its expected date set from the transit days. The review shows the recommendation’s as-of date, cover horizon and review period. Create draft saves one draft transfer order; nothing ships until it is confirmed. The result reads Draft saved with the transfer’s name and offers Open draft. The review keeps the evidence used for that draft when the recommendation list refreshes.
If recommendation evidence is unavailable or has changed, choose Review latest. It refreshes the matching recommendation so you can review its latest units and evidence before choosing Create draft. If that recommendation is no longer in the refreshed list, the review closes and returns you to the list. A failed refresh keeps the review available to try again. An unconfirmed draft keeps Check transfer orders instead of offering another creation attempt.
Draft transfers, in the head, opens a three-step drawer: choose variants, set the routes with units from each source, review. The consequence line before the button says it creates draft transfer orders from the available units and that nothing ships until each is confirmed. From a proposed move the variants arrive sized and the first step is skipped, and units a proposal leaves uncovered can go to the Bench.
From an order row's menu: Open and Duplicate; Cancel on any transfer not yet delivered, completed or cancelled; Delete on a draft. Each asks first. A read-only seat sees Review transfer disabled with the words needs write access; the server refuses its other writes.
Refusals are the server's own sentences, in place. A draft that asks for more than a warehouse holds:
{warehouse} holds {available} available units of {variant}; this transfer asks for {asked}. Nothing was drafted.
A proposed-moves scope too wide to rank:
This scope covers {pairs} variant-location pairs, over the {limit} a single request can rank. Filter by location or variant and try again.
When it is empty or failed
The transfer book could not be read.
The orders read failed.
No transfer orders yet.
The book is empty; the door is Draft transfers.
Nothing to move between warehouses.
The engine ranked and found nothing worth moving. When the ranking read fails, the page shows the server's sentence where it gave one and offers Try again, and never prints the empty sentence over a failed read.