A few questions here if you are willing to provide some detail.
- Can you list the issues you had and filed in our bug tracker so we have some context
- We are working on transactions but we have to be slow and careful here to not introduce breaking changes: Use transactions and expose a transactional API by alexandrebodin · Pull Request #14389 · strapi/strapi · GitHub
- We are aware of the lack of component lifecycles: Lifecycle hooks for Components | Voters | Strapi
- Can you provide some more information on the issues around lifecycles in general and your use-case, generally a middleware might better fit your need
As @Paul_Brats mentioned, we are open source and we provide paid support options (of which I am on the team that provides that support). This is common in the open source world, your use-case seems in line with one that would most likely be better fit by our enterprise offering to get dedicated support.
I’d certainly like to know more, primarily we are a headless CMS, not headless eCommerce (such as Medusa but it’s common for us to hook into ecom platforms such as shopify: https://market.strapi.io/plugins/strapi-plugin-shopify / Shopify Fields | Strapi Market