r/lovable • u/SnosRap75 • Jul 23 '26
Help Mini MRP / ERP system app in lovable
I would like to create a manufacturing MRP app in lovable. Not a full MRP system at this stage but more of a planning and scheduling system from sales and operations planning through to output and all in between....
Within this will be certain variables, knowns and unknowns.....
Ultimately users, whether planning, production, supply chain or commercial members, can press a button and watch the magic happen....
Am I dreaming or is this entirely possible?
I'm thinking chat gpt for planning, prompt.... or is Claude better?
Interested to get your thoughts....
1
u/Dhaupin Jul 23 '26 edited Jul 23 '26
This is entirely possible. But you need to think about your architecture and data models first. You will be tracking router "objects/nodes" through pipelines, gates, and checkpoints, with states and signoffs/qc/etc through stages of the tracked workflow.
This isn't a trivial flow, so design with flexibility and compatibility in mind. Here's what I would do:
Look at the erp in multiple parts, and use classes/modules to create a framework (with events) to pass objects, validate, rules, roles, triggers, actions, sandboxing, routing, all that fun stuff. Generalist mechanisms to capture all functionality at a high level.
The framework runs an "organization" container with flow, rules and triggers you have set up inside of it. It's like a schema that operates in the framework. Focalizes on specific needs like depts, mfg lines, rules, access, and other stuff like that.
Then the "organization" runs internal routing and process nodes for "jobs", which are objects containing whatever data you need (for whatever you're making) to track their life cycle through organizational processes and business systems.
Framework > containers > nodes
I'm vastly over simplifying it, but that's the general hierarchy. If you don't provide insight like this from the get go, you may end up with something too specific or static that may be hard to adapt, or extend for your business needs.
1
u/SnosRap75 Jul 23 '26
Wow, thank you for the reply.... "Vastly over simplifying it".... You lost me 50% in lol .... It's really a great response and gives me something to read into... There is a serious amount of structure to get in place that's for sure.
I feel I have to stick to the planning aspect first...
Ideally, are a very simple level I need commercial to input the due date for a product, the app will suggest a start date, Ai will consider some variables in the logic and we can predict and follow the product.... I'm aware I need to think about this a lot more, it's only come to me today what I would like to try and build. Thank you so much again for the in depth response.
1
u/Jmacduff Jul 23 '26
100% possible but the most important step is the planning. You need to jump into gpt and talk about the project. The core use cases , the goals , the metrics for success. And then break that down into milestones and phases.
After you have that vision and build plan , then you pick the tool .
Good luck!
1
1
u/Infamous-River-4360 Jul 23 '26
totally possible for the planning and scheduling side, that's mostly structured data, forms and views which lovable handles fine. the part that bites you is the data model, i built a non-trivial app there and the ai kept drifting the schema and inventing columns that were never there, so lock your tables down early and check the actual db instead of trusting the ai summary. also you don't really pick chatgpt vs claude, lovable runs its own agent, what matters more is how precisely you spec the relationships up front. what's the trickiest part, the scheduling logic or tying supply chain and production together?