Works with
Nesting software that works with Epicor Kinetic
Epicor sells a named nesting integration for Kinetic called NESTLink. Lapas is not part of it. If you are not running NESTLink, here is what the plain file workflow looks like.
Read this first
Lapas does not integrate with Epicor Kinetic. There is no connector, no API link and nothing to install.
Epicor's own answer to this question is NESTLink, an API-based nesting integration for Kinetic that removes manual input and data re-entry between the ERP and the nesting software. Lapas is not a NESTLink partner and has no API integration with Kinetic of any kind. Everything below is files moved by a person. If data re-entry is the problem you are trying to solve, NESTLink is the product that solves it and this is not.
How the handoff actually works
Who does what, in order. Nothing here requires either system to know the other exists.
- 1 You Pull the DXF for the jobs you want to run
From CAD or the job attachments in Kinetic. Group them yourself by material and thickness, since nothing here will do that grouping for you.
- 2 You Upload to Lapas and set the sheet
Quantities, sheet size, kerf at measured cut width. No Kinetic material data reaches Lapas, so this is per job.
- 3 Lapas Nest
True-shape nesting on real outlines, multi-sheet where needed, no cap on parts per job. Live preview so you can stop when the layout is good enough.
- 4 Lapas Export DXF and PDF
DXF into your CAM. The PDF report carries sheet count and utilization for costing the job.
- 5 You Re-enter the numbers in Kinetic
This is the step NESTLink exists to delete. Material consumed and sheet counts are typed in. If that is unacceptable at your volume, buy the integration.
Epicor Kinetic behaviour checked against Epicor Kinetic NESTLink in July 2026. Lapas behaviour per the pricing page.
Epicor Kinetic is a trademark of its respective owner. Lapas is an independent product and is not affiliated with, endorsed by, sponsored by or certified as compatible by them.
What stays manual
- All data movement between Kinetic and Lapas, in both directions.
- Job grouping and material batching.
- Material consumption and sheet counts written back to the job.
- Remnant and offcut records.
- Anything NESTLink automates, which is most of the above.
When Lapas is the wrong tool here
- You run NESTLink. It is API-based and removes the re-entry this workflow requires.
- Data re-entry between systems is the specific problem you are solving.
- You are a metal service centre needing coil and plate inventory logic; Epicor sells a separate solution for that and Lapas does not address it.
- You need validated machine post-processors. Lapas exports DXF; G-code is beta and unvalidated across controllers.
Common questions
No. NESTLink is Epicor’s API-based nesting integration for Kinetic and Lapas is not part of it. There is no API connection between Lapas and Kinetic.
Because not every Kinetic site runs NESTLink. If nesting is currently done by eye or in a tool nobody maintains, the layout quality gain is real even though the data entry stays manual. If NESTLink is already in place, this is a downgrade.
No. Nothing is written to Kinetic. Sheet counts and material usage come off the PDF report and are entered by hand.
No. The free plan has no credit card and no expiry: 5 new projects a month, unlimited re-nests, no cap on parts per job, DXF export and the PDF report included.
Partly, and be careful. Lapas nests parts on a sheet well, but it has no coil, plate inventory or remnant management, which is usually the harder half of service centre work. Epicor sells a dedicated metal service centre solution and that gap is not something a nesting tool closes.
Other stacks: all ERP and MES workflows. Measured nesting results: the benchmark.
Don't take our word for it.
Upload one of your own DXF files and see the layout yourself. It's free and takes about two minutes.
Nest your own file for freeNo credit card · No install · Your files stay yours