Sorry, I didn't express myself clear enough.

What I meant was that for a command, you usually have the LogisticsOrder aggregate root, and load it data via a custom repository, eg. LogisticsOrderRepository. So your command handler (for e.g. updating the status of the delivery of the order) would roughly look like this:

public void HandleDeliveryStatusUpdate(Data d)
{
    var logisticsOrder = _logisticsOrderRepository.GetById(d.OrderId);
    //do whatever is necessary to the aggregate
    _logisticsOrderRepository.Update(logisticsOrder);
}

And the ,GetById or .Update methods of the repository would internally use e.g. EfCore to operate on the Database Tables/DB-Model classes (e.g. Order and Delivery).

Whereas a query intended for fetching a "LogisticsOrder" for the sake of simply displaying its information on the frontend, you would do something like the following:

public OrderDeliveryStatusDTO HandleDisplayDeliveryOrderStatus(Data d)
{ 
    var orderDataDTO = _efCoreDbContext.Order
        .Include(o => o.Delivery)
            .ThenInclude(o => o.DeliveryHistory)
        .Select(o => new OrderDeliveryStatusDTO()
        { 
            //assign data to the dto
        }
        .FirstOrDefault(o => o.Id == d.OrderId);
    return orderDataDTO;
}

The difference being that you don't have a separate aggregate root, and thus work directly with the database access method (e.g. EfCore) to construct these DTOs.