Wordpress/woocommerce marketplace development

Enterprise WordPress/WooCommerce Marketplace Development (Custom Plugin) – Senior Developer Required Project Overview We are building a custom B2B marketplace for the landscaping industry (gardeners/contractors). This is NOT a standard WooCommerce webshop. It is a lead marketplace where contractors purchase customer leads. Consumers do not create accounts and do not log in. Leads are manually reviewed and published by administrators. Registered contractors can browse available leads, purchase them through WooCommerce, and immediately unlock the customer’s contact information after successful payment. The platform must be built for long-term scalability, security, and maintainability. This is an enterprise-quality project rather than a quick MVP. ⸻ Technology Stack Required: * WordPress (latest version) * WooCommerce (latest version) * PHP 8.3+ * MySQL 8 / MariaDB * Object-Oriented PHP * Custom WordPress Plugin * Git Preferred: * ACF Pro * Composer * WP-CLI * Redis compatible * REST API ready No page builders. No low-code marketplace plugins. No unnecessary third-party plugins. The marketplace logic must be fully custom. ⸻ Business Concept The platform sells customer requests (“Leads”). Example: A homeowner requests a new fence. An administrator reviews the request. The administrator sets: * title * description * location * category * selling price * maximum number of sales The lead becomes visible to contractors. Contractors purchase access. Immediately after payment they receive the full customer information. ⸻ Important Business Rule A lead is NOT exclusive. Each lead may be sold up to a configurable maximum number of times. Default: Maximum sales = 7 Example: Lead #124 Sales limit: 7 Current sales: 5 Available: Yes After purchase: Current sales: 6 Still available. After the 7th purchase: Status automatically changes to: “SOLD OUT” The lead disappears from all contractor listings. No further purchases are possible. The implementation must guarantee that the maximum number of sales can never be exceeded, even under simultaneous purchase attempts. Race conditions must be prevented. ⸻ User Roles Administrator Can: * Create leads * Edit leads * Delete/archive leads * Set prices * Set maximum sales * View all purchases * Manage contractors * View reports * Export data * Issue refunds * Manage categories ⸻ Contractor Can: * Register * Log in * Browse available leads * Purchase leads * View purchased leads * Download invoices * Manage profile * Change password Cannot: * Edit leads * View customer details before purchase * View sold-out leads * Purchase the same lead twice ⸻ Lead Fields Each lead should support at least: * Title * Description * Category * Subcategory * Province * City * Postal code * Coordinates * Budget * Requested service * Price * Sales limit * Current sales count * Status * Customer name * Customer email * Customer phone * Customer address * Internal notes * Created date * Updated date * Audit history ⸻ Public Listing Before purchase contractors should only see: * Title * General description * City * Category * Asking price The following information must NEVER be visible before purchase: * Customer name * Email * Phone number * Address * Exact location ⸻ Purchase Flow 1. Contractor logs in. 2. Contractor opens a lead. 3. Limited information is shown. 4. Contractor clicks Buy. 5. Lead is added to WooCommerce cart. 6. Checkout. 7. Payment. 8. WooCommerce order completed. 9. Access granted immediately. 10. Customer information becomes visible. 11. Invoice generated. 12. Confirmation email sent. ⸻ Marketplace Logic The custom plugin should manage: * Lead availability * Sales counter * Purchase permissions * Access rights * Customer data visibility * Purchase history * Lead status * Audit logs WooCommerce should only handle: * Cart * Checkout * Payments * Orders * Taxes * Invoices * Emails ⸻ Dashboard Contractor dashboard should include: * Available Leads * Purchased Leads * Purchase History * Invoices * Account Settings Filters: * Province * City * Distance (future-ready) * Category * Price * Date * Availability ⸻ Admin Dashboard The administrator should be able to: * Create leads * Edit leads * Duplicate leads * Archive leads * Pause leads * Close leads * Change prices * Adjust sales limits * View all purchases * Search contractors * Export reports * Manage categories * View logs ⸻ WooCommerce Integration The solution must integrate cleanly with WooCommerce. No WooCommerce core modifications. No hacked templates. No direct database changes to WooCommerce tables. Use official hooks and APIs. ⸻ Security Requirements Enterprise-level security is mandatory. Requirements include: * WordPress Coding Standards * PSR-12 * Nonce verification * Capability checks * Prepared SQL statements * Input sanitization * Output escaping * CSRF protection * XSS prevention * SQL injection prevention * Rate limiting where appropriate * Secure password handling * No customer data leakage Customer information must only become accessible after a successful purchase. ⸻ Performance Requirements The platform should support thousands of leads and thousands of contractors. Requirements: * Optimized database queries * Proper indexing * Pagination * Object caching compatibility * Lazy loading where appropriate * No N+1 query issues * Efficient admin tables ⸻ Concurrency This is a critical requirement. If multiple contractors attempt to purchase the final available lead simultaneously, the system must never exceed the configured sales limit. The implementation must safely handle concurrent purchases using transactional logic and proper locking mechanisms where necessary. ⸻ Logging & Audit Trail Every important action should be logged. Examples: * Lead created * Lead edited * Lead purchased * Refund issued * Sales limit changed * Contractor registered * Login failures * Permission changes ⸻ Code Quality Required: * SOLID principles * Object-oriented architecture * Modular codebase * Reusable services * Clear folder structure * Dependency separation * PHPDoc documentation * Meaningful class names * Meaningful commit history No procedural spaghetti code. ⸻ Deliverables The project must include: * Complete custom WordPress plugin * Source code * Database migrations (if applicable) * Installation instructions * Configuration guide * Technical documentation * Inline documentation * README * Git repository ⸻ Future Scalability The architecture should allow future expansion without major refactoring. Possible future features include: * Credit-based purchasing system * Monthly subscriptions * AI lead scoring * Mobile application * REST API * Webhooks * CRM integrations * Stripe Connect * Multi-language support * Multi-country support * SMS and WhatsApp notifications ⸻ What We Are Looking For We are looking for a senior WordPress engineer with proven experience building complex custom plugins and enterprise-level WooCommerce integrations. Please provide: * Portfolio of similar projects * GitHub (if available) * Architecture approach * Estimated timeline * Estimated budget * Relevant experience with custom WooCommerce development This project prioritizes quality, maintainability, scalability, and clean architecture over speed. We are looking for a long-term development partner rather than someone who will simply assemble existing plugins.