Will we have to replace our current accounting software?
No. If you run a backbone such as Logo, Mikro or Netsis, it stays where it is; we do not disturb your receivables, invoicing or e-document set-up. The layer we build passes intake and dispatch records into it and reads cost and stock data out of it. The custom layer connects to your ERP through the routes its vendor supports (API, service layer or an approved import); it does not write directly into the ERP's database tables. The route depends on the version and licence and is agreed in writing during discovery.
Can it talk to our weighbridge and laboratory instruments?
On the weighbridge side, in most cases yes; we can show a set-up that brings a weighbridge and a label printer together on the same screen on a working example during discovery. Most electronic weighbridges output weight data over a serial port or the network, and we read it from there. With laboratory instruments it varies by brand; some provide file or database output, some do not. During discovery we list your instruments and tell you in advance which ones we can pull data from.
Will you be the ones setting the blend formula?
No, and that is deliberate. The blend decision is made with your miller's knowledge earned over years and the state of that day's silos; it would not be right for an outside software developer to set it. What we do is bring that decision onto a calculation screen: putting target values, silo qualities and costs side by side and showing the scenarios comparatively. The decision stays with the miller — the only difference is that the decision is now on record.
We are a small mill; won't this system be too heavy for us?
According to our own OSB research, the great majority of companies here are micro, small or medium-sized, and we shape the work accordingly. You can start with a single module. Starting with intake and laboratory records only, then moving on to blending and costing once data has accumulated, is the route we recommend most often. We do not think it is right to sell a large installation from day one.
Our team is not comfortable with computers; can they use it?
We design the screens knowing that reality. The weighbridge operator's screen has three to five fields and the rest fills in automatically; the laboratory screen is the digital counterpart of the analysis slip, so there is no new layout to learn. During go-live we stand beside your team on site and resolve the early snags in place. Writing software that nobody uses does nobody any good.
How long does this take, and how is the budget set?
Silo count, instrument integration and how many flour types you run directly change both the duration and the price. We do not quote a figure before discovery is complete; after discovery, each phase is written up with its own scope, duration and price. When the first phase ends, the decision to continue is yours — we do not ask for a long commitment up front. We also have a guide page explaining how you should choose between an off-the-shelf package and custom software.
Where will our data live, and who will own it?
Depending on your preference, it lives on your own server or in a cloud account opened in your name. 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. We hand over the handover file together with delivery.
What is a wheat blend (paçal)?
In milling, the blend (paçal in Turkish) is the mix created by combining wheat of different characteristics, held in different silos, in set ratios to hit the flour quality and cost you want. The blend decision is made according to the target protein, gluten and ash values and the state of the silos. Our blend calculation screen puts these targets side by side with the quality and cost data of the silos available and compares scenarios; your miller sets the formula, and the decision is recorded with the date and the user.