IGMarkt Schierstein: A Modern Market Management App with WhatsApp OTP Authentication

Digitizing Local Market Operations

Weekly markets and farmers‘ markets are a cornerstone of community life in German towns. But behind the vibrant stalls and fresh produce lies a complex management challenge: coordinating vendors, managing stall assignments, tracking attendance, handling payments, and communicating with dozens of independent operators. IGMarkt Schierstein is a modern web application purpose-built for the Schierstein weekly market (Wochenmarkt) that replaces paper-based processes with a digital platform accessible from any device.

What makes this application stand out is its WhatsApp OTP authentication — instead of forcing market vendors (many of whom are not tech-savvy) to remember yet another username and password, the system sends a one-time code via WhatsApp. Open your phone, tap the code, and you are in.

„No passwords to remember. No apps to install. Just your phone number and a WhatsApp message. That is how authentication should work for community platforms.“

The Problem

Market management in small to medium German towns faces persistent challenges:

• Paper-based operations: Vendor registrations, stall assignments, and attendance tracking happen on paper or in spreadsheets, leading to data loss and inefficiency
• Communication overhead: Market masters (Marktmeister) rely on phone calls and personal visits to notify vendors about schedule changes, weather alerts, or policy updates
• Authentication barriers: Many vendors are small business operators who struggle with traditional login systems; password resets and forgotten credentials create friction
• No mobile access: Existing tools (if any) are desktop-only, while market operations happen on foot in the field
• Limited visibility: Administrators lack real-time dashboards showing vendor status, market statistics, and operational metrics
• No notification system: Sending bulk notifications to vendors requires manual effort via phone or email

The Solution

IGMarkt Schierstein provides a role-based platform with three primary user types: Administrators, Market Masters (Marktmeister), and Vendors (Beschicker). Each role has tailored interfaces and permissions, all accessible through a responsive web application that works on both desktop and mobile devices.

The cornerstone innovation is the WhatsApp OTP authentication flow: users enter their phone number, receive a 6-digit code via WhatsApp, and are authenticated with a session cookie. This eliminates password management entirely while maintaining security through rate limiting, code expiration, and attempt limiting.

Key Features

Conclusion

IGMarkt Schierstein demonstrates that community-focused applications can be both powerful and accessible. By replacing passwords with WhatsApp OTP authentication, it removes the single biggest barrier to adoption for non-technical users. The role-based interface ensures that administrators, market masters, and vendors each see exactly what they need, while the mobile-first design makes the platform usable in the field where market operations actually happen. For other German towns looking to digitize their weekly market operations, this project provides a proven blueprint.

What I Learned

Building for a community of non-technical users in a real German town forced me to think about UX and authentication in ways that enterprise software rarely demands.

Authentication UX is a Product Decision, Not a Technical One

The choice to use WhatsApp OTP instead of traditional username/password was made after watching actual market vendors struggle with forgotten passwords in a prototype. For people who run a vegetable stand or artisan bakery, rotating passwords and recovery emails are genuine friction. WhatsApp is already on their phone and already understood. The technical complexity of implementing OTP via WhatsApp Web.js was justified entirely by the UX improvement for the end user.

Role-Based Design Must Match Real Organizational Structure

The three-role model (Administrator, Marktmeister, Beschicker) came from spending time with actual market staff before writing a line of code. Initial prototypes had a flat permission model, which quickly proved unworkable — market masters needed to see operational data but not financial settings, vendors needed to see their own profile but not other vendors‘. Getting roles right early saved significant rework.

Community Software Requires Trust-Building

Municipal and community organizations in Germany are conservative adopters. The market committee needed to see physical evidence of data security (GDPR compliance documentation, local server hosting), understand who owned the data, and have a clear answer to „what happens if you stop maintaining this?“ These questions are not technical — they are about institutional trust. Building in data export functionality and clear documentation was as important as the features themselves.

WhatsApp Rate Limits in Practice

Sending bulk notifications via WhatsApp to all vendors sounds simple until you hit the messaging rate limits. WhatsApp Web.js has per-number sending limits, and a market with 50 vendors means 50 messages in quick succession. Implementing a queue with configurable delays between messages — rather than firing all notifications at once — was essential to avoid being flagged as spam and having the WhatsApp account suspended.

Field Usage Reveals Hidden Requirements

Watching market masters use the application on Saturday morning — in the field, on a phone, with market setup chaos around them — revealed requirements that no amount of office-based user research would have uncovered. Key insights: the attendance tracking screen needed to work with one thumb, the stall assignment view needed to be scannable at a glance from 2 meters away, and the notification confirmation dialog needed to be impossible to trigger accidentally.