Yavuz Çelik

In manufacturing plants, downtime durations, downtime causes and scrap counts are still written onto paper forms by hand and retyped into a spreadsheet later. Because these values feed downtime and OEE calculations, a wrong value written silently to a database costs more than a rejected one.

I built a hybrid pipeline that routes each field to a recognition path suited to its type and attaches a quality decision to every output. The form is first aligned to its template and fields are read from their own cells; a quality layer then sends each value either to automatic acceptance or to a human review queue. The system does not promise guaranteed accuracy; it measures its uncertainty.

Companies with dealer networks across different industries (motorcycle parts, carpets, tractors, textile) took orders by phone and Excel, then entered them into their ERP by hand. Each client had its own price lists, stock rules and payment flows.

I built a multi-tenant B2B/B2C platform on .NET 8, derived from a single core product and customized per client. I designed an abstraction that supports both Logo and Bay.t ERPs in the same codebase, and automated the order-to-invoice cycle.

Account reconciliation was a slow, legally required process where accounting teams emailed hundreds of counterparties by hand every month and tracked replies in Excel. Handing out the ERP database password was also a security risk.

I built a multi-tenant SaaS with ASP.NET Core 8 and Clean Architecture. Companies email balance/statement reconciliations to their counterparties, who approve or dispute them through a tokenized page. ERP data is accessed through an allow-listed relay agent, so the database password never leaves the company.

Field sales reps noted visits on paper and called the office to learn customer balances. Managers had no visibility into who was where in the field.

I built a mobile app with React Native 0.81 + Expo 54 (TypeScript) and a JWT-protected Web API on ASP.NET Core 8. Visits are GPS-stamped, manager assignments are delivered via server-side Expo Push, and the customer's LOGO account statement can be viewed in the field.