Pan Enterprise Solutions, the software arm of Pan Innovation House · based in Gaziantep, Türkiye, with a London office
We do not replace your accounting backbone, whether it is Logo, Mikro, Netsis (widely used Turkish ERPs) or SAP. From yarn intake to weaving and knitting, from dyeing-finishing to cutting-sewing and the subcontract workshops, we move the production that currently runs on Excel and WhatsApp onto a single real-time, traceable and reconciled 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.
In this sector the accounting side is usually settled in an ERP, while production, subcontracting and quality data often sit outside it. If the points below sound familiar, the issue is not replacing the ERP — it is building the right layer on top of it.
The industry's software landscape splits in two: the horizontal accounting/ERP backbone and the sector-specific technical tools (CAD, colour, cutting, RIP). Each layer does its own job well, but the gap between them stays open. Let us lay the table out as it is, so it is clear where the solution fits.
| Layer | Software in use today | The gap it leaves |
|---|---|---|
| General ERP / accounting (the horizontal backbone) | Logo (Tiger/GO and textile editions), Mikro, Netsis, SAP ERP/S4HANA, Nebim V3, ETA, CanIAS | Solid for finance, e-invoice/e-dispatch/e-ledger, purchasing, stock and accounts; this backbone is fixed because of Turkish Revenue Administration (GİB) obligations. But it was not designed to track the yarn-weaving-dyeing-cutting-sewing floor and the subcontract flow in detail; production usually stays outside. |
| Textile-specific sector ERP / production tracking | Login ERP, True ERP (TrueBilişim), Netadam Startex, Enfotek EDS, Trendsoft, Solves, Extreme Business Solutions (TexTREME / AppsTREME); plus legacy DOS/Access programs written for individual firms | Close to the sector for work-order-based production, variant matrices and pre/post costing. In most installations, though, integration with the accounting ERP is only partial, subcontracting and shop-floor data capture fall short, and company-specific flows never quite fit the standard modules. |
| Design and weaving-knitting CAD (technical design) | NedGraphics (Texcelle, Loom Editor), EAT DesignScope Victor, Pointcarre, Shima Seiki SDS-ONE APEX, Stoll M1plus, AVA CAD/CAM | The standard for jacquard/dobby design, 3D fabric simulation and sending files to machines; NedGraphics and Pointcarre are widespread in carpet and home textiles. Once the design file is produced, connecting it to production tracking, costing and orders remains manual. |
| Apparel CAD/CAM — patterns, spreading, cutting | Lectra (Modaris, Diamino), Gerber AccuMark, Optitex, Audaces, Assyst/Bullmer, StyleCAD; CLO 3D and Browzwear in 3D | A strong ecosystem for patterns, size sets, marker optimisation and automatic cutting. The actual fabric consumption and marker efficiency in the output rarely reconcile automatically with the cost in the ERP or with subcontract cutting tracking. |
| Colour, dye house laboratory and quality | Datacolor (spectrophotometer + MATCH/PROCESS), X-Rite (Ci6x + Color iQC/iMatch), light booths, dye machine control/dosing systems | The industry standard for colour measurement, recipe calculation and Delta E quality control. Transferring the laboratory recipe to the dye house production recipe and dosing is usually done by hand; batch history and the cost of re-dyeing are not measured systematically. |
| Collection / PLM and sample management | Centric PLM, Lectra Kubix Link, Bamboo Rose, PTC FlexPLM, the Enfotek EDS PLM/PDM module | Corporate brands run real PLM: season planning, BOM/tech-packs and approval loops are digital. Most SME manufacturers either use no PLM or access their customer's PLM from outside, and manage samples and revisions in Excel. |
| E-export, B2B and digital print RIP | ideaSoft, Ticimax, T-Soft, B2B Store; marketplace (Trendyol/Hepsiburada/Amazon/Etsy) integrators; ErgoSoft, Caldera and Wasatch SoftRIP in printing | Functional for online sales, marketplace synchronisation and digital print colour management. Size-colour-design variants, tiered wholesale pricing and export order flows stretch the standard packages; two-way links to production and stock are usually left half-built. |
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 production, subcontracting, traceability, colour and quality to it. We start with an on-site survey, then build only the modules you genuinely need.
A one-way/two-way synchronisation bridge between Logo, Mikro, Netsis or SAP accounting and production tracking, CAD/PLM, Datacolor colour and e-commerce. Information is entered in one place and the correct data flows to every system; double entry and inconsistency end.
A mobile field application that sends work orders to the yarn, dyeing, printing and sewing workshops; tracks outgoing and incoming goods, waste, deadlines and prices with QR codes/barcodes; and generates automatic reconciliation and payment statements. It replaces WhatsApp and the notebook.
Barcode/QR terminals or machine counter integration at the weaving, knitting, dyeing, cutting and sewing points; a live board showing real-time output, downtime and OEE instead of end-of-shift paper.
A chain under a single batch number from yarn lot to dye recipe, from loom to dispatch. Root causes are found when claims arise; the infrastructure is ready for digital product passports and supply chain evidence in export.
Integration that automatically transfers the Datacolor/X-Rite laboratory recipe to the dye house production recipe and the dosing system; 4-point fabric inspection on tablets, defect maps and photo evidence; a quality scorecard per workshop.
Decision support showing order profitability, actual-versus-estimated cost variance, waste, workshop performance, machine efficiency and deadline deviation on a single screen. Simple and mobile, built for carpet and home textile business owners.
No company needs all of them. After the survey 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.
Work-order-based production from yarn intake to greige fabric and from knitting metreage to roll output, with efficiency and downtime tracking per loom and machine; shift reports are generated automatically.
Detailed page → QRA mobile field system that tracks goods going to and returning from workshops with QR codes/barcodes, measures waste and deadlines, and produces month-end reconciliation and payment statements automatically.
Detailed page → APIOne-way/two-way synchronisation of stock, accounts, order and invoice data between Logo/Mikro/Netsis/SAP and production, subcontracting, colour and e-commerce.
Detailed page →An integration layer that transfers the Datacolor/X-Rite laboratory recipe to the production recipe and dosing, and measures re-dyeing cost against batch history.
4-point fabric inspection on tablet/mobile, metreage, defect maps and photo evidence; a quality scorecard and trend analysis per workshop and supplier.
A management board showing order profitability, actual vs. estimated cost, waste, workshop and machine performance and deadline deviation on a single screen.
Detailed page →Simple, SME-friendly collection management that migrates you off Excel and handles tech-pack versioning, sample approval loops and costing.
A size-colour-design variant catalogue, multi-marketplace and B2B wholesale portal synchronisation, foreign currency and tiered wholesale pricing, and export order-dispatch-invoice automation.
Detailed page →A module that keeps the chemical inventory, SDS, ZDHC/OEKO-TEX/GOTS certificates and KKDIK registration records in one place, and generates the audit file for brand audits automatically.
Your finance and accounting backbone (Logo, Mikro, Netsis, SAP or CanIAS) stays in place; your e-invoice, e-ledger and accounts routines are 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, accounts, orders and invoices are kept in a single source of truth, and production and subcontracting data flow 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 product range (yarn, weaving, knitting, dyeing-finishing, apparel, carpet, home textiles), 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.
We observe the looms, knitting machines, dye vessels, cutting room, sewing lines and subcontract workshop flow in place. We map the data breaks between Logo/Mikro/Netsis/SAP, CAD, Datacolor and e-commerce, and chart the waste, reconciliation and traceability gaps.
We turn the survey findings into a prioritised roadmap: which module comes first, which integration connects where, which gain arrives first. We present a clear plan that protects your ERP, is module-based and is phased to your budget.
We start with the module that creates the most value (usually subcontract tracking or production/MES) and develop iteratively. At the end of every sprint we show a working version, fine-tuned with feedback from the craftsmen and managers on the floor.
We commission the system on the floor and in the office, and train operators, foremen and managers by role. After go-live, maintenance and development support continue under a separate written agreement. The source code we write and your data are handed over to you as defined in the contract.
We are based in Gaziantep. We write down your flow at the looms, dye vessels and subcontract workshops 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 shop-floor gap; your existing routines are not disturbed.
No two carpet factories, no two dye houses are the same. We build for your flow, your variant structure and your subcontracting model; we carry no unnecessary features.
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.
We design in lot-based traceability and ZDHC/OEKO-TEX/GOTS/KKDIK compliance from the start; we make preparing for the export market's audit demands easier. Certification and conformity decisions belong to the certification body.
We never push 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 accounts routines are not disturbed. The production, subcontracting 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 aim is not to install a second accounting system but to connect the floor your ERP cannot see.
We send work orders to the workshops from the system and record outgoing and returning goods with QR codes/barcodes. How much went out, how much came back, how much was wasted and which workshop missed its deadline are visible in real time. At month end, reconciliation and payment statements are calculated automatically; the process that ran on WhatsApp and notebooks rests on a shared record instead.
Usually possible, but the route depends on your Datacolor/X-Rite version and the file, service or database access you have; we confirm it in discovery before committing in writing. Where access allows, we build a bridge that transfers the colour recipe produced in the laboratory to the dye house production recipe and the dosing system. We store batch history and measure the cost of re-dyeing. Batch-to-batch colour inconsistency and the waste caused by manual recipe transfer fall as a result.
Usually possible, but the route depends on the export options of your version; 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. For example, we match the actual fabric consumption from Lectra/Gerber marker efficiency with the cost of the order and with subcontract cutting tracking, closing the gap between design and production.
Yes, it can be a good fit. In machine-made carpet, towel, bathrobe, curtain and blanket production, the needs that stand out are yarn-weaving traceability, subcontract tracking and the owner's dashboard. Unlike retail-focused solutions, we concentrate on the production and traceability side.
We build a compliance module that keeps the chemical inventory, SDS, certificates and KKDIK records in one place. When a brand audit comes, you can compile the required file from the system instead of preparing it from scratch every time. The certification decision belongs to the certification body; we keep the records needed for audit preparation in one place.
No. After the on-site survey we start with the module that creates the most value; this is usually subcontract tracking or production/MES. Once you have seen the gain, we add the other modules — the colour bridge, quality, 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.
Mostly the systems to be connected: the ERP, CAD and the colour laboratory, for example. On top of that come the terminals and screens needed on the floor, the size of the subcontract workshop network, the number of users and any migration of old data. We discuss a budget range in the first call; the exact scope, timeline and price are put in writing after discovery.
A process owner who knows the flow, IT or ERP-vendor support to show how the ERP can be connected, access to the plant for on-site observation, and sample documents (work orders, subcontract delivery notes, dispatch lists). Getting the subcontract workshops on board is also easier with your backing.
We choose a few measures with you during discovery: for example, the time spent on month-end subcontract reconciliation, goods sent to workshops without a record, or the delay before production data reaches the system. 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.
Let us observe your production in place, from loom to dye vessel and from subcontract workshop to dispatch. Without replacing your existing ERP, let's draw up a realistic roadmap that starts where it hurts most. The first step is a discovery meeting.
