What we are talking about here is not machine automation. We don't install PLCs, SCADA, sensors or robot arms. We take the place in your factory where people wait for each other — the paper traffic running from purchase requests to leave forms, from quote approvals to advances and document flows — and move it into software. We travel from zone one to zone five of the Başpınar organised industrial zone (OSB) and to the administrative offices in Şehitkamil, map the process desk by desk, and then we write it.
Prepared by Pan Innovation House, a software company based in Gaziantep, Türkiye · Last reviewed:
We are based in Gaziantep, Türkiye, with a London office at Unit 6 Cranford Way, Hornsey, London N8 9DG. On-site discovery covers plants in and around Gaziantep; elsewhere in Türkiye and abroad it starts by video call and a visit is planned if needed. The first 30-minute call is free; the scope of an on-site discovery, and its fee if any, is agreed in writing during that call.
We don't dress your factory in an off-the-shelf approval package. We take the arrangement that genuinely operates in your business — who can sign off what, and up to what amount — and carry it into software as it is. Not all of the modules below will be needed; we start where the complaints are loudest.
Every form — purchase request, leave, advance, expense, material issue, quote approval — opens from a single place. From the moment a request is opened, whose desk it is on, what stage it is at and how long it has been waiting are visible to everyone involved. You never have to phone anyone to find out who is waiting on what.
Approval steps are written into the system by amount range, department, cost centre and request type. A purchase below the limit you set ends at the supervisor; anything above it comes to you. The deputy who steps in while you are out of town or at a fair — and the time limit on that — is defined in advance; the signature queue waits for no one.
When a pending request exceeds the set time, the system first reminds the person responsible, then moves it up a level. Delays become visible before anyone even notices them — not when the line stops. How many days each approver keeps things waiting becomes measurable data.
The approval screen is designed for mobile. From a fair, the road or a customer visit, you see the request, the attached quote and the past prices of the same material — and approve. A system that requires sitting down at a computer simply doesn't work for an owner who works in the field and on the road.
Quotes, proformas, contracts, delivery notes and certificates are attached to the request and kept version by version. The record of who did what and when is stored so it cannot be altered afterwards. The evidence requested in an export customer's audit or an inspection comes out of the system, with no hunting through binders.
Your existing accounting backbone — Logo, Mikro, Netsis — stays where it is. An approved request lands there as an order, and the incoming invoice is tied to the request. We don't build a second accounting system; we simply connect the approval path your ERP cannot see. If there is no suitable interface, we say so up front and put the limits of the alternative in writing.
We come to your plant in Başpınar or Şehitkamil. We watch how a request actually travels across the purchasing, accounting, production and HR desks. The written procedure and the reality on the floor are rarely the same; we take the reality on the floor as our basis.
Which form, at what amount, goes from whom to whom; what the exceptions are; how the rule flexes in an emergency. We reduce this to a one-page diagram, show it to you, and only start writing code after your sign-off. Misunderstandings end at this step.
We usually start with purchase request-approval, because that is where most of the complaints come from. A single flow goes live and runs on real requests for a few weeks. Fine-tuning follows the objections of the staff who use it.
Once the pilot has settled, leave, advances, expenses, quote approvals and document flow are added in turn. Each flow goes live separately; we don't switch everything on in one day and throw a shift into confusion.
We give short role-based training: approvers, requesters and field staff separately. We then continue under a maintenance and support agreement. The source code we write and your data are handed over to you as defined in the contract; you can carry on with another team whenever you choose.
No — and the distinction matters. In industry, automation usually means the control systems that run the machines: PLC and SCADA. What we do is workflow automation — moving the approval and document traffic where people wait for each other into software. Nobody touches your machines, and your control panels stay exactly as they are. If you want to discuss the production-data side, that is a separate job and is planned separately.
No. Your accounting and finance backbone stays as it is, and your e-invoice and e-ledger arrangements are untouched. The flow layer we build connects to your ERP through the routes its vendor supports (API, service layer or an approved import) and does not write directly into its database tables: an approved request lands in the ERP as an order, and the incoming invoice is tied back to the request. The aim is not to install a second accounting system.
Today even small purchases come to you, because the limit was set verbally. With the limit written into the system, requests below the amount you define end at the supervisor and never reach you; you look only at what genuinely needs a decision. A delegation rule that kicks in while you are out of town is also defined, so the signature queue never stops.
The deciding factor here is adoption, not technology. That is why we build the flow close to your staff's current habits, keep the screens simple, and launch the pilot with a single flow. Rather than forcing anyone, we make the paper genuinely unnecessary: once a request is opened in the system and its status can be seen, people stop asking for the paper after a while. On the foreman's side, the screen is big enough to use with gloves and takes only a few steps.
The duration depends on the number of flows and the depth of integration, so we don't quote a number of days up front. Our method is fixed: discovery, flow map, a pilot with a single flow, then staged expansion. For the pilot we usually pick purchase request-approval, because that is where the complaints come from and where the result shows fastest.
The system keeps who approved what amount, when and on what grounds as a record that cannot be altered afterwards, and stores the documents on the request together with their versions. That record covers the trail you need to show in inspections and in export customers' audits. If a process requires electronic signatures, we discuss that separately and clarify the legal side with your own adviser.
The source code we write and your data are handed over to you as defined in the contract; third-party and open-source components remain subject to their own licences. It can also be installed on your own server, and you can continue with another team later.
We do — but this page is precisely about proximity. Being able to reach a plant in Başpınar OSB or Şehitkamil the same day and watch the process at the desk makes a difference no remote analysis can match. It is also what makes it possible for us to be on site during go-live week.
A workflow is the process structure that sets out how a request or document moves through defined steps and approval levels: from whom to whom, and by which rule. When it is built in software, every step, waiting time and approval is recorded. In the workflows we set up, purchase requests, leave, cash advances and document approvals are opened from one place; amount limits, delegation and reminder rules are written into the system.
We come to your plant, spend half a day at the purchasing and approval desks, and map the flow exactly as it is. Even if no project comes out of the meeting, you are at least left with a written version of your own approval chain. We can be in Başpınar OSB or Şehitkamil the same day.
