Product Messages
Contextual alerts generated by product bricks during pricing calculations, displayed as colour-coded badges in MissionControl and Hub.
Contextual alerts generated by product bricks during pricing calculations, displayed as colour-coded badges in MissionControl and Hub.
Was this article helpful?
Did not find your answer?
Ask Luna, or write to our support team.
Note
Product messages are contextual alerts generated by product bricks during pricing calculations. They inform operators and customers about important conditions, constraints, or requirements related to a transport booking.
When a product is calculated for a transport request, the underlying product bricks can emit messages to communicate relevant information. These messages appear as colour-coded alerts throughout the booking flow and on order details, giving users immediate visibility into conditions that affect their transport.
Key highlights:
info, warning, or error) that determines its visual treatmentOrder and remain visible after bookingEach product message has one of three severity levels, displayed with a corresponding colour:
| Level | Colour | Purpose |
|---|---|---|
info | Blue | General information about the offer or transport conditions |
warning | Yellow | Conditions that may affect the transport but do not prevent booking |
error | Red | Critical issues the user should be aware of |
When multiple messages are present, a badge displays the total count and uses the colour of the highest severity message. Hovering over or tapping the badge reveals the full list of messages.
In Orbit MissionControl, product messages appear in two locations:
In Orbit Hub, product messages appear in two locations:
Order.Product messages are defined within context bricks and feasibility bricks as part of the product configuration. When a product is calculated for a transport, these bricks can include messages in their output to communicate conditions such as route constraints, load limitations, or scheduling notes.
Messages from all bricks of a product are automatically collected, deduplicated, and sorted by severity (errors first, then warnings, then informational messages). For details on configuring bricks to return messages, refer to the Products documentation.
Julia at Orion Industries in London books a next-day delivery through Orbit Hub. During the booking process, she sees a blue info badge on her selected product. Hovering over it reveals the message: "Route includes channel crossing via ferry, transit time may vary." After placing the Order, the same message remains visible on her order details page. Meanwhile, Mohammad, an operator at the logistics company in Berlin, sees the same message on the Order in Orbit MissionControl, along with a yellow warning: "Approaching maximum load weight for this vehicle class." These messages help both parties understand the conditions of the transport without interrupting the booking flow.
No. Product messages are informational only. To prevent a booking, the product's feasibility bricks must return the transport as not feasible. Messages communicate context but do not block the process.
Product messages are displayed in Orbit MissionControl and Orbit Hub. They are not shown in Orbit Cockpit.
Yes. Messages are optional. If no brick returns messages, no badge or indicator is shown.
Yes. Messages are stored on the Order and remain visible on the order details page in both Orbit MissionControl and Orbit Hub.
Duplicate messages with identical content are automatically removed. Each unique message appears only once.