Certain operators operate using only bookings, others only packages. Please make sure your ideal workflow is supported by the delivery operator as well.
Before going further into which option to go with, we'll quickly first define bookings and packages.
🚴♂️ Bookings: A booking is a request from a Customer to complete a Service. […] It can include one or multiple Stops. A Stop is a task to be completed at a specific location.
📦 Packages: A package is an individually trackable item that typically has its own properties like size or weight, comes with a scannable label and can be added onto a stop as a pickup or drop-off task.
Although there is some overlap between the two concepts, bookings are generally chosen when the goal is to track direct, express deliveries from one pickup location to the final drop-off location, whereas packages are better suited to track individual, scannable items across multiple legs involving at least one in-between hub.
When it comes down to the integration effort, bookings are easier to get started with due to their relative simplicity compared to packages. Packages, as mentioned above, come with additional properties (size, weight), concepts (scannable label), interaction & tracking flows, pricing, lifecycle, etc. There are all useful when modeling large parcel deliveries, but not always needed for short deliveries.
So while it is possible to model a simple restaurant → customer delivery using packages, where the meal bag is represented as a package within MotionTools, we generally recommend choosing bookings for this particular use case since the focus is on performing an simple express delivery, not on the tracking the meal bag across multiple legs.