How it fits
Your system stays in charge; Lescut only nests
No second place to keep orders, stock or patterns in step. Your ERP decides what to cut and from what, and Lescut answers with the nest. Any system that can call HTTPS can do it: SAP, Microsoft Dynamics, Odoo or one built in-house.
- 01
Your system sends the cut order
The parts of the order with their quantities, and the stock it has today: the hides it picked from the warehouse, the sheets on the rack, or the roll width.
- 02
Lescut nests it
On a dedicated, powerful cloud machine, for the time you set, by the rules each part carries: grades, defects, grain, flip, matching and sets.
- 03
Your system books the result
Placements per hide, sheet or marker, cutting files with your layers, and per part the batch and hide it is cut from, ready to post against the order.
- 04
The job is deleted
Your system deletes the job once it has the files, or Lescut does about 24 hours after it ends. Only the engine time used is kept, for billing.
What your integrator needs
A connector of four API calls
JSON over HTTPS, described in an OpenAPI document, with keys your owners and admins create in the app. Search settings come from a saved nesting profile, so the connector sends only the order and the stock.
POST /jobsStart a job: the cut order’s parts as outlines in mm with quantities and rules, the stock to use, the number of sets and the search time.
GET /jobs/{id}Poll its status and the best nest so far; the result and its file links appear when it ends.
GET /jobs/{id}/files/…Download a DXF and SVG per hide, sheet or marker, the per-part report.csv, or everything as one zip.
DELETE /jobs/{id}Delete the job, its geometry and its result once your system has what it needs.
Every endpoint, schema and error is in the API docs.
What comes back
Everything your system needs to book the cut
The result is data first: your ERP reads what was used and where every part went, and passes the files to the cutting room.
Placements per part
Every part’s hide, sheet or marker with its position, rotation and flip, in your drawing’s coordinates.
Traceable to the hide
A report per cut part with its batch and hide, and the job and hide named inside each cutting file.
Material used
Yield per hide, sheet or marker, and for leather the yield, leftover and complete sets per batch.
Remnants worth keeping
For leather, the usable remnant on each emptier hide, pushed into one piece, so your stock can record it.
Files for the cutter
One DXF and SVG per hide, sheet or marker with the original layers and curves, renamed for your machine by a cutter profile.
Complete sets
How many whole sets were placed, with prefer, strict or maximum utilisation per job, so a short stock never leaves half an order.
Enterprise plans
A whole production day, nested at once
Your system can send the day’s cut orders together and they nest in parallel on 10 cloud machines: 10 jobs of 60 minutes finish together in 60 minutes, not 10 hours one after another. No overnight nesting runs on a shop PC, and no morning surprises when the power went out or the machine hung.
Up to 10 jobs at a time, each on its own dedicated, powerful machine, 300 API requests a minute, jobs of 20 to 60 minutes and the priority queue. One plan per material; contact us for more capacity.
Textile Enterprise
from €190 per month
900 engine minutes, up to 16 vCPU per job, jobs up to 20 min
- Everything in Textile Pro
- 5× the engine minutes and jobs up to 20 min
- 10 jobs at a time, each on its own machine with up to 16 vCPU
- Priority queue
- Unlimited team members
- SSO (planned)
€0 for 7 days. Card required. Cancel any time.
Leather Enterprise
from €890 per month
4,500 engine minutes, up to 16 vCPU per job, jobs up to 60 min
- Everything in Leather Pro
- 5× the engine minutes and jobs up to 60 min for large orders
- 10 jobs at a time, each on its own machine with up to 16 vCPU
- Priority queue
- Unlimited team members
- SSO (planned)
€0 for 7 days. Card required. Cancel any time.
Sheet Enterprise
from €190 per month
900 engine minutes, up to 16 vCPU per job, jobs up to 30 min
- Everything in Sheet Pro
- 5× the engine minutes and jobs up to 30 min
- 10 jobs at a time, each on its own machine with up to 16 vCPU
- Priority queue
- Unlimited team members
- SSO (planned)
€0 for 7 days. Card required. Cancel any time.
Building nesting into a product you sell instead? See the nesting API for software and machine makers.
Questions about ERP integration
Can Lescut work with our ERP or warehouse management system?
Yes, through the Lescut REST API. Your ERP, WMS or MES sends each cut order with the stock it has chosen, and reads back the placements, cutting files and a per-part report to book against the order. Anything that can call HTTPS can do this, so a connector can be written for SAP, Microsoft Dynamics, a custom system or your middleware; your team or integrator writes the connector, and we help with the first jobs.
How much work is an ERP integration?
A connector needs four calls: start a job with the order and the stock, poll it, download the files and report, and delete it. It is JSON over HTTPS with an OpenAPI document, so your team or integrator can write it in any language or middleware, and we help with the first jobs on your own files.
Do you store our patterns?
Not when your system sends the outlines with the job. No file is stored, the geometry is kept only as part of the job, never in a library, and it is deleted when you delete the job or about 24 hours after it ends. What stays is the record of engine time used, with no geometry and no names. Encrypted database backups are overwritten within 30 days.
Where is our data processed?
The database and file storage are in EU (Frankfurt). The machines that run jobs receive the job encrypted with a key we hold, and our compute provider keeps only that encrypted copy, for up to 30 days. All traffic uses TLS. The Privacy Policy and the Data Processing Terms in Schedule 1 of our Terms list the providers and safeguards.
Is Lescut GDPR compliant?
Lescut is run under the GDPR: our Terms include Data Processing Terms (Schedule 1), in which we act as your processor for personal data in your files, our Privacy Policy lists the providers we use, and the database and file storage are in EU (Frankfurt).
Do you use our files to improve the engine?
No. We do not use your files to develop, train, tune or benchmark the nesting engine or any model used for other customers, and other customers never see them.
Does Lescut keep track of our stock?
No. Your system stays the record of stock. Each job brings the hides, sheet counts or roll width it should use, and the result tells your system what was used: yield per hide or sheet, leftover and complete sets per batch, and for leather the usable remnant on each emptier hide.
Can it run on our own servers?
Lescut runs on our cloud machines, which is what lets it be fast and private at once. Each job gets a dedicated, powerful cloud machine for its whole time limit, up to 10 at a time, so a production schedule nests in parallel. On your own servers it would queue on hardware your IT team has to size, patch and keep the engine current on, and the nests would only be as good as that hardware. Every engine improvement reaches you the same day, with no upgrade project. Privacy does not need your own servers: when your system sends the outlines with each job, nothing is stored as files, the job is deleted within 24 hours, and storage stays in EU (Frankfurt). The one case it does not fit is a network that no data may leave at all.
How do we know when a job is done?
Poll the job every few seconds; it reports the best nest so far while it runs, and its result and file links when it ends. A job can be stopped at any time and keeps its best nest.
Which plan do we need?
Any Pro or Enterprise plan includes the API. Enterprise plans run up to 10 jobs at a time, take 300 requests per minute, allow jobs of 20 to 60 minutes and use the priority queue. Every plan starts with a 7-day free trial, enough to test the connector on your own orders.