A logistics company's order, personnel and field data lived in three separate places: phone notes, WhatsApp groups and Excel. We unified it all into a single role-based panel.

Problem: no visibility, scattered responsibility

Reaching any piece of information meant calling someone; the manager could not get a real-time answer to 'what's happening in the field right now?'. As manual steps grew, errors and delays were inevitable.

Why custom architecture, not an off-the-shelf package?

We had to process bank movements, WhatsApp requests and feeds from existing cameras in one flow, then distribute them to different screens by role. That is solved with the right architecture, not plugin patches. (When is custom software a must?)

Architecture

Integration layer — Python: services that collect and normalize bank, WhatsApp and camera data.
Mobile — React Native: a single codebase where field and management reach the same data from their phones.
Dashboard — role-based access: the manager sees the whole operation; each staff member sees and acts only on their own screen.
Image processing: without changing the existing cameras, incoming feeds are processed and added to the system as data — zero hardware investment.

Result

Order, personnel and field data in one panel, in real time. Management and field act from the same screen; the 'call someone' step disappeared and manual data entry dropped to a minimum.

Takeaway

In B2B automation what matters is not 'which package to buy' but 'where the data actually comes from and where it flows'. With the right architecture, the phone–Excel load melts away on its own.

Ekursoft is an İzmir-based software studio; we build custom software, B2B portals and automation end to end with C#/.NET, React Native and Python. Thinking of a similar system? Talk to the engineers directly →