Hello,
In the HikaShop backend, you will see the "order subsale" but also the "HikaMarket transaction".
Transaction is the way introduced in HikaMarket 2.0 in order to improve the order workflow.
You're not paying anymore the vendors for the "subsales" but for the "transactions", so if the customer order is modified and the vendor transaction is already paid, a new transaction is created and you keep the record of when and how the previous transaction was paid (so does its order status). With the subsale system, you could lost that information and another kind of order type could be created for adjustment.
It was not flexible enough so we introduced the transaction system.
So you still have "sale" and "subsales" in the HikaShop order table, the "sale" for the customer and the "subsale" for the vendors.
We still display the subsales in the HikaShop backend so you have a record of the current state of the vendor order (including the total of its subsale, when the transaction could display something different depending if you paid the vendor, even partially)
Regarding the export, I can't tell you why you have duplicate lines for the sales, or the subsales. I don't have the knowledge of the SQL queries made for the export.
If you do want to have a classical export, you need to remove the subsales from that file. It should logically stop the duplicates since I have the feeling that more you have vendors (subsales), more you have duplicates lines.
Since you're talking about the export of the entire order, you do not want to have the subsales which are just for the vendors point of view.
Regards,