Dolibarr ERP CRM Wiki - User contributions [en]

Module Intervention Enhanced

2026-04-20T11:10:40Z

Mgribaudo:

[[File:Fig. 1.png|thumb]]
The " Interventions Enhanced" module has been designed for all companies whose management of customer interventions represents an essential part of their work activity.

Flow management starts from the planning of interventions on the agenda. The events are transformed into interventions and these can both give rise to customers invoices and move the warehouses in relation to the material used in the intervention.

Optionally, the intervention can:

*generate the operator's expense report
*calculate and include in the invoice the cost of personnel relating to the hours required for the intervention 

== '''Installation and configuration''' ==
The installation of the " Interventions Enhanced" module follows the standard Dolibarr methods, then download the package and install it in the usual way.

There are a number of configuration parameters to be set before using the module. These are

*The indicator that allows you to define whether or not you want to create expense reports at the same time as accounting for interventions (if the Expense Report module is enabled)
*The indicator that allows you to define whether or not VAT should be included in the prices of the expense reports (if the Expense Report module is enabled)
*The indicator that allows you to enable or disable the viewing of the amounts in the invoice associated with the intervention
*In order to use the features for accessing interventions via Google maps, it is necessary to enter the Google API Key
*An hourly cost
*The service code relating to the interventions. These last two parameters are used to calculate the cost of the intervention in the invoice based on the hours

=='''New features on the agenda'''==
A number of new features have been added to the agenda:

*a button that allows you to view the geographical location of the interventions of the period / operator.[[File:Image 2.png|thumb]]

Notice how:

. interventions are numbered in temporal order

. the interventions take on the color assigned to the operator (user)

. by clicking on the icon you can access the details of the intervention
[[File:Image 3.png|thumb]]
. it is possible, in the lower section of the window, to enter a new address and display it on the map together with the rest. This facilitates the assignment of a new intervention to the most suitable operator.

*a button that allows you to view the map of the best road route from the address associated with the operator to that of the intervention (in the absence of this, to the customer's address) 

=='''Creation of an intervention from the agenda'''==
After creating the event, it is possible from the latter to create:

. a new line of detail of the intervention.

The distance of the route is also stored in this line.

. a new invoice line

This through the new button [Create Intervention]

In this phase, the following indications should be taken into account:

*the interventions shown in the list are only those in the "Draft" or "Validated" status
*the "Create Intervention" button is active only if an intervention has been indicated and if the event is not in the "Done" state
*expense reports, if enabled, are assigned to the owner of the event
*for the automatic generation of expense reports, each operator (user) must be associated with his supervision. Only the supervisor can generate the note
*if there are notes for the service, these will be reported in the intervention

=='''Reporting of the intervention'''==
[[File:Image 4.png|thumb]]
The intervention sheet presents the new tab [Invoice] where you can:

*modify or integrate the data from the events that have been accounted for the intervention.

It is possible to insert, in this phase, the materials that were used during the interventions.

*after the intervention has been validated, generate the discharges of the material
*[[File:Image 5.png|thumb]]after the intervention has been validated, create the invoice or, alternatively, close the intervention without issuing an invoice

=='''Periodic billing'''==
[[File:Image 6.png|thumb]]
In the billing menu there is an item that allows you to generate a summary invoice for each customer for all the interventions carried out.
[[Category:Complementary modules]]

Module Intervention Enhanced

2026-04-20T11:09:50Z

Mgribaudo: /* Installation and configuration */

[[File:Fig. 1.png|thumb]]
The " Interventions Enhanced" module has been designed for all companies whose management of customer interventions represents an essential part of their work activity.

Flow management starts from the planning of interventions on the agenda. The events are transformed into interventions and these can both give rise to customers invoices and move the warehouses in relation to the material used in the intervention.

Optionally, the intervention can:

*generate the operator's expense report
*calculate and include in the invoice the cost of personnel relating to the hours required for the intervention 

'''Installation and configuration'''

The installation of the " Interventions Enhanced" module follows the standard Dolibarr methods, then download the package and install it in the usual way.

There are a number of configuration parameters to be set before using the module. These are

*The indicator that allows you to define whether or not you want to create expense reports at the same time as accounting for interventions (if the Expense Report module is enabled)
*The indicator that allows you to define whether or not VAT should be included in the prices of the expense reports (if the Expense Report module is enabled)
*The indicator that allows you to enable or disable the viewing of the amounts in the invoice associated with the intervention
*In order to use the features for accessing interventions via Google maps, it is necessary to enter the Google API Key
*An hourly cost
*The service code relating to the interventions. These last two parameters are used to calculate the cost of the intervention in the invoice based on the hours

=='''New features on the agenda'''==
A number of new features have been added to the agenda:

*a button that allows you to view the geographical location of the interventions of the period / operator.[[File:Image 2.png|thumb]]

Notice how:

. interventions are numbered in temporal order

. the interventions take on the color assigned to the operator (user)

. by clicking on the icon you can access the details of the intervention
[[File:Image 3.png|thumb]]
. it is possible, in the lower section of the window, to enter a new address and display it on the map together with the rest. This facilitates the assignment of a new intervention to the most suitable operator.

*a button that allows you to view the map of the best road route from the address associated with the operator to that of the intervention (in the absence of this, to the customer's address) 

=='''Creation of an intervention from the agenda'''==
After creating the event, it is possible from the latter to create:

. a new line of detail of the intervention.

The distance of the route is also stored in this line.

. a new invoice line

This through the new button [Create Intervention]

In this phase, the following indications should be taken into account:

*the interventions shown in the list are only those in the "Draft" or "Validated" status
*the "Create Intervention" button is active only if an intervention has been indicated and if the event is not in the "Done" state
*expense reports, if enabled, are assigned to the owner of the event
*for the automatic generation of expense reports, each operator (user) must be associated with his supervision. Only the supervisor can generate the note
*if there are notes for the service, these will be reported in the intervention

=='''Reporting of the intervention'''==
[[File:Image 4.png|thumb]]
The intervention sheet presents the new tab [Invoice] where you can:

*modify or integrate the data from the events that have been accounted for the intervention.

It is possible to insert, in this phase, the materials that were used during the interventions.

*after the intervention has been validated, generate the discharges of the material
*[[File:Image 5.png|thumb]]after the intervention has been validated, create the invoice or, alternatively, close the intervention without issuing an invoice

=='''Periodic billing'''==
[[File:Image 6.png|thumb]]
In the billing menu there is an item that allows you to generate a summary invoice for each customer for all the interventions carried out.
[[Category:Complementary modules]]

Module Intervention Enhanced

2026-04-20T11:06:56Z

Mgribaudo: Created

[[File:Fig. 1.png|thumb]]
The " Interventions Enhanced" module has been designed for all companies whose management of customer interventions represents an essential part of their work activity.

Flow management starts from the planning of interventions on the agenda. The events are transformed into interventions and these can both give rise to customers invoices and move the warehouses in relation to the material used in the intervention.

Optionally, the intervention can:

* generate the operator's expense report
* calculate and include in the invoice the cost of personnel relating to the hours required for the intervention 

== '''Installation and configuration''' ==
The installation of the " Interventions Enhanced" module follows the standard Dolibarr methods, then download the package and install it in the usual way.

There are a number of configuration parameters to be set before using the module. These are

* The indicator that allows you to define whether or not you want to create expense reports at the same time as accounting for interventions (if the Expense Report module is enabled)
* The indicator that allows you to define whether or not VAT should be included in the prices of the expense reports (if the Expense Report module is enabled)
* The indicator that allows you to enable or disable the viewing of the amounts in the invoice associated with the intervention
* In order to use the features for accessing interventions via Google maps, it is necessary to enter the Google API Key
* An hourly cost
* The service code relating to the interventions. These last two parameters are used to calculate the cost of the intervention in the invoice based on the hours

== '''New features on the agenda''' ==
A number of new features have been added to the agenda:

* a button that allows you to view the geographical location of the interventions of the period / operator.[[File:Image 2.png|thumb]]

Notice how:

. interventions are numbered in temporal order

. the interventions take on the color assigned to the operator (user)

. by clicking on the icon you can access the details of the intervention
[[File:Image 3.png|thumb]]
. it is possible, in the lower section of the window, to enter a new address and display it on the map together with the rest. This facilitates the assignment of a new intervention to the most suitable operator.

* a button that allows you to view the map of the best road route from the address associated with the operator to that of the intervention (in the absence of this, to the customer's address) 

== '''Creation of an intervention from the agenda''' ==
After creating the event, it is possible from the latter to create:

. a new line of detail of the intervention.

The distance of the route is also stored in this line.

. a new invoice line

This through the new button [Create Intervention]

In this phase, the following indications should be taken into account:

* the interventions shown in the list are only those in the "Draft" or "Validated" status
* the "Create Intervention" button is active only if an intervention has been indicated and if the event is not in the "Done" state
* expense reports, if enabled, are assigned to the owner of the event
* for the automatic generation of expense reports, each operator (user) must be associated with his supervision. Only the supervisor can generate the note
* if there are notes for the service, these will be reported in the intervention

== '''Reporting of the intervention''' ==
[[File:Image 4.png|thumb]]
The intervention sheet presents the new tab [Invoice] where you can:

* modify or integrate the data from the events that have been accounted for the intervention.

It is possible to insert, in this phase, the materials that were used during the interventions.

* after the intervention has been validated, generate the discharges of the material
* [[File:Image 5.png|thumb]]after the intervention has been validated, create the invoice or, alternatively, close the intervention without issuing an invoice

== '''Periodic billing''' ==
[[File:Image 6.png|thumb]]
In the billing menu there is an item that allows you to generate a summary invoice for each customer for all the interventions carried out.
[[Category:Complementary modules]]

File:Image 5.png

2026-04-20T11:06:08Z

Mgribaudo:

Image 5

File:Image 4.png

2026-04-20T11:02:55Z

Mgribaudo:

Image 4

File:Image 6.png

2026-04-20T11:01:45Z

Mgribaudo:

Image 6

File:Image 3.png

2026-04-20T10:54:29Z

Mgribaudo:

Image 3

File:Image 2.png

2026-04-20T10:53:01Z

Mgribaudo:

Image 2

File:Fig. 1.png

2026-04-20T10:51:41Z

Mgribaudo:

Image 1

Module SMS Everywhere

2026-04-20T10:00:57Z

Mgribaudo: Creata

The “SMS Everywhere” module allows the sending of SMS in the following situations

* from ALL the modules that are enabled to send emails (offers, orders, shipments, invoices ….) by adding a specific button for sending SMS. The phone number used is that of the mobile phone of the event manager and / or event guest, in relation to the company connected to the event. If such contacts do not exist, the company’s telephone number is used. The event is created for the associated document (the action type is customizable in the setup)
* from the events of the Agenda module

It also allows:

* to send a reminder SMS to the customer or collaborators to whom the event has been assigned
* to automatically send an SMS notification to customers of the event n hours before the event.

The telephone number is calculated with the logic described above

* all using the emai templates and the [[Variable substitution system|Substitution Variables]]

This module does not deal directly with the sending of messages, but requires the use of a third-party module for the forwarding of SMS

In this manual, the description of everything that follows the operating norms of Dolibarr is omitted, focusing only on the specific functions of the module itself.

== '''Module configuration''' ==
The following parameters are required:
[[File:Immagine-3-1024x551.png|thumb]]
'''Sender''' Contains the sender of the SMS. The value to be assigned depends on the SMS provider used (in principle they should coincide)

'''Delay before sending''' Contains the minutes of delay for sending SMS

'''Priority''' Contains the priority of the SMS, also in this case, the value takes on different meanings (pricing for example) depending on the provider used

'''Reminder recipients''' Defines whether the reminders (remionder) should be sent to the Third Party or to the internal operators to whom the event has been assigned

'''International prefix''' Allows you to replace in all numbers starting with zero, the initial zeo with the prefix indicated (eg by indicating +33 in the field, 0340xxxxx will become + 33340xxxxx).

If you leave the value empty, the replacement will not be carried out.

'''Automatic SMS advance hours''' Contains the hours in advance, compared to the time of the event, for sending the automatic SMS

'''Automatic SMS Template''' Contains the template used for the automatic SMS. The list of templates present for the emails is proposed.

SMS Action Type Indicates the event type that will be used for the SMS sending event

== '''Automatic sending of reminders for events in the Agenda''' ==
[[File:Image-11.png|thumb]]
In the setup, indicate which model to use and the reminder advance time

== '''Manual sending of reminders for events in the Agenda''' ==
[[File:Image-12-1024x201.png|thumb]]
On the Events page, there is a new Tab. From this it is possible to both send an immediate SMS and create a reminder (as shown in the image)
[[Category:Complementary modules]]

File:Image-12-1024x201.png

2026-04-20T09:58:08Z

Mgribaudo:

Manual sending of reminders for events in the Agenda

File:Image-11.png

2026-04-20T09:55:23Z

Mgribaudo:

IAutomatic Remindes

File:Immagine-3-1024x551.png

2026-04-20T09:48:06Z

Mgribaudo:

Setup Image

Bulk Price/Pricelist Change

2026-04-03T08:33:22Z

Mgribaudo:

It allows you to massively modify the purchase or sale prices for the selected items.

Once the prices to be changed have been identified (on pricelist, on the categories, on the supplier, on the title, …) and introduced the discount/increase criteria, through a percentage and a rounding criterion, with a simple click it is possible to massively vary the prices of products.

==Setup==
No configuration parameters are required for this module.

==Usage==
Once the specific item that will appear in the "Products" menu has been selected, the massive modification of prices is possible through the following simple steps:

*selection of the items for which you want to change the price according to Dolibarr's standard methods
*insertion of a discount / surcharge percentage and of the rounding-off criterion
*the new prices will be calculated, displayed and checked individually
*confirmation of the massive operation 

Note that:

*for purchase prices, it is possible to vary only the prices relating to one supplier at a time
*it is possible to vary the list prices (price levels) of sales

[[Category:Complementary modules]]
__INDEX__

Bulk Price/Pricelist Change

2026-04-03T08:21:02Z

Mgribaudo: Inserted

It allows you to massively modify the purchase or sale prices for the selected items.

Once the prices to be changed have been identified (on pricelist, on the categories, on the supplier, on the title, …) and introduced the discount/increase criteria, through a percentage and a rounding criterion, with a simple click it is possible to massively vary the prices of products.

== Setup ==
No configuration parameters are required for this module.

== Usage ==
Once the specific item that will appear in the "Products" menu has been selected, the massive modification of prices is possible through the following simple steps:

* selection of the items for which you want to change the price according to Dolibarr's standard methods
* insertion of a discount / surcharge percentage and of the rounding-off criterion
* the new prices will be calculated, displayed and checked individually
* confirmation of the massive operation 

Note that:

* for purchase prices, it is possible to vary only the prices relating to one supplier at a time
* it is possible to vary the list prices (price levels) of sales

[[Category:Complementary modules]]

Advanced warehouse management

2026-03-25T10:32:25Z

Mgribaudo: Update

{{DISPLAYTITLE:Module Advanced warehouse management}}
{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM warehouse movement management
|editor=OPG
|web=www.opigi.com
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opg}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM projec]t, integrate and improve warehouse movement management.

Movements are managed through “''Warehouse movements''” identified by:

*a reason that defines their characteristics (loading and/or unloading warehouse, bom explosion, etc.).
*n lines that correspond to the individual warehouse movements.

This organization allows for::

*a better organization and access to movements (for example, customized numbering of records is possible)
*faster management: the warehouse is pre-set and there is the option to delete records (and therefore movements) and restore stock levels

Ability to perform complex movements, loading, unloading, transfers, breakdowns of lists, etc. (for example, it is possible to unload all the components of a list or transfer them from one warehouse to another for production)

This module allow

*better organization and access to movements (for example, customized record numbering is possible)
*faster management
*deletion of records (and therefore ''movements'') with stock replenishment
*complex movements, loadings, unloadings, transfers, BOM explosions, etc. (for example, it is possible to unload all the components of a BOM or transfer them from one warehouse to another for production)

Other features include:

*Inventory management (a load or discharge is created to balance the current stocks)
*Allocation and related inventory management
*Stock analysis function by allocation/lot
*Ability to generate loading or unloading lines from an Excel spreadsheet (requires the Import from Excel module)

==Usage==

===Warehouse Reason Management===
Reasons allow you to define the behavior of recordings by defining the loading and/or unloading methods and the warehouses involved.

They can be of 3 types:

*Warehouse
*Orders (creating a reason from this family generates a new entry in the Shortcuts of the customer orders menu)
*Delivery Notes (creating a reason generates a new entry in the Shortcuts of the advanced shipping menu)

The definable parameters vary depending on the modules installed. They are:

'''Customer''' Used only if the Advanced Shipment module module is installed

'''Inventory''' Indicates whether the reason generates an inventory movement. The inventory generate a mouvement to a load or discharge a quantity to balance the current stocks

'''Loading Warehouse''' Warehouse where the goods are loaded (or origin if transfer)

'''Unloading Warehouse''' Unloading warehouse (or destination if transfer)

'''Move Allocations''' If you use allocation management, this parameter allows you to define the behavior when transferring materials between warehouses.

The possible values are:

''None:'' The allocation is not considered

''Both'': The allocation is transferred between warehouses

''Load'': Only the loading warehouse uses the allocation

''Unload'': The same applies to unloading

'''BOM Explosion''' '''upon loading''' If enabled and if the product is a finished product with a BOM, it explodes the BOM and loads all components

'''BOM Explosion for unloading''' The same applies to unloading. If both indicators are on, it is possible to transfer all the components of a list from one warehouse to another .

'''Use DDT Counter n.''' Used only if the [https://www.opigi.com/sito/documentation/advanced-shipments/ Advanced Shipment module] is installed. Refer to the specific document.

'''Exclude 1st row''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''Use supplier code''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''File Routine''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

==='''Allocation Management'''===
As mentioned, it is possible to manage the details of the allocations (departments, shelves, etc.) where the goods are stored within individual physical warehouses.

To enable this management, you must:

*Enable management in setup
*Create the list of allocations in a dedicated table in the dictionaries

For each movement line, the allocation will be requested

===Stock Analysis by Batch/Allocation===
The module’s side menu contains an item that allows you to access this list.

The available functions are the classic Dolibarr ones.

*

==='''Setup'''===
The module setup allows the following settings

*'''Display Description''' Allows you to display or hide product descriptions in the transaction lines.
*'''Use Allocations''' Enables/disables the allocation management described above.
*'''Hide Custom Fields''' Hides custom fields on transaction lines.

Finally, the page includes a [Recalculate Inventory] button that allows you to recalculate inventory, lots, and allocations based on current transactions.

==Note to programmers==
If the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed, the “''ExcelAddLine”'' hook is available which allows you to manage imports in complex situations.
[[Category:Complementary modules]]
__INDEX__

Third parties Processing

2026-03-05T12:50:35Z

Mgribaudo: Changed category

{{DISPLAYTITLE:Module Third parties Processing}}
{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM Third parties Processing
|editor=OPG
|web=www.opigi.com
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opg}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to manage the flow of materials and inventory in situations such as processing or repairing materials at third-party locations.

It consists of two phases:

*Upon shipment, new inventory at the third-party location is tracked.
*Upon return, the material can be deducted from previous shipments.

The result is traceability of material movements and inventory at the third-party location.

Requires the “''[https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse Management]''” and [https://www.opigi.com/sito/documentation/advanced-shipments/ “''Advanced Shipments''”] modules.

==Usage==
For management, you must create, in the “''[https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse Management]''” reason list, the reasons to be used for Opening (Sending of Material) and Closing (Return) of Shipments (DDT) for opening and closing.

These reasons must:

*be of the “''Shipping''” type
*use the “''Processing at Third Parties''” field, setting the value '''Opening:''' Can be used for shipments; the reported quantities increase the inventory at third parties '''Closing:''' Can be used for returns; the reported quantities decrease the inventory at third parties. 

Finally, upon activation of the module, a new menu item, “'''List of Processing at Third Parties''',” will be available on the shipments page. This item allows you to view movements and inventory.

Creating and deleting the DDT line using the aforementioned reason will create and delete inventory at third parties.

Note that when the last item is returned, the shipment line will be classified as closed.

==Setup==
There are no configuration parameters associated with the module.

__INDEX__
[[Category:Complementary modules]]

Third parties Processing

2026-03-05T12:44:43Z

Mgribaudo: Categorized

Third parties Processing

2026-03-05T12:44:10Z

Mgribaudo: Changed Title

{{DISPLAYTITLE:Module Third parties Processing}}
{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM Third parties Processing
|editor=OPG
|web=http:\\www.opigi.com
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opg}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to manage the flow of materials and inventory in situations such as processing or repairing materials at third-party locations.

It consists of two phases:

*Upon shipment, new inventory at the third-party location is tracked.
*Upon return, the material can be deducted from previous shipments.

The result is traceability of material movements and inventory at the third-party location.

Requires the “''[https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse Management]''” and [https://www.opigi.com/sito/documentation/advanced-shipments/ “''Advanced Shipments''”] modules.

==Usage==
For management, you must create, in the “''[https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse Management]''” reason list, the reasons to be used for Opening (Sending of Material) and Closing (Return) of Shipments (DDT) for opening and closing.

These reasons must:

*be of the “''Shipping''” type
*use the “''Processing at Third Parties''” field, setting the value '''Opening:''' Can be used for shipments; the reported quantities increase the inventory at third parties '''Closing:''' Can be used for returns; the reported quantities decrease the inventory at third parties. 

Finally, upon activation of the module, a new menu item, “'''List of Processing at Third Parties''',” will be available on the shipments page. This item allows you to view movements and inventory.

Creating and deleting the DDT line using the aforementioned reason will create and delete inventory at third parties.

Note that when the last item is returned, the shipment line will be classified as closed.

==Setup==
There are no configuration parameters associated with the module.
[[Category:Complementary module]]
__INDEX__

Third parties Processing

2026-03-05T12:42:53Z

Mgribaudo: Changed Title

{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM Third parties Processing
|editor=OPG
|web=www.opigi.com
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opg}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to manage the flow of materials and inventory in situations such as processing or repairing materials at third-party locations.

It consists of two phases:

*Upon shipment, new inventory at the third-party location is tracked.
*Upon return, the material can be deducted from previous shipments.

The result is traceability of material movements and inventory at the third-party location.

Requires the “''[https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse Management]''” and [https://www.opigi.com/sito/documentation/advanced-shipments/ “''Advanced Shipments''”] modules.

==Usage==
For management, you must create, in the “''[https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse Management]''” reason list, the reasons to be used for Opening (Sending of Material) and Closing (Return) of Shipments (DDT) for opening and closing.

These reasons must:

*be of the “''Shipping''” type
*use the “''Processing at Third Parties''” field, setting the value '''Opening:''' Can be used for shipments; the reported quantities increase the inventory at third parties '''Closing:''' Can be used for returns; the reported quantities decrease the inventory at third parties. 

Finally, upon activation of the module, a new menu item, “'''List of Processing at Third Parties''',” will be available on the shipments page. This item allows you to view movements and inventory.

Creating and deleting the DDT line using the aforementioned reason will create and delete inventory at third parties.

Note that when the last item is returned, the shipment line will be classified as closed.

==Setup==
There are no configuration parameters associated with the module.
[[Category:Complementary module]]

Custom labels

2026-03-05T12:37:20Z

Mgribaudo: Changed Title

{{DISPLAYTITLE:Module Custom labels}}
{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM Custom Labels
|editor=OPG
|web=www.opigi.com
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opg}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to define labels relating to products and then print them on thermal printers.

It allows you to configure different type of labels that can contain information:

– related to a product (code, description, supplier, batch, etc.)

– defined at the time of printing (e.g. the batch when printing a delivery note)

– derived from other archives (product master data, third-party providers, etc.)

In case of presence of multiple thermal printers inside the warehouse, each label type can be addressed to a specific printer, or the same label can be addressed to different printers for different users.

These labels can be:

*printed extemporaneously when needed
*printed automatically when orders are placed (customers and suppliers), supplier invoices are received and delivery notes are issue. In this case, a copy of the label will be printed for each individual product in the document.

It assumes the ability to generate labels in the various languages (ZPL, EPL, FGL, ESC / POS, EPCL, ….) in which labels can be programmed. For this purpose, some printer suppliers provide programs (eg ZDesigner for Zebra printers) that can generate labels in a simple and intuitive way.

==Usage==
The setup and label definition phase is crucial for the use of the module, so it is best to carry out these operations carefully before proceeding with printing.

===Manual printing of labels===
To obtain manual printing, select the “''Tools”'' item in the main menu and then the “''Custom labels''” item, the list of available labels is shown.

Upon selecting the desired label, a page will allow you to enter the necessary data and define the number of labels you want to print.
[[File:Custom Label1.png|thumb]]
 

===Printing of labels from document (Orders, Shipments, Invoicess)===
If, during the setup phase, the label to be used in the specific document (orders, invoices, shipments, …) was selected, a new button will be proposed,

this will allow you to print the labels relating to the document itself.

Depending on the setting of the other parameter “Request for label date in DDT / Orders”, the page that allows you to modify or complete the label data before printing them will be displayed or not.

==Module configuration==

===Settings===
The following information must be entered:
[[File:Custom Label2.png|thumb]]
'''Connector Used''': Allows you to select the connector used.

Here you can select one of the two connectors described below, or, by leaving the field blank, use printer addressing via IP. This latter option requires greater technical expertise and likely requires the intervention of a systems engineer.

'''Label Printer Name or IP Address:''' Contains:

*the name of the “Print Type” in the case of using the “''Webapp Hardware Bridge''” (see later)
*the network name or IP address assigned to the printer.
*if the value is instead left blank (this is the case in which the PHP Socket extension has not been enabled or printers cannot be reached with an IP address), the printing of each label is preceded by a printer selection window; it is understandable how having to confirm this page slows down the functionality of the module considerably, in this situation the correct functioning of the module is also not guaranteed with all thermal printers on the market.

It is therefore recommended, for optimal operation of the module, to connect the thermal printer via one of the two connectors.

'''Label used in … (Expeditions/Invoices/Receptions/Orders)'''

For each of the documents for which labels can be generated, it allows you to define which, among the various defined labels, is used at the time of issuing the document .

Associating a document type with a particular label causes a button for printing labels to appear in the document form.

====Using the Label Dispatcher====
This is the simplest option if you have a Windows terminal on your local network that can see the printers you want to use.

This application can be downloaded [https://www.opigi.com/download/Install%20Label%20Disptcher%201.0.exe from here] and offers the following advantages over the first one:

*Multiple label printers can be used
*The same label can be redirected to a different printer for each user[[File:Labels-Dispatcher.png|thumb]]

The connector must be configured by entering the following two parameters:

'''Server URL''': Contains the URL to point to the Dolibarr API (usually <code><mydolibarrURL>/htdocs/api/index.php</code>)

'''Api Key''': Contains the API key of one of the Dolibarr users with permissions to access the various documents

====Using the Webapp Hardware Bridge connector====
This is the option that allows you to address printers even in local Linux networks.

The Webapp Hardware Bridge connector application can be [https://github.com/imTigger/webapp-hardware-bridge/releases/download/0.14.0/whb-0.14.0.exe downloaded and installed] on all clients using the module.

Its use, through a [https://www.youtube.com/watch?v=RHFC3dtMBe4 simple configuration procedure], allows to considerably simplify the addressing phase of the printers, and does not require any technical skills.
[[File:Custom Label3.png|thumb]]
If you opt for this option, it will be sufficient to associate a “''Printer Type''” to the label printer in the connector setup window (as in the following image) and then indicate the same value in the Setting field “''Label Printer Name or IP Address''” (in the two images, the previous and the following one, the '''RETE''' value)

===Custom labels definition (label structure)===
As mentioned it is necessary, for each of the labels to be defined, to generate a text file in one of the standard languages used by thermal printers (ZPL, EPL, FGL, ESC / POS, EPCL, ….), for this purpose the hardware manufacturers generally make label design programs available, in the absence of these it is necessary to manually define the label using the syntax of the specific language.

It is important in this phase to define the “'''''placeholders'''''” where you want the values taken from the database to be entered, when the labels are printed.

These placeholders are identified by inserting the strings [param1], [param2], … [paramn] in the text of the label, these strings will be associated with the database fields when defining the label fields, an operation described in the following paragraph.
[[File:Custom Label4.png|thumb]]
The figure illustrates a placeholder label generated by the [https://www.youtube.com/watch?v=sdXt7D6xZoo ZDesigner] program for Zebra printers.

'''''ZDesigner tips''''' ''As regards the generation of the file with the ZDesigner, to obtain the necessary text file, follow the path “File>>Print”, turn on the “Print to File” checkbox and press the [Print] button. The obtained file (.prn) must be sent to the module.''

''Not all fonts are converted into text by Zdesigner, some are transformed into images and therefore the module is not able to replace the content. It is therefore advisable to open the .prn file with a text editor and check the presence of the text of all the placeholders ([param1], [param2], .…). If the strings are not present, you need to change the font of the placeholders.''

===Custom labels definition (label’s fields)===
The second phase required for the definition of the label is that which, as shown in the figure, allows you to:

*associate the previously defined text file to the label
*associate each of the previously defined placeholders with a label field.

For this purposeyou need to access the module setup and use the [Custom labels] tab.

From here, you can enter the list of label types you want to use, each label contains a set of general information and a set of information specific to each placeholder.

The general informations are:

'''Title''' Indicate here the title you want to assign to the specific label

'''Type''' Allows you to define the type of label to be printed, there are three types of labels:

. '''Third Parties''' To print, from the tools menu, information relating to a third party

. '''Products''' To print, from the tools menu, information relating to a product

. '''Advanced''' To print labels from various documents (offers, orders, invoices, …)

'''Content of the label''' From here you can upload the previously generated text file for the label (see previous paragraph)
[[File:Custom Label5.png|thumb]]
For each placeholder the following information must be defined:

'''Position''': It is the position that identifies the placeholder number as defined in the label text.

For example, by entering the value 2 here, the text [param2] of the label will be replaced with the value of the database field identified by the “Type” parameter (described below) itto)

'''Label''': Contains a description of the field

'''Type'''; Allows you to define the specific database value that will be used to replace the placeholder. The associated list allows you to report one of the following values:

*'''Text''' When the label is printed, it allows you to manually enter a text string that will be printed on the label. This field, together with the two that follow, makes no sense if the label must be automatically printed at the time of the order or DDT
*'''Number''' When the label is printed, it allows you to manually enter a numerical value that will be printed on the label.
*'''Date''' When the label is printed, it allows you to manually enter a date that will be printed on the label.
*'''Product Code''' On the label, instead of the placeholder, the code of the selected product will be printed.
*'''Product Description''' The product description will be printed instead of the placeholder.
*'''Product Barcode''' The product barcode is printed.
*'''Third Party Code''' The third party code is printed.
*'''Batch''' The batch of the product is printed.
*'''Batch expiration date''' The expiration date for the batchis printed.
*'''Third Party''' The company name of the third party is printed
*'''Quantity''' Contains the quantity of products indicated in the document. If this particular type is present on the label, only one label will be printed showing the quantity, otherwise n (n = quantity of the document products) different labels will be printed
*'''Custom fields'''It allows you to manage the printing of other fields, these fields are defined through functions that can be created in the file <code><kbd>“customlabels/lib/customlabels.lib.php”</kbd></code> This file contains examples for creating functions

[[File:Custom Label6.png|thumb]]
For example, having defined the placeholder [param2] in the text of the label, and having defined a label item as shown in the following figure, this placeholder will bereplaced, when the label is printed, with the description of the product
[[Category:Complementary modules]]
__INDEX__

Custom labels

2026-03-05T12:34:40Z

Mgribaudo: Changed category

{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM Custom Labels
|editor=OPG
|web=www.opigi.com
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opigi}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to define labels relating to products and then print them on thermal printers.

It allows you to configure different type of labels that can contain information:

– related to a product (code, description, supplier, batch, etc.)

– defined at the time of printing (e.g. the batch when printing a delivery note)

– derived from other archives (product master data, third-party providers, etc.)

In case of presence of multiple thermal printers inside the warehouse, each label type can be addressed to a specific printer, or the same label can be addressed to different printers for different users.

These labels can be:

*printed extemporaneously when needed
*printed automatically when orders are placed (customers and suppliers), supplier invoices are received and delivery notes are issue. In this case, a copy of the label will be printed for each individual product in the document.

It assumes the ability to generate labels in the various languages (ZPL, EPL, FGL, ESC / POS, EPCL, ….) in which labels can be programmed. For this purpose, some printer suppliers provide programs (eg ZDesigner for Zebra printers) that can generate labels in a simple and intuitive way.

==Usage==
The setup and label definition phase is crucial for the use of the module, so it is best to carry out these operations carefully before proceeding with printing.

===Manual printing of labels===
To obtain manual printing, select the “''Tools”'' item in the main menu and then the “''Custom labels''” item, the list of available labels is shown.

Upon selecting the desired label, a page will allow you to enter the necessary data and define the number of labels you want to print.
[[File:Custom Label1.png|thumb]]
 

===Printing of labels from document (Orders, Shipments, Invoicess)===
If, during the setup phase, the label to be used in the specific document (orders, invoices, shipments, …) was selected, a new button will be proposed,

this will allow you to print the labels relating to the document itself.

Depending on the setting of the other parameter “Request for label date in DDT / Orders”, the page that allows you to modify or complete the label data before printing them will be displayed or not.

==Module configuration==

===Settings===
The following information must be entered:
[[File:Custom Label2.png|thumb]]
'''Connector Used''': Allows you to select the connector used.

Here you can select one of the two connectors described below, or, by leaving the field blank, use printer addressing via IP. This latter option requires greater technical expertise and likely requires the intervention of a systems engineer.

'''Label Printer Name or IP Address:''' Contains:

*the name of the “Print Type” in the case of using the “''Webapp Hardware Bridge''” (see later)
*the network name or IP address assigned to the printer.
*if the value is instead left blank (this is the case in which the PHP Socket extension has not been enabled or printers cannot be reached with an IP address), the printing of each label is preceded by a printer selection window; it is understandable how having to confirm this page slows down the functionality of the module considerably, in this situation the correct functioning of the module is also not guaranteed with all thermal printers on the market.

It is therefore recommended, for optimal operation of the module, to connect the thermal printer via one of the two connectors.

'''Label used in … (Expeditions/Invoices/Receptions/Orders)'''

For each of the documents for which labels can be generated, it allows you to define which, among the various defined labels, is used at the time of issuing the document .

Associating a document type with a particular label causes a button for printing labels to appear in the document form.

====Using the Label Dispatcher====
This is the simplest option if you have a Windows terminal on your local network that can see the printers you want to use.

This application can be downloaded [https://www.opigi.com/download/Install%20Label%20Disptcher%201.0.exe from here] and offers the following advantages over the first one:

*Multiple label printers can be used
*The same label can be redirected to a different printer for each user[[File:Labels-Dispatcher.png|thumb]]

The connector must be configured by entering the following two parameters:

'''Server URL''': Contains the URL to point to the Dolibarr API (usually <code><mydolibarrURL>/htdocs/api/index.php</code>)

'''Api Key''': Contains the API key of one of the Dolibarr users with permissions to access the various documents

====Using the Webapp Hardware Bridge connector====
This is the option that allows you to address printers even in local Linux networks.

The Webapp Hardware Bridge connector application can be [https://github.com/imTigger/webapp-hardware-bridge/releases/download/0.14.0/whb-0.14.0.exe downloaded and installed] on all clients using the module.

Its use, through a [https://www.youtube.com/watch?v=RHFC3dtMBe4 simple configuration procedure], allows to considerably simplify the addressing phase of the printers, and does not require any technical skills.
[[File:Custom Label3.png|thumb]]
If you opt for this option, it will be sufficient to associate a “''Printer Type''” to the label printer in the connector setup window (as in the following image) and then indicate the same value in the Setting field “''Label Printer Name or IP Address''” (in the two images, the previous and the following one, the '''RETE''' value)

===Custom labels definition (label structure)===
As mentioned it is necessary, for each of the labels to be defined, to generate a text file in one of the standard languages used by thermal printers (ZPL, EPL, FGL, ESC / POS, EPCL, ….), for this purpose the hardware manufacturers generally make label design programs available, in the absence of these it is necessary to manually define the label using the syntax of the specific language.

It is important in this phase to define the “'''''placeholders'''''” where you want the values taken from the database to be entered, when the labels are printed.

These placeholders are identified by inserting the strings [param1], [param2], … [paramn] in the text of the label, these strings will be associated with the database fields when defining the label fields, an operation described in the following paragraph.
[[File:Custom Label4.png|thumb]]
The figure illustrates a placeholder label generated by the [https://www.youtube.com/watch?v=sdXt7D6xZoo ZDesigner] program for Zebra printers.

'''''ZDesigner tips''''' ''As regards the generation of the file with the ZDesigner, to obtain the necessary text file, follow the path “File>>Print”, turn on the “Print to File” checkbox and press the [Print] button. The obtained file (.prn) must be sent to the module.''

''Not all fonts are converted into text by Zdesigner, some are transformed into images and therefore the module is not able to replace the content. It is therefore advisable to open the .prn file with a text editor and check the presence of the text of all the placeholders ([param1], [param2], .…). If the strings are not present, you need to change the font of the placeholders.''

===Custom labels definition (label’s fields)===
The second phase required for the definition of the label is that which, as shown in the figure, allows you to:

*associate the previously defined text file to the label
*associate each of the previously defined placeholders with a label field.

For this purposeyou need to access the module setup and use the [Custom labels] tab.

From here, you can enter the list of label types you want to use, each label contains a set of general information and a set of information specific to each placeholder.

The general informations are:

'''Title''' Indicate here the title you want to assign to the specific label

'''Type''' Allows you to define the type of label to be printed, there are three types of labels:

. '''Third Parties''' To print, from the tools menu, information relating to a third party

. '''Products''' To print, from the tools menu, information relating to a product

. '''Advanced''' To print labels from various documents (offers, orders, invoices, …)

'''Content of the label''' From here you can upload the previously generated text file for the label (see previous paragraph)
[[File:Custom Label5.png|thumb]]
For each placeholder the following information must be defined:

'''Position''': It is the position that identifies the placeholder number as defined in the label text.

For example, by entering the value 2 here, the text [param2] of the label will be replaced with the value of the database field identified by the “Type” parameter (described below) itto)

'''Label''': Contains a description of the field

'''Type'''; Allows you to define the specific database value that will be used to replace the placeholder. The associated list allows you to report one of the following values:

*'''Text''' When the label is printed, it allows you to manually enter a text string that will be printed on the label. This field, together with the two that follow, makes no sense if the label must be automatically printed at the time of the order or DDT
*'''Number''' When the label is printed, it allows you to manually enter a numerical value that will be printed on the label.
*'''Date''' When the label is printed, it allows you to manually enter a date that will be printed on the label.
*'''Product Code''' On the label, instead of the placeholder, the code of the selected product will be printed.
*'''Product Description''' The product description will be printed instead of the placeholder.
*'''Product Barcode''' The product barcode is printed.
*'''Third Party Code''' The third party code is printed.
*'''Batch''' The batch of the product is printed.
*'''Batch expiration date''' The expiration date for the batchis printed.
*'''Third Party''' The company name of the third party is printed
*'''Quantity''' Contains the quantity of products indicated in the document. If this particular type is present on the label, only one label will be printed showing the quantity, otherwise n (n = quantity of the document products) different labels will be printed
*'''Custom fields'''It allows you to manage the printing of other fields, these fields are defined through functions that can be created in the file <code><kbd>“customlabels/lib/customlabels.lib.php”</kbd></code> This file contains examples for creating functions

[[File:Custom Label6.png|thumb]]
For example, having defined the placeholder [param2] in the text of the label, and having defined a label item as shown in the following figure, this placeholder will bereplaced, when the label is printed, with the description of the product
[[Category:Complementary Modules]]

Supplier Return

2026-03-05T12:32:18Z

Mgribaudo: Changed Title

{{DISPLAYTITLE:Module Supplier Return}}
{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM Supplier Return
|editor=OPG
|web=www.opigi.com
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opigi}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to quickly and easily manage returns of goods to suppliers.

There are two ways to perform these operations, which differ in their operational logic and the results obtained:

'''Goods Shipping Mode (only together with the the [https://www.opigi.com/sito/documentation/advanced-shipments/ Advanced Shipments module])'''

Management is activated when the goods are shipped, using the standard Dolibarr shipping module.

This mode is simpler and faster, and also uses the standard expedition document.

'''Tabular Mode'''

Management requires an item to appear in the main menu. Returns are managed, similarly to other Dolibarr documents, through a dedicated management system and printed using a specific layout.

This mode allows for more comprehensive returns management.

==Usage==

===Goods Shipping Mode===
In this mode, the shipment page contains a [''Create shipment from reception''] button. Pressing this button allows you to generate a shipment for the specified material.

The unloading movements are generated upon shipment confirmation.

===Tabular Mode===
In this mode, a main menu item allows you to manage returns in a manner similar to that of other standard documents (status, notes, documents, etc.).

The unloading movements are generated upon return processing.

Some of the module’s specific features are listed below:

*the “''Create From Reception''” menu item allows you to create a return for a specific shipment.
*the setup includes a table of reasons that can be associated with each return.
*only products purchasable from the supplier can be used.

==Setup==
In addition to the usual parameters for defining document numbering (used only in the Tabular mode), the following parameter is available:

'''Turn returns into shipments:''' This parameter allows you to enable the “Goods Shipping mode” (if On) or the “Tabular mode” (if Off).

Attention! The “Export” module must be enabled to use the “Goods Shipping mode”.

As mentioned previously, the setup page includes the “Return Reasons” section, which allows you to create the specific table (used only in the Tabular mode).
[[Category:Complementary modules]]
__INDEX__

Advanced Shipments

2026-03-05T12:29:26Z

Mgribaudo: Changed Title

{{DISPLAYTITLE:Module Advanced Shipments}}
{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM Advanced shipment
|editor=OPG
|web=www.opigi.com
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opg}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], improves the shipping management, introducing the following possibilities not present in the standard shipping functions.

*enter new shipments directly, '''overcoming the need to switch from the sales order'''
*complete row management (similar to all other documents in Dolibarr)
*possibility of sending material and generating the transfer document '''also for suppliers''' and not only for customers (returns to suppliers, sending to subcontractors for processing, …)
*material transfer between 2 warehouses (internal management of the warehouse on behalf of contractors, …)
*possibility of using '''multiple numbering''' (if the [https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse module] is installed)

All other functions (invoicing from shipment, management of statuses, printing of documents, ….) reflect those of shipments (*).

==Using the form==
Upon installation, a new item is added to the main menu.

From this you access the list of shipments (only generated by the module), the remaining operation is the standard Dolibarr one.

On the other hand, by accessing the list of standard shipments, all shipments (advanced and not) will be displayed.

===Setup===
The module has no parameters
[[Category:Complementary modules]]
__INDEX__

Advanced warehouse management

2026-03-05T12:27:48Z

Mgribaudo: Changed Title

{{DISPLAYTITLE:Module Advanced warehouse management}}
{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM warehouse movement management
|editor=OPG
|web=www.opigi.com
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opg}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM projec]t, integrate and improve warehouse movement management.

Movements are managed through “''Warehouse movements''” identified by:

*a reason that defines their characteristics (loading and/or unloading warehouse, bom explosion, etc.).
*n lines that correspond to the individual warehouse movements.

This organization allows for::

*a better organization and access to movements (for example, customized numbering of records is possible)
*faster management: the warehouse is pre-set and there is the option to delete records (and therefore movements) and restore stock levels

Ability to perform complex movements, loading, unloading, transfers, breakdowns of lists, etc. (for example, it is possible to unload all the components of a list or transfer them from one warehouse to another for production)

This module allow

*better organization and access to movements (for example, customized record numbering is possible)
*faster management
*deletion of records (and therefore ''movements'') with stock replenishment
*complex movements, loadings, unloadings, transfers, BOM explosions, etc. (for example, it is possible to unload all the components of a BOM or transfer them from one warehouse to another for production)

Other features include:

*Inventory management (a load or discharge is created to balance the current stocks)
*Allocation and related inventory management
*Stock analysis function by allocation/lot
*Ability to generate loading or unloading lines from an Excel spreadsheet (requires the Import from Excel module)

==Usage==

===Warehouse Reason Management===
Reasons allow you to define the behavior of recordings by defining the loading and/or unloading methods and the warehouses involved.

They can be of 3 types:

*Warehouse
*Orders (creating a reason from this family generates a new entry in the Shortcuts of the customer orders menu)
*Delivery Notes (creating a reason generates a new entry in the Shortcuts of the advanced shipping menu)

The definable parameters vary depending on the modules installed. They are:

'''Customer''' Used only if the Advanced Shipment module module is installed

'''Inventory''' Indicates whether the reason generates an inventory movement. The inventory generate a mouvement to a load or discharge a quantity to balance the current stocks

'''Loading Warehouse''' Warehouse where the goods are loaded (or origin if transfer)

'''Unloading Warehouse''' Unloading warehouse (or destination if transfer)

'''BOM Explosion''' '''upon loading''' If enabled and if the product is a finished product with a BOM, it explodes the BOM and loads all components

'''BOM Explosion for unloading''' The same applies to unloading. If both indicators are on, it is possible to transfer all the components of a list from one warehouse to another .

'''Use DDT Counter n.''' Used only if the [https://www.opigi.com/sito/documentation/advanced-shipments/ Advanced Shipment module] is installed. Refer to the specific document.

'''Exclude 1st row''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''Use supplier code''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''File Routine''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

==='''Allocation Management'''===
As mentioned, it is possible to manage the details of the allocations (departments, shelves, etc.) where the goods are stored within individual physical warehouses.

To enable this management, you must:

*Enable management in setup
*Create the list of allocations in a dedicated table in the dictionaries

For each movement line, the allocation will be requested

===Stock Analysis by Batch/Allocation===
The module’s side menu contains an item that allows you to access this list.

The available functions are the classic Dolibarr ones.

*

==='''Setup'''===
The module setup allows the following settings

*'''Display Description''' Allows you to display or hide product descriptions in the transaction lines.
*'''Use Allocations''' Enables/disables the allocation management described above.
*'''Hide Custom Fields''' Hides custom fields on transaction lines.

Finally, the page includes a [Recalculate Inventory] button that allows you to recalculate inventory, lots, and allocations based on current transactions.

==Note to programmers==
If the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed, the “''ExcelAddLine”'' hook is available which allows you to manage imports in complex situations.
[[Category:Complementary modules]]
__INDEX__

Advanced Shipments

2026-03-05T12:25:42Z

Mgribaudo: Changed category

{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM Advanced shipment
|editor=OPG
|web=www.opigi.com
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opg}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], improves the shipping management, introducing the following possibilities not present in the standard shipping functions.

*enter new shipments directly, '''overcoming the need to switch from the sales order'''
*complete row management (similar to all other documents in Dolibarr)
*possibility of sending material and generating the transfer document '''also for suppliers''' and not only for customers (returns to suppliers, sending to subcontractors for processing, …)
*material transfer between 2 warehouses (internal management of the warehouse on behalf of contractors, …)
*possibility of using '''multiple numbering''' (if the [https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse module] is installed)

All other functions (invoicing from shipment, management of statuses, printing of documents, ….) reflect those of shipments (*).

==Using the form==
Upon installation, a new item is added to the main menu.

From this you access the list of shipments (only generated by the module), the remaining operation is the standard Dolibarr one.

On the other hand, by accessing the list of standard shipments, all shipments (advanced and not) will be displayed.

===Setup===
The module has no parameters
[[Category:Complementary modules]]

Advanced Shipments

2026-03-05T12:24:44Z

Mgribaudo: Changed category

Advanced Shipments

2026-03-05T12:23:42Z

Mgribaudo:

Advanced warehouse management

2026-03-05T12:19:37Z

Mgribaudo: modified link

{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM warehouse movement management
|editor=OPG
|web=www.opigi.com
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opg}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM projec]t, integrate and improve warehouse movement management.

Movements are managed through “''Warehouse movements''” identified by:

*a reason that defines their characteristics (loading and/or unloading warehouse, bom explosion, etc.).
*n lines that correspond to the individual warehouse movements.

This organization allows for::

*a better organization and access to movements (for example, customized numbering of records is possible)
*faster management: the warehouse is pre-set and there is the option to delete records (and therefore movements) and restore stock levels

Ability to perform complex movements, loading, unloading, transfers, breakdowns of lists, etc. (for example, it is possible to unload all the components of a list or transfer them from one warehouse to another for production)

This module allow

*better organization and access to movements (for example, customized record numbering is possible)
*faster management
*deletion of records (and therefore ''movements'') with stock replenishment
*complex movements, loadings, unloadings, transfers, BOM explosions, etc. (for example, it is possible to unload all the components of a BOM or transfer them from one warehouse to another for production)

Other features include:

*Inventory management (a load or discharge is created to balance the current stocks)
*Allocation and related inventory management
*Stock analysis function by allocation/lot
*Ability to generate loading or unloading lines from an Excel spreadsheet (requires the Import from Excel module)

==Usage==

===Warehouse Reason Management===
Reasons allow you to define the behavior of recordings by defining the loading and/or unloading methods and the warehouses involved.

They can be of 3 types:

*Warehouse
*Orders (creating a reason from this family generates a new entry in the Shortcuts of the customer orders menu)
*Delivery Notes (creating a reason generates a new entry in the Shortcuts of the advanced shipping menu)

The definable parameters vary depending on the modules installed. They are:

'''Customer''' Used only if the Advanced Shipment module module is installed

'''Inventory''' Indicates whether the reason generates an inventory movement. The inventory generate a mouvement to a load or discharge a quantity to balance the current stocks

'''Loading Warehouse''' Warehouse where the goods are loaded (or origin if transfer)

'''Unloading Warehouse''' Unloading warehouse (or destination if transfer)

'''BOM Explosion''' '''upon loading''' If enabled and if the product is a finished product with a BOM, it explodes the BOM and loads all components

'''BOM Explosion for unloading''' The same applies to unloading. If both indicators are on, it is possible to transfer all the components of a list from one warehouse to another .

'''Use DDT Counter n.''' Used only if the [https://www.opigi.com/sito/documentation/advanced-shipments/ Advanced Shipment module] is installed. Refer to the specific document.

'''Exclude 1st row''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''Use supplier code''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''File Routine''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

==='''Allocation Management'''===
As mentioned, it is possible to manage the details of the allocations (departments, shelves, etc.) where the goods are stored within individual physical warehouses.

To enable this management, you must:

*Enable management in setup
*Create the list of allocations in a dedicated table in the dictionaries

For each movement line, the allocation will be requested

===Stock Analysis by Batch/Allocation===
The module’s side menu contains an item that allows you to access this list.

The available functions are the classic Dolibarr ones.

*

==='''Setup'''===
The module setup allows the following settings

*'''Display Description''' Allows you to display or hide product descriptions in the transaction lines.
*'''Use Allocations''' Enables/disables the allocation management described above.
*'''Hide Custom Fields''' Hides custom fields on transaction lines.

Finally, the page includes a [Recalculate Inventory] button that allows you to recalculate inventory, lots, and allocations based on current transactions.

==Note to programmers==
If the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed, the “''ExcelAddLine”'' hook is available which allows you to manage imports in complex situations.
[[Category:Complementary modules]]
__INDEX__

Advanced warehouse management

2026-03-05T12:17:32Z

Mgribaudo: Added editor

{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM warehouse movement management
|editor=OPG
|web=www.opigi.com
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opigi}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM projec]t, integrate and improve warehouse movement management.

Movements are managed through “''Warehouse movements''” identified by:

*a reason that defines their characteristics (loading and/or unloading warehouse, bom explosion, etc.).
*n lines that correspond to the individual warehouse movements.

This organization allows for::

*a better organization and access to movements (for example, customized numbering of records is possible)
*faster management: the warehouse is pre-set and there is the option to delete records (and therefore movements) and restore stock levels

Ability to perform complex movements, loading, unloading, transfers, breakdowns of lists, etc. (for example, it is possible to unload all the components of a list or transfer them from one warehouse to another for production)

This module allow

*better organization and access to movements (for example, customized record numbering is possible)
*faster management
*deletion of records (and therefore ''movements'') with stock replenishment
*complex movements, loadings, unloadings, transfers, BOM explosions, etc. (for example, it is possible to unload all the components of a BOM or transfer them from one warehouse to another for production)

Other features include:

*Inventory management (a load or discharge is created to balance the current stocks)
*Allocation and related inventory management
*Stock analysis function by allocation/lot
*Ability to generate loading or unloading lines from an Excel spreadsheet (requires the Import from Excel module)

==Usage==

===Warehouse Reason Management===
Reasons allow you to define the behavior of recordings by defining the loading and/or unloading methods and the warehouses involved.

They can be of 3 types:

*Warehouse
*Orders (creating a reason from this family generates a new entry in the Shortcuts of the customer orders menu)
*Delivery Notes (creating a reason generates a new entry in the Shortcuts of the advanced shipping menu)

The definable parameters vary depending on the modules installed. They are:

'''Customer''' Used only if the Advanced Shipment module module is installed

'''Inventory''' Indicates whether the reason generates an inventory movement. The inventory generate a mouvement to a load or discharge a quantity to balance the current stocks

'''Loading Warehouse''' Warehouse where the goods are loaded (or origin if transfer)

'''Unloading Warehouse''' Unloading warehouse (or destination if transfer)

'''BOM Explosion''' '''upon loading''' If enabled and if the product is a finished product with a BOM, it explodes the BOM and loads all components

'''BOM Explosion for unloading''' The same applies to unloading. If both indicators are on, it is possible to transfer all the components of a list from one warehouse to another .

'''Use DDT Counter n.''' Used only if the [https://www.opigi.com/sito/documentation/advanced-shipments/ Advanced Shipment module] is installed. Refer to the specific document.

'''Exclude 1st row''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''Use supplier code''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''File Routine''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

==='''Allocation Management'''===
As mentioned, it is possible to manage the details of the allocations (departments, shelves, etc.) where the goods are stored within individual physical warehouses.

To enable this management, you must:

*Enable management in setup
*Create the list of allocations in a dedicated table in the dictionaries

For each movement line, the allocation will be requested

===Stock Analysis by Batch/Allocation===
The module’s side menu contains an item that allows you to access this list.

The available functions are the classic Dolibarr ones.

*

==='''Setup'''===
The module setup allows the following settings

*'''Display Description''' Allows you to display or hide product descriptions in the transaction lines.
*'''Use Allocations''' Enables/disables the allocation management described above.
*'''Hide Custom Fields''' Hides custom fields on transaction lines.

Finally, the page includes a [Recalculate Inventory] button that allows you to recalculate inventory, lots, and allocations based on current transactions.

==Note to programmers==
If the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed, the “''ExcelAddLine”'' hook is available which allows you to manage imports in complex situations.
[[Category:Complementary modules]]
__INDEX__

Advanced warehouse management

2026-03-05T12:14:51Z

Mgribaudo:

{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM warehouse movement management
|editor=DOLYWM
|web=
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opigi}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM projec]t, integrate and improve warehouse movement management.

Movements are managed through “''Warehouse movements''” identified by:

*a reason that defines their characteristics (loading and/or unloading warehouse, bom explosion, etc.).
*n lines that correspond to the individual warehouse movements.

This organization allows for::

*a better organization and access to movements (for example, customized numbering of records is possible)
*faster management: the warehouse is pre-set and there is the option to delete records (and therefore movements) and restore stock levels

Ability to perform complex movements, loading, unloading, transfers, breakdowns of lists, etc. (for example, it is possible to unload all the components of a list or transfer them from one warehouse to another for production)

This module allow

*better organization and access to movements (for example, customized record numbering is possible)
*faster management
*deletion of records (and therefore ''movements'') with stock replenishment
*complex movements, loadings, unloadings, transfers, BOM explosions, etc. (for example, it is possible to unload all the components of a BOM or transfer them from one warehouse to another for production)

Other features include:

*Inventory management (a load or discharge is created to balance the current stocks)
*Allocation and related inventory management
*Stock analysis function by allocation/lot
*Ability to generate loading or unloading lines from an Excel spreadsheet (requires the Import from Excel module)

==Usage==

===Warehouse Reason Management===
Reasons allow you to define the behavior of recordings by defining the loading and/or unloading methods and the warehouses involved.

They can be of 3 types:

*Warehouse
*Orders (creating a reason from this family generates a new entry in the Shortcuts of the customer orders menu)
*Delivery Notes (creating a reason generates a new entry in the Shortcuts of the advanced shipping menu)

The definable parameters vary depending on the modules installed. They are:

'''Customer''' Used only if the Advanced Shipment module module is installed

'''Inventory''' Indicates whether the reason generates an inventory movement. The inventory generate a mouvement to a load or discharge a quantity to balance the current stocks

'''Loading Warehouse''' Warehouse where the goods are loaded (or origin if transfer)

'''Unloading Warehouse''' Unloading warehouse (or destination if transfer)

'''BOM Explosion''' '''upon loading''' If enabled and if the product is a finished product with a BOM, it explodes the BOM and loads all components

'''BOM Explosion for unloading''' The same applies to unloading. If both indicators are on, it is possible to transfer all the components of a list from one warehouse to another .

'''Use DDT Counter n.''' Used only if the [https://www.opigi.com/sito/documentation/advanced-shipments/ Advanced Shipment module] is installed. Refer to the specific document.

'''Exclude 1st row''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''Use supplier code''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''File Routine''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

==='''Allocation Management'''===
As mentioned, it is possible to manage the details of the allocations (departments, shelves, etc.) where the goods are stored within individual physical warehouses.

To enable this management, you must:

*Enable management in setup
*Create the list of allocations in a dedicated table in the dictionaries

For each movement line, the allocation will be requested

===Stock Analysis by Batch/Allocation===
The module’s side menu contains an item that allows you to access this list.

The available functions are the classic Dolibarr ones.

*

==='''Setup'''===
The module setup allows the following settings

*'''Display Description''' Allows you to display or hide product descriptions in the transaction lines.
*'''Use Allocations''' Enables/disables the allocation management described above.
*'''Hide Custom Fields''' Hides custom fields on transaction lines.

Finally, the page includes a [Recalculate Inventory] button that allows you to recalculate inventory, lots, and allocations based on current transactions.

==Note to programmers==
If the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed, the “''ExcelAddLine”'' hook is available which allows you to manage imports in complex situations.
[[Category:Complementary modules]]
__INDEX__

Supplier Return

2026-03-04T09:29:38Z

Mgribaudo: Changed category

{{TemplateDocDevEn}}
{{TemplateDocUser}}
=Informations=
{{TemplateModuleInfo
|modulename=DOLYWM Supplier Return
|editor=DOLYWM
|web=
|webbuy={{LinkToPluginDownloadDoliStore|keyword=opigi}}
|status=Stable
|prerequisites=
|minversion=
|note=
}}

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to quickly and easily manage returns of goods to suppliers.

There are two ways to perform these operations, which differ in their operational logic and the results obtained:

'''Goods Shipping Mode (only together with the the [https://www.opigi.com/sito/documentation/advanced-shipments/ Advanced Shipments module])'''

Management is activated when the goods are shipped, using the standard Dolibarr shipping module.

This mode is simpler and faster, and also uses the standard expedition document.

'''Tabular Mode'''

Management requires an item to appear in the main menu. Returns are managed, similarly to other Dolibarr documents, through a dedicated management system and printed using a specific layout.

This mode allows for more comprehensive returns management.

==Usage==

===Goods Shipping Mode===
In this mode, the shipment page contains a [''Create shipment from reception''] button. Pressing this button allows you to generate a shipment for the specified material.

The unloading movements are generated upon shipment confirmation.

===Tabular Mode===
In this mode, a main menu item allows you to manage returns in a manner similar to that of other standard documents (status, notes, documents, etc.).

The unloading movements are generated upon return processing.

Some of the module’s specific features are listed below:

*the “''Create From Reception''” menu item allows you to create a return for a specific shipment.
*the setup includes a table of reasons that can be associated with each return.
*only products purchasable from the supplier can be used.

==Setup==
In addition to the usual parameters for defining document numbering (used only in the Tabular mode), the following parameter is available:

'''Turn returns into shipments:''' This parameter allows you to enable the “Goods Shipping mode” (if On) or the “Tabular mode” (if Off).

Attention! The “Export” module must be enabled to use the “Goods Shipping mode”.

As mentioned previously, the setup page includes the “Return Reasons” section, which allows you to create the specific table (used only in the Tabular mode).
[[Category:Complementary modules]]

Third parties Processing

2026-02-06T11:09:07Z

Mgribaudo: Categorized

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to manage the flow of materials and inventory in situations such as processing or repairing materials at third-party locations.

It consists of two phases:

*Upon shipment, new inventory at the third-party location is tracked.
*Upon return, the material can be deducted from previous shipments.

The result is traceability of material movements and inventory at the third-party location.

Requires the “''[https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse Management]''” and [https://www.opigi.com/sito/documentation/advanced-shipments/ “''Advanced Shipments''”] modules.

==Usage==
For management, you must create, in the “''[https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse Management]''” reason list, the reasons to be used for Opening (Sending of Material) and Closing (Return) of Shipments (DDT) for opening and closing.

These reasons must:

*be of the “''Shipping''” type
*use the “''Processing at Third Parties''” field, setting the value '''Opening:''' Can be used for shipments; the reported quantities increase the inventory at third parties '''Closing:''' Can be used for returns; the reported quantities decrease the inventory at third parties. 

Finally, upon activation of the module, a new menu item, “'''List of Processing at Third Parties''',” will be available on the shipments page. This item allows you to view movements and inventory.

Creating and deleting the DDT line using the aforementioned reason will create and delete inventory at third parties.

Note that when the last item is returned, the shipment line will be classified as closed.

==Setup==
There are no configuration parameters associated with the module.
[[Category:Complementary module]]

Third parties Processing

2026-02-06T11:08:22Z

Mgribaudo: Created

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to manage the flow of materials and inventory in situations such as processing or repairing materials at third-party locations.

It consists of two phases:

* Upon shipment, new inventory at the third-party location is tracked.
* Upon return, the material can be deducted from previous shipments.

The result is traceability of material movements and inventory at the third-party location.

Requires the “''[https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse Management]''” and [https://www.opigi.com/sito/documentation/advanced-shipments/ “''Advanced Shipments''”] modules.

== Usage ==
For management, you must create, in the “''[https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse Management]''” reason list, the reasons to be used for Opening (Sending of Material) and Closing (Return) of Shipments (DDT) for opening and closing.

These reasons must:

* be of the “''Shipping''” type
* use the “''Processing at Third Parties''” field, setting the value '''Opening:''' Can be used for shipments; the reported quantities increase the inventory at third parties '''Closing:''' Can be used for returns; the reported quantities decrease the inventory at third parties. 

Finally, upon activation of the module, a new menu item, “'''List of Processing at Third Parties''',” will be available on the shipments page. This item allows you to view movements and inventory.

Creating and deleting the DDT line using the aforementioned reason will create and delete inventory at third parties.

Note that when the last item is returned, the shipment line will be classified as closed.

== Setup ==
There are no configuration parameters associated with the module.

Custom labels

2026-02-06T11:05:12Z

Mgribaudo: Categorized

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to define labels relating to products and then print them on thermal printers.

It allows you to configure different type of labels that can contain information:

– related to a product (code, description, supplier, batch, etc.)

– defined at the time of printing (e.g. the batch when printing a delivery note)

– derived from other archives (product master data, third-party providers, etc.)

In case of presence of multiple thermal printers inside the warehouse, each label type can be addressed to a specific printer, or the same label can be addressed to different printers for different users.

These labels can be:

*printed extemporaneously when needed
*printed automatically when orders are placed (customers and suppliers), supplier invoices are received and delivery notes are issue. In this case, a copy of the label will be printed for each individual product in the document.

It assumes the ability to generate labels in the various languages (ZPL, EPL, FGL, ESC / POS, EPCL, ….) in which labels can be programmed. For this purpose, some printer suppliers provide programs (eg ZDesigner for Zebra printers) that can generate labels in a simple and intuitive way.

==Usage==
The setup and label definition phase is crucial for the use of the module, so it is best to carry out these operations carefully before proceeding with printing.

===Manual printing of labels===
To obtain manual printing, select the “''Tools”'' item in the main menu and then the “''Custom labels''” item, the list of available labels is shown.

Upon selecting the desired label, a page will allow you to enter the necessary data and define the number of labels you want to print.
[[File:Custom Label1.png|thumb]]
 

===Printing of labels from document (Orders, Shipments, Invoicess)===
If, during the setup phase, the label to be used in the specific document (orders, invoices, shipments, …) was selected, a new button will be proposed,

this will allow you to print the labels relating to the document itself.

Depending on the setting of the other parameter “Request for label date in DDT / Orders”, the page that allows you to modify or complete the label data before printing them will be displayed or not.

==Module configuration==

===Settings===
The following information must be entered:
[[File:Custom Label2.png|thumb]]
'''Connector Used''': Allows you to select the connector used.

Here you can select one of the two connectors described below, or, by leaving the field blank, use printer addressing via IP. This latter option requires greater technical expertise and likely requires the intervention of a systems engineer.

'''Label Printer Name or IP Address:''' Contains:

*the name of the “Print Type” in the case of using the “''Webapp Hardware Bridge''” (see later)
*the network name or IP address assigned to the printer.
*if the value is instead left blank (this is the case in which the PHP Socket extension has not been enabled or printers cannot be reached with an IP address), the printing of each label is preceded by a printer selection window; it is understandable how having to confirm this page slows down the functionality of the module considerably, in this situation the correct functioning of the module is also not guaranteed with all thermal printers on the market.

It is therefore recommended, for optimal operation of the module, to connect the thermal printer via one of the two connectors.

'''Label used in … (Expeditions/Invoices/Receptions/Orders)'''

For each of the documents for which labels can be generated, it allows you to define which, among the various defined labels, is used at the time of issuing the document .

Associating a document type with a particular label causes a button for printing labels to appear in the document form.

====Using the Label Dispatcher====
This is the simplest option if you have a Windows terminal on your local network that can see the printers you want to use.

This application can be downloaded [https://www.opigi.com/download/Install%20Label%20Disptcher%201.0.exe from here] and offers the following advantages over the first one:

*Multiple label printers can be used
*The same label can be redirected to a different printer for each user[[File:Labels-Dispatcher.png|thumb]]

The connector must be configured by entering the following two parameters:

'''Server URL''': Contains the URL to point to the Dolibarr API (usually <code><mydolibarrURL>/htdocs/api/index.php</code>)

'''Api Key''': Contains the API key of one of the Dolibarr users with permissions to access the various documents

====Using the Webapp Hardware Bridge connector====
This is the option that allows you to address printers even in local Linux networks.

The Webapp Hardware Bridge connector application can be [https://github.com/imTigger/webapp-hardware-bridge/releases/download/0.14.0/whb-0.14.0.exe downloaded and installed] on all clients using the module.

Its use, through a [https://www.youtube.com/watch?v=RHFC3dtMBe4 simple configuration procedure], allows to considerably simplify the addressing phase of the printers, and does not require any technical skills.
[[File:Custom Label3.png|thumb]]
If you opt for this option, it will be sufficient to associate a “''Printer Type''” to the label printer in the connector setup window (as in the following image) and then indicate the same value in the Setting field “''Label Printer Name or IP Address''” (in the two images, the previous and the following one, the '''RETE''' value)

===Custom labels definition (label structure)===
As mentioned it is necessary, for each of the labels to be defined, to generate a text file in one of the standard languages used by thermal printers (ZPL, EPL, FGL, ESC / POS, EPCL, ….), for this purpose the hardware manufacturers generally make label design programs available, in the absence of these it is necessary to manually define the label using the syntax of the specific language.

It is important in this phase to define the “'''''placeholders'''''” where you want the values taken from the database to be entered, when the labels are printed.

These placeholders are identified by inserting the strings [param1], [param2], … [paramn] in the text of the label, these strings will be associated with the database fields when defining the label fields, an operation described in the following paragraph.
[[File:Custom Label4.png|thumb]]
The figure illustrates a placeholder label generated by the [https://www.youtube.com/watch?v=sdXt7D6xZoo ZDesigner] program for Zebra printers.

'''''ZDesigner tips''''' ''As regards the generation of the file with the ZDesigner, to obtain the necessary text file, follow the path “File>>Print”, turn on the “Print to File” checkbox and press the [Print] button. The obtained file (.prn) must be sent to the module.''

''Not all fonts are converted into text by Zdesigner, some are transformed into images and therefore the module is not able to replace the content. It is therefore advisable to open the .prn file with a text editor and check the presence of the text of all the placeholders ([param1], [param2], .…). If the strings are not present, you need to change the font of the placeholders.''

===Custom labels definition (label’s fields)===
The second phase required for the definition of the label is that which, as shown in the figure, allows you to:

*associate the previously defined text file to the label
*associate each of the previously defined placeholders with a label field.

For this purposeyou need to access the module setup and use the [Custom labels] tab.

From here, you can enter the list of label types you want to use, each label contains a set of general information and a set of information specific to each placeholder.

The general informations are:

'''Title''' Indicate here the title you want to assign to the specific label

'''Type''' Allows you to define the type of label to be printed, there are three types of labels:

. '''Third Parties''' To print, from the tools menu, information relating to a third party

. '''Products''' To print, from the tools menu, information relating to a product

. '''Advanced''' To print labels from various documents (offers, orders, invoices, …)

'''Content of the label''' From here you can upload the previously generated text file for the label (see previous paragraph)
[[File:Custom Label5.png|thumb]]
For each placeholder the following information must be defined:

'''Position''': It is the position that identifies the placeholder number as defined in the label text.

For example, by entering the value 2 here, the text [param2] of the label will be replaced with the value of the database field identified by the “Type” parameter (described below) itto)

'''Label''': Contains a description of the field

'''Type'''; Allows you to define the specific database value that will be used to replace the placeholder. The associated list allows you to report one of the following values:

*'''Text''' When the label is printed, it allows you to manually enter a text string that will be printed on the label. This field, together with the two that follow, makes no sense if the label must be automatically printed at the time of the order or DDT
*'''Number''' When the label is printed, it allows you to manually enter a numerical value that will be printed on the label.
*'''Date''' When the label is printed, it allows you to manually enter a date that will be printed on the label.
*'''Product Code''' On the label, instead of the placeholder, the code of the selected product will be printed.
*'''Product Description''' The product description will be printed instead of the placeholder.
*'''Product Barcode''' The product barcode is printed.
*'''Third Party Code''' The third party code is printed.
*'''Batch''' The batch of the product is printed.
*'''Batch expiration date''' The expiration date for the batchis printed.
*'''Third Party''' The company name of the third party is printed
*'''Quantity''' Contains the quantity of products indicated in the document. If this particular type is present on the label, only one label will be printed showing the quantity, otherwise n (n = quantity of the document products) different labels will be printed
*'''Custom fields'''It allows you to manage the printing of other fields, these fields are defined through functions that can be created in the file <code><kbd>“customlabels/lib/customlabels.lib.php”</kbd></code> This file contains examples for creating functions

[[File:Custom Label6.png|thumb]]
For example, having defined the placeholder [param2] in the text of the label, and having defined a label item as shown in the following figure, this placeholder will bereplaced, when the label is printed, with the description of the product
[[Category:Complementary Modules]]

Custom labels

2026-02-06T11:03:04Z

Mgribaudo: Inserted images

File:Custom Label6.png

2026-02-06T10:59:46Z

Mgribaudo:

Custom Label6

File:Custom Label5.png

2026-02-06T10:58:52Z

Mgribaudo:

Custom Label5

File:Custom Label4.png

2026-02-06T10:57:46Z

Mgribaudo:

Custom Label4

File:Custom Label3.png

2026-02-06T10:56:51Z

Mgribaudo:

Custom Label3

File:Labels-Dispatcher.png

2026-02-06T10:55:29Z

Mgribaudo:

Labels-Dispatcher

File:Custom Label2.png

2026-02-06T10:54:25Z

Mgribaudo:

Custom Label2

File:Custom Label1.png

2026-02-06T10:53:15Z

Mgribaudo:

Image

Custom labels

2026-02-06T10:51:40Z

Mgribaudo: Created

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to define labels relating to products and then print them on thermal printers.

It allows you to configure different type of labels that can contain information:

– related to a product (code, description, supplier, batch, etc.)

– defined at the time of printing (e.g. the batch when printing a delivery note)

– derived from other archives (product master data, third-party providers, etc.)

In case of presence of multiple thermal printers inside the warehouse, each label type can be addressed to a specific printer, or the same label can be addressed to different printers for different users.

These labels can be:

* printed extemporaneously when needed
* printed automatically when orders are placed (customers and suppliers), supplier invoices are received and delivery notes are issue. In this case, a copy of the label will be printed for each individual product in the document.

It assumes the ability to generate labels in the various languages (ZPL, EPL, FGL, ESC / POS, EPCL, ….) in which labels can be programmed. For this purpose, some printer suppliers provide programs (eg ZDesigner for Zebra printers) that can generate labels in a simple and intuitive way.

== Usage ==
The setup and label definition phase is crucial for the use of the module, so it is best to carry out these operations carefully before proceeding with printing.

=== Manual printing of labels ===
To obtain manual printing, select the “''Tools”'' item in the main menu and then the “''Custom labels''” item, the list of available labels is shown.

Upon selecting the desired label, a page will allow you to enter the necessary data and define the number of labels you want to print.

=== Printing of labels from document (Orders, Shipments, Invoicess) ===
If, during the setup phase, the label to be used in the specific document (orders, invoices, shipments, …) was selected, a new button will be proposed,

this will allow you to print the labels relating to the document itself.

Depending on the setting of the other parameter “Request for label date in DDT / Orders”, the page that allows you to modify or complete the label data before printing them will be displayed or not.

== Module configuration ==

=== Settings ===
The following information must be entered:

'''Connector Used''': Allows you to select the connector used.

Here you can select one of the two connectors described below, or, by leaving the field blank, use printer addressing via IP. This latter option requires greater technical expertise and likely requires the intervention of a systems engineer.

'''Label Printer Name or IP Address:''' Contains:

* the name of the “Print Type” in the case of using the “''Webapp Hardware Bridge''” (see later)
* the network name or IP address assigned to the printer.
* if the value is instead left blank (this is the case in which the PHP Socket extension has not been enabled or printers cannot be reached with an IP address), the printing of each label is preceded by a printer selection window; it is understandable how having to confirm this page slows down the functionality of the module considerably, in this situation the correct functioning of the module is also not guaranteed with all thermal printers on the market.

It is therefore recommended, for optimal operation of the module, to connect the thermal printer via one of the two connectors.

'''Label used in … (Expeditions/Invoices/Receptions/Orders)'''

For each of the documents for which labels can be generated, it allows you to define which, among the various defined labels, is used at the time of issuing the document .

Associating a document type with a particular label causes a button for printing labels to appear in the document form.

==== Using the Label Dispatcher ====
This is the simplest option if you have a Windows terminal on your local network that can see the printers you want to use.

This application can be downloaded from here and offers the following advantages over the first one:

* Multiple label printers can be used
* The same label can be redirected to a different printer for each user 

The connector must be configured by entering the following two parameters:

'''Server URL''': Contains the URL to point to the Dolibarr API (usually <code><mydolibarrURL>/htdocs/api/index.php</code>)

'''Api Key''': Contains the API key of one of the Dolibarr users with permissions to access the various documents

==== Using the Webapp Hardware Bridge connector ====
This is the option that allows you to address printers even in local Linux networks.

The Webapp Hardware Bridge connector application can be downloaded and installed on all clients using the module.

Its use, through a simple configuration procedure, allows to considerably simplify the addressing phase of the printers, and does not require any technical skills.

If you opt for this option, it will be sufficient to associate a “''Printer Type''” to the label printer in the connector setup window (as in the following image) and then indicate the same value in the Setting field “''Label Printer Name or IP Address''” (in the two images, the previous and the following one, the '''RETE''' value)

=== Custom labels definition (label structure) ===
As mentioned it is necessary, for each of the labels to be defined, to generate a text file in one of the standard languages used by thermal printers (ZPL, EPL, FGL, ESC / POS, EPCL, ….), for this purpose the hardware manufacturers generally make label design programs available, in the absence of these it is necessary to manually define the label using the syntax of the specific language.

It is important in this phase to define the “'''''placeholders'''''” where you want the values taken from the database to be entered, when the labels are printed.

These placeholders are identified by inserting the strings [param1], [param2], … [paramn] in the text of the label, these strings will be associated with the database fields when defining the label fields, an operation described in the following paragraph.

The figure illustrates a placeholder label generated by the ZDesigner program for Zebra printers.

'''''ZDesigner tips''''' ''As regards the generation of the file with the ZDesigner, to obtain the necessary text file, follow the path “File>>Print”, turn on the “Print to File” checkbox and press the [Print] button. The obtained file (.prn) must be sent to the module.''

''Not all fonts are converted into text by Zdesigner, some are transformed into images and therefore the module is not able to replace the content. It is therefore advisable to open the .prn file with a text editor and check the presence of the text of all the placeholders ([param1], [param2], .…). If the strings are not present, you need to change the font of the placeholders.''

=== Custom labels definition (label’s fields) ===
The second phase required for the definition of the label is that which, as shown in the figure, allows you to:

* associate the previously defined text file to the label
* associate each of the previously defined placeholders with a label field.

For this purposeyou need to access the module setup and use the [Custom labels] tab.

From here, you can enter the list of label types you want to use, each label contains a set of general information and a set of information specific to each placeholder.

The general informations are:

'''Title''' Indicate here the title you want to assign to the specific label

'''Type''' Allows you to define the type of label to be printed, there are three types of labels:

. '''Third Parties''' To print, from the tools menu, information relating to a third party

. '''Products''' To print, from the tools menu, information relating to a product

. '''Advanced''' To print labels from various documents (offers, orders, invoices, …)

'''Content of the label''' From here you can upload the previously generated text file for the label (see previous paragraph)

For each placeholder the following information must be defined:

'''Position''': It is the position that identifies the placeholder number as defined in the label text.

For example, by entering the value 2 here, the text [param2] of the label will be replaced with the value of the database field identified by the “Type” parameter (described below) itto)

'''Label''': Contains a description of the field

'''Type'''; Allows you to define the specific database value that will be used to replace the placeholder. The associated list allows you to report one of the following values:

* '''Text''' When the label is printed, it allows you to manually enter a text string that will be printed on the label. This field, together with the two that follow, makes no sense if the label must be automatically printed at the time of the order or DDT
* '''Number''' When the label is printed, it allows you to manually enter a numerical value that will be printed on the label.
* '''Date''' When the label is printed, it allows you to manually enter a date that will be printed on the label.
* '''Product Code''' On the label, instead of the placeholder, the code of the selected product will be printed.
* '''Product Description''' The product description will be printed instead of the placeholder.
* '''Product Barcode''' The product barcode is printed.
* '''Third Party Code''' The third party code is printed.
* '''Batch''' The batch of the product is printed.
* '''Batch expiration date''' The expiration date for the batchis printed.
* '''Third Party''' The company name of the third party is printed
* '''Quantity''' Contains the quantity of products indicated in the document. If this particular type is present on the label, only one label will be printed showing the quantity, otherwise n (n = quantity of the document products) different labels will be printed
* '''Custom fields'''It allows you to manage the printing of other fields, these fields are defined through functions that can be created in the file <code><kbd>“customlabels/lib/customlabels.lib.php”</kbd></code> This file contains examples for creating functions

For example, having defined the placeholder [param2] in the text of the label, and having defined a label item as shown in the following figure, this placeholder will bereplaced, when the label is printed, with the description of the product

Advanced Shipments

2026-02-06T10:49:11Z

Mgribaudo: Categorized

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], improves the shipping management, introducing the following possibilities not present in the standard shipping functions.

*enter new shipments directly, '''overcoming the need to switch from the sales order'''
*complete row management (similar to all other documents in Dolibarr)
*possibility of sending material and generating the transfer document '''also for suppliers''' and not only for customers (returns to suppliers, sending to subcontractors for processing, …)
*material transfer between 2 warehouses (internal management of the warehouse on behalf of contractors, …)
*possibility of using '''multiple numbering''' (if the [https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse module] is installed)

All other functions (invoicing from shipment, management of statuses, printing of documents, ….) reflect those of shipments (*).

==Using the form==
Upon installation, a new item is added to the main menu.

From this you access the list of shipments (only generated by the module), the remaining operation is the standard Dolibarr one.

On the other hand, by accessing the list of standard shipments, all shipments (advanced and not) will be displayed.

===Setup===
The module has no parameters
[[Category:Complementary Modules]]

Advanced Shipments

2026-02-06T10:48:33Z

Mgribaudo: Created

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], improves the shipping management, introducing the following possibilities not present in the standard shipping functions.

* enter new shipments directly, '''overcoming the need to switch from the sales order'''
* complete row management (similar to all other documents in Dolibarr)
* possibility of sending material and generating the transfer document '''also for suppliers''' and not only for customers (returns to suppliers, sending to subcontractors for processing, …)
* material transfer between 2 warehouses (internal management of the warehouse on behalf of contractors, …)
* possibility of using '''multiple numbering''' (if the [https://www.opigi.com/sito/documentation/advanced-warehouse-management/ Advanced Warehouse module] is installed)

All other functions (invoicing from shipment, management of statuses, printing of documents, ….) reflect those of shipments (*).

== Using the form ==
Upon installation, a new item is added to the main menu.

From this you access the list of shipments (only generated by the module), the remaining operation is the standard Dolibarr one.

On the other hand, by accessing the list of standard shipments, all shipments (advanced and not) will be displayed.

=== Setup ===
The module has no parameters

Supplier Return

2026-02-06T10:45:58Z

Mgribaudo: Categorized

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to quickly and easily manage returns of goods to suppliers.

There are two ways to perform these operations, which differ in their operational logic and the results obtained:

'''Goods Shipping Mode (only together with the the [https://www.opigi.com/sito/documentation/advanced-shipments/ Advanced Shipments module])'''

Management is activated when the goods are shipped, using the standard Dolibarr shipping module.

This mode is simpler and faster, and also uses the standard expedition document.

'''Tabular Mode'''

Management requires an item to appear in the main menu. Returns are managed, similarly to other Dolibarr documents, through a dedicated management system and printed using a specific layout.

This mode allows for more comprehensive returns management.

==Usage==

===Goods Shipping Mode===
In this mode, the shipment page contains a [''Create shipment from reception''] button. Pressing this button allows you to generate a shipment for the specified material.

The unloading movements are generated upon shipment confirmation.

===Tabular Mode===
In this mode, a main menu item allows you to manage returns in a manner similar to that of other standard documents (status, notes, documents, etc.).

The unloading movements are generated upon return processing.

Some of the module’s specific features are listed below:

*the “''Create From Reception''” menu item allows you to create a return for a specific shipment.
*the setup includes a table of reasons that can be associated with each return.
*only products purchasable from the supplier can be used.

==Setup==
In addition to the usual parameters for defining document numbering (used only in the Tabular mode), the following parameter is available:

'''Turn returns into shipments:''' This parameter allows you to enable the “Goods Shipping mode” (if On) or the “Tabular mode” (if Off).

Attention! The “Export” module must be enabled to use the “Goods Shipping mode”.

As mentioned previously, the setup page includes the “Return Reasons” section, which allows you to create the specific table (used only in the Tabular mode).
[[Category:Complementary Modules]]

Supplier Return

2026-02-06T10:39:14Z

Mgribaudo: Created

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM project], this module allows you to quickly and easily manage returns of goods to suppliers.

There are two ways to perform these operations, which differ in their operational logic and the results obtained:

'''Goods Shipping Mode (only together with the the [https://www.opigi.com/sito/documentation/advanced-shipments/ Advanced Shipments module])'''

Management is activated when the goods are shipped, using the standard Dolibarr shipping module.

This mode is simpler and faster, and also uses the standard expedition document.

'''Tabular Mode'''

Management requires an item to appear in the main menu. Returns are managed, similarly to other Dolibarr documents, through a dedicated management system and printed using a specific layout.

This mode allows for more comprehensive returns management.

== Usage ==

=== Goods Shipping Mode ===
In this mode, the shipment page contains a [''Create shipment from reception''] button. Pressing this button allows you to generate a shipment for the specified material.

The unloading movements are generated upon shipment confirmation.

=== Tabular Mode ===
In this mode, a main menu item allows you to manage returns in a manner similar to that of other standard documents (status, notes, documents, etc.).

The unloading movements are generated upon return processing.

Some of the module’s specific features are listed below:

* the “''Create From Reception''” menu item allows you to create a return for a specific shipment.
* the setup includes a table of reasons that can be associated with each return.
* only products purchasable from the supplier can be used.

== Setup ==
In addition to the usual parameters for defining document numbering (used only in the Tabular mode), the following parameter is available:

'''Turn returns into shipments:''' This parameter allows you to enable the “Goods Shipping mode” (if On) or the “Tabular mode” (if Off).

Attention! The “Export” module must be enabled to use the “Goods Shipping mode”.

As mentioned previously, the setup page includes the “Return Reasons” section, which allows you to create the specific table (used only in the Tabular mode).

Advanced warehouse management

2026-02-06T10:35:11Z

Mgribaudo: Inserted category

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM projec]t, integrate and improve warehouse movement management.

Movements are managed through “''Warehouse movements''” identified by:

*a reason that defines their characteristics (loading and/or unloading warehouse, bom explosion, etc.).
*n lines that correspond to the individual warehouse movements.

This organization allows for::

*a better organization and access to movements (for example, customized numbering of records is possible)
*faster management: the warehouse is pre-set and there is the option to delete records (and therefore movements) and restore stock levels

Ability to perform complex movements, loading, unloading, transfers, breakdowns of lists, etc. (for example, it is possible to unload all the components of a list or transfer them from one warehouse to another for production)

This module allow

*better organization and access to movements (for example, customized record numbering is possible)
*faster management
*deletion of records (and therefore ''movements'') with stock replenishment
*complex movements, loadings, unloadings, transfers, BOM explosions, etc. (for example, it is possible to unload all the components of a BOM or transfer them from one warehouse to another for production)

Other features include:

*Inventory management (a load or discharge is created to balance the current stocks)
*Allocation and related inventory management
*Stock analysis function by allocation/lot
*Ability to generate loading or unloading lines from an Excel spreadsheet (requires the Import from Excel module)

==Usage==

===Warehouse Reason Management===
Reasons allow you to define the behavior of recordings by defining the loading and/or unloading methods and the warehouses involved.

They can be of 3 types:

*Warehouse
*Orders (creating a reason from this family generates a new entry in the Shortcuts of the customer orders menu)
*Delivery Notes (creating a reason generates a new entry in the Shortcuts of the advanced shipping menu)

The definable parameters vary depending on the modules installed. They are:

'''Customer''' Used only if the Advanced Shipment module module is installed

'''Inventory''' Indicates whether the reason generates an inventory movement. The inventory generate a mouvement to a load or discharge a quantity to balance the current stocks

'''Loading Warehouse''' Warehouse where the goods are loaded (or origin if transfer)

'''Unloading Warehouse''' Unloading warehouse (or destination if transfer)

'''BOM Explosion''' '''upon loading''' If enabled and if the product is a finished product with a BOM, it explodes the BOM and loads all components

'''BOM Explosion for unloading''' The same applies to unloading. If both indicators are on, it is possible to transfer all the components of a list from one warehouse to another .

'''Use DDT Counter n.''' Used only if the [https://www.opigi.com/sito/documentation/advanced-shipments/ Advanced Shipment module] is installed. Refer to the specific document.

'''Exclude 1st row''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''Use supplier code''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''File Routine''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

==='''Allocation Management'''===
As mentioned, it is possible to manage the details of the allocations (departments, shelves, etc.) where the goods are stored within individual physical warehouses.

To enable this management, you must:

*Enable management in setup
*Create the list of allocations in a dedicated table in the dictionaries

For each movement line, the allocation will be requested

===Stock Analysis by Batch/Allocation===
The module’s side menu contains an item that allows you to access this list.

The available functions are the classic Dolibarr ones.

*

==='''Setup'''===
The module setup allows the following settings

*'''Display Description''' Allows you to display or hide product descriptions in the transaction lines.
*'''Use Allocations''' Enables/disables the allocation management described above.
*'''Hide Custom Fields''' Hides custom fields on transaction lines.

Finally, the page includes a [Recalculate Inventory] button that allows you to recalculate inventory, lots, and allocations based on current transactions.

==Note to programmers==
If the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed, the “''ExcelAddLine”'' hook is available which allows you to manage imports in complex situations.
[[Category:Complementary modules]]

Advanced warehouse management

2026-02-06T10:32:13Z

Mgribaudo: Created

Component part of the [https://www.opigi.com/sito/doliwm-ecosystem/ DOLYWM – ECOSYSTEM projec]t, integrate and improve warehouse movement management.

Movements are managed through “''Warehouse movements''” identified by:

* a reason that defines their characteristics (loading and/or unloading warehouse, bom explosion, etc.).
* n lines that correspond to the individual warehouse movements.

This organization allows for::

* a better organization and access to movements (for example, customized numbering of records is possible)
* faster management: the warehouse is pre-set and there is the option to delete records (and therefore movements) and restore stock levels

Ability to perform complex movements, loading, unloading, transfers, breakdowns of lists, etc. (for example, it is possible to unload all the components of a list or transfer them from one warehouse to another for production)

This module allow

* better organization and access to movements (for example, customized record numbering is possible)
* faster management
* deletion of records (and therefore ''movements'') with stock replenishment
* complex movements, loadings, unloadings, transfers, BOM explosions, etc. (for example, it is possible to unload all the components of a BOM or transfer them from one warehouse to another for production)

Other features include:

* Inventory management (a load or discharge is created to balance the current stocks)
* Allocation and related inventory management
* Stock analysis function by allocation/lot
* Ability to generate loading or unloading lines from an Excel spreadsheet (requires the Import from Excel module)

== Usage ==

=== Warehouse Reason Management ===
Reasons allow you to define the behavior of recordings by defining the loading and/or unloading methods and the warehouses involved.

They can be of 3 types:

* Warehouse
* Orders (creating a reason from this family generates a new entry in the Shortcuts of the customer orders menu)
* Delivery Notes (creating a reason generates a new entry in the Shortcuts of the advanced shipping menu)

The definable parameters vary depending on the modules installed. They are:

'''Customer''' Used only if the Advanced Shipment module module is installed

'''Inventory''' Indicates whether the reason generates an inventory movement. The inventory generate a mouvement to a load or discharge a quantity to balance the current stocks

'''Loading Warehouse''' Warehouse where the goods are loaded (or origin if transfer)

'''Unloading Warehouse''' Unloading warehouse (or destination if transfer)

'''BOM Explosion''' '''upon loading''' If enabled and if the product is a finished product with a BOM, it explodes the BOM and loads all components

'''BOM Explosion for unloading''' The same applies to unloading. If both indicators are on, it is possible to transfer all the components of a list from one warehouse to another .

'''Use DDT Counter n.''' Used only if the [https://www.opigi.com/sito/documentation/advanced-shipments/ Advanced Shipment module] is installed. Refer to the specific document.

'''Exclude 1st row''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''Use supplier code''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

'''File Routine''' Used only if the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed. Refer to the specific document.

=== '''Allocation Management''' ===
As mentioned, it is possible to manage the details of the allocations (departments, shelves, etc.) where the goods are stored within individual physical warehouses.

To enable this management, you must:

* Enable management in setup
* Create the list of allocations in a dedicated table in the dictionaries

For each movement line, the allocation will be requested

=== Stock Analysis by Batch/Allocation ===
The module’s side menu contains an item that allows you to access this list.

The available functions are the classic Dolibarr ones.

*

=== '''Setup''' ===
The module setup allows the following settings

* '''Display Description''' Allows you to display or hide product descriptions in the transaction lines.
* '''Use Allocations''' Enables/disables the allocation management described above.
* '''Hide Custom Fields''' Hides custom fields on transaction lines.

Finally, the page includes a [Recalculate Inventory] button that allows you to recalculate inventory, lots, and allocations based on current transactions.

== Note to programmers ==
If the [https://www.opigi.com/sito/documentation/importfromexcel/ Import from Excel module] is installed, the “''ExcelAddLine”'' hook is available which allows you to manage imports in complex situations.