Seshat's file check, ready-made for your own site

A print file is best checked while your customer is still ordering, not after the order has reached your prepress desk. Until now that meant building the upload screen yourself on top of Seshat's calls. Now there is a ready-made one: the file check.

Four steps your customer understands

1. Upload. The customer drops the artwork on your product page.
2. Check. Seshat checks it against your specs: size, trim and bleed, colours and total ink, pictures and fonts, the safe zone.
3. Read. Every finding has Seshat's decision (we fix this, your choice, can't print or a note). Next to it is a proof of the page with the trim, bleed and safe zone drawn on it.
4. Fix and verify. One click makes the fixes, and the fixed file is checked again in the same step. The customer then downloads the print-ready file.

Your workflow

You pass the specs per product, or a recipe you keep in your Rekhu account. The fixes can happen in four ways:

• On a click: the customer presses Fix it for me.
• The customer picks: they tick which fixes to make.
• At once: the fixes are made right after the check.
• Check only: the findings and the proof, with nothing changed.

You can switch the proof, the explanation for the customer and the download on or off. Your server decides which fixes are allowed at all.

It comes in Rekhu's own look, light or dark, and takes your colours, fonts and corners through CSS. The words come in English, Dutch, German, French and Arabic, or your own.

One component, one package

The widget, @rekhu/seshat-widget, works in Vue, React, Next.js, Nuxt or plain HTML. It talks only to your own server, with your own login. Version 0.14.0 of the core packages adds the routes it needs:

• Node.js: rekhu.seshatServer({ user }), with .express() or .fetch.
• Laravel: REKHU_SESHAT_ROUTES=true. The Laravel package also serves the widget, so a Blade page needs no npm.

Your Rekhu key stays on your server. Problems with your Rekhu account, such as the key or the credit, are logged for you and never shown to your customer.

Also in this release

When the explanation for the customer cannot be written for a moment, a check now still returns its findings, without the explanation. Before, the whole check failed even though it had been done.

Prices

The widget is free. A check costs $0.05 per file up to 20 pages and a fix $0.02, as in your own code; the proof and the explanation are included.

See it on the file check page, and the set-up in the core package docs.