Skip to main content
WEBLET Integration

WEBLET and Priority Integration

Organizations use Priority as a central ERP and business management system for managing orders, customers, items, inventory, service, and business processes. When part of the execution takes place outside the office, a seamless connection is required between the information managed in Priority and the drivers, technicians, salespeople, installation teams, and field employees.

WEBLET makes it possible to connect Priority to field activity, so that relevant information is transferred to execution in an organized way, work results return to the organizational system, and the organization gets an updated and more controlled picture of actual activity.

WEBLET has ready-made interfaces for Priority, and the connection is already active with customers. The existing interfaces provide a proven foundation for connecting the systems, while each project involves adapting the fields, data, and work rules to the organization's business process.

The integration between WEBLET and Priority connects the organizational ERP system to the operational processes carried out in the field.

Instead of copying information between systems, transferring files manually, managing separate lists, or waiting for updates from field employees, a connected workflow can be created, from opening an order, shipment, task, or service call in Priority through to returning the execution results to the system.

  • Transferring orders, tasks, service calls, and operational information from Priority to WEBLET.
  • Displaying the relevant information to drivers, technicians, salespeople, and field teams.
  • Route planning, employee scheduling, task assignment, and work order management.
  • Updating statuses and execution results from the field.
  • Returning signatures, photos, documents, execution times, and proof of delivery to Priority.
  • Reducing repetitive data entry and manual work between systems.
  • Reducing errors, duplication, and mismatches between office information and field execution.
  • Creating operational continuity between Priority, activity managers, and field employees.

This way, Priority continues to serve as the organization's core system, while WEBLET provides the organization with a dedicated work environment for managing, planning, controlling, and optimizing field activity.

Ready-made interfaces and experience with active connections

The connection between WEBLET and Priority is not based solely on a theoretical possibility of developing a new interface.

WEBLET has ready-made interfaces for Priority, and they are already used by customers in ongoing operations. The accumulated experience makes it possible to start from an existing, proven infrastructure, instead of designing and developing the entire connection from scratch.

However, every organization has its own data structure, documents, approval processes, and work rules. Therefore, as part of the implementation, the required fields, data transfer directions, sync frequency, permissions, and adjustments needed for the customer's Priority environment are examined.

The existence of ready-made interfaces shortens the path to connection, but does not replace a professional analysis of the business process.

A unique advantage interface engine and AI optimization

WEBLET has a unique advantage: combining an advanced interface engine with AI-based optimization capabilities for managing field activity.

After information moves from Priority to WEBLET, it is used not only for display to drivers, technicians, and field teams, but also for planning, scheduling, and controlling activity. This way the organization benefits from advanced field-management capabilities while continuing to use Priority and the information and processes already managed in it. Connecting Priority also lets you enjoy advanced AI-based distribution and logistics optimization.

The connection between Priority and WEBLET is suitable for organizations where business and operational information is managed in Priority, while a significant part of the work takes place at customer sites, service locations, on the road, at delivery points, or at facilities outside the office.

The integration is especially relevant for

  • Distribution and logistics companies.
  • Companies managing delivery lines and distribution routes.
  • Service organizations and technicians.
  • Installation, maintenance, and field project companies.
  • Field sales and customer order operations.
  • Organizations running Van Sale or Pre Sale processes.
  • Companies managing equipment delivery, equipment pickup, or returns.
  • Organizations managing drivers, technicians, salespeople, and mobile employees.
  • Companies that need documentation of execution, signatures, photos, or documents from the field.
  • Organizations that want to connect ERP data to planning, scheduling, and operational control.

Suitability is determined by the scope of field activity, process complexity, number of users, and the information that needs to move between systems, not just by the size of the organization.

More than 10 field agents?

Leave us a WhatsApp message and we'll get back to you with an initial fit check.

Send a WhatsApp message now

Instead of managing field activity separately from Priority, the integration makes it possible to transfer to WEBLET the information required for execution, manage field activity through it, and then return the work results to Priority.

Priority
WEBLET
Field teams
WEBLET
Priority
Ongoing updates
Up-to-date information according to your settings
Two-way sync
Continuous updates between all parties
Reliable and secure
Accurate and always available information

The process can work as follows

  • An order, shipment, service call, task, or visit is created in Priority.
  • The relevant data is transferred to WEBLET according to the interface rules.
  • WEBLET is used to plan activity, schedule employees, build routes, and manage the execution order.
  • The driver, technician, salesperson, or field worker receives the information required for execution.
  • During the work, statuses, arrival times, signatures, photos, documents, quantities, notes, and additional execution data are collected.
  • The data defined in the analysis is returned to Priority.
  • The updated information is available for further operational, service, logistics, commercial, or financial handling in the organizational system.

Information transfer can take place in real time, following certain events, or at a predefined frequency, depending on the process, the Priority environment, and the interface structure defined for the organization.

The interface content is determined by the business process, Priority version, active modules, permissions, data structure, and the needs of the organization.

In many cases, the following data can be transferred from Priority to WEBLET:

  • Customers and contacts.
  • Branches, sites, and service points.
  • Addresses and location details.
  • Customer orders and order lines.
  • Shipments and delivery notes.
  • Service calls and tasks.
  • Equipment, machine, or asset details handled at the customer site.
  • Products, items, and catalogs.
  • Price lists and commercial terms.
  • Inventory and warehouses.
  • Vehicle stock or stock designated for field employees.
  • Serial numbers and equipment items.
  • Drivers, technicians, salespeople, and work teams.
  • Time windows.
  • Delivery or visit dates.
  • Service levels and SLA commitments.
  • Documents and execution instructions.
  • Special notes for the customer, order, or task.

From WEBLET, according to the defined process, the following information can be returned to Priority:

  • Task, visit, or shipment status.
  • Departure, arrival, and completion times.
  • Delivery status or reason for non-delivery.
  • Quantities delivered, collected, returned, or sold.
  • Customer signature.
  • Digital proof of delivery.
  • POD documents.
  • Photos from the field.
  • Attached files and documents.
  • Field employee notes.
  • Execution and handling details.
  • Work time.
  • Parts or items used.
  • Visit or service call results.
  • Exceptions, faults, and events requiring further handling.
  • Orders taken by field salespeople.
  • Additional information defined as part of the integration analysis.

Not every type of information is required by every organization. The purpose of the analysis is to select the data that supports the actual process, without creating unnecessary transfer of information between systems.

Common use cases

Distribution and Logistics

Orders, addresses, time windows, and shipment details are transferred from Priority to WEBLET for route planning, building delivery lines, scheduling drivers, and managing delivery execution with transportation management. The driver receives the order of stops and the information required for each delivery. After execution, the delivery status, arrival time, quantities delivered, customer signature, photos, proof of delivery, or reason for non-delivery can be returned to Priority. This way, a connection is maintained between the order and delivery note in Priority and what actually happened at the delivery point.

Service and Technicians

A service call or maintenance task opened in Priority can be transferred to WEBLET with the customer's details, address, equipment, fault type, service level, and execution instructions. WEBLET makes it possible to assign the task to a technician within technician management, manage the order of visits, track progress, and document the work in the field. Upon completion of the treatment, the call status, work times, treatment description, parts used, photos, customer signature, and service documents can be returned to Priority.

Installations and Field Projects

When the organization manages installations, equipment delivery, or project tasks through Priority, the task details, address, contacts, equipment, documents, and execution instructions can be transferred to WEBLET. The installation team receives the information required for execution within installer management and documents in the field the progress of the work, exceptions, photos, documents, and the customer's approval. Upon completion of the task, the work results can be returned to Priority for further organizational processing.

Field Sales and Van Sale

Salespeople working outside the office can receive, via WEBLET, relevant information from Priority, such as customers, addresses, products, price lists, commercial terms, inventory, and relevant activity history. During the visit, activity results can be documented, an order can be taken, products can be reported, visit status can be updated, and the data can be returned to Priority for further handling. In Van Sale processes, the work route, vehicle inventory, sale or delivery, and documentation of activity at the customer site can be combined, according to the process structure defined by the organization.

More than 10 field agents?

Leave us a WhatsApp message and we'll get back to you with an initial fit check.

Send a WhatsApp message now

Extending capabilities with a B2B portal

Alongside the connection between Priority and field activity, the process can also be extended to external users — enabling them to perform actions and receive information through a secure B2B portal.

Alongside the interface engine, WEBLET makes it possible to extend business processes with a secure B2B portal, adapted to the organization's needs and existing workflows. The portal can allow authorized users to act independently — including placing and managing orders, viewing information and documents, tracking statuses, opening requests, and updating data.

The portal can serve customers, suppliers, distributors, franchisees, agents, subcontractors, business partners, and even internal users, with permissions and actions defined for each user type.

By integrating with Priority and with field activity, a digital workflow can be created between the organization and the parties that work with it. Customers can place orders and track handling, suppliers can update information, distributors and agents can manage business activity, and partners can receive the data and documents they need.

In this way WEBLET is not only an interface between systems, but a platform that extends Priority capabilities, improves service, and reduces manual work for office teams.

In many organizations, the problem is not a lack of an information system, but the gap between the information managed in the organizational system and what actually happens in the field.

Priority centralizes the organization's business data and processes. WEBLET connects to it to provide a dedicated work environment for planning, optimizing, executing, and controlling field activity.

The connection can provide the organization with:

  • Less manual transfer of information between employees and systems.
  • Less double data entry.
  • Reduced errors and data mismatches.
  • A faster and more orderly transition from opening an order or task to execution in the field.
  • Better planning of routes and tasks.
  • More efficient scheduling of drivers, technicians, and work teams.
  • Better control over activity status.
  • Orderly documentation of what happened at the customer site.
  • Returning execution data to Priority.
  • Better availability of field documents, signatures, and proof of delivery.
  • Adapting field activity to the organization's business processes.
  • The ability to expand the interface as activity develops.

WEBLET connects Priority more effectively to the people and processes operating outside the office.

Business advantage for the organization

The connection between Priority and WEBLET allows the organization to keep the core system it already uses, while at the same time dedicating specific management to the operational activity that takes place in the field.

Instead of information getting stuck in the organizational system or returning from the field late and inconsistently, a connected process can be created in which data moves to execution and returns after completion.

The result is a more transparent, measurable, and controlled workflow, from the creation of the order, task, or service call to the actual completion of execution.

The existence of ready-made interfaces and experience with connections already active with customers allow WEBLET to offer a proven starting point, while adapting the interface to the process and Priority environment of each organization.

Frequently asked questions about integration with Priority

No. The purpose of the integration is to allow Priority to continue serving as the organization's ERP and core system, while connecting it to field activity planning, execution, and documentation through WEBLET.
Yes. WEBLET has ready-made interfaces for Priority, and they are already active with customers. However, every organization works with a slightly different data structure, documents, and processes. Therefore, an analysis and adaptation of the fields, data transfer directions, permissions, and sync rules to the customer's environment is required.
Yes. Depending on the need, information can be transferred from Priority to WEBLET, and execution data, statuses, signatures, documents, photos, and additional information collected in the field can be returned to Priority. The direction of the information and the exact content are determined as part of the analysis.
The method and frequency of information transfer can be defined according to business need and the technological environment. In some processes, an update close to execution or following a certain event is required, while in others, synchronization can be performed at fixed cycles. The definition is determined by the type of activity, the scope of data, and the organization's requirements.
Yes. It is possible to define which entities and fields will move between the systems, what the direction of information transfer will be, when synchronization will take place, and what validation and update rules will apply to it. The goal is to transfer the information required for the process, not to automatically copy all the existing data in Priority.
The integration can be carried out using API, Web Services, files, databases, and additional communication mechanisms, depending on the existing infrastructure. As part of the analysis, the Priority environment, access method, relevant entities, data structure, information security, and synchronization requirements are examined.
Organization size alone does not determine suitability. The connection is mainly suitable for organizations managing significant field operations, a large number of tasks, deliveries, visits, or mobile employees, or an operational process that requires continuous contact with Priority. Suitability is assessed according to the scope of activity, process complexity, and the business value that can be derived from the connection.
Yes. Every organization uses Priority slightly differently, so the interface is adapted to the data structure, documents, statuses, permissions, and existing work process. The ready-made interfaces provide a foundation for the connection, and the adaptation complements it according to the organization's needs.
Yes. It is possible to start with a defined process, such as transferring orders and returning proof of delivery, and later expand the connection to additional processes, data, or units. The expansion depends on the infrastructure, data structure, and the organization's business needs.

Connecting Priority to field activity

When Priority manages the organization's data and processes and WEBLET manages the planning, execution, and control of field activity, the integration between them creates a more connected and continuous workflow. The required information flows from Priority to field employees, work results are documented during execution, and the relevant data returns to the organizational system for further handling. This way, the organization improves the control, efficiency, documentation, and up-to-dateness of field activity alongside Priority.

Among WEBLET solutions relevant to this integration

Want to connect Priority to field activity using WEBLET?

Contact Us