Works with
Nesting software that works with Plex
Plex is an ERP and MES platform with real nesting integrations behind it, including remnant tracking. Lapas is not one of them, so this is a file workflow with a manual step at the end.
Read this first
Lapas does not integrate with Plex. There is no connector, no API link and nothing to install.
Plex's nesting integrations create and modify nesting work orders, sync that data straight back to the ERP, and track remnant inventory after production, with CAD data reaching the BOM through partner connectors like CADLink. Lapas does none of that. It has no Plex connector, creates no work orders and writes no remnants. If your Plex deployment already includes a nesting integration, it is doing strictly more than this and you should not replace it.
How the handoff actually works
Who does what, in order. Nothing here requires either system to know the other exists.
- 1 You Export part geometry as DXF
From your CAD, or from wherever the released job keeps its drawings. Explode blocks before export; block references are the most common reason a DXF imports empty in any nesting tool.
- 2 You Upload to Lapas and set the sheet
Quantities, sheet size, kerf at measured cut width, minimum spacing. Lapas does not read Plex material master data, so this is entered per job.
- 3 Lapas Nest and review
True-shape nesting across as many sheets as the batch needs. Watch it place parts live and stop early once the layout is good enough.
- 4 Lapas Export DXF and PDF
DXF is the nested layout for CAM. The PDF report carries sheet count, utilization and part placement. Both on the free plan.
- 5 You Record consumption in Plex by hand
Material used, sheet count and any remnant worth keeping. An integrated nester would create the work order and post the remnant automatically. This does not.
Plex behaviour checked against Plex ERP, Rockwell Automation in July 2026. Lapas behaviour per the pricing page.
Plex 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
- Everything crossing the boundary. No connector, no sync, no API exchange.
- Creating and updating nesting work orders in Plex.
- Remnant inventory after the nest, which Plex integrations normally maintain.
- Material master and sheet selection, which Lapas cannot read.
- Traceability from the nest back to individual work orders.
When Lapas is the wrong tool here
- Your Plex deployment already has a nesting integration. Keep it; this is a step backwards.
- Remnant inventory accuracy is part of how you cost jobs.
- You need nesting work orders created automatically when jobs release.
- You need validated post-processors. Lapas exports DXF; G-code is beta and unvalidated across controllers.
Common questions
No. There is no Plex connector, no work-order creation and no remnant write-back. Plex nesting integrations do all three, so if you have one this workflow is a downgrade.
When nesting is not integrated today. Plenty of Plex sites run the ERP and MES fully while the actual sheet layout is done by eye or in whatever tool the laser operator has. Replacing that with true-shape nesting is a real gain; replacing a working integration is not.
No. The report tells you what is left on the sheet, but nothing is written to Plex. Remnant handling stays manual unless you have the integration.
Nothing. The free plan is 5 new projects a month with unlimited re-nests and no cap on parts per job. Run one real job through it and compare the sheet count against what you get today.
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