Qiutrex Food Planner
Multi-Vendor Food Planning & Ordering SaaS
Qiutrex Food Planner is a multi-vendor food planning and ordering system engineered as a custom WordPress/PHP application.
The platform is designed to help food vendors manage structured meal offerings while allowing customers to plan meals, select portions and schedules, review availability, and proceed through a vendor-specific ordering workflow.
Rather than functioning as a conventional WordPress website, the Food Planner extends WordPress into a dedicated application environment with custom business logic, database structures, scheduling workflows, vendor management, payment infrastructure, and customer-facing interfaces.
Product Vision
The objective is to simplify recurring and planned food ordering by connecting:
Customer → Meal Plan → Schedule → Vendor → Availability → Order → Payment
The system is designed around the operational realities of food businesses rather than treating food ordering as a simple product catalogue.
Core Capabilities
Vendor Management
The system supports food vendors through dedicated workflows for managing their participation in the Food Planner ecosystem.
Vendor functionality is designed to remain separated from the customer's ordering experience.
Meal Planning
Customers can work with structured meal options and planning workflows rather than simply browsing an unstructured product catalogue.
Meal Scheduling
The application contains custom scheduling logic for planned meals.
The scheduler is designed around dates, meal periods, portions, availability and vendor-specific operational rules.
Portion & Availability Logic
Food availability is treated as business logic rather than a static product field.
The system can account for available portions and scheduled meal requirements before an order progresses.
Ordering Workflow
The Food Planner connects meal selection and scheduling with the appropriate vendor ordering workflow.
The architecture is designed to support the progression from planning to fulfillment without unnecessarily coupling unrelated marketplace functionality.
Payment Infrastructure
The application is designed to integrate payment processing and vendor payment workflows.
Payment architecture includes business rules around transactions, vendor revenue and platform-level financial logic.
Vendor Payment Models
The architecture supports flexible vendor commercial models.
A vendor may operate under different payment/pricing arrangements according to eligibility and administrative rules rather than being permanently locked into a single model.
This allows the platform to evolve from fixed subscription arrangements toward transaction-based models where appropriate.
White-Label Customer Experience
A key architectural requirement is separation between the platform infrastructure and the vendor-facing customer experience.
Once a vendor subscribes to the white-label ordering system, the customer-facing workflow is designed around the vendor's own business identity rather than exposing the underlying platform brand throughout the ordering experience.
Architecture
At a high level, the Food Planner follows this workflow:
CUSTOMER
│
▼
Meal Planning
│
▼
Meal Selection
│
▼
Scheduling
│
▼
Portion / Availability
│
▼
Vendor Routing
│
▼
Order
│
▼
Payment
│
▼
Vendor Fulfillment
Application Architecture
The system is implemented through custom WordPress/PHP application components.
The architecture emphasizes separation of concerns between:
- Customer workflows
- Vendor workflows
- Meal planning
- Scheduling
- Availability
- Ordering
- Payments
- Notifications
- Platform administration
This modular approach makes it possible to evolve individual components without unnecessarily coupling the entire application.
Technology Stack
Backend
- PHP
- WordPress
- Custom WordPress Plugin Development
- WordPress APIs
- MySQL
Frontend
- JavaScript
- AJAX
- HTML
- CSS
Infrastructure & Integrations
- Paystack
- Firebase
- REST APIs
- Server-side application logic
Development
- Git
- GitHub
- AI-assisted engineering workflows
- Application debugging
- Database-driven development
- API integration
Engineering Challenges
The Food Planner involves several problems that go beyond conventional WordPress development.
Scheduling
Meal scheduling requires application logic capable of handling planned dates, meal periods and vendor-specific operational constraints.
Availability
The system must distinguish between what a vendor generally offers and what can actually be fulfilled for a particular scheduled requirement.
Portions
Portion availability introduces inventory-like business rules into the planning workflow.
Vendor Isolation
The platform must maintain clear boundaries between platform infrastructure and individual vendor operations.
Payment Flexibility
Vendor payment arrangements need to remain configurable so the commercial model can evolve without requiring a complete rewrite of the application.
Application Modularity
The Food Planner is part of the wider Qiutrex ecosystem, but its scheduler and food-planning functionality must remain architecturally isolated from unrelated platform modules.
Design Principles
The development of the Food Planner follows several principles:
- Business Logic First
Features are designed around real operational requirements rather than simply adding interface elements.
- Modular Architecture
Major systems should be independently maintainable where practical.
- Data Integrity
Scheduling, portions, availability and transactions must be represented consistently within the application's data model.
- Extensibility
Commercial rules should be configurable rather than hard-coded wherever future changes are reasonably foreseeable.
- Vendor Independence
Vendor operations should remain isolated enough to support independent businesses and white-label experiences.
- Security
Credentials, payment secrets and sensitive production data are never committed to the public repository.
Project Structure
The production implementation contains application-specific components for areas including:
Meal Planning Meal Scheduling Availability Portions Vendor Management Ordering Payments Notifications Customer Workflows Administration
The public repository focuses on architecture, documentation and selected technical demonstrations.
Project Status
Active Development
Qiutrex Food Planner is an actively developed product within the wider Qiutrex platform ecosystem.
This repository is intended to document the engineering architecture, technical approach and selected implementation concepts.
Proprietary production code, credentials, private configuration and sensitive business information are intentionally excluded.
About the Developer
Omasha Developer
WordPress Application Architect & PHP Engineer
Specializing in:
- Custom WordPress applications
- PHP development
- SaaS architecture
- Marketplace systems
- Payment integrations
- Database-driven applications
- Business automation
- API integrations
- Location-aware systems
- Real-time application infrastructure
Professional Opportunities
Available for:
Remote Engineering Roles · Contract Development · Technical Consulting · SaaS Product Development
Interested in working with companies building complex WordPress/PHP applications, SaaS platforms, marketplaces, business automation systems and API-driven products.
Qiutrex
Building application infrastructure for real-world businesses.