A packaging and plastics plant in Gaziantep gets squeezed from two directions at once: at the machine, and behind the promises made to customers. Injection and extrusion settings sit in the setter's notebook, nobody counts how many shots the mould has run, and how many pieces a reel will yield is talked through as a guess at quotation time. Without touching your accounting side (Logo, Mikro, Netsis), we build a layer that records the machine, mould, printing and scrap side. If your factory is in Başpınar, we come to you for the discovery visit.
Our aim is not to install a second accounting system in the plant. Your accounting backbone stays in place; we build the operational layer it cannot see — recording the machines, the moulds, the plates and the scrap — and connect it to your existing system. Modules can go live separately; we decide together which comes first after the site visit.
We open a digital card for every injection press, extrusion line and mould. The parameter recipe is stored with its versions; who changed what and when is visible. A shot counter runs on each mould, and when it reaches the threshold you set, a maintenance job drops onto the list by itself. Setting knowledge leaves the setter's notebook and becomes company property.
A screen that records the granule, masterbatch, additive and regrind ratio per lot. The ratio written in the recipe and the amount actually weighed on the floor sit side by side. On a colour or strength complaint, which raw-material lot and which ratio that lot was produced with reads back from a single screen.
A screen that calculates the cutting layout from reel or sheet width, product dimensions, die arrangement and edge margins. It puts alternative layouts side by side, showing how many pieces each yields and how much edge waste it leaves. When quoting, you use a calculation instead of a guess — and the decision remains yours.
Customer, job and plate/cylinder/die mapping, with shelf location, usage history and condition. When a repeat order arrives, where the plate is and whether it is fit for use is visible without a search. Print preparation rests on records, not memory.
Scrap stops being a single line; setup scrap, production scrap, print scrap and returns are recorded under separate codes. Every entry is tied to a machine, a shift and a work order. Tracing runs on one lot number from raw-material lot to shipped carton; the file your food or pharmaceutical customer asks for is produced from this record.
A board that reads orders from the ERP and places them on the machine and mould calendar. Sales sees which press frees up when, as it gives a delivery date. Because mould changeover times are recorded too, the true machine cost of short-run jobs becomes visible in its own right.
We talk about your machine park (how many presses, how many extrusion lines, whether you print), your current accounting software and the point that hurts most. In this call we are not trying to sell, but to understand whether your problem is genuinely one that software can solve. No obligation.
Whichever zone of Başpınar OSB or wherever in Şehitkamil you are, we come to your plant. We follow the flow in person from raw-material intake to the mould shop, from the printing unit to the cutting and packing line, and open the setter's notebook, your Excel files and your ERP screens together. The output is a written map of the broken links.
We turn the findings into a prioritised plan: which module first, which next, which integration connects where, and the timeline and budget of each phase. We do not propose doing everything at once; we present a phased plan that starts where it hurts most.
We build the approved first module and show working versions at short intervals. We design the screens simple enough for an operator to use with gloves on; wherever the foreman on the floor objects, we change the design. Any request outside the scope is discussed separately — it is never quietly added to the invoice.
We install the system on the line and train operators and managers according to their roles. After go-live we continue under a maintenance and support agreement. The source code and data stay with you; if you ever want to work with another team, you hold a system that can be handed over.
No. Your accounting, receivables and e-invoicing setup stays exactly as it is; we do not touch it. The layer we build talks to your ERP through its database or API: it reads orders and stock items from there and writes production and scrap results back. We have built a production layer alongside Netsis before without touching it at all; that is our approach.
It depends on what the machine offers. Newer machines carry an interface such as OPC UA or Euromap, or the maker's own database; where one exists, we read from it. If the machine is older, we set up simple counting from the cycle counter or a PLC signal and complete the rest with an operator terminal. During discovery we draw up the make-and-model list together and tell you in advance what can be captured from each; we do not write down something we do not know on the hope that it works.
We make no such claim. What it does is calculate alternative layouts within the die and edge-margin constraints you define, and show them side by side with piece counts and edge waste. Your setter makes the decision; the system simply grounds that decision in a visible calculation. What we say is that we move a job done on paper onto a screen — we promise nothing beyond that.
By our own OSB research, the great majority of companies here are micro, small or medium-sized. That is why we do not sell this as a single piece. You can start with one module — say, just the mould cards and shot counters — and continue if you see it earning its keep. Moving phase by phase is healthier for both the budget and the team's adjustment.
Yes — the tracing chain we build runs from raw-material lot to shipped carton: which granule lot, on which machine, in which shift, with which recipe it was produced, and on which dispatch note it left. But let us say this plainly: the software does not issue certificates, it keeps records. Responsibility for declarations of conformity and certification stays with you and your laboratory; we collect the production data that stands behind that declaration.
It depends on the number of machines, whether printing is involved and the systems we will integrate with. That is why we do not quote a single figure and then grow the scope; after discovery we put each phase in writing with its own timeline and its own price. At the end of the first phase, you decide whether to continue. We also have a guide page explaining in detail how our pricing is built.
The source code and database are yours. We talk about transfer of ownership, not a right to use, and we write it into the contract. We also deliver a handover file, so that if another team ever takes over, the knowledge needed to stand the system up is in your hands. Since part of our work is taking on and untangling software whose developers can no longer be reached, we take particular care never to put our own customers in that position.
Being in Gaziantep has one advantage: there is no need to guess from a distance. Tell us a day that suits you and we will come to your plant in Başpınar, follow the flow from raw-material intake to packing, and establish together which parts genuinely need software and which do not. This meeting is a discovery meeting; it can end without a quote.
