Bursa
Software for manufacturers operating in Bursa
In a manufacturing company, software gets judged on one thing first: shifts. A system that miscalculates a shift is not forgiven for any other feature.
What we build most often here
An automotive-supplier and textile manufacturing base.
Workforce and shift management
Timesheets, overtime and leave across multiple shifts — with no biometric data, in line with the 2026 Turkish prohibition.
Workforce managementERP and production links
Two-way flow of order, stock and production data into accounting. Spreadsheets stop being the transport layer.
IntegrationsDealer and B2B portal
Dealers see their own pricing, stock availability and order history. Phone-order load drops.
Web developmentWhy shift calculations fail so often
The single most common defect is a system that cannot split a night shift across two calendar days. A shift running 23:00 to 07:00 becomes two incomplete days in any system built on calendar-day logic, and payroll disputes follow immediately.
The second is break and overtime rules. Every company has its own practice and the defaults shipped with off-the-shelf products rarely match. When the rules cannot be expressed in the system, the team exports to a spreadsheet and corrects by hand — at which point the system is no longer being used.
The third is shift rotation: the week in which an employee changes shift. Fewer systems handle this correctly than claim to. So the first thing we do here is take your real shift scenarios and verify the arithmetic by hand before anything is bought.
Test these before you buy
Watching a demo is not testing. Enter your own scenarios.
- Enter a night shift. Is 23:00–07:00 one day or split in two?
- Enter a rotation week. Does the arithmetic hold when someone changes shift mid-week?
- Enter your own break rule. Is it configurable, or fixed?
- Enter work on a public holiday. Is the multiplier applied correctly?
- Export to payroll. Does it come out in the format your payroll team uses, or does someone reformat it by hand?
Frequently asked
Do you have an office in Bursa?
No — we work remotely. Setup, training and go-live run online with screen sharing. Work requiring physical installation on site — terminal mounting, cabling — needs a local supplier and we treat it as a separate line in the project plan rather than implying we cover it.
We use fingerprint readers. What happens now?
Turkish data-protection principle decision 2026/921 (Official Gazette, 2 June 2026) made fingerprint and face-recognition attendance tracking unlawful — even with employee consent. The good news is that most terminals keep working in card or PIN mode, so the hardware is not necessarily wasted. The steps and their order are set out in our migration guide. We handle the technical migration; the legal documents are your lawyer’s work. Note this is a Turkish rule — your plants in other countries need a separate assessment.
Connectivity on the shop floor is poor. Does mobile check-in work?
It works, but the setup has to account for it. The app records offline and syncs when the connection returns, so a record is not lost in a weak-signal corner of the plant. We raise this early because not every product advertised as “cloud-based” works offline, and on a production floor that is the most common disappointment.
Is a dealer portal the same as an e-commerce site?
No. In a dealer portal, pricing varies per customer, stock visibility can be restricted per dealer, payment usually runs through an account balance, and orders go through an approval flow. Forcing a retail commerce platform into that role generates manual work at every price change. We do build setups that run both, but the distinction has to be made up front.
Tell us how your plant runs
Describe your shift structure and existing systems. We will run your own scenarios through it — if the arithmetic does not hold, you will see it before you commit.