Lantek Importer
Your Lantek nests, already in Odoo
Lantek Expert describes every nest in its NXP export: the sheets and their weight, the remnants, the parts with their own weight and how many pieces of each fit on a plate. This module reads those files for Nest Importer, so each Lantek program becomes a manufacturing order without retyping anything, and the sheet's cost is shared by the weights Lantek calculated.
Part weights come from the file, so the cost share matches what Lantek planned.
One file can hold several sheets and remnants; each program takes its own.
Remnants are created as by-products in kg, ready to be cut again.
From an NXP file to a manufacturing order
Upload your NXP files
In Manufacturing, Import Nests, add one or more NXP files. Each one shows Lantek NXP as its format, with the orders and plates it will create, before anything is imported.
Choose how sheets and parts are weighed
The Nest Import settings decide where the sheet's weight comes from, whether parts and remnant are scaled to it, and the code of a miscellaneous product for the generic parts Lantek numbers in sequence, such as MISC-LASER-01 and MISC-LASER-02.
Check the plate weights
Lantek gives the weight of every plate. With the weight check on, a plate that weighs more or less in the file than in Odoo, beyond both tolerances, is listed before importing so you can confirm it.
The sheet becomes the component
Each Lantek program is a confirmed order with the sheet it consumes as its component, in units or in kg depending on how the sheet is counted, and a Laser operation on your work center.
Parts and remnant share the cost
The parts and the remnant are the order's by-products. Their weight comes from the file and their cost share is computed from it, so the sheet's whole cost is accounted for.
Considerations
- Installs Nest Importer. The import itself, its settings and the orders it creates come from Nest Importer, which is installed with this module.
- Product codes in brackets. Sheets, remnants and parts are found by the code in brackets in the file, such as [SHEET-A36-6MM], or by the text before an ampersand.
- Several sheets per file. Each program uses the sheet and remnant it names; when it names none, the file's only sheet or remnant is used.
- Real part weights. The weight Lantek reports for each piece is used for the cost share rather than the product's weight in Odoo.
- Skipped parts. Parts the file lists but that were nested zero times are left out.
- Files without a sheet. A file with no sheet in it cannot be imported and is marked Not ready.
Contact us
Kaitim · Odoo 18.0
Your Lantek nests, already in Odoo
Lantek Expert describes every nest in its NXP export: the sheets and their weight, the remnants, the parts with their own weight and how many pieces of each fit on a plate. This module reads those files for Nest Importer, so each Lantek program becomes a manufacturing order without retyping anything, and the sheet's cost is shared by the weights Lantek calculated.
Part weights come from the file, so the cost share matches what Lantek planned.
One file can hold several sheets and remnants; each program takes its own.
Remnants are created as by-products in kg, ready to be cut again.
From an NXP file to a manufacturing order
Upload your NXP files
In Manufacturing, Import Nests, add one or more NXP files. Each one shows Lantek NXP as its format, with the orders and plates it will create, before anything is imported.
Choose how sheets and parts are weighed
The Nest Import settings decide where the sheet's weight comes from, whether parts and remnant are scaled to it, and the code of a miscellaneous product for the generic parts Lantek numbers in sequence, such as MISC-LASER-01 and MISC-LASER-02.
Check the plate weights
Lantek gives the weight of every plate. With the weight check on, a plate that weighs more or less in the file than in Odoo, beyond both tolerances, is listed before importing so you can confirm it.
The sheet becomes the component
Each Lantek program is a confirmed order with the sheet it consumes as its component, in units or in kg depending on how the sheet is counted, and a Laser operation on your work center.
Parts and remnant share the cost
The parts and the remnant are the order's by-products. Their weight comes from the file and their cost share is computed from it, so the sheet's whole cost is accounted for.
Considerations
- Installs Nest Importer. The import itself, its settings and the orders it creates come from Nest Importer, which is installed with this module.
- Product codes in brackets. Sheets, remnants and parts are found by the code in brackets in the file, such as [SHEET-A36-6MM], or by the text before an ampersand.
- Several sheets per file. Each program uses the sheet and remnant it names; when it names none, the file's only sheet or remnant is used.
- Real part weights. The weight Lantek reports for each piece is used for the cost share rather than the product's weight in Odoo.
- Skipped parts. Parts the file lists but that were nested zero times are left out.
- Files without a sheet. A file with no sheet in it cannot be imported and is marked Not ready.
Contact us
Kaitim · Odoo 18.0
Requires
Specifications
| Odoo Version | 18.0, 19.0, 20.0 |