Connect your field teams with the systems your business runs on.

Consider Enterprise when branches, reporting levels, approvals or system dependencies need a tailored setup beyond your selected standard package. Begin with the workflow that is difficult today and the people responsible for it.

Enabled modules and role permissions can shape what users work with. Confirm the required combination for each team; specialised processes and exceptions need assessment rather than an assumption that every module is included.

Reporting relationships, territories and customer assignments provide operating structure. Share the branch hierarchy and access boundaries so the proposed mapping can be tested, especially where managers cover overlapping teams.

Review the selected package, enabled modules and written implementation scope together. Integration objects, custom work, usage limits and support arrangements should be explicit before rollout.

There are verified scoped Business One reads and ERPNext workforce workflows. Other ERP products and additional objects require assessment of edition, authorised interfaces, sample records and ownership. The directory distinguishes these cases.

Yes, where the enabled workflow has a supported template, such as product CSV import. Start with a sample and review validation results. A general Excel file or a deployment-specific importer is not automatically supported for every account.

Agree an owner for each record and field. An ERP may own product codes and posted invoices while SalesTOS owns visit notes and follow-ups. Resolve conflicting updates through that mapping rather than letting both systems overwrite every field.

The implemented workflow determines when data refreshes. Configured jobs and file uploads have different timings. Agree refresh windows and visible data cut-offs; neither an API nor Enterprise status implies real-time updates.

Only for specifically implemented and authorised objects. For example, ERPNext check-in events have a configured outbound path. A read-only ERP master feed does not imply order, payment or invoice posting.

Supported workflows have their own job or error records. An owner must review the failure, correct the cause and use the supported retry path. Monitoring, retry limits and reconciliation for a new connector must be part of its acceptance criteria.

Roles, module permissions, reporting relationships and assignments control access in the relevant workflows. Test representative employee and manager accounts during the pilot. Custom access rules require review; SSO is not assumed.

Review a redacted sample, stable customer codes, required fields and ownership. Customer migration must use an appropriate enabled importer or an agreed implementation task; do not assume any spreadsheet can be uploaded unchanged.

Export availability depends on the enabled report or workflow and the user’s permissions. Confirm the required fields and format in a demo. Custom extracts, automated feeds and external BI access need their own scope.

Share team-size range, branches, reporting structure, existing systems and the main operational problem. Redacted sample records and interface documentation help define the data scope. Do not submit passwords or API secrets through this form.

A representative pilot is a useful proposed rollout stage. Agree its participants, enabled modules, data, duration and acceptance criteria as part of the engagement; a free or fixed-length pilot is not promised.

Scope depends on users, modules, source interfaces, data objects, mapping complexity, custom workflows and rollout support. Agree implementation work and recurring charges separately, including third-party costs where applicable.

Identify employee, manager and administrator training needs and who will own day-to-day operation. Training format, support channels, coverage and escalation commitments must be agreed for the engagement.

Changes to provider APIs, fields, permissions or business rules can affect a connection. Define an owner and review process for those changes. Additional development, testing and commercial terms should be agreed before expanding the scope.