Six focused mobile and AI applications for ERPNext
Put ERPNext in the hands of the people doing the work
Reyn Business Suite combines ReynScanner, Reyn Retail, Reyn Workflow, Reyn OPS, BrassERP and Reyn Textile. Each application gives a specific role a focused mobile or intelligence workspace while ERPNext remains the operational system of record.
Six applications, six operational constraints
- ReynScanner captures or uploads a business card, extracts contact data with OCR, allows human review and creates an ERPNext Lead.
- Reyn Retail creates Sales Orders, checks warehouse stock, shows customer statements and outstanding balances, and shares ERPNext sales documents from mobile.
- Reyn Workflow sends approval notifications and lets authorized users review, approve or reject ERPNext workflow documents with comments and history.
- Reyn OPS analyzes operational events, presents evidence and recommended actions, creates ERPNext To-Do records for follow-up and tracks OKRs.
- BrassERP provides mobile Work Order, job work, production, inventory, barcode and QR workflows connected to ERPNext Manufacturing.
- Reyn Textile connects textile production, material consumption, warehouse stock, quality inspections and delivery tracking with ERPNext.
Technical deployment path
- Review the ERPNext and Frappe version, hosting environment, installed apps, authentication and API constraints.
- Map each user action to ERPNext DocTypes, fields, permissions, workflow transitions and expected outputs.
- Confirm standard fit, required field mapping or customization, pilot users and acceptance tests.
- Validate mobile behavior, sync errors, audit trail and operational ownership before rollout.
Frequently asked questions
- Is Reyn Business Suite a replacement for ERPNext? No. The applications are focused mobile and intelligence workspaces around ERPNext. ERPNext remains the operational system of record for the documents, permissions and business processes described on this page.
- Can we deploy only one application? Yes. Midocean maps the users, ERPNext records, permissions, integrations and rollout outcome, then scopes only the applications that fit the operating problem.
- Will the applications work with custom ERPNext workflows and fields? Reyn Workflow is designed for standard and custom workflows, while other applications may require field mapping or API adjustments. Custom fields, permissions, print formats and business rules are reviewed before deployment.
- Which ERPNext versions, hosting setups and mobile platforms are supported? Compatibility is confirmed during the technical fit review because ERPNext and Frappe versions, installed apps, authentication, hosting restrictions and device requirements can change the deployment approach.
- How are security and permissions handled? The deployment is designed around authenticated APIs and ERPNext role permissions. The review also covers endpoint exposure, user roles, data access, private files and provider-specific controls.
- How is commercial scope calculated? Scope depends on the selected applications, ERPNext version, custom fields and workflows, data mapping, authentication, hosting, device support, providers, testing and rollout support.