Pan Enterprise Solutions, the software arm of Pan Innovation House · based in Gaziantep, Türkiye, with a London office
Pan Innovation House (Gaziantep, Türkiye) develops custom software for machine-made carpet factories. We do not replace your accounting backbone, whether it is Logo, Mikro, Netsis (widely used Turkish ERPs) or SAP. We take the speed, downtime and yarn-break data coming from your Van de Wiele and Schönherr looms; your jacquard designs and yarn recipes; your roll, length and lot traceability; and your quality and weight-list records out of the Excel-and-notebook routine on the shop floor, and move them into a single real-time, traceable operational layer. Not an off-the-shelf package — built for your business. The source code we write and your data are handed over to you as defined in the contract.
Asking about price? We listen to the scope in a short call and share the budget frame and timeline in writing. 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 work on site for plants in and around Gaziantep; elsewhere in Türkiye and abroad, discovery starts by video call and a visit is planned if needed. Our London office is at Unit 6 Cranford Way, Hornsey, London N8 9DG.
Machine-made carpet production is concentrated in Gaziantep, and in this sector the finance backbone is usually settled in an ERP. The trouble is that looms, designs, yarn recipes and shipments run outside the system. If the points below sound familiar, the issue is not replacing your ERP but building the right layer on top of it.
The sector's software landscape is layered: a horizontal accounting/ERP backbone, carpet-specific production tracking (MES), imported design CAD, loom control software and e-transformation tools. Each layer does its own job, but the gaps between them stay open. Here is the landscape as it stands, so it is clear where our layer fits.
| Layer | Software in use today | The gap it leaves |
|---|---|---|
| General ERP / accounting (horizontal backbone) | Logo Tiger 3 Enterprise, Logo Netsis 3 Enterprise, Mikro, SAP, Aaro, DIA, ETA, CanIAS | Solid for current accounts, stock, purchasing, cost accounting, finance and e-invoicing; because of Revenue Administration (GİB) obligations this backbone stays fixed. In the carpet sector it is a common approach to connect weaving-tracking software to the accounting ERP through a separate integration. On its own, however, it cannot cover sector-specific production depth such as looms, designs and yarn. |
| Carpet-specific ERP + production/shop-floor tracking (MES) | KeyCarp + Netsim ERP (Pkey Labs, Gaziantep), Netloom, Login ERP (textiles), LEO Textile (Güncel Yazılım), Kaitek textile solutions, Konzek MES, Fi-Mes productivity system | Close to carpet-specific needs such as weight-based yarn consumption and waste tracking, loom speed/downtime/yarn-break monitoring, OEE, anti-slip backing/gel/print process management and barcoded weight lists. In most installations, however, they are only partly integrated with the general ERP; company-specific workflows do not fully fit the standard modules, and shop-floor data collection can remain incomplete. |
| Design / jacquard CAD-CAM (sector-specific, mostly imported) | NedGraphics (Texcelle, Jacquard Design), EAT DesignScope, Booet, Simetri Desen Tasarım pattern-design software for Bonas/Stäubli/Grosse/Schleicher jacquard systems, Zimmer/Colortec tufting interfaces | The standard for drawing carpet, jacquard and tuft designs, colour reduction, yarn consumption estimates, weaving simulation (Wilton/Shaggy/Axminster) and sending files directly to the loom. The problem the sector openly highlights is that all of this software is imported; connecting the yarn and colour recipes coming from the design to production tracking and costing remains manual. |
| Machine integration / weaving loom software | Van de Wiele loom control software, Schönherr/Vandewiele weaving controllers, machine PLC/SCADA data (API, database or XML-CSV file integration) | It is possible to pull loom speed, downtime, yarn-break counts and produced metreage from the machine; API-based integration is the healthiest option, with database or file-based integration as alternatives. In most plants this data is either never collected or entered manually; unless it flows automatically into the MES/ERP, OEE and downtime analysis are impossible. |
| Export / e-transformation / customs | The Revenue Administration (GİB) export e-invoice portal (efatura.gtb.gov.tr), Logo/Mikro/Paraşüt/Mysoft e-invoice and e-archive modules, ETGB (declarations via DHL/UPS/PTT) | Handles export e-invoices, English invoices and packing lists with GTİP/HS codes, fast exports via ETGB (Türkiye's e-commerce customs declaration; check the Ministry of Trade's current announcements for value and weight limits) and VAT refund processes. In most firms, however, the link between the customs and destination-country document set and production and shipment data is manual. |
| Shop-floor data collection / identification (hardware-software) | Barcode/RFID labelling (e.g. Ilgazi RFID), handheld-terminal roll/metreage scanning, production boards and andon screens | Used for barcoding rolls, printing length and lot details on labels, scanning at dispatch and tracking warehouse locations; carpet-specific MES products (KeyCarp etc.) also include barcode modules. Without a standard infrastructure, stock discrepancies and missing backward traceability persist. |
Product names are compiled from vendors' public pages (September 2026); PAN is not affiliated with them. The "gap" column summarises situations we commonly meet in discovery and is not a statement about any specific product.
Our solution is not a rival to your existing software; it is the operational layer that fills the disconnect between them. Your accounting ERP stays as the finance backbone; we connect the loom, design, yarn-recipe, traceability, quality and export side to it. We start with on-site discovery, then build only the modules you genuinely need.
An MES layer that pulls speed, downtime, yarn-break and metreage data from Van de Wiele/Schönherr looms via API, database or files, and shows real-time OEE instead of end-of-shift paperwork. Automatic downtime-reason classification and Pareto analysis make the root causes of unplanned stoppages visible.
Integration that automatically pulls yarn consumption and colour recipes from NedGraphics or EAT design files and links them to work orders, stock reservations and costing. Double data entry and design-driven waste variance are reduced, and the gap between design and production closes.
A layer that holds the recipe for every design-colour-yarn variation and compares weight-based consumption, planned versus actual. Because recipe accuracy is the foundation of costing, waste and variance become measurable by design and by loom.
Every roll is barcode/RFID labelled with its loom, yarn batch, shift and operator. It is scanned at dispatch, a customer complaint can be traced fully backwards, and weight lists are generated automatically; wrong-roll shipments and stock discrepancies end.
Operators record quality (first/second grade, weaving defects), scrap and rework in real time via handheld terminals or touch panels. Central andon screens showing the live state of the production line make the shop floor transparent.
Decision support showing true yarn cost, OEE, waste rate, profit per m2 and delivery deviations by loom, design and customer on a single screen. Simple, mobile and data-driven — built for the carpet company owner.
No firm needs all of them. After discovery we start where it hurts most and grow module by module. The scope is set in discovery; modules are designed to fit your ERP and your floor.
An MES that pulls speed, downtime, yarn breaks and metreage from Van de Wiele/Schönherr looms and produces real-time OEE by loom and line, automatic downtime-reason classification and Pareto analysis.
See the module → APIA one-way/two-way integration layer connecting Van de Wiele/Schönherr PLC/SCADA data and Logo/Mikro/Netsis/SAP at stock, current-account, order and invoice level.
See the module →Integration that automatically pulls yarn consumption and colour recipes from NedGraphics/EAT design files and links them to work orders, stock reservations and costing; it puts an end to double data entry.
A shop-floor system that barcode/RFID labels every roll with its loom, yarn batch, shift and operator, scans it at dispatch, and delivers full backward traceability and automatic weight lists.
See the module →First/second grade, weaving defect, scrap and rework records via handheld terminals and touch panels; central andon screens showing live production-line status, plus a quality scorecard.
A management panel showing true yarn cost, OEE, waste, profit per m2 and delivery deviations by loom, design and customer on a single screen.
See the module → APIA module that automatically generates English invoices with GTİP/HS codes, packing/weight lists and the ETGB e-invoice set from production and shipment data, making VAT refunds and customs paperwork traceable.
See the module → AIA design assistant aligned with the sector's declared goal of independence from imported software: it generates colour reductions and design variations, and checks producibility against yarn and loom constraints.
See the module →Shelf addressing by roll, barcoded goods-in and goods-out, location tracking and dispatch preparation; the warehouse and the system stay identical at all times, and the risk of shipping wrong quantities drops.
Your finance and accounting backbone (Logo Tiger/Netsis 3 Enterprise, Mikro, SAP or CanIAS) stays in place; your e-invoice, e-ledger and current-account order is never disturbed. The operational 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: stock, current accounts, orders and invoices are kept in a single source of truth, and loom and design data flows into it. You neither end up with a second accounting system nor keep running the shop floor on Excel.
Our integration approach →We discuss your production set-up (Wilton/Shaggy/Axminster, loom park, design and yarn variety), your current ERP and the operational point that hurts most. We clarify expectations and scope and draw a realistic frame; at this stage the priority is understanding, not selling. The call carries no obligation. 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 come to the factory; we observe your Van de Wiele/Schönherr looms, your design and yarn-recipe flow, your roll-length-lot practice, quality and dispatch in person. We map the disconnects between Logo/Mikro/Netsis/SAP, NedGraphics/EAT and loom data, along with waste and traceability gaps.
We turn the discovery findings into a prioritised roadmap: which module comes first, which integration connects where, which gain arrives earliest. We present a clear plan that protects your ERP, is module-based and phased to your budget. Not a fantasy — field-ready and staged.
We start with the module that creates the most value (usually loom MES/OEE or roll-lot traceability) and develop iteratively. At the end of every sprint we show a working version; we fine-tune with feedback from the master weavers and managers on the floor. No surprises.
We commission the system on the shop floor and in the office, and train operators, foremen and managers by role. After go-live we stay at your side with maintenance, SLAs and development support. The software grows with you as new needs emerge; The source code we write and your data are handed over to you as defined in the contract.
We are based in Gaziantep, where machine-made carpet production is concentrated. We write down your looms, jacquard, yarn recipes and shifts by listening to you on site; the starting point is your flow, not our assumptions.
Your Logo, Mikro, Netsis, SAP or CanIAS backbone stays in place. We build the operational layer that works alongside it and closes the gap between loom and dispatch; your existing order is not disturbed.
No two carpet factories are the same; loom parks, design structures and yarn variety differ. We write to your flow and never charge for modules you do not use.
Dependence on imported design and production software is a concern often raised in the sector. Without forcing you to replace your existing tools, we build a Turkish-language layer that fits the floor; AI-assisted helpers can be added to the scope where useful.
We build a chain on a single batch number from yarn batch to loom, from roll to dispatch and on to the ETGB paperwork; records for complaints, audits and exports sit in one chain.
We never force you to build everything at once. We start where it hurts most, demonstrate the gain, then grow; we spread your budget across phases and lower the risk.
No. Your accounting and finance backbone stays exactly as it is; your e-invoice, e-ledger and current-account order is not disturbed. The loom, design and traceability 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. The route depends on the version and licence and is agreed in writing during discovery. The goal is not to build a second accounting system but to connect the shop floor the ERP cannot see.
Usually possible, but the route depends on the loom's control software version and the access its maker allows; we confirm it in discovery before committing in writing. Where access allows, we pull loom speed, downtime, yarn-break counts and produced metreage from the machines. API-based integration is the healthiest option; where that is not possible we connect via the database or XML-CSV files. Feeding this data into the MES layer, we deliver real-time OEE, automatic downtime-reason classification and Pareto analysis.
Usually possible, but the route depends on your design software's version and export options; we confirm it in discovery before committing in writing. We do not replace these CAD tools; we connect their outputs to the production and costing side. Yarn consumption and colour recipes coming from the design file are transferred automatically to work orders, stock reservations and costing. The double data entry and waste variance caused by keying recipes into the ERP by hand are reduced.
We never force you to abandon your existing NedGraphics/EAT investment; we first fix the disconnect through integration. Alongside that, we can also develop an AI-assisted local design assistant that generates colour reductions and design variations and checks producibility against yarn and loom constraints. We define the scope together during on-site discovery.
We barcode or RFID-label every roll with its loom, yarn batch, shift and operator. We scan at dispatch and, in a customer complaint, trace back exactly which loom and yarn batch caused the problem. Weight lists are also generated automatically from this data; wrong-roll shipments and stock discrepancies end.
We can automate the document preparation; the declaration itself remains the responsibility of your customs broker and you. We build a module that prepares English invoices with GTİP/HS codes, packing and weight lists and the documents needed for the ETGB (e-commerce customs declaration) e-invoice set from production and shipment data. Because ETGB value and weight limits can change with regulation, the system keeps them configurable rather than hard-coded; check the Ministry of Trade's announcements for the current limit. It makes the VAT refund process traceable and reduces operational errors and delays as e-exports grow.
No. After on-site discovery we start with the module that creates the most value; usually that is loom MES/OEE or roll-lot traceability. Once you see the gain, we add the other modules — the design bridge, quality/andon, BI or e-export. We spread the budget across phases and lower the risk.
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. You can continue with another team later if you wish.
The number of looms and their data output, the need for a bridge to the design software, roll and lot labelling points, the export document set, and the route into your ERP. We discuss a budget range in the first call; the exact scope, timeline and price are put in writing after discovery.
One person each from production and design, a loom list with control software details, the export options of your design software, ERP connection details, and a sample work order, roll label and packing list.
During discovery we choose the measures that suit you, such as loom efficiency, how consistently downtime reasons are recorded, or how long it takes to find the faulty batch behind a customer complaint. We do not set targets before measuring the starting point; we agree them with you, based on your current data, before work begins, and results are not guaranteed.
An MES (manufacturing execution system) is the software layer that captures, in real time at the machine and on the line, how a work order is actually carried out on the shop floor, and records production, downtime, waste and batch data. In carpet, it means loom speed, downtime, the number of yarn breaks and the metres produced come from the loom rather than from paper at the end of the shift. The MES layer we build uses this data to provide real-time OEE, automatic downtime-reason classification and Pareto analysis.
We would like to see your production on site — from the looms to the yarn store, from the design desk to dispatch and the weight list. Without replacing your existing ERP, we then draw up a realistic roadmap that starts where it hurts most. The first step is a free initial call; the scope of an on-site discovery, and its fee if any, is agreed in writing during that call.
