Get Monitor ERP analytics in plain language. Connect Monitor G5 to Ronja in four steps. Once connected, Ronja maps your production orders, BoMs, inventory, purchase and sales orders, and supplier data into a governed analytics layer. Then anyone can ask manufacturing questions and get answers traced back to the underlying Monitor records. No spreadsheets, no manual exports, no data engineering.
How to analyze Monitor ERP data with Ronja
Setup is two parts: a one-time technical step (network access to your Monitor server and an API user provisioned), then the actual connection inside Ronja which takes minutes.
Step 1: Connect Monitor ERP to Ronja
Just ask Ronja to connect to Monitor. Ronja surfaces a form for your Monitor server URL and a dedicated API-user login. Ronja signs in to your local Monitor G5 server, receives a session, and starts analyzing the data. Self-signed certificates are handled automatically. Sessions are scoped per company and per user.
Step 2: Let Ronja map your production data
Ronja's agents map your production orders, bills of materials, inventory by warehouse, purchase orders, sales orders, suppliers, customers, parts, and accounting entries into structured tables. You don't define a schema. The platform recognizes Monitor's data model (G5 REST/CQRS API) and organizes it for analysis.
Step 3: Ask your first question in plain language
With your data mapped, ask anything. "Which production orders are running behind schedule, and by how many days?" "What's our current stock level for each raw material, which items are below reorder point?" Ronja runs the query against the mapped tables and shows exactly which Monitor records the answer came from. Every number traces to source.
Step 4: Combine Monitor with the rest of your stack
Monitor ERP alone gives you production and inventory analytics. Combined with HubSpot CRM, Fortnox accounting, or your sales pipeline, it's transformative. Ronja unifies all your sources into a single governed layer, so you can finally answer questions like "show production efficiency by customer segment" or "which manufacturing delays correlate with late invoicing" in a single query.
Just ask
Questions you can answer with Monitor ERP data
Ask in plain language. Get answers traced to source. No analysts, no dashboards, no waiting.
What Monitor ERP data Ronja maps
When you connect Monitor ERP, Ronja's agents map the following data into its governed analytics layer:
- Production and manufacturing orders: work orders, planned vs actual time, status
- Bills of materials (BoMs): product structure, components, revisions
- Inventory and stock: levels by warehouse, reorder points, transactions
- Purchase orders: supplier orders, delivery dates, receipt status
- Sales orders: customer orders, delivery status, pricing
- Suppliers and customers: master data, performance, transaction history
- Parts and items: product master, costing, attributes
- Accounting and GL: financial entries, cost centers, dimensions
- Quality management: inspection records, non-conformances
Key takeaways
- The Monitor ERP connector works with Monitor G5 on-premise installations
- One-time setup needs network access to your Monitor server plus a dedicated API user
- Ronja maps your production, inventory, and supplier data automatically. No schema definition needed
- Combines with HubSpot, Fortnox, and 100+ other sources for cross-system manufacturing analytics
- All answers trace back to the underlying Monitor records
Frequently asked questions
How long does it take to connect Monitor ERP to Ronja?
Before you start: you need network access from Ronja to your on-premise Monitor server, plus a dedicated API user provisioned on the Monitor side. Once those prerequisites are in place, most teams complete the connection in 10 to 15 minutes. Ronja signs in to your local Monitor G5 server with the API user, opens a session, and starts mapping data immediately.
Is Monitor ERP cloud or on-premise, and how does that affect the connection?
Monitor ERP is typically installed on-premise on a customer-owned server (default API port 8001). For Ronja to reach it, you either expose the API endpoint externally with proper security or run a local gateway. Self-signed certificates are handled by Ronja automatically. Sessions are scoped per company and per user (one active session per user at a time).
What Monitor ERP data does Ronja have access to?
Production and manufacturing orders, bills of materials, inventory and stock levels, purchase and sales orders, suppliers, customers, parts, accounting and GL, and quality data. Access is scoped to whichever Monitor company and user the API account has rights to.
Do I need a developer or data engineer to use this?
For day-to-day analysis, no. Business users ask production, inventory, and supplier questions in plain language and get answers in seconds. The one-time technical setup (network access to the Monitor server, provisioning the API user) is something an IT or Monitor administrator handles once.
Can I combine Monitor ERP data with HubSpot, Fortnox, or other systems?
Yes. Combining production data with CRM (HubSpot, Salesforce) or accounting (Fortnox, Visma) is one of the most valuable Monitor use cases. You can ask cross-system questions like "which late deliveries correlate with our biggest customers" or "which production runs ate the most cost this quarter" and get a unified answer.
Does Ronja modify any data in Monitor ERP?
Read access is used by default for analytics, and Monitor's read API is free for all customers. Monitor's API supports write commands through a separate "Monitor ERP API" add-on; Ronja does not write to Monitor unless that add-on is purchased and Ronja is explicitly configured to do so for a specific workflow.
Looking for the launch announcement? Read Ronja now connects to Monitor ERP (February 2026).