Proposal stops
An ordered stop on a route proposal, linked to a shipment stop or service visit, with ETA and load.
Fields
The API name is what the API, MCP and the CLI use.
| Name | API name | Type | Required | Description |
|---|---|---|---|---|
| ID | id | Record ID | Yes | |
| Route proposal | logisticsrouteproposalId | Reference | Yes | |
| Sequence | sequence | Whole Number | Yes | Whole number without fractional part. |
| Target kind | targetKind | Constant | Yes | Fixed option from the allowed set for this field. |
| Stop | logisticsshipmentstopId | Reference | ||
| Visit | servicevisitId | Reference | ||
| ETA | datetimeEta | Date and Time | ||
| Distance (km) | distanceKm | Decimal | Yes | Kilometers from the previous stop in the proposal sequence. |
| Load after stop | loadAfterStop | Decimal | Yes | Numeric value stored with decimal precision. |
| Created at | createdAt | Date and Time | Yes |
Relations
Owned records (solid line) are deleted with their owner. Grouped records (dashed line) can exist alone.
| Field | Points to | Kind |
|---|---|---|
Route proposal logisticsrouteproposalId | Route proposals | owned by |
Actions
What you can do with a record. Every action also sends the webhook event logisticsrouteproposalstops.<action>. Reads (find, get, count) work on every table.
| Name | API name | Description | Where |
|---|---|---|---|
| Delete | delete | Delete this proposal stop and the data that belongs with it. This cannot be undone. | App · WebMCP · API · MCP · CLI |