The orderCreate mutation is pretty nice since you can do most things in one API call. However, it fails at one of the most basic things: discounts.
Why does it allow to only set a single discount per order? What if I have many? What if there are line item discounts?
These cases are covered in draftOrderCreate for example.
Is there any reasoning behind this, or is it something that will be developed in the future? From my POV, I would like to use the mutation since I could create the order in one go (one API call), but I think I have to stick back to first creating the draft, then doing the rest… making it into an order, fulfillments, payments …