The approval layer: how BaskıGATE works
BaskıGATE does not run production, does not issue job numbers and does not replace your ERP. It takes on one interval: the time between the artwork being ready and the customer’s approval landing. In a print shop that is the interval that loses the most money.
Size, bleed and safe area — some of the details the customer approves
A job from beginning to end
1 · The job is opened
The account manager enters the customer and the job number. The customer’s WhatsApp or email text is pasted in as it is — any WeTransfer, Drive or Dropbox links inside it are picked up automatically and kept as the source file record. The source file itself is never uploaded: it stays on the designer’s computer.
2 · The specification is entered
Size, quantity, material, colours, unwind direction, roll diameter, barcode, deadline. Typed in by hand — because what the customer is shown must be what the print shop commits to, not what was guessed from a file. Every change creates a new version; the old one is not deleted.
3 · The approval artwork is uploaded
The designer uploads the JPG that will go to the customer. Front, back and die line can each be added separately. The server converts nothing: the file the customer sees is the file the designer uploaded.
4 · Approval is requested
The system generates a single link and seals the combined fingerprint of all the current artwork and the current specification onto it. The email goes out by itself; for WhatsApp a prepared message opens on the account manager’s own phone.
5 · The customer decides
Six items are approved separately. If any one is objected to, the job goes back for revision. If they say "I will not approve without seeing a sample", the job moves to awaiting sample and cannot reach production until the sample is approved.
6 · The approval is sealed
The approved files are locked, the job enters the product archive and a printable approval certificate is generated. From then on, if a file or a detail changes the approval falls away by itself — and that cannot be switched off.
To see how these steps follow one another on a single job, look at the example workflow: from the moment the enquiry arrives to the moment a dispute starts, with what goes on the record at each step.
See the example workflowWhat it does
Itemised approval
Artwork, size, colour, material, quantity and deadline are each approved separately. The "I approved it, but the quantity was wrong" argument disappears.
Two-way notes on the artwork
The customer drops a pin on the problem and writes; the designer replies under the same note. Only the customer can close it — saying "done" is not enough.
Reminder chain
Email after 4 hours, WhatsApp after 1 day, backup approver after 2 days, a "call them" alert to your team after 3. Never outside working hours or at weekends.
The customer keeps a copy
The moment they approve, a summary of the decision and the file fingerprints land in their own inbox. The record does not live on your server alone.
Approval certificate
Not a stored PDF but a document rebuilt from the record every time. Artwork, specification, timestamps and chain verification, all on one sheet.
Export an expert witness can read
The job’s entire record chain is exported together with the hash algorithm and the method used. The independent verifier runs without ever connecting to BaskıGATE.
The chain tip is sealed off-site
Every day the tip of the record chain is copied off the server: to the owner’s inbox and to the backup store. A timestamp from a certificate authority can be added on top.
Customer portal
One permanent link for the customer: every job’s status, one tap into whatever is waiting for approval, and the certificate for finished work. No account, no password.
Approval from a sample
The customer may say "I can’t decide on screen, I need to see a sample". The job moves to awaiting-sample; nothing goes to press until the sample is seen.
Assignment and whose court the ball is in
Every job has an owner, and the screen shows who is holding the ball: the account manager, the designer, or the customer.
Source file link
A WeTransfer, Drive or Dropbox link is attached to the job and marked once downloaded. The heavy working file never enters the system, but its trail is never lost.
Owner’s report
Daily, weekly, monthly. It splits elapsed time in two: time spent inside the print shop and time spent at the customer. The first share is usually higher than expected.
Product archive
Every approved job becomes a product record. Eight months later, on the repeat run, the last approved artwork and specification are right there — and what changed is shown separately.
Print file archive
The production PDF is uploaded after approval and then locked. Because the working file stays with the designer, this is the company’s permanent copy.
Your brand, not ours
Your logo, your colour and your name on every screen and every email your customer sees. If you prefer, the mail leaves from your own server.
Nightly off-site backup
Database and files are sent every night to a provider other than your host, and the size is verified at the far end.
Open to your ERP
Job numbers and production stay in the ERP. The two systems meet over a read-only view; nobody types the same data twice.
The customer sees what they are approving
The approval screen is a direct equivalent of the print shop’s own approval form: size and bleed, the unwind direction diagram, colour swatches, the barcode area. The customer sees the document they are used to — they learn no new interface.
These details are part of the approval: if one of them changes afterwards, the approval falls away.
| Product | Kraft label · 70 × 45 mm |
| Quantity | 15.000 |
| Unwind direction | C |
| Colour | CMYK + varnish |
| Material | Coated, matt varnish |
What it does not do
Saying what a product does not do matters as much as saying what it does. There are no surprises after it is set up.
Put your approvals on the record
BaskıGATE is being developed together with pilot print shops. Pilot shops use the product free of charge, set their own priorities directly, and steer what gets built next.