v1.029

Receivings now carry a Movement Reference Number (MRN).
An MRN identifies the customs declaration a shipment was cleared under. ShipMonk now requires one to be recorded against shipments arriving at its United Kingdom warehouses before receiving can start. This release adds an optional mrn field to the Create or Update Receiving request and exposes it on all receiving reads. The change is fully backward-compatible — existing integrations keep working unchanged.

🚀 New Endpoints

None

🛠 Schema & Property Updates

• Create or Update Receiving — new optional request property mrn (string|null) - Movement Reference Number of the customs declaration: 18 characters made of a 2-digit year, a 2-letter country code and 14 alphanumeric characters. The grouping spaces printed on customs documents are accepted and stripped, and lowercase letters are canonicalized to uppercase, so the value as printed can be sent verbatim. On update, null or an omitted value leaves the stored MRN unchanged — the MRN cannot be cleared through this API.
• Get Receiving, Retrieve List of Receivings, Create or Update Receiving (response) — new response property mrn (string|null) - the Movement Reference Number stored on the receiving, or null if none has been provided yet.

📖 Documentation & Constraints Changes

• UK-destined receivings must have an MRN on file before receiving can start at the warehouse. The MRN can be supplied through this API at creation or later, or entered in the ShipMonk app. Receivings destined to non-UK warehouses are unaffected.
• An MRN is only accepted on receivings that require one — sending it for other receivings (e.g. non-UK destinations) is rejected with a validation error.

All changes are additive and fully backward-compatible.