Request to create an order, one or more shipments and optionally tours. Order can be priced automatically or pre-priced and may require payment info to be processed. Shipments are sent in groups: every group that sets a tourCreationStrategy becomes one tour over its own shipments, and a group without a strategy creates its shipments without a tour, so one request can create several tours. A predefinedLayout counts its shipment indexes within its own group; a layout that does not fit its group's shipments is rejected with 400 wherever it is read, which is when the tour is built and when the order is priced with calculate-fare. An order with status requested and pre-priced line items never reads the layout. With priceStrategy calculate-fare every group is priced on its own, laid out by its own strategy, and the order carries the line items of all groups; a request in which the product prices some groups but not all is rejected with 400. So is a request in which a group's line items do not add up with the other groups' prices, such as a discount or a percentage line, because the order keeps one list of line items and such a line applies to the whole list. Set matchShipperAddresses to true to match each stop against the assigned shipper's saved address book. Saved-address references sent on a stop (shipperAddressId, shipperAddressContactId, shipperAddressLoadingPoint) are always checked against the assigned shipper: with matchShipperAddresses true a reference that does not belong to that shipper is rejected with 400, otherwise it is removed and the order is created without it. For an order with status requested the flag applies the reference validation only; the stored shipment requests are not matched when the order is confirmed later. customer and invoiceRecipient may each be linked to a shipper via shipperId (narrowed by shipperTeamId / shipperUserId): the customer's link is the order's shipper assignment and must agree with the shipment groups, the invoice recipient may name a different shipper; a shipper that does not exist in the tenant, or a team or user of another shipper, is rejected with 422. Either block may be omitted when the order has a shipper assignment (a shipperId on a shipment group, its shipments or, for the invoice recipient, the customer): the omitted block is filled from the assigned shipper's master data: name, address and contact details of the shipper team (the one sent, or else the shipper user's team) or, without a team, of the shipper, with missing contact details taken from the shipper user. Without an assignment an omitted block is rejected with 400. A shipment group or its shipments may name the assignment with shipperLookup instead of ids: the shipper, shipper team or shipper user that holds a property value, for example a customer number on the team (see the shipperLookup field for the rules and outcomes). It counts as a shipper assignment for omitted blocks, which are then filled from the team or user found. The order and its shipments store the resolved ids; a lookup that names no active holder, or more than one, is rejected with 422, and one that cannot be answered right now with 503.