ERPNext programmes
Connect non-trivial third-party systems without filling ERPNext with brittle point-to-point logic.
- Integration spine
- Governed interfaces
Middleware · Integrate
Connect.Orchestrate.Synchronize.
Middleware that coordinates ERPNext, payments, messaging, GPS, IoT, logistics, and external platforms through one governed integration spine.
- Production context
- Tanaqol scale
- Web, mobile, and kiosk orchestration
- Pre-built connectors
- KSA + Egypt
- Reference market coverage
Audience and fit
Built for teams with a clear job to do.
Start with the operating context, not a feature checklist.
Industrial operations
Coordinate MES, production systems, devices, and IoT events.
- Device data
- Operational sequencing
Multi-channel platforms
Keep web, mobile, kiosk, payments, and core records synchronized.
- Channel orchestration
- Shared state
How it works
One connected workflow.
A short path from the operational trigger to a governed result.
01 · 01
Connect
Use pre-built or custom connectors to establish governed system boundaries.
- API contracts
- Authentication path
02 · 02
Orchestrate
Route, transform, sequence, and retry data across systems.
- Process rules
- Failure handling
03 · 03
Synchronize
Keep records and events consistent in real time across channels.
- State reconciliation
- Operational monitoring
Core capabilities
What the product does.
Focused capabilities cover the work that makes this product distinct.
Regional connectors
Accelerate common KSA and Egypt payment, SMS, and GPS integrations.
- Reusable foundations
- Scoped configuration
API orchestration
Transform and sequence calls through one monitored integration layer.
- Routing
- Retries
IoT and device flows
Bring production and field signals into ERPNext-connected processes.
- Device events
- Operational actions
Operating boundary
Know what connects, where it runs, and what requires scoping.
Deployment, integrations, ownership, and limitations stay visible before rollout.
Engagement enabler
LavaHub is deployed under a scoped ERPNext, LavaSell, or integration engagement.
- Architecture discovery
- Integration backlog
Dependency boundary
API-dependent delivery
Timelines depend on third-party documentation, credentials, test environments, and vendor readiness.
- Sandbox access
- Vendor coordination
Documented handover
Interfaces, runbooks, monitoring, and custom IP boundaries are agreed with the delivery scope.
- Operational runbook
- IP transfer
Proof and commercial path
The integration spine behind Tanaqol.
The reference cites Tanaqol orchestration across web, mobile, and kiosk for 1M users, 10M transactions, and peaks of 400 sign-ups per minute, alongside Nusuk national-platform integration and Infonas legacy-system consolidation.
The integration spine behind Tanaqol.
The reference cites Tanaqol orchestration across web, mobile, and kiosk for 1M users, 10M transactions, and peaks of 400 sign-ups per minute, alongside Nusuk national-platform integration and Infonas legacy-system consolidation.
- 1M — Users
- 10M — Transactions
- 400 — Peak sign-ups per minute
Scoped quote
Scoped under the integration engagement.
Systems, interfaces, events, throughput, security, environments, deployment, support, and third-party dependencies determine scope.
- No standalone public price
- Discovery confirms delivery path
Scope the right next step
Ready to put this product in your operating flow?
Share the systems, users, volumes, locations, and constraints involved. LavaLoon will map them to an accountable next step.