Cutting List, Roll Tracking, Installation Calendar and Packaging

This guide covers four practical needs: exporting the panel cutting list to a nesting program, tracking the metres left on a fabric or foam roll, laying the installation team's jobs onto a calendar, and splitting a shipment into cases with a packing list.

1. Cutting list — HNR does NOT nest; it builds a bridge

The program that lays out panels (nesting) is a separate one — Adeko, CutRite, Ardis and the like. HNR's job is the bridge: it exports the code, size, quantity and material of the panels on open work orders as CSV, and you import that file into the nesting program.

⚠ Where does the size come from?

Every row states an size source: card (read from a size card — reliable), guessed-from-description (extracted from text such as "1200x600x18" in the stock description — verify it) or NONE. The list also counts how many panels have carded sizes, how many are guesses and how many are missing. The system never invents a size; if it is missing, it says so.

2. Roll tracking — "how much is left on which roll?"

Stock says "there are 120 metres of fabric". The shop floor asks "how much is left on which roll?" A roll is a physical object: it has a barcode, it starts at 50 metres, shrinks with every cut, runs out and closes. Its record is never deleted — so that "when did this roll finish and who finished it" stays answerable.

The Warehouses window → Rolls tab. The Handheld box at the top is designed to work with a barcode scanner: the box starts focused, scanning a barcode opens the roll's remainder and history, then you type the metres cut and press Enter.

Deduct — the metres cut come off. When the remainder hits zero the roll closes by itself.
Split — a piece is taken off and registered as a new roll; the new roll carries the parent roll's number.
Close — if the last 2 metres became scrap, the roll is closed. A reason is mandatory: without it a reconciliation gap can never be explained later.
You cannot deduct more than is left — showing a roll longer than it is makes the next job get planned wrong.

⚠ Deducting metres does NOT create a stock movement

The roll ledger follows the physical roll; stock is already reduced by the document or the production confirmation. Reducing it again here would be double counting. If the two ledgers diverge, the Reconciliation block shows the gap plainly — the system does not fix it by itself, because it cannot know which number is right.

3. Installation calendar — "which crew is busy this week?"

The Departments window → Dispatch tab has three views:

Day — today's jobs in time order. The crew can also mark on-the-way / installed from here.
Calendar — a 7, 14 or 30 day day × crew grid. Which crew is full on which day is visible at a glance.
Candidate documents — invoices and delivery notes issued but with no installation job opened. One click creates the job; the account and delivery address come from the document.

💡 Why isn't a job created automatically when an invoice is issued?

Not every invoice needs installation — nobody sends a crew because one hinge was sold. If the system created jobs by itself, the calendar would fill with noise in the first week and nobody would look at it. Instead candidates are shown: the planner decides which one is an installation job, and none of them gets forgotten.

Photos: the installation crew uses the 📷 Photo button in the My jobs tab of the /saha page to shoot from their phone. The photos appear as thumbnails on the Dispatch screen. Against a damage claim raised later, the only defence is a frame taken at the moment of installation.

4. Packaging: case split and packing list

You define a packaging card on the stock item: units per case, case type, case tare, unit net weight, cases per pallet. Then "how many cases is 1000 pieces" is answered in one call: 8 full cases + 40 left over = 9 cases. The remainder case is its own row — the odd amount is never hidden.

⚠ SSCC is never invented

An SSCC-18 label can be printed for every case, but your company's GS1 company prefix must be configured first. Without it the system does not invent a number: cases are cut without SSCC and the response says so plainly. A label printed with a made-up prefix shows up in the carmaker's system as another company's goods.

The packing list is what goods-inwards compares against the truck paperwork: case no, SSCC, product, quantity, net and gross kg, pallet. The TOTAL row at the bottom is the standard expected on customs and freight documents. The CSV export opens cleanly in a Turkish Excel.

🔗 Related guides

Related guides: Production, Warehouse, Field and B2B, PPAP and SPC.