What it writes

The split of a purchase order moves through four states, and three acts move it. The plan is read, never written: the order's Where it goes section works it out every time it is read, and nothing is stored.

Record the split stores the plan as placements, one per line per warehouse, on record as the recommendation as read. Recorded, it is the split everyone else sees and the one the next two acts fire against. The section types no quantity, so a split recorded there is never an override of the recommendation. It moves no stock and no money.

Call off asks for the units at the warehouses you tick and marks their placements called. Nothing is held back and no availability moves. Whatever stays planned is returned as units still at the supplier: money on order with no warehouse and no month, never spread across cells to tie.

Record receipt says the goods have landed at the ticked warehouses and marks their placements received, whether they were called off first or not. It is the only act in the product that can arm a channel earmark, holding stock for the channel it was placed for; an armed earmark moves on-hand, cover and what Tightly reorders. Arming is off by default for every tenant, so the receipt works out the earmarks and reports them as worked out and not armed.

Split a purchase across dated deliveries

On a commitment, Allocate by delivery saves editable placements against the purchase order's existing deliveries. Choose the product and dated delivery, destination, whole units and optional channel.

The recorded quantity must fit the delivery and the remaining purchase order quantity. For linked placements, call-off and receipt name the delivery as well as the destinations. A receipt cannot exceed that delivery's actual received units, including receipts already recorded for other destinations. A linked delivery cannot be deleted while its allocation is still in use; resolve the allocation first. Existing placements without a delivery link keep their existing workflow.

Who may press it

A writing seat, in the order's Where it goes section. On Pro an order stamped to a commitment is split on that commitment's Allocation wall instead, and the section is absent from the order. A read-only seat reads the split and presses nothing; the disabled button says needs write access beside it. The section performs all three; none is on Ask Tightly's allowlist, so Ask can explain a split and never records, calls off or receives one. One act runs at a time; the others wait while it is in flight.

What you see

Record the split is the section's one button; Call off and Record receipt sit in the menu beside it, More acts on this order. Each opens a drawer with its consequence, one button, and its answer. Record the split says what it would record against what is on the order, all of the order's units or the placed units of the total when some have nowhere to go, then:

It becomes the split everyone reads.

Call off, over a table of the warehouses the split sends to with ticks, every one ticked meaning every warehouse:

Asks for the units at the ticked warehouses.

Nothing is held back or moved.

Record receipt, over the same table:

The goods have landed at the ticked warehouses.

Channel earmarks arm and stock moves with it.

Call off and Record receipt show the number of warehouses on their buttons. The result names the placements changed, units still at the supplier, earmarks and stock updates. A zero result is stated. Units without a destination remain visible. The receipt stays below the section after closing the drawer, until dismissed.

What to do

There is no fourth act that undoes these three. Recording the split again replaces only the placements still planned, with the recommendation as it now reads. A call-off and a receipt are statements about goods and stand: re-recording never rewrites them. What actually landed is recorded on the order under Deliveries. None of the three moves money.

Refusals you may read

A button with nothing to act on is disabled with its reason in ink beside it, on the section's head before the drawer opens and in the drawer before the press:

No unit has a destination.

No warehouse is ticked.

A refusal from the server is shown in its own words. An order with no products on it:

That purchase order has no products on it to split.

On the Pro Allocation wall, which names its commitment, an order re-stamped to another commitment since the page was opened answers a 409 in the server's own words, asking you to reopen it from the commitment's own order list; the act did not run. The order's section names no commitment, so it cannot arise there. An order too wide to split has no plan to read, so the section says its split could not be read and no act can be pressed. A refusal with no sentence of its own reads one per cause. A write whose outcome is unknown reads:

The allocation change could not be confirmed. Review the saved allocation before making another change.

An identical act already on its way is not sent twice:

The same change is already being saved, so it was not sent again.