The hard part of exporting is not the loading; it is the commitment left behind once the loading is done. If, as your Inward Processing Authorisation Certificate (DİİB) runs towards expiry, you learn how much of your commitment has been discharged by checking when an Excel file was last updated, you are carrying a financial risk that nobody is tracking. We build an operations layer that brings the certificate, production, documents, letters of credit and containers together in one place. Your accounting software stays where it is; we come to your plant in Başpınar or Şehitkamil and open your file together.
The system we build does not take your customs broker's place, nor does it replace your accounting software. Its job is to create the link between the certificate, production and dispatch, and to stop deadlines slipping past unnoticed. In other words, it does not file the declaration; it keeps the data the declaration needs ready, and tells you how many days remain until closure before you ask.
Every certificate is registered in the system: import and export lines, GTİP codes, quantities and currency amounts, the certificate deadline and the time remaining for the closure application. Fulfilled and outstanding commitments are calculated continuously. When the thresholds you set are reached, alerts go to the responsible people; the reminder is not left to anyone's diary.
The imported raw material lot, the works order, the finished product and the resulting customs declaration are linked in a single chain. The equivalence link is recorded at the moment it happens, not while the closure file is being prepared. The closure file stops being an archive exercise compiled from scratch months later.
ATR, EUR.1, EUR-MED, certificates of origin and other documents are collected in a single file per shipment. A checklist shows which documents the destination country requires; a shipment cannot be closed while anything is missing. During an audit or a customer request, everything comes out of one screen.
The documents the letter of credit requires, the latest shipment date and the presentation period are entered into the system and tied to the shipment schedule. The production and dispatch teams see on their own screens which terms they must meet. Alerts fire as critical dates approach, and discrepancy risk is discussed before loading.
The proforma, the weight and packing lists and the invoice are generated from the same order data. A revision made in one place flows through to all of them; three separate Excel files disagreeing with each other is no longer a possibility. Documents come out in the language and layout your customer requires.
A screen that plans container placement using pallet and carton dimensions, weight and volume. Loading order, weight distribution and remaining volume are visible before the truck reaches the ramp. Because the plan lives in the system rather than on paper, the question of what was loaded has a recorded answer after dispatch.
We talk through how many countries you export to, how many DİİBs are open at the same time, how the division of labour with your customs broker is set up, and where the greatest risk sits right now. The aim is not to write a proposal but to work out whether the problem is genuinely one that software solves. No obligation.
We come to your plant in Başpınar or Şehitkamil, sit down with your foreign trade team and open a real certificate file from start to finish. Which information comes from where, which step waits in whose hands, which check depends solely on one person's attention — we put all of it in writing. Without this step, the right scope for this work cannot be produced.
We phase the findings in order of risk. In most companies the first phase is the DİİB register and deadline alerts, because that is where an oversight produces the heaviest consequences. The document file, letter of credit tracking and the loading plan are left to later phases. The duration, scope and price of each phase are written up separately.
We build the module, then enter an already closed certificate into the system and check whether the result matches the known outcome. Verifying against an old certificate before moving to a new one is a solid way to reduce the chance of surprises. We ask your customs broker to take part in this check as well.
We take the system live and train the foreign trade and dispatch teams by role. When regulations change, we review the affected areas together; the maintenance and support agreement covers this. The source code and the data stay with you and are delivered together with the handover file.
No, and we want to say that plainly. Obtaining the certificate, filing the closure application and interpreting the regulations are the work of your customs broker and, where required, your sworn financial advisor; we do not do that work and do not claim we can. The system we build keeps the data that application needs accurate and up to date, counts down the deadlines and holds the file ready and waiting. In other words, it does not take your advisor's place — it hands them a ready file.
They will not, because the two look at different jobs. The broker's software sits on the declaration and customs side; our layer sits inside your factory: which imported lot produced which finished product, which shipment it went on, which certificate it was written against. Where possible, we bring in the declaration print-outs your broker provides and compare them against your own records. In most companies, that comparison turns out to be the most useful part.
Let's not overpromise here. The interfaces official systems expose are limited and change over time; we do not commit to a direct automatic connection up front. In practice, what we do is take declaration and certificate print-outs into the system as files, match them against your records and show the differences. During discovery we look at which data arrives by which route, and only then say what can genuinely be automated.
Standard foreign trade modules generally hold the invoice, the declaration and the account; but they usually do not hold the equivalence link between the certificate and production, or the deadline countdown. And that is exactly where the problem appears. If the module in your ERP does create that link, we will not sell you new software — we will tell you that you need to use what you already have properly. It is one of the first things we look at during discovery.
This is an area where risk grows as the team shrinks, because everything depends on the attention of those one or two people. When that person goes on leave or resigns, the calendar goes with them. In a small team, starting with a single module — just the certificate register and deadline alerts — is often enough. According to our own OSB research, most of the exporters here are SME-sized anyway.
The number of open certificates, the countries and document variety you work with and the systems we need to integrate with directly change the duration. We do not quote a figure before discovery is complete; after that, each phase is written up with its own scope, duration and price, and at the end of the first phase the decision to continue is yours. We also have a guide page explaining what to watch out for when preparing a specification.
Depending on your preference, the system runs on your own server or in a cloud account opened in your name; the data stays under your control. Customer lists, price history and certificate files are protected with role-based permissions, and who accessed what is logged. The source code is yours as well, and we write that into the contract.
They will change — we design with that accepted from the outset. Deadlines, thresholds and document checklists are not hard-coded; they are kept as parameters you can change from the admin screen. So when a deadline or a rule changes, there is no need to rewrite the software — you update the setting. If a structural change is needed, we handle it together under the maintenance and support agreement.
If you export from Gaziantep, you have at least one certificate with the clock running on it right now. Name a convenient day and we will come to your plant and open that file together from start to finish. Let's see on site where information goes missing and whose diary each deadline depends on; then let's draw up a realistic plan in order of risk. In this meeting we do not talk sales — we look at the file.
