Seshat 1.9.3 checks folded products for what should not be folded
Send the folds of a folder and Seshat reports text near a fold, barcodes whose quiet zone a fold touches, faces cut by a fold and small logos a fold runs through.
A folder can pass every check and still fail in the hand: a headline broken by the fold, a QR code that no longer scans, a face folded in two. Seshat 1.9.3 checks folded products for exactly that.
How it works
Send the folds with the order, measured from the trim's top left, for example "folds": [{"axis": "x", "at_mm": 99}, {"axis": "x", "at_mm": 198}] for a tri-fold. You work out the positions from the product yourself, because roll folds with a narrower inside panel, Z-folds and gate folds all differ. Seshat then reports:
- Text that crosses a fold or comes closer to it than the safe distance.
- Barcodes and QR codes whose bars or quiet zone a fold touches. GS1 does not allow barcodes on a fold, crease or seam, quiet zone included. For retail barcodes (EAN, UPC) this is an error; for other codes, such as a QR code on a flyer, a warning.
- Faces in photos that a fold cuts through or comes close to. They are found by face detection on the page, which also finds small faces in group photos.
- Small pictures and shapes, such as a logo or an icon, that a fold runs through, as a note.
Photos and backgrounds that run across the panels are folded by design and are left alone. Each finding gives the fold and the place.
The shop decides the distance
There is no official standard for folds, so each shop sets its own safe distance (fold_safe_mm), and what counts as small (fold_small_mm). Without them, Seshat keeps 3 mm from a fold, as is common practice, and counts pictures and shapes up to 50 mm as small. The GS1 rule for barcodes always applies.