Delivery schedules

A supplier sometimes ships one product in portions rather than all at once — 12 units as 4 in August, 4 in September, and 4 in October. A delivery schedule lets you record that plan against a single line, on a single purchase order, instead of creating three separate orders or waiting to update dates one shipment at a time.

What a delivery schedule is

Every line on a purchase order already has one delivery — its ordered quantity, against one delivery date. Splitting a line just means giving it more than one delivery: each with its own quantity and its own date, all adding up to the line’s total ordered quantity.

A line stays a single, simple delivery until you deliberately split it. Nothing changes about how an unsplit line behaves.

Splitting a line into deliveries

Two ways to open the editor:

On the line-item table, hover a row and click the Split into deliveries icon next to the edit (pencil) action. It’s hidden once the order reaches Completed, Cancelled, or Received.
From the Schedules view (see Line items & costs → Views and layouts), click the pencil next to any line.

Either entry point opens the line’s edit panel scrolled straight to the Delivery schedule section.

The delivery schedule editor

The Delivery schedule section shows one row per planned delivery:

Column	What it is
Qty	How many units arrive on this delivery.
Delivery date	The date you expect this portion to arrive. Every delivery needs one once there’s more than one on the line.
Status	Scheduled, Partially received, Received, or Cancelled — tracked automatically as receipts come in.
Received	How many units of this delivery have actually arrived so far.

Click + Add delivery to add another row. The new row starts empty and nothing is moved from the other rows — type its quantity and date yourself; the line’s total is simply what the rows add up to. Each row can be removed with its ✕ — except a row that already has received, confirmed, or supplier-rejected units against it; that one is locked to protect activity that already happened. A row that’s only confirmed (nothing received or rejected yet) can still be removed. The section shows a running total, like “12 of 12 scheduled,” so you can see at a glance whether the deliveries add up to what you ordered.

Once a line has more than one delivery, the line’s own Qty ordered field becomes read-only — the deliveries collectively own that number. To change the total, resize the individual deliveries instead. To change the total the old way, merge everything back down to one delivery first.

Saving the section checks each delivery has a valid quantity and a date. If a delivery is missing a date, saving is blocked with Each delivery needs a date — dates are what determines the order deliveries are received in (see Receiving a split line below).

What happens to the line’s own date

An unsplit line shows and uses its own single delivery date, exactly as before. Once you split it:

The line’s own delivery-date field becomes read-only, with a hint “Set per delivery below” — the individual deliveries now own it.
Anywhere the line’s date is shown elsewhere in Logistified — the order list, the detail page header, exports — it displays the earliest still-open delivery’s date. Once August’s portion is received, the line’s shown date automatically becomes September’s.

Receiving a split line

There’s no separate “receive this one delivery” picker. You receive a split line exactly like any other — enter the total quantity that arrived in the receive dialog — and Logistified fills the deliveries earliest date first. Receiving 4 units against a line with August, September, and October deliveries closes out August; receiving 4 more closes out September; and so on.

This is also why every delivery on a split line needs its own date: Logistified sorts undated deliveries first, so a delivery with no date would receive before ones that actually have an earlier date.

Confirmed quantities carry across a split

If a line already has a confirmed quantity when you split it, Logistified doesn’t discard that promise. What happens depends on where the order is in its lifecycle:

Order past the confirmation step (Confirmed, In Progress, On Hold, Partially Received): every delivery counts as confirmed — the ones you resized and any you added. There is no confirmation step left to run, and a delivery that stayed unconfirmed here could never be received, so adding a delivery of 12 to a line confirmed at 18 gives you 30 confirmed, ready to receive.
Order still Sent: the supplier hasn’t answered yet, so Logistified spreads the line’s existing confirmed total across the deliveries, earliest first, and nothing is invented — a line confirmed 10 of 12 that you split into 4/4/4 comes out confirmed 4/4/2, still totalling 10.

Either way, you don’t need to re-confirm anything just because you changed how a line is delivered.

The supplier PDF

When a line has more than one delivery, the printed purchase order shows the breakdown underneath the quantity:

12
4 pcs · Aug 15, 2026
4 pcs · Sep 15, 2026
4 pcs · Oct 15, 2026

The Expected Delivery date in the document header also follows the plan on such an order: it shows the earliest delivery still to come, with a small “3 schedules” badge next to it, rather than the order-level date.

This is controlled by the “Show delivery schedule on split lines” toggle on your PDF export template — on by default. Turn it off if you’d rather the supplier PDF only ever show the total. It only ever adds sub-lines to a line you’ve actually split; a single-delivery line prints exactly as it always has. See Settings → Export templates.

Cancelled deliveries are left off the printed breakdown — they’re not something the supplier needs to plan for.

Viewing schedules on the Schedules tab

Switch the line-item table to its Schedules view (see Line items & costs) to see every line’s deliveries listed as sub-rows, each with its own quantity, requested date, expected date, lead time, and fulfillment mode. Hovering the quantity in this view also shows the requested date for each delivery.

Things to know

“Split Delivery Date” is a different, unrelated setting. The Split delivery date preference only relabels the delivery-date column on the PO list (showing “Requested” / “Expected” / “Estimated” instead of the generic label) — it has nothing to do with splitting a line into multiple deliveries. That naming collision is exactly why this feature is worded “Split into deliveries” in the app.
A bulk file update skips dates on a split line. Update lines from a file can’t tell a single spreadsheet cell which of several deliveries it means, so it skips that cell with a note pointing you to the order page.
Every edit is logged. Adding, resizing, moving, or removing a delivery shows up in the order’s activity log with the before-and-after quantity and date, so you (and anyone else on the order) can see exactly what changed and when.
Deliveries survive a merge. Moving or merging lines between purchase orders preserves their deliveries — see Lifecycle & statuses → Merging POs.
You can’t create a purchase order with a plan already split. Split a line after the order exists, from the line-item table.
Stocky-imported and already-received orders are locked, like everything else about those orders — there’s no plan to edit.