Priyank DaveProblem GE Powerzone runs on ServiceM8 (jobs) and Xero (accounting), but critical workflows are still manual: work orders arrive as emails/PDFs and must be hand-entered; technician notes are messy free-text needing cleanup before quoting/invoicing; job status, quote follow-ups, supplier responses, and parts stock all require checking multiple systems with no single view. Solution A centralized operations intelligence layer that integrates with ServiceM8 + Xero via their APIs and adds automation + a unified dashboard on top — without replacing either system. Automation components: Extract structured data from incoming work-order emails/PDFs (customer, location, appliance, fault) → drafts jobs for review before creation Clean up technician notes into structured repair records (appliance, fault, action, parts, follow-up quotes needed) Track job status end-to-end (created → diagnosis → quote → parts → repair → invoice), synced with ServiceM8 Automate supplier price/availability inquiries + auto-follow-up if no response in 7 days Automate customer quote/estimate follow-ups if no response in 3–7 days Track inventory (stock levels, storage locations, min-stock alerts, usage per job) Track payments/invoices via Xero (paid/unpaid/overdue) Dashboard: single view combining job pipeline, quote/estimate status, supply chain (POs, supplier responses, inventory), financials, and admin alerts (missing data, overdue quotes/suppliers, delayed repairs). Analytics (post-digitization): parts usage/failure trends, supplier performance (response time, delivery, pricing), repair trend analysis, technician/job efficiency metrics. Later add-on scope — Parts Intelligence & Reconciliation Engine: prevent duplicate part ordering/quoting across overlapping open jobs via a central parts usage ledger, cross-job matching (SKU/name/appliance/issue), install-event tracking, pre-quote validation with override, job linking, and AI-assisted similarity detection + alerts. Rollout Phase 1 — Digitization & visibility (ingestion, notes cleanup, dashboard, job tracking) Phase 2 — Supply chain & quote automation (inventory, supplier tracking/follow-ups, customer quote follow-ups) Phase 3 — Financial + operational analytics (Xero payments, parts/supplier/repair analytics) Core principle Automation drafts/suggests (jobs, formatted notes, alerts) — a human always reviews and approves before anything writes into ServiceM8 or Xero. Above is my project. Ask me any questions you want before assuming anything about this project before building.
Sign in to leave a comment
Design and implement database schema, migrations, and indexes for user, admin, job, and integration entities.
As a frontend developer, implement the LoginFooter section which includes a footer with copyright information and links to Dashboard, Settings, and Analytics. Note that links to Dashboard, Settings, and Analytics must be conditionally shown based on persona access: Dashboard and Settings are Admin-only, Analytics is Admin-only. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the JobsFiltersBar section which includes interactive filter chips, dropdowns for status, date range, assigned to, and priority, and a search input. Utilize gsap for animations on filter chips and badges. This section is accessible to Admin, Office Staff, and Technician personas. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the JobsPipeline section which displays job cards in columns representing different job statuses. Each column includes job details such as customer, location, technician, and priority. Use gsap for animations when jobs move between columns. This section is accessible to Admin, Office Staff, and Technician personas. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the JobsTable section which displays a sortable and filterable table of jobs. The table includes columns for customer, location, technician, status, and priority, with styles applied based on status and priority. Use gsap for animations on sorting and filtering actions. This section is accessible to Admin, Office Staff, and Technician personas. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the JobsDetailPanel section which provides detailed information about a selected job, including customer details, appliance information, notes, attachments, and history. Use gsap for animations when expanding or collapsing the panel. This section is accessible to Admin, Office Staff, and Technician personas. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the JobsBulkActions section which allows bulk operations on selected jobs, such as assigning technicians, tagging, and deleting. Use gsap for animations when toggling the bulk actions bar and updating the selected count. This section is accessible to Admin, Office Staff, and Technician personas. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the InventorySearchBar section which includes a search input with dynamic suggestions and a clear button. The component uses state hooks to manage dropdown visibility and filtered suggestions. It also handles outside clicks to close the dropdown. This section is accessible by Admin, Office Staff, and Technician personas. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the InventoryFilters section which includes collapsible filter sections for various inventory attributes. The component uses useMemo for calculating item counts and manages filter state with onFilterChange. This section is accessible by Admin, Office Staff, and Technician personas. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the InventoryAlerts section which displays alert badges for low stock, out of stock, and pending supplier items. The component includes buttons to filter by alert type and dismiss the alert bar. This section is accessible by Admin, Office Staff, and Technician personas. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the InventoryTableContainer section which includes a sortable table with columns for item details and actions. The component handles sorting logic and displays a message when no items are found. This section is accessible by Admin, Office Staff, and Technician personas. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the InventoryTableActions section which provides action buttons for editing, moving stock, setting alerts, and viewing history. The component manages a dropdown menu for mobile view. This section is accessible by Admin, Office Staff, and Technician personas. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the InventoryPagination section which includes controls for navigating pages, selecting items per page, and jumping to specific pages. The component manages pagination state and updates the view accordingly. This section is accessible by Admin, Office Staff, and Technician personas. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the NotesJobContext section which displays detailed job information such as customer name, job description, technician, completion date, and location. This section is essential for technicians to quickly review job details. Ensure the status is dynamically styled based on the job's completion status. Page access: Technician only.
As a frontend developer, implement the NotesOriginalInput section which displays the original technician notes in a read-only textarea. Include a copy button that allows technicians to copy the notes to the clipboard, with a visual confirmation when copied. This feature is crucial for technicians to easily transfer notes for further processing. Page access: Technician only.
As a frontend developer, implement the NotesCleanedOutput section which allows technicians to view and edit AI-cleaned repair records. This section includes editable fields for repair issue, root cause, and quote notes, with save and cancel functionality. This feature is essential for technicians to ensure the accuracy of the cleaned notes before they are used for quoting and invoicing. Page access: Technician only.
As a frontend developer, implement the NotesPartsTable section which allows technicians to manage parts used in a job. This section includes functionality to add, remove, and update parts, with calculations for total cost. This feature is crucial for technicians to accurately document parts usage for inventory and billing purposes. Page access: Technician only.
As a frontend developer, implement the NotesLaborAndRecommendations section which allows technicians to input labor hours and recommendations. This section calculates total labor cost based on hours and a static rate, and includes fields for preventive measures and recommendations. This feature is essential for technicians to provide comprehensive job documentation. Page access: Technician only.
As a frontend developer, implement the NotesReviewActions section which provides technicians with options to approve, save as draft, or reject notes. This section includes a rejection reason input that appears conditionally. This feature is crucial for technicians to finalize the review process of repair notes. Page access: Technician only.
Implement secure API authentication and role-based access control for Admin, Office Staff, and Technician roles.
Develop backend services and APIs for job management, integration management, and inventory tracking.
As a frontend developer, implement the LoginForm section which includes a form for user login with fields for email and password, a 'Remember Me' checkbox, and a 'Forgot Password?' button. The form uses state hooks for managing input values and error messages. It also includes a loading state during form submission. This section is accessible by Admin, Office Staff, and Technician. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the LoginHero section which features a 3D globe with interactive region markers using @react-three/fiber and gsap for animations. Users can interact with the globe to select regions, which triggers animations and updates the active region state. This section is accessible by Admin, Office Staff, and Technician. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the LoginNavbar section which includes a navigation bar with a brand logo and a toggleable hamburger menu. The navbar contains a link to the Login page. Ensure the navbar is responsive and the menu can be toggled open and closed. This section is accessible by Admin, Office Staff, and Technician. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the Navbar section for the Dashboard page. This section includes a responsive navigation bar with links to various pages such as Dashboard, Integrations, Settings, Jobs, Analytics, Inventory, Work Orders, Suppliers, Quotes, Search, and Notes. The Navbar features a toggleable hamburger menu for mobile views, a brand logo with a gradient, and a user menu with an avatar. Note that links to restricted pages must be conditionally shown based on persona access. This component may already exist from a previous page and should integrate with the Login page dependencies. Page access: Admin only.
As a Data Engineer, design and implement data models for jobs, inventory, and integrations, including necessary migrations and indexes.
As a Data Engineer, define and implement data retention policies for job, inventory, and integration data to ensure compliance and efficient storage management.
Create API endpoints for managing integrations with ServiceM8, Xero, AWS, and other services.
Implement service for extracting structured data from work-order emails/PDFs.
Develop service for tracking inventory levels, storage locations, and min-stock alerts.
As a frontend developer, implement the DashboardSidebar section for the Dashboard page. This section includes a vertical sidebar with navigation links to sections such as Overview, Alerts, Jobs, Inventory, and Integrations. The sidebar highlights the active section and displays a role badge indicating 'Admin'. Ensure the sidebar is styled according to the design specifications. Page access: Admin only.
As a frontend developer, implement the DashboardHeader section for the Dashboard page. This section displays the current date and time, a greeting message for the Admin, and action buttons for 'Run Plan All', 'Refresh Data', and 'Export'. Ensure the header is responsive and styled according to the design specifications. Page access: Admin only.
As a frontend developer, implement the DashboardAlerts section for the Dashboard page. This section displays a list of alerts with varying severity levels (error, warning, info) and actions such as 'Retry', 'View items', and 'Contact now'. Alerts can be dismissed by the user. Ensure the alerts are styled with appropriate severity colors and are responsive. Page access: Admin only.
As a frontend developer, implement the DashboardKPICards section for the Dashboard page. This section displays KPI cards with metrics such as 'Active Jobs', 'Quote Conversion', 'Avg. Turnaround (days)', and 'Inventory Level %'. Each card includes a trend arrow, percentage change, and a sparkline graph. Ensure the cards are styled and responsive. Page access: Admin only.
As a frontend developer, implement the DashboardJobPipeline section for the Dashboard page. This section displays the job pipeline with stages such as 'Pending Approval', 'Scheduled', 'In Progress', 'Completed', and 'Invoiced'. Each stage shows the count and percentage of jobs. Ensure the pipeline is styled and responsive. Page access: Admin only.
As a frontend developer, implement the DashboardQuotesEstimates section for the Dashboard page. This section displays a list of quotes with details such as customer name, days pending, status, and automation status. It includes actions like 'Send Reminder' for quotes with a 'sent' status. Ensure the section is styled and responsive. Page access: Admin only.
As a frontend developer, implement the DashboardInventorySnapshot section for the Dashboard page. This section displays inventory categories with stock percentages and alerts for low stock. It also lists the top 5 low stock items with their quantities. Ensure the section is styled and responsive. Page access: Admin only.
As a frontend developer, implement the DashboardSupplierStatus section for the Dashboard page. This section displays supplier inquiries with statuses such as 'no response', 'response received', and 'pending follow-up'. It includes follow-up counts and next follow-up times. Ensure the section is styled and responsive. Page access: Admin only.
As a frontend developer, implement the DashboardFinancialsSummary section for the Dashboard page. This section displays financial metrics such as 'MTD Revenue', 'Pending Invoices', and 'Xero Sync' status. It includes a button to view pending invoices. Ensure the section is styled and responsive. Page access: Admin only.
As a frontend developer, implement the WorkOrdersHeader section for the WorkOrders page. This section includes a 3D rotating icon using @react-three/fiber and animations with gsap for the breadcrumb, title, subtitle, and action buttons. The header also manages state for import menu visibility and handles outside clicks to close the menu. This section is accessible by Office Staff ONLY. Page access: Office Staff only.
As a frontend developer, implement the WorkOrdersSearch section for the WorkOrders page. This section includes a search input with dynamic suggestions based on the WORK_ORDER_INDEX. It highlights matches in the suggestions and manages focus and active index state. The search functionality is accessible by Office Staff ONLY. Page access: Office Staff only.
As a frontend developer, implement the WorkOrdersStatusFilter section for the WorkOrders page. This section includes status filter chips with animations using gsap, allowing users to toggle filters and reset them. It manages state for active filters and date range, and provides a label summarizing the active filters. This section is accessible by Office Staff ONLY. Page access: Office Staff only.
As a frontend developer, implement the WorkOrdersList section for the WorkOrders page. This section displays a list of work orders with details such as customer, location, appliance, fault, status, and notes. It uses gsap for animations and manages state for expanded details. This section is accessible by Office Staff ONLY. Page access: Office Staff only.
As a frontend developer, implement the WorkOrdersStatusPanel section for the WorkOrders page. This section includes a 3D donut chart using @react-three/fiber and THREE.js to visualize work order statuses. It manages hover interactions to highlight segments and display status details. This section is accessible by Office Staff ONLY. Page access: Office Staff only.
As a frontend developer, implement the WorkOrdersBulkActions section for the WorkOrders page. This section provides bulk action capabilities such as approve, reject, download as CSV, and export to ServiceM8. It uses gsap for modal animations and manages state for selected work orders and pending actions. This section is accessible by Office Staff ONLY. Page access: Office Staff only.
As a frontend developer, implement the SearchInput section for the Search page. This section includes a search input field with animations using gsap, state management for query input and focus, and a debounce mechanism for search execution. The component should trigger the onQueryChange callback when the query changes. Ensure the input field is styled according to the design and integrates with the page's search functionality. Page access: Office Staff only.
As a frontend developer, implement the SearchFilters section for the Search page. This section includes filter buttons with icons from lucide-react, state management for active filters, and animations for filter selection. The component should update the displayed results based on selected filters and provide a clear all filters option. Ensure the filters are styled and functional according to the design specifications. Page access: Office Staff only.
As a frontend developer, implement the Footer section for the Search page. This section includes contact information, platform links, and a scroll-to-top button. The component should integrate with existing styles and functionality from previous pages. Ensure the footer is styled and functional according to the design specifications. Page access: Office Staff only.
As a frontend developer, implement the IntegrationsHeader section which includes a breadcrumb navigation linking to the Dashboard and a header with an SVG icon and title. This section is accessible by Admin ONLY and must include page-level dependencies from the Dashboard page. Page access: Admin only.
As a frontend developer, implement the SettingsNav section for the Settings page. This component includes a navigation menu with items such as 'Access Control', 'Integration Management', and 'Security Settings'. Each item has an icon and a label, and the active section is highlighted. The component uses a button to handle section changes via the onSectionChange callback. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the AnalyticsHeader section for the Analytics page. This section includes a title and subtitle for the page, and action buttons for exporting reports and refreshing the page. The export button triggers an alert indicating the feature is coming soon, while the refresh button reloads the page. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the JobsPageHeader section which includes a 3D spinning hub using @react-three/fiber and gsap animations for the header and status badges. This section displays summary statistics and status badges with animated counters. Ensure the header is accessible to Admin, Office Staff, and Technician personas. This section depends on the Dashboard page implementation. Page access: shared by all personas (Admin, Office Staff, Technician).
As a Backend Developer, create API endpoints for job management, inventory tracking, and integration management to support frontend functionalities.
As a Backend Developer, implement role-based access control middleware to ensure Admin, Office Staff, and Technician roles have appropriate access to API endpoints.
Develop integration tests for critical workflows including job creation, inventory updates, and integration management.
As a frontend developer, implement the SearchResults section for the Search page. This section includes paginated lists of job, customer, and note results, with animations using gsap for transitions. The component should handle pagination logic and display results based on the current search query and active filters. Ensure the results are styled and functional according to the design specifications. Page access: Office Staff only.
As a frontend developer, implement the SearchEmptyState section for the Search page. This section includes an empty state message with suggestions and search tips, using gsap for animations. The component should toggle the visibility of search tips and provide links to browse other sections. Ensure the empty state is styled and functional according to the design specifications. Page access: Office Staff only.
As a frontend developer, implement the IntegrationsStatus section which displays the connection status of various services like ServiceM8, Xero, AWS, and others. It includes a grid of StatusCard components showing service name, status, last sync time, and action buttons. This section is accessible by Admin ONLY. Page access: Admin only.
As a frontend developer, implement the IntegrationsServiceM8 section which includes IntegrationCard components for ServiceM8 integrations like Job Sync and Notes Extraction. Each card displays the integration name, description, status, last sync time, and action buttons. This section is accessible by Admin ONLY. Page access: Admin only.
As a frontend developer, implement the IntegrationsXero section which includes IntegrationCard components for Xero integrations like Payment Sync and Invoice Tracking. Each card displays the integration name, description, status, last sync time, webhook information, and action buttons. This section is accessible by Admin ONLY. Page access: Admin only.
As a frontend developer, implement the IntegrationsAWS section which includes IntegrationCard components for AWS integrations like S3 Storage and Lambda Functions. Each card displays the integration name, description, status, last sync time, extra information, and action buttons. This section is accessible by Admin ONLY. Page access: Admin only.
As a frontend developer, implement the IntegrationsOther section which includes IntegrationCard components for additional integrations like Email Automation and Webhooks. Each card displays the integration name, description, status, last sync time, details, and action buttons. This section is accessible by Admin ONLY. Page access: Admin only.
As a frontend developer, implement the IntegrationsAdd section which allows Admin users to add new integrations. It includes a button with an SVG icon to add integrations and displays badges for available services like ServiceM8, Xero, AWS, Webhooks, and Email Automation. Page access: Admin only.
As a frontend developer, implement the SettingsPageHeader section for the Settings page. This component displays a breadcrumb navigation leading back to the Dashboard and a title 'Settings'. It also shows a description based on the active section. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the AccessControl section for the Settings page. This component allows Admin users to assign roles and manage permissions. It includes a dropdown for role selection and checkboxes for toggling permissions. The component uses state to manage selected roles and permissions, and includes a save function to confirm changes. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the IntegrationManagementServiceM8 section for the Settings page. This component displays the connection status of ServiceM8 integration, with options to show details, reconnect, or disconnect. It uses state to manage the expanded view of integration details. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the IntegrationManagementXero section for the Settings page. This component displays the connection status of Xero integration, with options to show details, reconnect, or disconnect. It uses state to manage the expanded view of integration details. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the IntegrationManagementAWS section for the Settings page. This component displays the connection status of AWS integration, with options to show details, reconnect, or disconnect. It uses state to manage the expanded view of integration details. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the SecuritySettingsTwoFactor section for the Settings page. This component allows Admin users to enable or disable two-factor authentication. It includes a modal for setup with QR code scanning and backup code generation. The component uses state to manage the setup process and 2FA status. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the SecuritySettingsAPIKeys section for the Settings page. This component allows Admin users to manage API keys, including generating new keys, toggling visibility, copying, and revoking keys. It uses state to manage the list of keys and their visibility. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the SecuritySettingsSessionTimeout section for the Settings page. This component allows Admin users to set session timeout durations using a slider and preset buttons. It uses state to manage the selected timeout and includes a save function to confirm changes. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the DateRangeFilter section for the Analytics page. This section allows Admin users to select date ranges using presets like 'Last 7 Days', 'Last 30 Days', 'Last Quarter', 'Year-to-Date', or a custom range. It uses state hooks to manage date inputs and applies the selected range via the onApply callback. Page access: Admin only.
As a frontend developer, implement the KeyMetrics section for the Analytics page. This section displays key performance indicators such as 'Total Jobs', 'Jobs Completed', and 'Quote Conversion' with trends and sparklines. It uses mock data and renders MetricCard components for each metric. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the JobPipelineChart section for the Analytics page. This section visualizes the job pipeline stages with a funnel chart, showing stages like 'Created', 'Quoted', and 'Completed'. It includes hover effects to display tooltips with job counts and conversion rates. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the JobVolumeTrend section for the Analytics page. This section provides a line chart to display job volume trends over time, with options to toggle between Month-over-Month (MoM) and Year-over-Year (YoY) views. It uses state hooks to manage the display mode and includes interactive tooltips. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the RevenueTrend section for the Analytics page. This section features a bar chart to visualize revenue trends, with toggles for Month-over-Month (MoM) and Year-over-Year (YoY) data. It includes interactive elements such as hoverable bars that display revenue values. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the SupplierPerformance section for the Analytics page. This section displays a sortable table of supplier performance metrics such as response time, quote accuracy, and fulfillment rates. It includes pagination and sorting functionality. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the TechnicianEfficiency section for the Analytics page. This section ranks technicians based on selected metrics such as jobs completed, average rating, and first-time fix rate. It includes a bar chart visualization and allows metric selection via a dropdown. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the TopPartsChart section for the Analytics page. This section uses a pie chart to display the usage of top parts, with interactive slices that show detailed usage percentages on hover. It includes a donut hole for total parts used. This section is accessible by Admin only. Page access: Admin only.
As a frontend developer, implement the InventoryHeader section which includes interactive elements such as view toggles (table/grid), filter toggle, and action buttons for 'Add Stock' and 'Import CSV'. This section also displays a title and description with an optional role badge. Ensure that the view toggle buttons update the viewMode state and that the action buttons trigger the respective onAddStock and onImportCSV functions. This section is accessible by Admin, Office Staff, and Technician personas. Page access: shared by all personas (Admin, Office Staff, Technician).
As a frontend developer, implement the NotesHeader section which includes a breadcrumb navigation and a title group displaying the job number and a subtitle. This section is crucial for technicians to navigate back to job details and understand the context of the repair notes. Ensure the breadcrumb links are conditionally shown based on the technician's access rights. This section depends on the Jobs page header task to ensure consistent navigation elements. Page access: Technician only.
As a frontend developer, implement the QuotesHeader section for the Quotes page. This section includes a 3D particle animation using @react-three/fiber and gsap for animations. It features a breadcrumb navigation with links to 'Dashboard' and 'Quotes', where the current page is highlighted. The section also includes animated content that fades in using gsap. This page is accessible by Office Staff only, and links to restricted pages must be conditionally shown. Page access: Office Staff only.
As a frontend developer, implement the SuppliersHeader section which includes a title 'Suppliers', a button to add a new supplier with an SVG icon, and displays metrics such as Total Suppliers, Response Rate, and Avg Lead Time. This section is accessible by Office Staff only and should conditionally show navigation links to restricted pages. Page access: Office Staff only.
As a Backend Developer, implement business rules for job status tracking, inventory alerts, and automated follow-ups as per SRD specifications.
As a QA Engineer, develop integration tests for end-to-end workflows including job creation, inventory updates, and integration management.
As a Backend Developer, create backend logic for managing integrations with ServiceM8, Xero, AWS, and other services through a dedicated integrations tab.
As a Full Stack Developer, implement navigation guards to ensure pages are accessible only by allowed personas, such as Admin-only access to Analytics and Settings.
As a Backend Developer, implement API authorization to ensure endpoints are accessed only by authenticated users with appropriate roles.
As a Backend Developer, create API endpoints for managing job lifecycle including creation, updates, and status tracking. Ensure integration with ServiceM8 for real-time sync.
As a Backend Developer, develop API endpoints for inventory management including stock levels, storage locations, and min-stock alerts. Ensure integration with the frontend inventory sections.
As a Tech Lead, verify the end-to-end integration between the Dashboard frontend implementation and the backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.
Set up CI/CD pipelines for automated testing and deployment of the GEP platform.
As a frontend developer, implement the QuotesFilters section for the Quotes page. This section includes interactive filters with state management for tabs, search, job reference, status, and response filters. It uses gsap for animations, such as moving a pill indicator between tabs and expanding/collapsing advanced filter panels. This page is accessible by Office Staff only. Page access: Office Staff only.
As a frontend developer, implement the QuotesList section for the Quotes page. This section displays a list of quotes with details such as customer, job reference, amount, status, and history. It uses gsap for animations and manages state for displaying quote details. This page is accessible by Office Staff only. Page access: Office Staff only.
As a frontend developer, implement the QuotesTimeline section for the Quotes page. This section visualizes the timeline of quote events using @react-three/fiber for 3D elements and gsap for animations. It includes interactive elements to display event details and manage state for timeline updates. This page is accessible by Office Staff only. Page access: Office Staff only.
As a frontend developer, implement the SuppliersFilter section which includes a search input, status filter, sort field selector, sort direction toggle, and a clear button. This section uses state hooks to manage filter criteria and is accessible by Office Staff only. Page access: Office Staff only.
As a frontend developer, implement the SuppliersList section which displays a table of suppliers with columns for name, contact, last contact, response status, and next follow-up. It uses conditional styling for overdue follow-ups and selected rows. This section is accessible by Office Staff only. Page access: Office Staff only.
As a frontend developer, implement the AddSupplierModal section which provides a form to add new suppliers. It includes fields for name, contact person, email, phone, address, payment terms, and parts supplied. This modal is accessible by Office Staff only. Page access: Office Staff only.
As a Backend Developer, setup scheduled jobs for automated follow-ups on supplier inquiries and customer quotes.
As a Tech Lead, verify the end-to-end integration between the frontend implementation and the backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.
As a Backend Developer, implement business logic for automated customer quote/estimate follow-ups if no response is received in 3–7 days. Ensure follow-ups are sent to the correct recipients.
As a frontend developer, implement the SuppliersDetail section which shows detailed information about a selected supplier, including contact details, address, and payment terms. It includes buttons for editing, sending inquiries, and calling. This section is accessible by Office Staff only. Page access: Office Staff only.
As a Backend Developer, setup scheduled jobs for automated follow-ups on supplier inquiries every 6 hours until a response is received. Maintain a history of requests and responses.
As a frontend developer, implement the FollowupHistory section which displays a timeline of communication history with suppliers. It includes expandable items to show details and uses state to manage expanded items. This section is accessible by Office Staff only. Page access: Office Staff only.
Automate workflows, track every job end-to-end, and gain real-time insights across your entire field service operation.
Drag to spin the globe · click a region for analytics
Sign in to your GEP account
Automate workflows, track every job end-to-end, and gain real-time insights across your entire field service operation.
Drag to spin the globe · click a region for analytics
Sign in to your GEP account
No comments yet. Be the first!