Page layouts — customizing what each screen shows

Every record page in Linbis — quotes, shipments, shipping orders, warehouse receipts and releases — can be rearranged to match how your team actually works. Move the cards you use to the top, hide the fields you never fill in, rename a label to your own wording, and save the result as a layout you can switch back to.

Nothing you do here changes the data. A layout decides what you see; the record keeps every value it had.

Making a change

Open any record and choose Customize this page. The page stays exactly where it is — you edit it in place, on the real record, not in a preview.

While you are editing you can:

• Move a card — drag it, or use the arrow buttons on its edit bar.
• Hide a card or a field — click the eye. Hidden items drop into a tray so you can bring them back.
• Rename a field — click the pencil and type the wording your team uses.
• Change the column count — one, two or three columns.
• Switch between tabs and one page — one page stacks every section with a jump bar at the top.

Undo steps back through your changes, and Cancel puts the page back exactly as it was. Nothing is saved until you choose Save.

Fields that refuse to hide

Some fields cannot be hidden. Customs and compliance fields — entry number, bond number, FIRMS code, in-bond number, AMS status on air and ocean imports — stay on screen whatever layout you build, because a shipment record has to show them.

When you try to hide one, the editor tells you why rather than letting you save a layout that would be rejected. The same applies to a card: if a card holds one of these fields, it cannot be hidden either, since hiding a card hides everything inside it.

Saving: just for you, or for everyone

When you save, you choose:

Just for me — the layout lands under a name you pick, and only your screens change. Save as many as you like and switch between them from the layout menu. Useful when the same screen serves different jobs: a customs-focused layout and a booking-focused one, for example.

Publish to the company — available if you have the publisher permission. This becomes the company screen: the layout every colleague sees unless they have chosen one of their own. Company screens keep a version history, so you can look back at what changed and restore an earlier version.

If you edit a layout that someone else published, saving makes your own copy rather than changing theirs. The sheet says so before you confirm.

Saving under a name that already exists replaces that layout, and personal layouts keep no history. Linbis warns you and asks you to confirm before that happens — read the name in the warning before ticking Replace it.

Creating a new record

The creation form uses the same layout as the record page, so a quote you create shows the fields your quote layout shows. Charges and commodities are the exception: they attach to a saved record, so they only appear once the record exists.

The Freight Desk rail

The panel beside an email on Freight Desk can be customized too, and it is remembered per email type — a quote request and an arrival notice each keep their own arrangement.

On a quote request, you can also choose which of the extracted fields appear. Teams that quote several services often need a different set for each: an FCL import quote asks for different information than an air quote. Build one layout per quote type, name it, and pick it when you read the email.

Two things hold whatever you choose:

• Fields needed to price a quote always show. Customer, mode, operation, origin, destination, incoterm, weight and volume stay on screen, so a layout can never hide the reason a quote is not ready to price.
• Nothing the agent read is thrown away. Fields your layout leaves out are still saved with the quote. Any that carry a value appear under Also found in this email, with the value, so you can check them without adding them back.

Starting over

Set to default returns the screen to the Linbis standard arrangement. If your company has published a company screen, you go back to that instead.