Using chartering
What the fixtures page will cover, and what this build actually shows.
Chartering is the desk for an estimate, a fixture, laytime and demurrage, hire, TCE and the voyage result. The catalogue treats a full fixture book as a later product and points at Veson for that desk. Pruva’s port call stays the ship’s visit. It is not rewritten into a worksheet. Selin Demir is the chartering and finance manager in the demo. She has publish on this module. Kaan Erdem has view. The master does not have it.
Dashboard and pages
Fixtures is http://localhost:4400/app/chartering . In this build the page is a placeholder. It names the module and links to integrations. It does not list estimates, fixtures or a voyage result. Integrations is http://localhost:4400/app/integrations/chartering .
The catalogue describes five screens that are not built: open estimates; one estimate that becomes a fixture; a laytime statement; the voyage result with freight, hire, bunkers and the ETS cost read from the emissions ledger; and the port calls on that voyage. None of those screens exist in this build. Migration 12 is reserved.
Workflows
The manifest names no publish action. The placeholder has no buttons, so Selin’s publish level has nothing to press. There is no award, no fixture confirmation and no demurrage invoice. When the module is built, money that leaves the company should follow the same rule as the other modules: a person with publish, never an agent. That rule is not implemented here yet, because there is no action.
Shared records
Bunkers and ETS are reads. Noon owns the fuel. Emissions owns the allowance cost. The port call is the port module’s record. Cargo files and disbursement accounts sit beside the voyage. They are not copied into a chartering worksheet. Finance owns the ledger. A voyage result, if it is added, should not post a second set of journals.
What the demo simulates
There is no fixture, no laytime statement and no TCE. The connectors are mocks. The price-list summary names estimates, fixtures, laytime and a voyage result. Those are the intended scope, not pages you can open.
Integrations
The Baltic Exchange and the Shipfix inbox are mocks. No index is fetched and no chartering mailbox is read. See Connections and the module reference.