# Record delivery Source: https://docs.tightly.io/help/supply/record-delivery Reviewed: 2026-09-26 ## The question this page answers Which of the outstanding lines arrived, how many of each, and does this delivery close the order? ## What you see ::: shot page ::: Record delivery is a page of its own rather than a drawer. It serves purchase orders and transfer orders alike, and its way back is the order it was opened from. The head carries the order's name as the way back and the title, **Record delivery**. The one sentence under it is live and recomputes on every edit. With nothing booked it says how many units are outstanding across how many lines, or, where exceptions on this order wait, how many of them need a decision instead of the line count. Once you enter quantities it says how many units you are booking in and what they are worth, then either that nothing stays outstanding or how many units still do. Under the sentence stands the one button, **Record delivery**, with **Cancel** beside it, which goes back to the order. Before it stands the consequence line: stock moves according to your sync settings once this is saved. Cautions follow it when they are true: a line booking in more than was outstanding, a ticked line left at zero, and a line with no price. Where the order has not shipped, the button is disabled and the sentence beside it names why, for example that the order has not shipped yet and a delivery can only be recorded once it has. The table is one row per line: Product, Variant, SKU, Ordered, Outstanding, Booking in and Unit cost (Received against a cost per case, where the order was placed that way). Outstanding is the reference figure beside the Booking in stepper; typing a quantity ticks the line and seeds it at its Outstanding, the words all of it appear once you change it, and over appears beside a figure above Outstanding. **Tick every outstanding line** does the common case in one press, and toggles to **Untick** once every line is ticked; with a search in force it reads every line shown instead. Lines with nothing outstanding sort last and read 0. The footer sums Outstanding, Booking in and Left. Beside the act, once the order carries lines, stand **Booked in already** (the tranches already recorded, each with its date and units) and a compact bar chart, Outstanding, one bar per line against its Ordered tick. Beneath both, **Exceptions** lists what this order's receipts could not settle on their own: an over or short receipt, an unknown item, an oversell, a return mismatch, a sync disagreement, an unmatched line or an order cancelled after it was sent, each with the server's own sentence. Opening a row offers a resolution and closes with **Back to the delivery**. In the retailer chair the page is named Receive and what lands is a Receipt, read at retail as well as at cost, with a line short of what was outstanding called out on its own. ## What to do 1. Type the quantity that arrived for each line, or press **Tick every outstanding line** to seed every line at its own Outstanding figure. 2. Correct any quantity that differs from what was outstanding. 3. Press **Record delivery**. 4. Open a row in **Exceptions** to put down what it could not settle on its own, choosing a resolution and pressing it. A writing seat presses; a read-only seat can open the page and presses nothing. The write records one instant delivery of the lines with a quantity above zero. It never sets the order's status and never sets an expected date: the order moves to Delivered on its own once every unit is in. After it saves, the head reads what was recorded, on which day, how many units across how many lines and what they are worth, and what stays outstanding on the order; the lines booked stand beneath, with **Back to {order}** and, while anything is outstanding, **Record another delivery**. On the order the tranche stands under Deliveries with the state word Landed. The way back is on the order: a recorded tranche's row menu offers Add products to this delivery and Remove, and removing one marks its products as not delivered. ## When it is empty or failed > This order could not be read. The read failed; **Purchase orders** goes back to the book. > No order lines. An order with no lines reads this. Searching a line reads: > Nothing matches “{search}”. On a completed or cancelled order the head says the order is completed, or cancelled, and no further deliveries can be recorded, and the button is absent. > Delivered quantities can only be added to FULLY SHIPPED purchase orders. The server's own rule, rendered under the button, where the order has not shipped in full. > The delivery was not recorded. Any other write failure. > The deliveries against this order could not be read. Booked in already's own read failed. Exceptions can fail or come up empty too: > The exception queue could not be read. > Nothing on {order} needs a decision. In the retailer chair every sentence here names the receipt.