VECTOVRA RC — Milestone 2: Supabase-Backed Catalogue Foundation for Lovable/React Ecommerce Project

Job Title: VECTOVRA RC — Milestone 2: Supabase-Backed Catalogue Foundation for Lovable/React Ecommerce Project Project Overview: VECTOVRA RC is an upcoming international ecommerce platform for remote control models, parts and accessories, including RC aircraft, cars, boats, motors, servos, electronics, tools and spare parts. Milestone 1 has now been cleaned and QA-reviewed. The site is currently a frontend demonstration foundation built with Lovable.dev, React/TypeScript and GitHub. Milestone 2 is not about building checkout/payment/order functionality yet. The goal of Milestone 2 is to create a solid Supabase-backed catalogue foundation, so the public catalogue, category pages, brand pages and product pages can work from one clean source of truth instead of hardcoded demo data scattered across multiple files. Current Status: - Lovable.dev project exists - GitHub repository exists - Milestone 1 frontend cleanup is complete - Supabase is not yet connected - No database migration has been executed yet - No backend/auth/order/payment system is implemented yet - Public pages and admin pages are currently demo/placeholder foundation only - The live domain vectovra.com is not connected yet Milestone 2 Scope: 1. Supabase Setup - Connect the project to Supabase properly. - Set up environment variables safely. - Do not hardcode secrets. - Do not make dashboard-only database changes that are not reflected in GitHub. - All schema/migration work must be committed to GitHub. 2. Database Schema / Catalogue Foundation Create or refine the Supabase/Postgres schema for the catalogue foundation, including: - products - categories - product_categories - brands - suppliers - product_images - product_attributes / product_specifications - product_variants or product_options if needed - product status fields - basic pricing placeholder fields - basic MOQ placeholder fields - timestamps and soft-delete/status fields where appropriate The schema must support future Milestone 3 work, including product import, admin review workflow, pricing rules and MOQ rules. 3. Single Source of Truth Currently, demo product data exists in multiple places. Milestone 2 must create one source of truth for sample catalogue data. The public catalogue pages should no longer rely on separate hardcoded product lists that disagree with each other. The following areas should use the same product source wherever practical: - Shop / All Products - Category pages - Brand pages - Product detail pages - Product cards - Product list items - Cart placeholder items - Checkout placeholder items - Account/wishlist sample references where practical If any area cannot reasonably be moved to the shared source within this milestone, it must be clearly documented. 4. Public Catalogue Pages Update the public catalogue routes so they work from the structured catalogue source: - /shop - category pages - /rc-airplanes - /rc-boats - /rc-cars-trucks - /motors-propulsion - /servos-electronics - /engines-spare-parts - /tools-accessories - /brands - product detail pages Requirements: - Product slugs must work correctly. - Invalid product URLs must continue to return a proper product-not-found page. - Category and brand filtering/navigation must be coherent. - Product cards must display consistent demo/placeholder pricing, stock and product status wording. - No fake stock, reviews, discounts, sale claims, shipping promises or warranty claims. - GBP/£ formatting must remain consistent. - All demo/sample data must remain clearly labelled. 5. Product Status Foundation The system should support product lifecycle statuses such as: - Draft - Needs Review - Approved - Published Imported or draft products must not automatically appear as live public products. For Milestone 2, a simple status-based visibility rule is enough. 6. Admin Placeholder Alignment Admin pages do not need full CRUD in this milestone unless agreed separately. However, admin pages should be aligned with the new catalogue data structure where appropriate. Admin routes should remain clearly labelled as Milestone 1/Milestone 2 placeholders if they are not functional. Do not create unsafe public write access to the database. If admin editing is introduced, it must be protected properly with Supabase Auth/RLS. Otherwise, keep admin actions as placeholder-only. 7. Future-Ready Architecture Please prepare the structure for future milestones: - product import workflow - admin review workflow - pricing rules - MOQ rules - customer accounts - checkout/order system But do not build those future systems unless explicitly included in this milestone. 8. QA Requirements Before requesting approval, please complete a full QA pass. QA must include: - production build - TypeScript check - lint check for edited files - desktop and mobile route review - no horizontal overflow regressions - no console errors - no broken internal links - product/category/brand route testing - invalid product URL testing - no regression from Milestone 1 placeholder wording standards - GitHub clean status - Lovable published/updated after GitHub push 9. Final Delivery Final delivery must include: - GitHub push confirmation - confirmation that there are no unpushed local changes - confirmation that Lovable has been published/updated after the push - list of migrations/schema files created or changed - concise QA report - screenshots or short walkthrough video - summary of what was implemented - summary of what remains placeholder-only - summary of what belongs to Milestone 3 Acceptance Criteria: Milestone 2 will only be accepted if: - Supabase is connected safely - database/schema work is versioned in GitHub - catalogue sample data has a single clear source of truth - public catalogue/category/brand/product pages work from that structure - no misleading live-business claims return - no fake stock/reviews/discounts/security/shipping/warranty claims return - invalid product URLs still show proper not-found behaviour - GBP/£ formatting remains consistent - demo/placeholder wording remains honest and clear - admin pages are not misleadingly functional - no unsafe public database writes exist - build and TypeScript checks pass - GitHub is clean and pushed - Lovable live site is published/updated after push - QA report and handover are provided Budget: Fixed price target: $ 550 I am open to discussing the exact structure as sub-milestones, but I want this milestone kept focused on the catalogue/data foundation only. Checkout, payment, real orders, import automation and full admin CRUD should be scoped separately later.