Raleigh, North Carolina
We build our own software. Then we build yours.
eRP Systems runs four products in production across logistics, healthcare supply chain, and commerce — two of them installed inside customer networks. That operating experience is what we bring to custom web and mobile development.
- Products built and operated
- 4Products built and operated
- Industries served
- 3Industries served
- Deployed in private customer networks
- On-premDeployed in private customer networks
Our products
Four products, three industries
Not a portfolio of client logos — software we designed, shipped, and still run. We carry their uptime and their support load.
Mail carrier scanning and route logistics, integrated with USPS.
Logistics & Last-Mile DeliveryOn-premise / private networkRead the case studyMedical inventory, procurement, and supply chain for hospitals.
Healthcare Supply ChainOn-premise / private networkRead the case studyA marketplace for powersports and RV buyers and sellers.
Marketplace & CommercePublic SaaSRead the case studySimplyShop.ai
In developmentAn AI agent that shops around so you do not overpay.
Marketplace & CommercePublic SaaSRead the case study
What we do for clients
Custom web and mobile development
From concept to deployment, built for the operational reality your software has to survive.
Web Application Development
Business systems that hold up under real operational load.
We build custom web applications for organisations whose requirements do not fit an off-the-shelf product: multi-sided marketplaces, internal operations portals, procurement systems, and dashboards that pull from systems that were never designed to talk to each other. Our own products run on the same stack we recommend, which means the architecture advice we give is advice we have had to live with.
Mobile Application Development
Apps built for the field, not the demo.
We build mobile applications for people doing a job with a phone in one hand — scanning packages, counting stock in a supply room, working a route. That imposes constraints most consumer apps never face: patchy connectivity, gloved hands, long shifts, and hardware that has to survive being dropped. We design for those conditions first and make it look good second.
Why eRP Systems
Built by people who operate what they ship
We build our own products
Four of them, in production, across logistics, healthcare supply chain, and commerce. We carry the uptime, the support load, and the cost of ownership — so the architecture advice we give is advice we have had to live with.
We ship into regulated networks
Two of our products are installed inside hospital and logistics customer networks. Procurement review, security posture, and data residency are part of how we deliver, not obstacles we discover at the end.
Integration is the work
USPS, hospital procurement systems, payment processing, customer identity providers. Most business software is judged on how well it talks to systems it did not choose, and that is where we spend our time.
Built for the field
Offline-first mobile applications for people scanning packages and counting stock. Patchy connectivity and one-handed operation shape the design more than any style guide.
Agile delivery you can see
Two-week sprints, each ending with a working demo of the real application. You watch it get built rather than reading about it.
Support that continues
Security updates, dependency upgrades, monitoring, and feature work after launch. We run our own software in production and treat client systems the same way.
On-premise deployment
Installed inside hospital and logistics customer networks, integrated with their identity providers. Data stays within your security boundary.
Offline-first mobile
Field applications that keep working through connectivity dead zones and reconcile cleanly when signal returns.
Integration-heavy systems
USPS, hospital procurement platforms, payment processing, customer identity. Most business software is judged on what it talks to.
FAQ
Common questions
What does eRP Systems do?
We build custom web and mobile applications, and we build and operate our own software products. Our products run across logistics, healthcare supply chain, and commerce — PSTracker for mail carrier scanning and route logistics, MediVentory for hospital medical inventory and procurement, AllVHub for powersports and RV sales, and SimplyShop.ai for AI-assisted shopping. Client work draws on the same engineering practice.
What technologies do you use for web and mobile development?
For web applications we work with React, Next.js, TypeScript, Node.js, .NET, and Python, deployed primarily on Azure. For mobile we use React Native and Flutter for cross-platform work, and Swift or Kotlin when a project genuinely needs native. We pick the stack from your requirements and constraints rather than defaulting to whatever we used last.
Can you deploy inside our own network instead of a hosted service?
Yes. Two of our products, PSTracker and MediVentory, are installed inside customer-controlled networks rather than offered as hosted SaaS, because the hospital and logistics operators who run them have data-residency and security requirements that a multi-tenant service cannot meet. We are used to procurement and security review as part of delivery rather than an obstacle discovered at the end.
How long does it typically take to develop an application?
Timelines vary with scope. A focused mobile application is commonly in the range of two to three months; a complex web application with substantial integration work is more often four to six months or longer. We work in two-week sprints with a working demo at the end of each, so progress is visible rather than reported. We give a specific timeline after discovery, once we understand the integration surface.
Do you provide support after launch?
Yes. We offer maintenance and support covering bug fixes, security updates, dependency upgrades, performance monitoring, and feature work. We operate our own products in production, so ongoing support is a normal part of how we work rather than an afterthought bolted on at handover.
Can you work with our existing development team?
Yes. We take on full delivery, augment an existing team with specific skills, or provide architecture and consulting input. For an existing codebase we start with a short assessment so estimates reflect the real state of the code.
How do you handle application security?
Security is handled during development rather than audited in at the end. We follow OWASP guidance, validate and authorise on the server rather than relying on client-side checks, keep secrets out of client bundles, and use managed identity for service-to-service authentication where the platform supports it. For on-premise deployments we work to the customer security baseline and integrate with their existing identity provider.
Where are you based?
We are based in Raleigh, North Carolina, and work with clients across the United States.
Have a system that needs building?
Tell us what you’re trying to do. We serve clients across 3 industries from Raleigh, NC.