In carpet, a product is not a single item; when one design is produced in five sizes and three colours, you are looking at dozens of separate stock items. General-purpose ERPs were not designed to carry this matrix, so in most plants the gap is patched with Excel. Without touching your accounting software, we bring the assortment, weaving lots, loom status and export packing lists into one system. We start by coming to your weaving floor in Başpınar and watching a shift in person.
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.
In carpet the basic unit is not the design but the design-size-colour triple. Build the system on that assumption and stock, orders, production and packing lists all feed from the same data. You do not need to do everything below at once; we decide together which comes first after the site visit.
Every combination is defined with its own stock identity but appears on screen as a matrix under its design, so you are not lost among hundreds of items. Warehouse stock, open orders and quantities in production intersect in the same table. A mixed assortment order is entered and tracked line by line, not as a single item.
Which loom is running which design and which lot, how long it stood idle and why — all gathered on one screen. Downtime reasons are picked from a fixed list so that later you can count how much time each cause consumed. Whether the data comes from the machines or from operator entry is decided by looking at your loom park.
Every roll or piece is labelled with its loom, yarn lot, shift and date, and scanned at dispatch. On a customer complaint you walk back through the chain and see what happened at which link; the conversation turns on records, not guesses.
Defect types are recorded from a standard list; over time it becomes visible which defect repeats on which design and which loom produces more rejects. Second-quality stock is held separately by size and design, turning the goods on hand into a sellable list.
What goes into each bale is scanned and recorded; the packing list and weight list are generated from that record. Because the assortment on the list and the goods in the container come from the same data, no gap can open between them. The document sent to the customer comes from the same source.
Once yarn consumption, wastage, loom downtime and subcontract labour are collected in one place, real cost per square metre becomes calculable. The management screen gives a simple summary by design, customer and loom; no need to ask for reports.
We talk about your loom count, product range, export share and the software you currently use. A half-hour conversation, at no charge — and if we think this work is not right for you, we say that too.
We come to the factory. We watch the weaving floor, the yarn store, the quality table, the warehouse layout and dispatch in person, and talk separately with operators, the quality lead and the storekeeper. The output is a written map of where data is created and where it goes missing.
We settle your design, size, colour and quality coding into a single standard. This step comes before any software; no stock system ever holds up unless the coding is built properly first. Together we also produce the conversion list that carries your existing codes into the new structure.
We usually start with the assortment and stock side, because everything else rests on it. At each stage we show a working version; only after the storekeeper and the planner have tried it do we move to the next. Before stepping outside the scope, we talk first.
While the system goes live, the old record-keeping runs in parallel for a while; we do not switch the old way off until a stock count shows the two sides match. Maintenance and development support continue afterwards. The source code we write and your data are handed over to you as defined in the contract.
It will. Whether you run Logo, Mikro, Netsis or something else, your receivables, invoicing and finance side stays where it is. The layer we build holds the production and stock side and exchanges data with your accounting. 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.
It depends on the loom park. If the machine side offers a data interface, a database or a file output, we read from it. If not, we set up operator entry at a terminal — kept up consistently, that too produces usable data. We tell you which route is possible during discovery, after looking at your looms; we do not make promises up front.
No. Your design tools stay where they are; we connect their output to the production and costing side. Our aim is not to draw designs, but to make visible how many pieces of a drawn design were produced in which sizes, and what they cost.
It grows in the background, not on screen. The user opens the design card and sees the size and colour matrix beneath it; nobody hunts through individual cards. This is exactly where complexity should be loaded onto the system rather than the user — and exactly where general-purpose ERPs struggle with carpet.
We generate the packing and weight lists from production and dispatch data; the assortment breakdown sent to the customer comes from the same data. Customs and tax declarations continue to be handled by your existing setup with your customs broker; we feed it the data.
In that case we start by understanding what you have. If the installed program and database are available, what the system does can usually be worked out from its running state, within the limits the program's licence agreement allows. We write down plainly what could and could not be recovered. We can show this approach on a working example during discovery; we do not name clients without their consent.
It depends on loom count, product range and the state of your current data. We split the work into fixed-scope phases; the first phase is usually the assortment and stock side. Timeline and price are put in writing up front, and after seeing the result the decision to continue is yours.
We do. But on the carpet side our real value is being here: reaching a factory in Başpınar the same day and watching a shift in person is a different thing from an arrangement run remotely. This page was written for producers within the city anyway.
Let us see your production in person — from the loom to the yarn store, from the quality table to container loading. Together we pinpoint where the assortment is recorded and where it goes missing. You end up with a roadmap that starts where you struggle most, without replacing your current software.
