Skip to main content
WEBLET Integration

WEBLET and Hashavshevet Integration

Many organizations in Israel use Hashavshevet to manage business processes such as customers, orders, items, inventory, price lists, documents, and financial processes. When part of the activity takes place outside the office, in distribution, service, technician work, installations, or field sales, a continuous connection is required between the information managed in Hashavshevet and the employees who carry out the tasks in practice.

WEBLET makes it possible to connect Hashavshevet to field activity, so that information moves between the systems in an organized way, work processes stay continuous, and the organization gets better control over execution.

Using the WEBLET interface engine, which includes interfaces for leading ERP, CRM, and organizational systems, information can be transferred from Hashavshevet to WEBLET and execution data from the field can be returned to Hashavshevet. The interface structure is adapted to the processes, data types, and needs of the organization.

The integration between WEBLET and Hashavshevet connects the business information managed in the office to the activity carried out in the field.

Instead of re-entering data, transferring files manually, or updating the same order in several different systems, one continuous workflow can be created, from creating the order, task, or service call through to completing execution and updating the results back in Hashavshevet.

  • Transferring orders, tasks, service calls, and operational information from Hashavshevet 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 Hashavshevet.
  • Reducing repetitive data entry and manual work between systems.
  • Reducing errors, duplication, and mismatches between business-system information and field execution.
  • Creating operational continuity between Hashavshevet, activity managers, and field employees.

Hashavshevet continues to serve as the core system for managing business information, while WEBLET manages planning, scheduling, routes, execution, reporting, and documentation of field activity. This way each system performs the role it is meant for, and information moves between them automatically and under control.

The WEBLET Interface Engine

The WEBLET interface engine was developed to connect ERP, CRM, and organizational systems to field activity.

Using the engine, it is possible to define which data will move between Hashavshevet and WEBLET, in which direction each type of information will be transferred, how often synchronization will run, which checks and control rules will apply, and how updates, changes, and exceptions will be handled.

WEBLET allows Hashavshevet to continue managing business information, while WEBLET manages the execution layer in the field.

The interface is adapted to the organization's work process, so that only the data required by field employees is transferred, and only the execution results relevant to continued handling in Hashavshevet are returned.

Depending on the existing infrastructure, the connection can rely on API, Web Services, files, databases, and additional communication mechanisms.

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 Hashavshevet to WEBLET, customers, orders, items, and inventory, it is used not only for display to drivers and field staff, but also for planning distribution lines, scheduling, and controlling activity. This way the organization benefits from advanced field-management capabilities while continuing to use Hashavshevet and the information and processes already managed in it. Connecting Hashavshevet also enables AI-based distribution-line and delivery optimization.

The connection between Hashavshevet and WEBLET is especially suitable for organizations where Hashavshevet centralizes customer, order, item, and inventory data, while a significant part of the activity takes place outside the office.

The integration is especially relevant for

  • Distribution and logistics companies.
  • Importers, distributors, and wholesalers.
  • Service organizations and technicians.
  • Installation and maintenance companies.
  • Field sales and Van Sale operations.
  • Companies managing drivers and mobile employees.
  • Organizations performing many deliveries or visits every day.
  • Companies that need to return statuses, signatures, and proof-of-delivery documents to the business system.

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 Hashavshevet, the interface makes it possible to transfer the required information to WEBLET, manage planning and execution in the field, and then return the activity results to Hashavshevet.

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

This is how a continuous workflow is created

  • An order, shipment, service call, or task is created in Hashavshevet.
  • The required data is transferred automatically to WEBLET.
  • WEBLET plans the activity, builds routes, and schedules the right employees.
  • The driver, technician, or salesperson carries out the task using the WEBLET app.
  • When the work is done, statuses, execution times, signatures, photos, delivery documents, and other defined information are returned to Hashavshevet.

This way office employees get up-to-date information on what was done in the field, without waiting for manual reporting and without re-entering the same data.

Depending on the organization's needs and business process, relevant process information can be transferred between the systems. The integration does not require transferring all information. It is possible to choose the necessary data and define the appropriate sync direction.

In many cases, data such as the following can be transferred from Hashavshevet to WEBLET:

  • Customers and contacts.
  • Delivery, service, and visit addresses.
  • Orders and shipments.
  • Products, items, and catalogs.
  • Price lists and discounts.
  • Inventory and warehouses.
  • Business documents.
  • Service calls and tasks.
  • Drivers, technicians, and salespeople.
  • Vehicles.
  • Time windows and customer commitments.
  • Distribution lines and routes.

From WEBLET, depending on the defined process, information such as the following can be returned to Hashavshevet:

  • Execution statuses.
  • Arrival and completion times.
  • Digital signatures.
  • Photos and files from the field.
  • POD documents and delivery confirmations.
  • Notes and reasons for non-completion.
  • GPS and location data.
  • Orders created during a sales visit.

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

Common use cases

Distribution and logistics

An order is created in Hashavshevet and transferred to WEBLET for planning a distribution line and delivery route in the transportation management system. The driver receives the tasks and carries out the deliveries. When done, the delivery status, arrival time, customer signature, photos, and POD document can be returned to Hashavshevet. This way a link is kept between the order in the business system and what actually happened at the delivery point.

Service and technicians

A service call or task is opened in the system and the information is transferred to WEBLET. The task is scheduled to the right technician as part of technician management. The technician carries out the work and documents it in the field. When done, the service report, work times, photos, signature, and status can be returned to the system.

Field sales and Van Sale

Customers, products, price lists, and inventory information are transferred from Hashavshevet to WEBLET. The salesperson visits the customer. An order is created or the sales process is documented, including in Van Sale processes. The data returns to Hashavshevet for continued business, logistics, and financial handling.

Installations and field projects

An installation order or execution task is created in the system. WEBLET schedules the team as part of installer management and transfers addresses, documents, and instructions. The work is carried out and documented in the field. When done, status, photos, signatures, and completion forms are returned to Hashavshevet.

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

The integration does not have to end with a connection between two systems. In many cases the process can also be extended beyond the organization, enabling customers, suppliers, and business partners to work with information in a secure and controlled way.

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 Hashavshevet 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 Hashavshevet capabilities, improves service, and reduces manual work for office teams.

In many organizations the business data already exists in Hashavshevet, but field execution is managed by phone, messages, files, or systems that are not connected to the central system.

That gap can cause double entry, errors, delays in updating information, and difficulty knowing in real time what was completed and what is still open.

Hashavshevet provides the business management layer, while WEBLET adds planning, scheduling, execution, documentation, and control of field activity.

One of the advantages of the WEBLET interface engine is the ability to incorporate Hashavshevet into the existing process, without replacing the system and without managing the same activity in two disconnected places.

The connection makes it possible to:

  • Reduce manual work and duplicate data entry.
  • Reduce errors and mismatches between systems.
  • Shorten the time between receiving an order and execution.
  • Get faster reporting on activity results.
  • Improve control over distribution, service, and field sales.
  • Keep business data in the central system.
  • Document signatures, photos, and proof-of-delivery documents.
  • Get an up-to-date picture of field employee activity.
  • Expand the integration as the organization grows.

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

Business advantage for the organization

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

Instead of information getting stuck in the business 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 creating the order, task, or service call through to actual completion of execution.

Frequently asked questions about integration with Hashavshevet

No. The purpose of the integration is to allow Hashavshevet to continue managing business data and processes, while connecting field activity to it through WEBLET.
Yes. The WEBLET interface engine makes it possible to connect Hashavshevet to field activity and adapt data transfer to the work processes, data structure, and requirements of the organization. The connection can be set up using API, Web Services, files, databases, and additional communication mechanisms, according to the existing infrastructure.
Yes. Information can be transferred from Hashavshevet to WEBLET, and execution data, statuses, signatures, photos, POD documents, and additional information collected in the field can be returned to Hashavshevet. Not every data item has to move in both directions. The sync direction is determined by the type of information and the business process.
Yes. It is possible to define which data, fields, and documents will move between the systems, in which direction, how often, and according to which rules.
Yes. Orders and related data can be transferred for distribution planning, task assignment, delivery execution, or field sales and service activity.
Yes. Delivery statuses, signatures, photos, execution times, reasons for non-delivery, and POD documents can be returned, according to the defined interface.
Yes. Depending on the work process, customers, addresses, items, catalogs, price lists, and additional information required for field activity can be transferred.
Yes. Salespeople can receive customer, product, and pricing information, and after the visit orders, sales results, and additional information can be returned to Hashavshevet.
Not necessarily. The WEBLET interface engine is designed to adapt the integration to existing processes as much as possible, so that each system continues to perform its role.
Yes. Additional data, fields, documents, and processes can be added as activity develops and according to the organization's needs.

Connecting Hashavshevet to field activity

Hashavshevet centralizes the organization's business data and processes, while WEBLET manages the activity carried out in the field. The integration between the systems makes it possible to create a continuous digital process, from receiving the order or task, through planning and executing the activity, to returning execution results to Hashavshevet. Using the WEBLET interface engine, the connection can be adapted to the organization's work processes, reducing manual work, improving data quality, and gaining better control over distribution, service, technician, and field sales activity. As part of the analysis, the types of data, sync direction, update frequency, and actions to be performed in each system can be defined, in order to create a complete workflow between Hashavshevet and field activity.

WEBLET solutions that work with this integration

Want to see how WEBLET can connect to Hashavshevet?

Contact Us