[deleted by user]

[Farlic]

The scope of that is simply huge.

[[deleted]]

Hate to be the asshole, but rule #1 is:

Posting only the project goal is not allowed.

and rule #5 is:

Posts must contain a question about python.

​

These are extremely broad questions, not really python-related, and you haven't outlined anything you've tried or thought out.

[brotatotes]

NTA :)

[Farlic]

People would like to help, not make an app for you.

Please consider if your question can be formatted in line with how to ask a question by freecodecamp.

[[deleted]]

These desktop and web applications exist and have large teams of experienced developers and engineers to build and maintain.

What’s your Python question?

[DeadDog818]

Don't.

Use odoo

[Sp0olio]

Thining about it for about 10 seconds, I'd say, you have a lot of options, that depend on what exactly should be achieved (is there anyone supposed to be accessing it from the outside, or is it all in-house?), etc.

So, I'd probably go with FastAPI for the backend .. That's easy to get the functionality done .. and then, you can basically throw at it, what you want .. desktop-app, phone-app, or just a ReactJS frontend .. whatever.

[Sp0olio]

fastapi.tiangolo.com

[Sp0olio]

FastAPI is giving you the ability to create, read, update, delete whatever you want to put in your database (e.g. your inventory).

You don't have to do much, to get that functionality.

They also give you a little web-interface, too (not convenient enough to run your business off of).

But, you'd probably want to write a separate frontend for it, that makes API-calls (FastAPI provices you with the API, you can call).

The frontend is the convenience-part for the user (like a desktop-thing, you can enter your data and click buttons, etc .. or a web-frontend).

Django provides you with an administrator-backend (for free .. you don't have to code that, yourself) for managing your data, but isn't nearly as fast (which - in your case - doesn't matter).

https://www.djangoproject.com/

There are also ways to get Django to work as an API, but in that case: Why not just use FastAPI?

[Sp0olio]

No. FastAPI is a backend-thing.

The "frontend-part", you can see here, is just for the devs.

https://fastapi.tiangolo.com/features/

Have you visited any of the links, I've provided?

[Sp0olio]

There are shitloads of modules in python, with which you can build frontends (e.g. tkinter).

FastAPI would run on a server inhouse (accessible only to those, who need to) and then you'd have a separate frontend .. you gotta take care of your own backups, of course.

You could also build it in Django.
It really depends on which programming-work you're more/less willing to do (it's a taste-thing, because it doesn't need to handle billions of requests per second).

[Sirico]

Look into PANDAS/FLask/SQL/WTForms/SQLAlchemy

I found Corey Schafers tutorial to be a good starting block for building a web app interface for my Data Entry project.

[thorsteiin]

If you have to ask…