The vessel's stock is the single source of truth for on-board quantities. The office therefore cannot change an on-board stock quantity directly — a change made ashore would be overwritten by the next data transfer, and the correction would quietly disappear.

Instead, every office action that would change an on-board quantity becomes a **stock correction request** that goes to the vessel. The crew approves or rejects it, and only an approved request actually books the quantity.

**In short: the office proposes, the vessel approves, then the stock is booked.**

## What the office sees

* **The quantity field is read-only** — in the article view as well as in batch editing, with a note that the quantity is maintained on board.
* **Stock actions still work**, but as a request. The action is written to the transfer history straight away, so it is traceable, while the on-board quantity stays as it was.
* **The quantity does not update immediately.** A figure that looks unchanged right after an office action usually means the request is still waiting for approval on board. This is expected behaviour, not a fault.

## What the vessel does

The list **Stock Corrections from Office** in the Stock module shows all pending requests. For each one the crew can:

* **Approve** — the quantity is booked on board. The history entry was already written by the office, so nothing is counted twice.
* **Reject** — the request is declined with a reason and the stock stays as it is.

Both need the permission **Approve Stock Corrections (on board)**. Without it the buttons stay disabled.

Pending requests also appear on the on-board **User Dashboard** under the entry *Stock Corrections from Office*, listing article, current quantity, change, new quantity and who requested it when, with a link that opens the confirmation list directly. That way requests are noticed even when nobody opens the Stock module. The entry has to be switched on once per user and is only available on board, and only to users holding the permission above — see [User Dashboard](/General/Global-Features/User-Dashboard/).

## Which office actions create a request

Anything done ashore that changes the quantity of an on-board article:

* **receiving goods** on a purchase order, and correcting a received quantity afterwards,
* **recording consumption** — from maintenance jobs, stevedore damage repairs and ship defect repairs,
* **stock exception reports**.

Components carry no stock quantity and catalogue items such as lube oil follow their own logic; neither goes through this mechanism.

## What is no longer possible

A **free-hand correction without a business context** — not tied to a goods receipt or a consumption — is no longer offered. Such a change could not be kept stable against the data transfer in the first place. Every correction now follows a real business action.

## Setting it up

The permission **Approve Stock Corrections (on board)** has to be granted to those on-board roles that may approve corrections. Without anyone holding it, requests arrive but cannot be confirmed.

*[PO]: Purchase Order  
*[AZA]: local folder
*[(PO]: Purchase Order  
*[RQ]: Requisition  
*[(RQ]: Requisition  
*[RfQ]: Request for Quotation  
*[(RfQ]: Request for Quotation  
*[SO]: Service Order  
*[(SO]: Service Order  
*[SQ]: Service Requisition  
*[(SQ]: Service Requisition  
*[SRfQ]: Service Request for Quotation  
*[OoB]: Open on Board  
*[(OoB]: Open on Board 
*[ART]: Average Running Time (operation hours per day) 
*[MC]: Master Contract
*[ADS]: Advantage Database Server (database engine used in previous versions of the ZeeBORN software)
*[.replic]: file extension for replication files (aka data transfer files)