Loading
Verification, document, and listing screens can take a moment while protected data is checked.
Service level requirements
This page tracks the requirements extracted from the 2026-05-15 service level agreement for the AutomotiveHub marketplace, finance lead, verification, support, and compliance platform.
Total
21
Implemented
16
Provider integrations
2
Ops prerequisites
3
SLA-FE-01 | Sections 4, 5.1, Appendix A
Next.js public marketplace pages use responsive layouts and shared public shell navigation.
SLA-FE-02 | Section 5.1
Search supports make, model, province, city, price, year, mileage, body type, fuel, transmission, trust badge, and sorting.
SLA-FE-03 | Appendix A
Buyers can save a listing, save the current search filters, and see those records on the buyer dashboard.
SLA-FE-04 | Appendix A
The comparison page shows selected vehicles side by side and falls back to current live listings when fewer vehicles are selected.
SLA-FE-05 | Section 5.1
Authentication, roles, sessions, phone verification, and audit events are implemented.
SLA-FIN-01 | Sections 4, 5.1, 5.3, Appendix A
Finance remains lead-routing only and includes visible disclaimers that AutomotiveHub is not a lender.
SLA-FIN-02 | Section 5.3, Appendix A
Buyer finance leads, consent, routed provider submissions, status updates, and dashboard tracking exist.
SLA-FIN-03 | Sections 5.3, 5.5
Finance applications use a dedicated provider integration layer designed for approved finance providers.
SLA-SELL-01 | Sections 4, 5.2, Appendix A
Seller dashboards show live, sold, and draft assets with manage, photo, message, and mark-sold controls.
SLA-SELL-02 | Section 5.2
Sellers can paste a CSV batch and create multiple draft listings for later verification.
SLA-SELL-03 | Section 5.2, Appendix A
Seller dashboards summarize open messages, inventory states, sold assets, and reply actions.
SLA-ADM-01 | Section 5.4, Appendix A
Admin queues cover users, KYC, listings, documents, finance leads, conversations, audit, data access, notifications, and SLA evidence.
SLA-ADM-02 | Section 5.4, Appendix A
Non-essential advertising is intentionally blocked until privacy/consent and production marketing policy are approved.
SLA-ADM-03 | Sections 8.3, 9
The admin SLA page and docs list the required operational reports and response targets.
SLA-INT-01 | Sections 5.5, 17
Dedicated provider interfaces support KYC, communications, finance, payments, and third-party integrations.
SLA-INT-02 | Sections 4, 5.5
Enquiries, conversations, offers, finance leads, and notifications provide the lead management workspace.
SLA-SEC-01 | Sections 5.6, 17, Appendix B
Production TLS is a hosting requirement; the app enforces RBAC, hashed passwords/session tokens, audit logs, data access logs, and validation.
SLA-SEC-02 | Sections 4, 17, Appendix B
Consent, privacy boundaries, document access logging, verification gates, and finance disclaimers are implemented across the platform.
SLA-SEC-03 | Appendix B, Appendix C
The app exposes health checks and runbooks; production backups, restore drills, and managed monitoring must be provisioned by the host.
SLA-DEL-01 | Sections 7, 8, 14
The repo includes unit/integration tests, Playwright smoke tests, type checks, build checks, and acceptance documentation.
SLA-DEL-02 | Sections 10, 13, 15, 16, 20, 21, 22, 23, 24
These are contractual/operational controls rather than application features; they are tracked in the checklist.