Open Nexus
Booking Notes Module

Errors and Warnings

What blocks submission and what only asks for a check.

Errors and Warnings

The form distinguishes between errors, which block submission, and warnings, which ask for a value to be checked.

ErrorsWarnings
EffectBlock submissionDo not block anything
MeaningA rule has been brokenA value looks unlikely
ResponseFix itCheck it, then continue if correct

Warnings exist because the system cannot tell an unusual booking from a misread document. It flags what looks odd and leaves the decision to the person completing the form.

Errors that block submission

Missing required fields

Fields marked with a red asterisk must be filled in before submission. They are enforced at submission, not during entry, so a booking note can be saved incomplete.

Check collapsed sections. A missing field in a collapsed Cargo entry stays invisible until the section is expanded.

Package Type and Package Amount

Validated as a pair. Give both or neither:

EnteredResult
Package Type and Package Amount greater than 0Valid
Package Type, no Package Amount or amount of 0Blocked
Package Amount, no Package TypeBlocked
NeitherValid

Dangerous goods fields

Setting Dangerous Goods to Yes on a cargo entry makes IMDG Class and UN Number mandatory on that entry. Packaging Group stays optional. See Dangerous Goods.

Warnings that ask for a check

Cargo Ready Date looks wrong

The Cargo Ready Date is checked both when extracted from a source and when entered by hand. A warning appears if the date is:

  • in the past, or
  • more than six months in the future.

The field is flagged with a message along the lines of CRD not plausible – please verify. Where the booking note came from a document, the corresponding value is highlighted in the source preview, showing exactly what was read.

The date can be confirmed and submission continued. Before that, the source should be checked. An implausible CRD is far more often a misread date format than a genuinely unusual booking — a document written in one date convention and read in another produces exactly this.

Latest Shipping Date in the past

A warning appears if the Latest Shipping Date is in the past, whether extracted or entered by hand. It is informational and does not block saving or submitting.

The system never fills in a default date to resolve one of these warnings, and never changes a date that has been entered.

Getting past a blocked submission

  1. Select Submit and read the fields the form has flagged.
  2. Expand every section, including collapsed ones.
  3. Check each cargo entry, particularly any marked as dangerous goods.
  4. Fix the errors.
  5. Review any warnings. Confirm the values or correct them.
  6. Submit again.

If a required value genuinely is not available — a weight not yet confirmed, a dangerous goods declaration not yet received — use Save & Exit. The booking note stays in Draft and editable until the missing value is available. See How to Submit a Booking Note.

Copyright © 2026