File format
A spreadsheet with one row per piece. .csv, .xlsx, or a .zip containing one of those.
The ZIP package
exemplo.zip
├── pieces.csv ← exactly ONE spreadsheet, at the root
├── images/ ← optional: the original order drawing
│ └── imagem.png
└── shapes/ ← optional: SVG or RC2 of the piece outline
└── forma.svg
Exactly one spreadsheet at the root. Two, or none, rejects the whole package before any row is read.
The Drawing and Shape columns accept either the content inline, or the name of a file inside shapes/. Same for OrderImage and images/.
Columns
The separator is semicolon (;).
| Column | Required | Notes |
|---|---|---|
Barcode | Yes | Your business key. See Overview |
Description | Yes | What the piece is, in human words |
Width · Height | Yes | In millimetres |
Thickness | Yes | In millimetres. Decimals allowed |
Services | Yes | The operations, in square brackets: [SERVICE_A],[SERVICE_B]. Without at least one there is no production route — unless the row sends Phases (below) |
GlassType | Yes | Glass type. Created automatically if new |
CustomerName | Yes | Created automatically if new |
DueDate | No | The deadline, in plant time and without a time zone: YYYY-MM-DD or YYYY-MM-DDTHH:MM[:SS] — see below. Missing means the plant's today plus 30 days |
Quantity | No | Missing means a single piece |
Item | No | The order line, for serial lots |
Cancelled | No | True refuses the piece — see below |
CustomerOrder · InternalOrder | No | Your order references |
Urgent | No | Raises the scheduling priority |
Notes | No | Free text, carried through to the shop floor |
Route | No | Delivery route |
Priority | No | Scheduling priority, as a number |
Cutouts | No | Number of cut-outs |
ParentBarcode | No | Barcode of the parent piece, for assemblies |
Shape | No | Piece outline in rc2. Inline content, or the name of a file in shapes/ |
Drawing | No | Technical drawing (SVG). Inline content, or the name of a file in shapes/ |
OrderImage | No | Name of an image in images/ |
Weight | No | The weight of one unit, in kg. Missing or empty: Mover.Glass calculates it from the size and the thickness |
EdgingAllowance | No | The edging allowance, in mm, the same on the four sides (1,5). See below |
EdgingAllowanceSides | No | The edging allowance per side, in mm: four values separated by hyphens, top-right-bottom-left (1,5-3-1,5-0). See below |
Phases | No | The ERP phase codes, instead of Services: CODE[*count][@mark], separated by commas (FL,FOR*2,TEMPCM@E). See below |
The contract publishes the English names above. The previous Portuguese names — CodigoBarra, Largura, Espessura, ServicosAplicaveis, Inativa and the rest — are still accepted, so a file you already generate keeps working. Both sets can even appear in the same header.
New integrations should use the English names: those are the ones this page will keep documenting.
Since 9 November 2026 the header is matched ignoring letter case and the spaces around a name (edgingallowance works). A column the reader does not know is still ignored, without a warning.
The .xlsx layout is read by position, not by header. Column names in a spreadsheet are ignored — what counts is the order. If you are starting fresh, use CSV: the header makes the file readable by a person and tolerant of a column being added later.
There are three exceptions, found by their header in any column (ignoring letter case): the weight, Weight, the edging allowance, EdgingAllowance and EdgingAllowanceSides, and the ERP phases, Phases. Without the header they are not read. In .xlsx, only the name Phases counts (not the Portuguese Fases). If the Phases header sits in the position of Services (column 20), that column is read only as Phases; in another column the sheet reads by position (1, 4 to 9, 11, 21 to 24), the whole file is refused, with the column in the message.
Inside the file, separate services with a comma: [SERVICE_A],[SERVICE_B].
The file itself is semicolon-delimited, so a semicolon inside a field becomes a new column and shifts the rest of the row silently.
How numbers are read
This applies to Width, Height, Thickness, Quantity, Weight and the edging allowance (EdgingAllowance and each side of EdgingAllowanceSides), in all three formats.
The decimal separator can be a dot or a comma — the system works out which, instead of demanding a format. What it will not do is guess when guessing is impossible:
| You send | Result | Why |
|---|---|---|
6.5 · 6,5 | 6.5 | A lone separator outside the thousands position is the decimal |
1.234,5 · 1,234.5 | 1234.5 | With both present, the last one is the decimal. Both conventions agree |
1.234.567 | 1234567 | The same separator repeated can only be grouping |
1.234 | REFUSED | Genuinely ambiguous: one thousand two hundred and thirty-four, or one point two three four? |
abc · 12mm · empty | REFUSED | Not a number |
Three guarantees that follow:
- Nothing becomes a plausible value. An unreadable number refuses the piece; it does not become
0in a measurement or1in a quantity. - The reason names the field, and lists every bad one in the row at once, so a spreadsheet can be fixed in a single pass.
- The result does not depend on our server. The same input reads the same way regardless of the machine's language settings.
1.234 meaning one thousandSend 1234. There is no way for the other side to tell that apart from a decimal, and guessing is exactly what we refuse to do.
Quantity missing means a single piece. Quantity fractional is refused rather than truncated — 2,5 pieces is an error in whatever produced the file, and rounding it to 2 would hide that.
How the due date is read
DueDate is the plant's local time, with no time zone. The same file means the same thing on any server.
| You send | Result |
|---|---|
2026-11-10 | The day, with no time: the piece is due by the end of that day, and it can leave in a load that departs any time that day |
2026-11-10T08:00 · 2026-11-10T08:00:00 · 2026-11-10 08:00 | That time at the plant |
2026-11-10T08:00:00Z · 2026-11-10T08:00:00+02:00 | REFUSED, and the reason quotes what you sent |
A time zone written by name: 2026-11-10T08:00:00 GMT · … UTC · … CET · 2026-11-10T08:00+01:00[Europe/Rome] · 2026-11-10 08:00:00 +0100 CET · 10/11/2026 08.00 cet · 2026-11-10 UTC | REFUSED, like the Z |
A word after the time or the date that is not a time zone: 2026-11-10 08:00 HS · … HRS · … ORE · … TURNO · 10/11/2026 N/A | CREATED with the default date and the warning, like the row below |
Text that cannot be read and has no time zone: 20261110 · 2026-02-30 · 08:00 (a time with no date) | CREATED with the default date, the plant's today plus 30 days, and a warning on the item that quotes what you sent |
| empty | The plant's today plus 30 days, with no time, and no warning |
Which names count as a time zone. Only these abbreviations, in any letter case: UTC, GMT, Z, CET, CEST, EET, EEST, WET, WEST, BST, MSK, EST, EDT, CST, CDT, MST, MDT, PST, PDT, BRT, BRST, ART, IST, JST, AEST, AEDT. They count after the time (08:00 or 08.00, and after AM or PM) or after a date with no time, also in parentheses or brackets. An IANA name counts by its area (Europe/Rome, America/…, Etc/… and the others, also in brackets), and so does an offset after the time. Any other word is unreadable text, so the piece goes in with the default date and the warning. This includes a Windows time zone id (W. Europe Standard Time).
DueDate refuses the pieceConverting it would destroy the date-only meaning: in Rome, 2026-11-10T00:00:00Z is 01:00, no longer midnight, and the deadline would move almost a whole day earlier. Until 5 November 2026 a time zone was silently converted to the server's clock instead, and a time zone written by name silently became the default date. Send the plant's local time, without Z, an offset or a zone name. This also applies to a date that is not ISO.
An unreadable date does not refuse the piece. Refusing would take a valid order out of production because of its deadline, so the piece goes in with the same default date as a file without the column, and the warning tells you what arrived. Read it: the deadline the plant works to is not the one your ERP meant. Until 5 November 2026 this happened with no warning at all.
A date that is not ISO (10/11/2026) is read in the language of the request, which for the Mover.Glass Connector is Portuguese (day first). The Accept-Language header changes how it is read: with en, 10/11/2026 is 11 October, and 13/11/2026 cannot be read (month 13), so it gets the default date and the warning. Send ISO: it is the only format that reads the same everywhere.
The edging allowance
Edging grinds a little glass off each side, so the piece is cut larger and edging brings it back to its final size. Width and Height stay the final size — the one on the label, in m² and in the weight. Mover.Glass adds the allowance only when it asks for the cutting plan. Both columns are optional: a file without them keeps working, and the piece uses the allowance of its glass type.
| You send | Result |
|---|---|
| Both columns missing or empty | The piece inherits the glass type's allowance on the four sides |
EdgingAllowance = 1,5 | 1.5 mm on the four sides; 0 means none |
EdgingAllowanceSides = 1,5-3-1,5-0 | One value per side, top-right-bottom-left |
| Both, with the same values | Accepted |
| Both, with different values | REJECTED, with both in the reason: guessing which one counts is how glass gets cut to the wrong size |
A value that is not a number (abc, 1.234) | REJECTED, with the field in the reason — the same rule as Width |
A negative value (-1) | REJECTED: to inherit the glass type's allowance, leave the column empty |
Other than four sides, or an empty side (1,5-3, 1,5--3-0) | REJECTED |
The inherited allowance only applies to a piece whose route includes edging; a value you send (or 0) always applies. A piece with a shape (Shape whose outline is not a rectangle; a rectangle with holes counts as a rectangle) stores the allowance but does not use it for cutting yet.
ERP phases
Instead of the ready-made list of services in Services, a row can send the phase codes of your ERP in Phases, and Mover.Glass turns them into services through the plant's phase mapping (a dictionary of codes and rules kept at the plant). The column is optional: a file without it keeps working.
The format is CODE[*count][@mark], separated by commas: FL,FOR*2,FOR*4,TEMPCM@E. The count is a positive whole number (1 when missing); the mark (internal or external) is kept as it arrives, letter case included. Codes ignore letter case. A lone * is reserved for the plant's implicit phase, whose rules apply to every row.
The separators * (count) and @ (mark) are provisional: they will be confirmed against your ERP's phase codes, and may change if the codes themselves use those characters.
| You send | Result |
|---|---|
| The column missing | No change: the row uses Services |
Phases filled and Services empty | The phase mapping: the piece is created with the services it gave, in the usual routing, in the plant's standard order, and the phases are stored as they arrived. The mapping decides which stages the piece has, not their order: FixedRouting does not apply to a row sent through Phases, and the item carries a warning when it came switched on |
Phases empty and Services filled | The ready-made list, as always |
Both Phases and Services filled | REJECTED: it is ambiguous; send one of the two |
A badly written phase (FL,,TEM, FOR*0, BIS@, a * in the row) | REJECTED, with Phases='…' and the reason, together with any unreadable number of the row |
| A code the plant has not registered | REJECTED, with the codes in the reason; they go to the plant's queue of codes to register. Once registered, send the row again |
| A deactivated code, a rule whose condition cannot be evaluated, or a code with rules where none applies to the row | REJECTED, with the code in the reason |
| Phases that give no service | REJECTED |
| A service of the mapping that the plant registered twice with the same description | REJECTED, with the service in the reason |
| Phases that give a single service | REJECTED by the routing, as a ready-made list with a single service |
- Keep the
Phasesfield on every row. A row with bothPhasesandServicesempty, and a row that stops before thePhasesfield (a CSV writer that drops the trailing separators), are not covered by this table: send the separators up to thePhasescolumn. - The material of a rule (laminated or not) is the one of the glass type already registered: a glass type created by the import starts as monolithic, so register laminated glass types first. The item carries a
warningwhen the glass type was new. - The shape is, for now, the
Shapeor theDrawingsent in the file; the rectangle Mover.Glass draws from the size does not count. This rule is provisional and may change..xlsxhas noShapeorDrawingcolumn, so a piece sent in.xlsxnever has a shape. - In
.xlsx,Phasesis found by its header.
Cancelled pieces
Cancelled=True returns REJECTED, and nothing is stored — not the piece, not the glass type or customer it would have created.
This is deliberate. Registering something that is already cancelled is noise, and returning CREATED for a piece your own system cancelled would be technically true and practically misleading.
Refusing does not reserve anything: the barcode stays free. If the cancellation is undone and you resend the piece active, it goes in normally.
Getting a sample
The Mover.Glass Connector that runs at your site ships with a working example package. The Send sample button drops it into the input folder and the normal cycle processes it — a way to prove the pipeline end to end without waiting for your ERP.