Freelance Developer Needed for Web MVP (Bar Ordering System – Extensible Architecture)
Budget: €1,500 – €3,000 EUR
PROJECT OVERVIEW
We are looking for a freelance developer to build a minimum, real-world MVP for a bar–supplier ordering system (supplier = beverage distributor / wholesaler).
The MVP focuses only on the core ordering flow, but it is critical that the codebase and data model are designed to be easily extensible in later phases (additional users, roles, messaging, analytics, integrations).
This is not a long-term role and not a full production system.
(Note: The term “supplier” is used generically and may represent different supplier types in the future (e.g. beverage, coffee, etc.), without changing the core ordering logic.)
MVP GOAL (VERY IMPORTANT)
Enable bars to place structured orders digitally and enable suppliers to receive those orders via email with an attached file, without requiring the supplier to log into the system.
The MVP must:
• work in real conditions
• be demo-ready
• avoid technical dead ends
USERS (PHASE 1)
Bar User
• One authenticated bar user
• One bar = one user (for now)
• Login / logout
Supplier
• No login
• No UI
• Receives orders only via email
However:
The data model must support future supplier users and multiple users per bar, without refactoring.
AUTHENTICATION (PHASE 1)
• Email + password login for bar users
• Clean structure allowing:
- multiple users per bar in the future
- additional user roles later (without implementing them now)
Do NOT hardcode logic assuming only one user forever.
BAR ↔ SUPPLIER RELATIONSHIP
• Each bar is assigned to one supplier
• Bar users can see only their assigned supplier
• Relationship should be modeled in a way that can later support:
- multiple suppliers per bar
- supplier users
(No UI for this in Phase 1.)
PRODUCTS
• Products belong to a supplier
• Bar user sees supplier product list
• Product fields:
o Product ID (internal reference)
o supplier’s product code
o product name
o unit (string)
No prices, no stock, no VAT is needed to be presented in phase 1.
ORDERING FLOW (CORE)
Create New Order
1. Select products & quantities
2. Review cart
3. Place order
System behavior:
• One order is created
• One unique Order ID is generated
• Order status = Placed
SUPPLIER EMAIL NOTIFICATION (CRITICAL)
When an order is placed:
Supplier receives an email containing:
• Subject:
New Order ORD-XXXX from Bar “Bar Name”
• Body:
o Bar name
o Order ID
o Order date/time
• Attachment (CSV) with:
o Order ID
o Product code
o Product name
o Quantity
The supplier must be able to:
• download the attachment
• copy/paste into their ERP
• process the order without clicking any external link
RESEND ORDER (SAME ORDER)
Bar user can:
• open order history
• open an order
• click:
“Resend order (in case supplier missed or deleted it)”
System rules:
• No new order created
• Same Order ID
• Same content
• Email subject must clearly indicate it is a resend (e.g. “RESENT – Order ORD-XXXX”)
This is mandatory to avoid duplicate orders.
ORDER HISTORY (BAR)
• List of past orders
• Each order shows:
- Order ID
- Date
- Status
• Order details view
SOURCE OF TRUTH
• Database is the single source of truth
• Emails and attachments are delivery mechanisms only
• Resending emails must never create duplicate orders
DEPLOYMENT
• MVP must be deployed to a demo / staging cloud environment
• Accessible via a public URL
• Not production-grade, but usable and testable
• All infrastructure access (server, database, email configuration) must be handed over to us.
EXPLICITLY OUT OF SCOPE (PHASE 1)
• Supplier login or UI
• Multiple bar users
• Permissions UI
• Messaging / chat
• Analytics
• ERP integrations
• SMS notifications
• Payments / invoicing
• Mobile native apps
EXTENSIBILITY REQUIREMENTS (VERY IMPORTANT)
The solution must be designed to support in future phases:
• multiple users per bar
• supplier users
• messaging / chat
• analytics
• integrations
Do not implement these features now.
Design the data model and structure so they can be added without refactoring.
TECHNICAL EXPECTATIONS
• Web application (frontend + backend)
• Clean, readable, documented code
• Git repository owned by us
• Git repository must be set up from day one, with regular commits
• Basic README (how to run / deploy)
• The data model and code structure should avoid hardcoded assumptions (e.g. single user, single supplier).
• Platform clarification (IMPORTANT):
- The MVP should be a web application, designed with a mobile-first / responsive UI, so that it works smoothly on both desktop and mobile browsers.
- Native mobile apps (iOS / Android) are explicitly out of scope for Phase 1, but the architecture should allow a future mobile app to be built on top of the same backend.
Preferred (not mandatory):
• Frontend: React or Angular
• Backend: Node.js / NestJS / Spring Boot
• Relational database
PROJECT TERMS
• MVP only (no long-term commitment)
• Payment will be milestone-based, with deliverables reviewed and approved at each stage.
• Full code ownership & IP transfer
• Clear communication and progress updates expected
TO APPLY
Please include:
1. Relevant past projects
2. Proposed tech stack
3. Estimated timeline for MVP delivery
4. Confirmation that you understand this is a minimal MVP with extensibility in mind
We are looking for a freelance developer to build a minimum, real-world MVP for a bar–supplier ordering system (supplier = beverage distributor / wholesaler).
The MVP focuses only on the core ordering flow, but it is critical that the codebase and data model are designed to be easily extensible in later phases (additional users, roles, messaging, analytics, integrations).
This is not a long-term role and not a full production system.
(Note: The term “supplier” is used generically and may represent different supplier types in the future (e.g. beverage, coffee, etc.), without changing the core ordering logic.)
MVP GOAL (VERY IMPORTANT)
Enable bars to place structured orders digitally and enable suppliers to receive those orders via email with an attached file, without requiring the supplier to log into the system.
The MVP must:
• work in real conditions
• be demo-ready
• avoid technical dead ends
USERS (PHASE 1)
Bar User
• One authenticated bar user
• One bar = one user (for now)
• Login / logout
Supplier
• No login
• No UI
• Receives orders only via email
However:
The data model must support future supplier users and multiple users per bar, without refactoring.
AUTHENTICATION (PHASE 1)
• Email + password login for bar users
• Clean structure allowing:
- multiple users per bar in the future
- additional user roles later (without implementing them now)
Do NOT hardcode logic assuming only one user forever.
BAR ↔ SUPPLIER RELATIONSHIP
• Each bar is assigned to one supplier
• Bar users can see only their assigned supplier
• Relationship should be modeled in a way that can later support:
- multiple suppliers per bar
- supplier users
(No UI for this in Phase 1.)
PRODUCTS
• Products belong to a supplier
• Bar user sees supplier product list
• Product fields:
o Product ID (internal reference)
o supplier’s product code
o product name
o unit (string)
No prices, no stock, no VAT is needed to be presented in phase 1.
ORDERING FLOW (CORE)
Create New Order
1. Select products & quantities
2. Review cart
3. Place order
System behavior:
• One order is created
• One unique Order ID is generated
• Order status = Placed
SUPPLIER EMAIL NOTIFICATION (CRITICAL)
When an order is placed:
Supplier receives an email containing:
• Subject:
New Order ORD-XXXX from Bar “Bar Name”
• Body:
o Bar name
o Order ID
o Order date/time
• Attachment (CSV) with:
o Order ID
o Product code
o Product name
o Quantity
The supplier must be able to:
• download the attachment
• copy/paste into their ERP
• process the order without clicking any external link
RESEND ORDER (SAME ORDER)
Bar user can:
• open order history
• open an order
• click:
“Resend order (in case supplier missed or deleted it)”
System rules:
• No new order created
• Same Order ID
• Same content
• Email subject must clearly indicate it is a resend (e.g. “RESENT – Order ORD-XXXX”)
This is mandatory to avoid duplicate orders.
ORDER HISTORY (BAR)
• List of past orders
• Each order shows:
- Order ID
- Date
- Status
• Order details view
SOURCE OF TRUTH
• Database is the single source of truth
• Emails and attachments are delivery mechanisms only
• Resending emails must never create duplicate orders
DEPLOYMENT
• MVP must be deployed to a demo / staging cloud environment
• Accessible via a public URL
• Not production-grade, but usable and testable
• All infrastructure access (server, database, email configuration) must be handed over to us.
EXPLICITLY OUT OF SCOPE (PHASE 1)
• Supplier login or UI
• Multiple bar users
• Permissions UI
• Messaging / chat
• Analytics
• ERP integrations
• SMS notifications
• Payments / invoicing
• Mobile native apps
EXTENSIBILITY REQUIREMENTS (VERY IMPORTANT)
The solution must be designed to support in future phases:
• multiple users per bar
• supplier users
• messaging / chat
• analytics
• integrations
Do not implement these features now.
Design the data model and structure so they can be added without refactoring.
TECHNICAL EXPECTATIONS
• Web application (frontend + backend)
• Clean, readable, documented code
• Git repository owned by us
• Git repository must be set up from day one, with regular commits
• Basic README (how to run / deploy)
• The data model and code structure should avoid hardcoded assumptions (e.g. single user, single supplier).
• Platform clarification (IMPORTANT):
- The MVP should be a web application, designed with a mobile-first / responsive UI, so that it works smoothly on both desktop and mobile browsers.
- Native mobile apps (iOS / Android) are explicitly out of scope for Phase 1, but the architecture should allow a future mobile app to be built on top of the same backend.
Preferred (not mandatory):
• Frontend: React or Angular
• Backend: Node.js / NestJS / Spring Boot
• Relational database
PROJECT TERMS
• MVP only (no long-term commitment)
• Payment will be milestone-based, with deliverables reviewed and approved at each stage.
• Full code ownership & IP transfer
• Clear communication and progress updates expected
TO APPLY
Please include:
1. Relevant past projects
2. Proposed tech stack
3. Estimated timeline for MVP delivery
4. Confirmation that you understand this is a minimal MVP with extensibility in mind