Delivery notifications
Overview
A delivery notification is the supplier's announcement: what is coming, when, in which parcel. The supplier reports it through the API, or it is created by hand.
The benefit shows at the loading dock. Without a notification, goods receipt means: open the parcel, find the delivery note, find the order, reconcile. With one it means: scan — and the expected lines are there.
Three states: announced, booked in, discarded.
Core tasks
Scan. The search field accepts a parcel code or notification number. If no notification matches, the application says so, quoting the scanned code — not a silent nothing.
Book in. Booking in creates the goods receipt for the corresponding purchase order.
Keep the overview. The list carries notification number, status and the assignment.
Fields in detail
The What it does column answers what changes in the system — not what the field is called. The grey name behind the label is the API field: the same thing runs under that name through automation, import and AI tools.
A delivery notification is the supplier's announcement: what arrives when — ahead of the goods, not with them.
| Field | Required | Values / format | What it does |
|---|---|---|---|
Number number | no | text, max. 60 characters | The supplier's number for this announcement. It ties notification, delivery note and invoice together. |
Order goodsOrderUlid | yes | an existing order | What the announcement belongs to. Only then does the system know which items are expected. |
Expected on expectedAt | no | date | The announced delivery date. It replaces the estimate from the lead time — planning becomes dependable instead of guessed. |
Items items | no | articles with quantity | What is actually coming. If it differs from the order you see that before goods receipt and not while unpacking. |
Packages packages | no | list of packages | How the delivery is split, with tracking numbers. The basis for receiving it in the warehouse. |
Note note | no | text | A note on the announcement. |
Brand brandId | no | one of your brands | Which brand the delivery is expected for. |
Settings & permissions
- Module
module.purchasing. - Permission
purchasing.receipt.recordfor booking in. - A notification is not a posting. Stock changes only on release of the goods receipt, see
- Notifications can arrive through the API — then they appear without any action.
FAQ & troubleshooting
No notification matches the scanned code. The message names the code. Check whether the supplier announced it — or create the notification by hand.
The notification is booked in but stock is unchanged. As expected: only releasing the goods receipt posts to the warehouse.
A notification matches no purchase order. Then the reference is missing. A notification without an order cannot sensibly be booked in.
The supplier announces nothing. Then you work without notifications, through the goods receipt on the purchase order — that route still works.