Özgür Işık Damar
ServicesService

Fulfillment & Warehouse Management

Off-the-shelf WMS products assume your warehouse works like everyone else's. Real warehouses never do. I build fulfillment software shaped around the operation that actually exists — and one of them runs a cross-border warehouse every day.

When you'd call me

  • The warehouse runs on Excel and one person's memory, and both are reaching their limits.
  • You've evaluated ready-made WMS products and every demo ended with "we'd have to change how we work to fit the tool".
  • Your operation crosses a border — customs declarations, status feeds and paperwork are part of the daily flow, not an edge case.
  • Operator errors are climbing, and every mis-scan or wrong shelf costs real money further downstream.

What I do

  • A package lifecycle modeled as a finite state machine — the current one has 45 states, so every package has exactly one truth and illegal transitions are impossible by construction.
  • Operator interfaces built for the floor — the bilingual Macedonian/Turkish UI I designed cut operator errors by 31%.
  • Customs integration — declaration API, webhook-driven status flow, and parsers defensive enough to survive 14 different schema variants.
  • Barcode scanning flows, role-based access that keeps drivers away from mutations they shouldn't touch, and a dedicated returns lane.
  • A Flutter field app covering both sides of the operation: warehouse floor and courier.

Numbers, not adjectives

The Skopje warehouse runs on this system daily: a 45-state package FSM, bilingual operator screens, barcode flows, driver RBAC and a returns lane. The interface redesign alone took operator errors down 31%, and the customs integration has digested every schema variant the declaration API has thrown at it — fourteen so far.

Field notes

Where we'd start

Discovery means standing in your flow: I map the current operation into an explicit state diagram — every step, every exception, every "that almost never happens" that happens weekly. You get the state map plus a build plan, and the map alone usually pays for the discovery.