I agree that b sounds like the best option for the problem stated. Happy for the work to go ahead.
To sanity check, the modifications history will not be captured for an order at all unless the user generates an invoice?
I know I am late to the party so I’m sure this has been discussed at length already and thus sorry for throwing a spanner in and I hope it doesn’t create complications…
To my mind I feel like there might be benefit in having all modification data stored, rather than overwriting the original order data - so there is orders data and a modification data. Then invoices are generated as a snapshot of the current state of the order, including up to date modifications.
This is a common ecommerce problem. I do wonder how spree handles order modifications?
@sauloperez @luisramos0 @maikel @Matt-Yorkley