Keep your ERP. Bring Kaela to the field.
Business Central, NAV, GP, Acumatica, and Aptean are established HandApps integrations, but they aren't the limits of the platform. If your company runs another ERP, HandApps can evaluate its APIs, data structure, and business processes to determine the right integration approach for Kaela.
Your ERP remains the back-office system of record. Kaela becomes the mobile sales and DSD experience your reps, drivers, and customers use in the field.
Your ERP shouldn't determine how well your reps can serve the customer
ERP systems are designed to manage accounting, inventory, customers, orders, and financial control. Field reps and drivers need something different: fast mobile workflows, offline operation, customer-specific information, route execution, and a straightforward way to complete the work while they're at the account.
HandApps integrates those two environments. Kaela gives the field a purpose-built experience while the ERP continues doing the back-office work it was selected to do.
Proven starting points, with room to support more
Microsoft Dynamics 365 Business Central
Mobile sales and DSD for Business Central cloud and supported on-premises environments, including continuity for organizations moving from NAV or GP.
Explore Business Central Integration
Microsoft Dynamics NAV
Modernize mobile sales, route activity, and DSD while NAV remains in place, with a path to carry Kaela forward when the ERP eventually changes.
Explore Dynamics NAV Integration
Microsoft Dynamics GP
Improve the field operation now while GP remains the system of record, without forcing every modernization decision into the same project.
Explore Dynamics GP Integration
Acumatica
Extend Acumatica pricing, inventory, customer, and order information into an offline-first mobile field experience.
Explore Acumatica Integration
Aptean
Support food, beverage, route-sales, presales, van-sales, and DSD workflows while Aptean remains the operational and financial foundation.
Explore Aptean Integration
Another ERP?
Kaela isn't limited to the five ERP families shown here. If your ERP provides suitable APIs or other approved integration methods, HandApps can evaluate its data, transaction requirements, security model, and deployment environment to determine the right integration approach.
Discuss Your ERP
Start with the operation, then define the integration
Understand the field
We document how your reps and drivers sell, deliver, price, collect, manage inventory, and serve customers.
Review the ERP
We work with your technical team or ERP partner to understand available APIs, data structures, transaction requirements, security, and deployment constraints.
Define the exchange
Together, we identify what Kaela needs from the ERP and what field transactions must return to it.
Build and validate
HandApps develops the Kaela-side integration, validates it against agreed workflows, and supports the field solution after deployment.
This is our typical engagement model, not a rigid promise that every project follows the same sequence.
The information the field needs, and the transactions the ERP expects
ERP to Kaela
- Customers and ship-to locations
- Products and descriptions
- Customer-specific pricing
- Promotions and discounts
- Inventory information
- Credit status and account balances
- Open orders and invoices
- Order history
- Routes, territories, and assignments
Kaela to ERP
- Sales orders
- Invoices
- Payments
- Credits and returns
- Delivery confirmations
- Signatures and supporting documents
- Inventory transfers and adjustments
- Field notes and transaction details
These are typical data categories, not a universal guarantee — the exact scope is confirmed during the integration assessment.
One integration plan, with clear responsibility on both sides
HandApps
Builds and supports Kaela, field workflows, synchronization, and the Kaela-side integration components.
Your ERP partner or team
Handles ERP-side configuration, approved endpoints, extensions, permissions, and changes inside the ERP environment.
Shared integration design
Defines data ownership, transaction flow, security, validation, exception handling, and implementation responsibilities.
Change the ERP without automatically replacing the field solution
Companies change ERPs because of growth, acquisitions, consolidation, new financial requirements, or changes in corporate strategy. Those decisions shouldn't automatically force every rep and driver to abandon the field workflows they know.
Because Kaela operates as the mobile field layer, HandApps can evaluate how to preserve the field experience while adapting the integration to a new ERP. The exact scope depends on the new system and the organization's requirements, but the field and ERP decisions don't have to be treated as the same decision.
Business Central
NAV
GP
Acumatica
Avalara
Common questions
Does Kaela work only with the five ERPs shown on the website?
No. Those are core ERP integrations that HandApps has already developed and supports. If your ERP isn't listed, we can evaluate its APIs, data access, transaction requirements, and deployment model to determine whether and how Kaela can integrate with it.
Can you guarantee integration with any ERP?
Not without reviewing the system. A successful integration depends on the ERP's available APIs or other approved integration methods, the data it exposes, the transactions required, and the customer's technical environment. HandApps begins with an integration assessment before confirming scope.
Who handles changes inside our ERP?
HandApps builds and supports the Kaela application and its side of the integration. Changes inside the ERP are generally handled by the customer's ERP partner or internal ERP team, with both sides working from an agreed integration design.
What happens if we replace our ERP later?
HandApps can evaluate adapting the Kaela integration to the new ERP while preserving the field experience wherever practical. The scope depends on the new system, available integration methods, data conversion, and any changes in your business processes.
Can we keep ERP-specific custom processes?
Kaela is configurable and can support customer-specific workflows, but requirements must be reviewed during discovery. HandApps will identify which needs can be handled through configuration, existing capabilities, optional modules, or additional development.
Tell us what ERP you run and how your field works
We'll start with your operation, review the ERP environment, and determine whether Kaela is the right fit and what the integration would require.
Discuss Your ERP