Net-Base Reference netNotdienst

Reference netNotdienst

Client-server software for pickup locker systems, status logic, code workflows, and real-world pharmacy operations.

At a glance

Reference netNotdienst at a glance

netNotdienst is, for us, one of the most important references when we want to demonstrate that we are strong beyond classic screen software as well. This solution connects client, server, hardware system, network, code logic, printing, and defined status transitions within real pharmacy operations. Projects exactly like this show whether software is merely presented—or can truly take responsibility in day-to-day work.

Client, server, hardware, and status logic as a shared system

Code keypad on a pickup locker system as part of the netNotdienst system
Code entry, the system side, and the security logic must interact precisely with the software.

The publicly documented BPV solution describes a clear two-component model. The server runs on the display computer, manages the pickup locker system, shows the on-call pharmacy service when idle, and provides visual feedback to the customer upon interaction. The client runs on checkout or workstation computers and implements the actual operating logic for staff: reserve a compartment, assign a code, print a receipt, place the goods inside, and advance the status.

The status logic is particularly strong. A compartment is not simply open or closed; it moves through defined states such as available, ready, active, and emptied. This turns a physical box into a controlled digital process. Staff always know the state of a handover, the customer receives a clear feedback channel, and operating errors are technically made more difficult.

In addition, there is the security logic around pickup codes, waiting times, expiring codes, and logging. Details like these turn a system into a robust operating system for a real process. Especially for clients, this is a strong signal: we do not build decorative digitizations, but systems that must deal with real risks, real actions, and real consequences of errors.

From an infrastructure perspective, the reference is equally clear. Communication takes place over the local network via TCP/IP, by default on port 8080, with a sensible recommendation for a fixed IP on the display PC. In addition, there are print paths for the pickup receipt and a configurable receipt design. Exactly these operational details separate calm, reliable enterprise software from hectic rework.

  • Server on the display PC as the technical lead for system setup, feedback, and process state
  • Client on POS and workstation PCs for fast, clear operation by staff
  • clear domain statuses instead of vague operating sequences: available, ready, active, and emptied
  • code logic, receipt printing, network paths, and hardware integration as part of the same architecture

Why netNotdienst sells so strongly as a reference

Real processes instead of theoretical software logic

netNotdienst shows that we remain sound even where software does not merely display data, but drives real processes, integrates devices, and must stay easy to operate for people in a demanding day-to-day situation.

Relevant far beyond the pharmacy

The pharmacy is only the visible field of use here. The same competence is needed in all projects with workstations, devices, fixed status transitions, approvals, codes, printing, and logged process steps.

Trust through technical calm

Anyone who sees that we implement such a solution cleanly and calmly immediately understands that we do not just build content pages or simple forms, but operationally relevant applications with real responsibility.

netNotdienst as a reference for operations-close enterprise software

If your own initiative works with devices, clear state models, feedback logic, networking, and safety-relevant process steps, netNotdienst makes it very clear that we can carry exactly such systems professionally and technically.

Read more: matching FAQ on netNotdienst

The questions behind netNotdienst usually go beyond the reference itself: services, portals, system boundaries, operational responsibility, and technical process control are classified in more depth in the FAQ hub.

Read more related FAQs about netNotdienst

The questions behind netNotdienst usually go beyond the reference itself: services, portals, system boundaries, operational responsibility, and technical process ownership are covered in more depth in the FAQ hub.