E Commerce Pre-Requisites Document

This document lists the foundational requirements and resources you need to provide or set up before we begin or finalize your eCommerce project. Having these items in place ensures a smoother development process and faster go-to-market timeline.

Payment Gateway

  • Preferred: Razorpay (India-focused)
  • Purpose: Enables secure online transactions (accepting credit/debit cards, net banking, UPI, etc.).
  • Action Steps:
    1. Create a Razorpay merchant account.
    2. Complete the KYC verification process (submitting business registration documents, bank details, etc.).
    3. Share the API Key and Secret with the development team securely.

Domain (Admin Access)

  • Requirement: Access to your domain registrar account (e.g., GoDaddy, Namecheap, Google Domains, etc.).
  • Purpose:Allow configuration of DNS records (A, CNAME, TXT, MX) to point to the hosting server.
  • Action Steps:
    1. Provide domain login credentials or give the development team the necessary privileges.
    2. Confirm domain ownership and set up SSL (HTTPS) once the environment is ready.

Server

  • Requirement: AWS (Amazon Web Services)
  • Purpose: Host your eCommerce application, databases, and related services.
  • Action Steps:
    1. Create an AWS account (if not already existing).
    2. Decide on the instance size (e.g., t2.micro, t2.medium) based on anticipated traffic.
    3. Provide the development team with access (IAM user or security credentials) to deploy and configure resources (EC2, S3, RDS, etc. as needed).

DUNS (Registration)

  • Requirement: Access to your domain registrar account (e.g., GoDaddy, Namecheap, Google Domains, etc.).
  • Purpose:Allow configuration of DNS records (A, CNAME, TXT, MX) to point to the hosting server.
  • Action Steps:
    1. Provide domain login credentials or give the development team the necessary privileges.
    2. Confirm domain ownership and set up SSL (HTTPS) once the environment is ready.

Twilio (Approved Account)

  • Purpose: Enables SMS notifications, two-factor authentication (2FA), and transactional messaging.
  • Action Steps:
    1. Create a Twilio account and add a valid billing method.
    2. Configure sender IDs or phone numbers as per local regulations.
    3. Share Account SID and Auth Token securely with the development team.

Firebase (Google-Verified Account)

  • Purpose: Provides push notifications, real-time database, analytics, and other mobile backend services (especially for Android apps).
  • Action Steps:
    1. Create or log in to your Google Firebase console.
    2. Provide access to the development team or generate service account credentials as required.
    3. Configure your project name, push notification settings, and environment (production vs. testing).

Google Play Store Developer Account (If Android App Required)

  • Purpose: Publish Android apps to the Google Play Store.
  • Action Steps:
    1. Create a Google Play Console account.
    2. Pay the one-time registration fee.
    3. Invite the development team as a user with the appropriate role (e.g., Release Manager).

Official Email Access

  • Requirement: A business email domain (e.g., [email protected]) for professional communication and transactional emails.
  • Purpose:
    1. Sending order confirmations, notifications, and support messages.
    2. Builds trust and brand identity with customers.In some cases, required for credit, regulatory compliance, or certain marketplace integrations (e.g., Apple Developer enrollment).
  • Action Steps:
    1. Set up email hosting (e.g., G Suite/Google Workspace, Microsoft 365, or another provider).
    2. Provide SMTP or API credentials to the development team (if transactional emails are to be sent from this account).

Company or Other Details as Required

  • Requirement: Any additional legal or corporate details needed for invoicing, compliance, or integration with government portals (e.g., GST, company registration proof, etc.).
  • Purpose: Ensures smooth operational setup and alignment with local regulations.
  • Action Steps:
    1. Provide essential information (Company Name, Registered Address, Tax IDs, etc.).
    2. If operating internationally, share relevant regulatory or compliance documentation.

Conclusion

Having these prerequisites in place is critical for the efficient setup and deployment of your eCommerce solution. Please ensure all accounts are verified, and credentials are shared securely via encrypted channels or official methods.

If you have any questions or need assistance with any of these steps, feel free to contact our support or project manager.