I would say this is an argument to improve the plugin installing system then. I agree, currently it is to complicated: searching via google or the plugin page on the website for a specific plugin, copy the package name and paste it to InvenTree and install it and maybe also restart inventree several times while running migrations or collect static inbetween. This should all be integrated into InvenTree like octoprint has it. In the end I imagine installing a plugin is a one click task after searching for the plugin directly in the admin ui.

We need some guidelines where we make a cut and don't install/ship it by default. I'm sure many don't want to clutter their plugin list with unnecessary builtins that cannot be removed neither disabled. And in my opinion mouser and digikey are some specific vendors. We need to make a cut somewhere, because otherwise some other people come and implement reichelt, rs, farnell, ... as builtins and then we end up with a long list of plugins by default, not everyone is using which makes the whole modular plugin system useless in my opinion.

1. I would suggest creating an inventree/inventree-plugins repository then and make a folder for each of these "official" plugins and publish them individually as pip packages.
2. I would suggest improving the plugin list a bit so that it can be fetched via some kind of api and directly integrated into InvenTree admin ui like octoprint, nodered and iobroker have it.
3. I would suggest that if the import Mixin is there, these plugins also provide official support for importing parts and maybe also syncing orders and pricing and much more integrations.

Originally posted by @wolflu05 in #5509 (comment)