"I never approved that" costs a print shop the price of a 15,000-unit label run. BaskıGATE lifts approval out of the chat log and turns it into evidence: the artwork approved, the specification as it stood, and the moment of decision, all recorded so they cannot be altered afterwards.
Your customer opens no account and installs no app — one link is enough.
| Approved by | Serkan Özdemir |
| Company | Anadolu Foods Ltd. |
| Product | Olive oil 500 ml back label |
| Quantity | 25,000 |
| Link | opened 3 times |
None of it is carelessness. It breaks because the process is built on tools that keep no record.
No installation, no server, no licence file. It opens in a browser; the designer from a desktop, the account manager from a phone and the customer from their own device all look at the same job.
Roll and sheet labels, shrink sleeves, self-adhesive products.
Unwind direction, roll diameter, core size and die number each stand as their own approval item — the "it came off the wrong way round" argument goes on the record instead.
Folding carton, micro-flute boxes, kraft and food packaging.
The die line is uploaded as its own layer; the customer sees the artwork and the cutting line on top of each other and approves both at once.
Books, catalogues, brochures, stationery and corporate print.
A multi-page PDF opens as it is; the customer zooms in on whichever page they like and leaves a correction note on that exact spot.
Tight deadlines, many jobs, small quantities.
The problem is not the approval itself but the waiting. The staged reminder chain chases the customer without you picking up the phone, and the dashboard shows in one screen which jobs sit with you and which sit with them.
Garment printing, promotional items, signage and wide-format digital.
Asking for a sample is its own decision: the customer can approve every other item and still ask for a sample on colour alone, and the job cannot reach production until that sample is approved.
Teams who design on behalf of a brand and send the printing out.
You collect the approval, so you carry the liability. Because the artwork and specification your client approved are bound to the same fingerprint as the file you hand the printer, no version gets lost in between.
The artwork is still prepared on the designer’s computer and the source file stays there. The only thing that changes is where the approval is recorded.
Unwind direction, size and colour — the details the customer approves
The JPG that goes to the customer is uploaded; size, quantity, unwind direction, colour and material are typed in. The source file is never uploaded — it is kept as a link.
One link, by WhatsApp or email. The customer opens no account and sets no password — they open it on their phone.
They approve, or they drop a pin on the artwork and write a correction. Notes become a two-way conversation; only the customer can close one.
If no answer comes the reminders go out by themselves: email first, then WhatsApp, then the backup approver. All within working hours.
Approval is bound to the combined fingerprint of the artwork and the specification as they stood. If either changes afterwards the approval falls away by itself and the job goes back to the designer. Nobody can print a new file on an old approval.
Nothing more. Each screen answers exactly one question.
Artwork, size, colour, material, quantity and deadline are each approved separately. The "I approved it, but the quantity was wrong" argument disappears.
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.
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 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.
Not a stored PDF but a document rebuilt from the record every time. Artwork, specification, timestamps and chain verification, all on one sheet.
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.
No. The customer gets a single link that opens in their phone’s browser. No account, no password, no app. The link itself stands in for identity, and it expires.
No. The source working file stays on the designer’s computer; the system keeps only a link to it. What does go into the system is the approval artwork shown to the customer and the print PDF.
The approval becomes void by itself, the job goes back to the designer and a fresh approval is requested from the customer. This cannot be switched off — it is the reason the system exists.
Yes. BaskıGATE does not manage production or job numbers; it is the approval layer. The ERP gets a read-only view and the two systems meet over it. Nobody types the same data twice.
The system stores the artwork, the specification, the wording shown and the decision as they were at the moment of approval, with timestamps, in a form that cannot be altered; the record chain shows whether anything was tampered with afterwards. That is strong evidence in a dispute — but it is not legal advice; talk to your lawyer about your contracts.
Yes. Language is set per customer: the approval screen, the reminder emails and the approval certificate all go out in that language. Your own team carries on in Turkish — the language of the panel is independent of the customer’s.
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.