What we need from you
To keep the seven-week delivery plan on track, please provide the following access, credentials, accounts and approvals before kickoff on 15 Jul 2026.
Note: All items listed below are needed by 15 Jul 2026 so we can begin work on schedule. Any delay may shift the corresponding milestone.
| Category | Required from client | Why it is needed | Needed by |
|---|---|---|---|
| Access & Cloud | Cloud platform account (AWS / Azure / GCP / Hostinger) with admin / project-owner access | Provision Dev, Testing, Pre-Prod and Production environments per BRD § 2 & 7 | Before kickoff · 15 Jul 2026 |
| Access & Cloud | Domain name and DNS (Route53 / Cloudflare) management access | Configure app URLs, SSL endpoints and email SPF/DKIM/DMARC records | Before kickoff · 15 Jul 2026 |
| Access & Cloud | Wildcard SSL / TLS certificate or Cloudflare SSL service access | Secure all public endpoints, mobile app backend calls and admin portal | Before kickoff · 15 Jul 2026 |
| Vehicle & Part Data | TecAlliance API subscription — VIN decode + OE/part-fitment + part catalogue | Primary source of truth for VIN decoding and OE/part matching (BRD § 7.1) | Before kickoff · 15 Jul 2026 |
| Vehicle & Part Data | Vincario (or equivalent) VIN decode API — fallback provider | Secondary/fallback VIN decode when TecAlliance is unavailable (BRD § 7.1) | Before kickoff · 15 Jul 2026 |
| Vehicle & Part Data | OCR service credentials — AWS Textract / Google Vision / Azure Document Intelligence | Trade licence, Emirates ID and Mulkiya scanning + VIN extraction at onboarding | Before kickoff · 15 Jul 2026 |
| Vehicle & Part Data | AI image-recognition API key (OpenAI Vision / Gemini / custom model endpoint) | AI-assisted part identification from uploaded photos with confidence score (BRD § 7.5) | Before kickoff · 15 Jul 2026 |
| WhatsApp Business API access — Meta Cloud API or BSP (Twilio / Gupshup / 360dialog / Infobip) | Primary GCC notification channel — enquiry alerts, quotes, order updates, chat (BRD § 7.4) | Before kickoff · 15 Jul 2026 | |
| Verified WhatsApp Business Sender profile + green-tick brand approval | Display verified PartsManager identity on customer WhatsApp messages | Before kickoff · 15 Jul 2026 | |
| Approved WhatsApp message templates for all notification events | Utility/authentication templates for OTP, enquiry broadcast, quotation, order, chat, delivery | Before kickoff · 15 Jul 2026 | |
| SMS / OTP | GCC SMS gateway account — Unifonic / Etisalat SMPP / du SMS / STC / Ooredoo / regional aggregator | Reliable OTP and SMS delivery across UAE, KSA, Kuwait, Bahrain, Oman and Qatar | Before kickoff · 15 Jul 2026 |
| SMS / OTP | SMPP endpoint credentials (host, port, system-id, password, source TON/NPI) | Direct SMPP binding for high-volume, low-latency GCC OTP and transactional SMS | Before kickoff · 15 Jul 2026 |
| SMS / OTP | Approved Sender IDs / Alphanumeric masks per GCC country (TRA / CITC / TRC registrations) | Compliant, whitelisted sender identity for OTP and transactional SMS in each market | Before kickoff · 15 Jul 2026 |
| Transactional email provider account (SendGrid / AWS SES / Mailgun / Postmark) | Transactional emails — OTP, enquiry alerts, quotations, orders (BRD § 7.4) | Before kickoff · 15 Jul 2026 | |
| Verified sending domain — DKIM, SPF, DMARC, MX records configured | Ensure deliverability, avoid spam-folder routing and pass GCC deliverability checks | Before kickoff · 15 Jul 2026 | |
| Dedicated sending IP or high-reputation shared IP allocation | Consistent deliverability at launch volume for OTP and order-critical email | Before kickoff · 15 Jul 2026 | |
| Push | Firebase project (FCM) + Apple Push Notification service (APNs) certificates / keys | Required push notifications for Workshop and Retailer apps (BRD § 4.8, 7.4) | Before kickoff · 15 Jul 2026 |
| Payments | UAE payment gateway merchant account — Network International / Telr / Checkout.com / PayTabs / Amazon Payment Services | Online payment collection alongside COD default at launch (BRD § 5.6 & 8.3) | Before kickoff · 15 Jul 2026 |
| Payments | Gateway sandbox + production API credentials, webhook URLs and IP allow-list | Build, UAT and go-live for payments, refunds and reconciliation workflows | Before kickoff · 15 Jul 2026 |
| Payments | Merchant bank account + KYC docs (trade licence, VAT/TRN, MOA, ownership) | Payment gateway onboarding and settlement to the client bank account | Before kickoff · 15 Jul 2026 |
| Location & Maps | Google Maps Platform (or Mapbox) API key — Maps SDK, Places, Geocoding, Directions | GPS pin, address search, distance/radius-based retailer matching (BRD § 3.1, 5.4, 7.2) | Before kickoff · 15 Jul 2026 |
| App Publishing | Google Play Console + Apple Developer Program (Organization) accounts with DUNS number | Build, sign and publish the Workshop and Retailer mobile apps | Before kickoff · 15 Jul 2026 |
| App Publishing | iOS distribution certificate, provisioning profiles and Android keystore/upload key | Signing and store submission of iOS and Android builds | Before kickoff · 15 Jul 2026 |
| Branding | Final logo, app icon, colour palette and typography package | Apply confirmed PartsManager brand across apps, admin panel and notification templates | Before kickoff · 15 Jul 2026 |
| Branding | Notification copy — WhatsApp / SMS / Email / Push templates in English (Arabic optional) | Approved wording for all event templates per BRD § 6.6 template management | Before kickoff · 15 Jul 2026 |
| Master Data | Brand master list per classification tier (Genuine / Premium / Economical / Budget) | Populates retailer brand picklists per part classification (BRD § 7.2) | Before kickoff · 15 Jul 2026 |
| Master Data | Default matching radius, quote expiry hours and notification retry rules | Admin configuration values for the matching engine and notification retries (BRD § 6.4) | Before kickoff · 15 Jul 2026 |
| Users & Approvals | Initial Platform Admin, Operations and Finance user list (names, emails, roles) | Create Phase 1 RBAC roles per BRD § 2.2 | Before kickoff · 15 Jul 2026 |
| Users & Approvals | Named UAT sign-off stakeholders and available test windows | Validate acceptance criteria and complete Go-Live sign-off | Before kickoff · 15 Jul 2026 |
| Compliance | Business registration, VAT / TRN and KYC documents (client entity) | Payment gateway, WhatsApp Business and SMS sender-ID onboarding | Before kickoff · 15 Jul 2026 |
| Compliance | Terms of Service, Privacy Policy and UAE PDPL data-residency confirmation | User onboarding, cross-border data flow policy and regional compliance | Before kickoff · 15 Jul 2026 |
| Security | SAST tool access / approval for static application security testing | Run static code analysis and dependency vulnerability checks in the build pipeline | Before kickoff · 15 Jul 2026 |
Cloud platform account (AWS / Azure / GCP / Hostinger) with admin / project-owner access
Provision Dev, Testing, Pre-Prod and Production environments per BRD § 2 & 7
Domain name and DNS (Route53 / Cloudflare) management access
Configure app URLs, SSL endpoints and email SPF/DKIM/DMARC records
Wildcard SSL / TLS certificate or Cloudflare SSL service access
Secure all public endpoints, mobile app backend calls and admin portal
TecAlliance API subscription — VIN decode + OE/part-fitment + part catalogue
Primary source of truth for VIN decoding and OE/part matching (BRD § 7.1)
Vincario (or equivalent) VIN decode API — fallback provider
Secondary/fallback VIN decode when TecAlliance is unavailable (BRD § 7.1)
OCR service credentials — AWS Textract / Google Vision / Azure Document Intelligence
Trade licence, Emirates ID and Mulkiya scanning + VIN extraction at onboarding
AI image-recognition API key (OpenAI Vision / Gemini / custom model endpoint)
AI-assisted part identification from uploaded photos with confidence score (BRD § 7.5)
WhatsApp Business API access — Meta Cloud API or BSP (Twilio / Gupshup / 360dialog / Infobip)
Primary GCC notification channel — enquiry alerts, quotes, order updates, chat (BRD § 7.4)
Verified WhatsApp Business Sender profile + green-tick brand approval
Display verified PartsManager identity on customer WhatsApp messages
Approved WhatsApp message templates for all notification events
Utility/authentication templates for OTP, enquiry broadcast, quotation, order, chat, delivery
GCC SMS gateway account — Unifonic / Etisalat SMPP / du SMS / STC / Ooredoo / regional aggregator
Reliable OTP and SMS delivery across UAE, KSA, Kuwait, Bahrain, Oman and Qatar
SMPP endpoint credentials (host, port, system-id, password, source TON/NPI)
Direct SMPP binding for high-volume, low-latency GCC OTP and transactional SMS
Approved Sender IDs / Alphanumeric masks per GCC country (TRA / CITC / TRC registrations)
Compliant, whitelisted sender identity for OTP and transactional SMS in each market
Transactional email provider account (SendGrid / AWS SES / Mailgun / Postmark)
Transactional emails — OTP, enquiry alerts, quotations, orders (BRD § 7.4)
Verified sending domain — DKIM, SPF, DMARC, MX records configured
Ensure deliverability, avoid spam-folder routing and pass GCC deliverability checks
Dedicated sending IP or high-reputation shared IP allocation
Consistent deliverability at launch volume for OTP and order-critical email
Firebase project (FCM) + Apple Push Notification service (APNs) certificates / keys
Required push notifications for Workshop and Retailer apps (BRD § 4.8, 7.4)
UAE payment gateway merchant account — Network International / Telr / Checkout.com / PayTabs / Amazon Payment Services
Online payment collection alongside COD default at launch (BRD § 5.6 & 8.3)
Gateway sandbox + production API credentials, webhook URLs and IP allow-list
Build, UAT and go-live for payments, refunds and reconciliation workflows
Merchant bank account + KYC docs (trade licence, VAT/TRN, MOA, ownership)
Payment gateway onboarding and settlement to the client bank account
Google Maps Platform (or Mapbox) API key — Maps SDK, Places, Geocoding, Directions
GPS pin, address search, distance/radius-based retailer matching (BRD § 3.1, 5.4, 7.2)
Google Play Console + Apple Developer Program (Organization) accounts with DUNS number
Build, sign and publish the Workshop and Retailer mobile apps
iOS distribution certificate, provisioning profiles and Android keystore/upload key
Signing and store submission of iOS and Android builds
Final logo, app icon, colour palette and typography package
Apply confirmed PartsManager brand across apps, admin panel and notification templates
Notification copy — WhatsApp / SMS / Email / Push templates in English (Arabic optional)
Approved wording for all event templates per BRD § 6.6 template management
Brand master list per classification tier (Genuine / Premium / Economical / Budget)
Populates retailer brand picklists per part classification (BRD § 7.2)
Default matching radius, quote expiry hours and notification retry rules
Admin configuration values for the matching engine and notification retries (BRD § 6.4)
Initial Platform Admin, Operations and Finance user list (names, emails, roles)
Create Phase 1 RBAC roles per BRD § 2.2
Named UAT sign-off stakeholders and available test windows
Validate acceptance criteria and complete Go-Live sign-off
Business registration, VAT / TRN and KYC documents (client entity)
Payment gateway, WhatsApp Business and SMS sender-ID onboarding
Terms of Service, Privacy Policy and UAE PDPL data-residency confirmation
User onboarding, cross-border data flow policy and regional compliance
SAST tool access / approval for static application security testing
Run static code analysis and dependency vulnerability checks in the build pipeline
See the platform in action
The existing proof-of-concept is still available for review while we finalise the requirements above.