How YRP works
ERPNext underneath. Your business on top.
ERPNext does the heavy lifting
We use ERPNext for everything it does well, accounting above all. Where the floor needs something it does not have yet, we add a thin layer of our own. When ERPNext ships that feature, we move onto it once it is compatible and tested.
Your business rules stay yours
Each company we implement gets its own app on top of YRP, holding its business logic exactly as it runs today. We never ask you to adapt to the software. YRP keeps the shared records underneath, so the numbers always add up.
One example: the Item
ERPNext’s item variants have no way to make one attribute depend on another. We added that, along with optional attributes shaped around how we actually make things. A small change, and it fixed a workflow we had fought for years.
Stable under upgrades
Your floor keeps its familiar screens.
When ERPNext changes, your operators keep the screens and workflows they know. YRP maintains the connections those screens use, called APIs. We change YRP to support the upgrade, so your team can keep working the same way.
What YRP adds today
Built around the work you do.
Sales and distribution
Retail, distributor and sales-rep management, with a companion app for agents, distributors, retailers and reps. Dispatch and billing are built together. Sales-agent commissions are managed in YRP, and customer credit is visible at the point of dispatch.
Manufacturing
Production purchase orders, time-and-action schedules and capacity planning are built. Material per finished unit is defined once in the bill of materials, for example kilograms of fabric per garment, and issue estimates generate themselves. The goods-movement core records hand-offs between departments. We use these on our own garment floor.
People
Actual wages paid are mapped into the factory profit and loss statement. Attendance and today’s punch status sit inside the floor screens, where operators used to cross-check them manually.
Accounting
We use ERPNext’s accounting as it is, because the accounting standards live there. We make a few direct customisations, such as discounting, and keep up with the latest ERPNext.
What is running today
The goods-movement core.
Department-to-department movement. Every inward and outward is recorded at the hand-off. On a garment floor, that means cutting to stitching, or stitching to ironing.
One accountable record. Sender and receiver work on the same movement record. Both sides answer to it, without a second transcription.
Live visibility. See where goods went and what has been sent but not yet received, while there is still time to act today.
Floor-first entry. Each screen is built around the operator’s real action and held to one bar: easier than the Excel sheet it replaces.
Provenance
Proven on our own floor.
We built YRP for ourselves. Daily tracking and distribution in our own manufacturing business run on software built in-house. Garment manufacturing is where these workflows were proven. We think they will help others too.
Stated plainly
What we will not pretend is already built.
Beyond the goods-movement core, time-and-action and capacity planning are running in daily use. What is not built yet: deep industrial-engineering integration (SAM value calculation, line balancing, skill matrices) and line-level production tracking.
If your scope needs them, we will design and build them with you — exactly what you want, scoped in the open as new work. What we will not do is demo an unbuilt capability as something already delivered. You have met that demo before.
Weighing SAP?
What you buy SAP for, one department at a time.
One set of numbers
That is what a manufacturer buys SAP for. Every movement on the floor is recorded once, the books agree with the floor, and any figure in the accounts traces back to the document behind it.
YRP builds it on ERPNext
Every hand-off between departments is recorded once, where it happens. Your accounts run on ERPNext’s accounting as it is. Today, a goods receipt in YRP posts its purchase invoice straight into ERPNext. The rest of the floor joins the books step by step, each link built and tested with your accounts team.
The difference is the path
We put one department live, watch it in use and correct it before the next one moves. Until a department moves over, we agree with your accounts team who reconciles the old records with the new. When your process changes later, the change goes into your own app, which your developers can read and extend.
Ownership
Yours, in the ways that matter.
The codebase travels with its history
Documented, readable, with the full development record — a system your own developers can read, extend and stand behind.
Your person runs it
One trained person is enough to run it. We train that person on your floor, on your movements, and hand over a running system.
The data is portable
Open stack, standard database, and your data exports whole, in formats any system can read.
Availability
YRP is coming to Frappe Cloud soon.
Frappe Cloud is the hosting platform run by Frappe, the company behind ERPNext.