Poetry is mainly used for managing an _application_ and its dependencies whereas Hatch is more agnostic to the project type and offers plugin-based functionality for the entire workflow (versioning, tox-like environments, publishing) so you can easily build things other than wheel/sdist, test in a Docker container, etc.
Hatch also strictly adheres to standards and eagerly adopts whatever behavior new PEPs dictate while Poetry has a persistent unwillingness to adopt new standards if they are deemed suboptimal (see comments on PEP 621 [1] and PEP 665 [2])
As such, locking support is temporarily blocked https://ofek.dev/hatch/latest/meta/faq/#libraries-vs-applica...
You can continue using other tools like Poetry at the same time https://ofek.dev/hatch/latest/meta/faq/#interoperability
By the way I very much appreciate the eye for design/UX of Poetry's creator, we also share strong opinions on pipenv :)
[1]: https://discuss.python.org/t/5243/12
[2]: https://github.com/python-poetry/poetry/issues/4710#issuecom...