Configuration¶
Every later workflow - quoting, booking, container execution, invoicing - reads master data that must exist first: who can see which shipments, which carriers and ports are valid, which products represent freight and local charges. Setting this up in the wrong order, or skipping a step, surfaces as a missing option or a wrong price much later, when it is harder to trace back to the cause.
By task¶
Task |
When to use |
Article |
|---|---|---|
Decide who can see and edit which shipments |
Before granting access to a new user working on shipments. |
|
Turn on the freight features you plan to use |
Before any other configuration step, right after installing the module. |
|
Confirm the order to enter master data |
Before the first shipment, to avoid a step that depends on data you have not created yet. |
|
Register carriers, agents, ports, airports, and border crossings |
Before booking any shipment on a lane you have not used before. |
Set up carriers, agents, ports, airports and border crossings |
Register HS codes, dangerous goods, cargo types, and Incoterms |
Before quoting or declaring cargo that uses a code not yet in the system. |
Tip
Quick checkpoint: if a field you expect on a shipment, booking, or quotation is missing or empty, check that the matching master data above has been created and activated before assuming it is a product defect.