Software Requirements

Specification

Author: Igor Kovalevych

1. Introduction

1.1 Purpose

This document provides a comprehensive Software Requirements Specification (SRS) for the
OA Hunter - eBay to Amazon Arbitrage SaaS platform. It serves as a reference for
stakeholders, detailing functional and non-functional requirements, system architecture, API
specifications, authentication protocols, error handling strategies, and a breakdown of project
milestones.

1.2 Scope

OA Hunter is a Software as a Service (SaaS) platform designed to automate the eBay-to-

Amazon arbitrage process. It facilitates real-time product scraping, comparison, and filtering to
uncover profitable opportunities. The platform aims to outperform competitors such as
Flipmine and Replen Catcher by delivering accurate data, superior filtering capabilities, and a
streamlined user experience.

1.3 Intended Audience

 Business Stakeholders: Interested in project outcomes and ROI.

 Product Managers: Responsible for project planning and execution.
 Senior Full Stack Engineer: Focused on system architecture and implementation.
 Senior Data Engineer: Responsible for data processing and analytics.
 QA Testers: Ensuring quality and performance of the application.
 UI/UX Designers: Tasked with designing user interfaces and experiences.

1.4 System Overview

The OA Hunter platform consists of the following components:

 Web Scraping Engine: Captures real-time product data from eBay and Amazon.
 Data Processing Module: Employs AI to filter and analyze data for actionable insights.
 User Dashboard: An intuitive web-based interface for user interaction and data
visualization.
 Subscription & Payment System: Integrates with payment gateways such as Stripe
and PayPal.
  Notification System: Provides automated alerts for detected profitable deals.
 Backend Infrastructure: A Node.js-based API that ensures data security and efficient
processing.
 Data Pipeline & Storage: Efficiently stores extracted data for further analysis.

2. Overall Description

2.1 Product Perspective

OA Hunter is a cloud-hosted SaaS solution designed for scalability and high availability,
primarily hosted on platforms like AWS or DigitalOcean.

2.2 Product Functions

The platform will support the following key functions:

 Data Scraping: Capture and store comprehensive eBay product data.

 Amazon Pricing Retrieval: Access Amazon’s pricing and fee structures via the
Amazon SP-API.
 Historical Price Tracking: Integrate with tools like Keepa for tracking historical price
trends.
 Advanced AI Filtering: Utilize machine learning algorithms to filter products based
on ROI, profitability, and brand restrictions.
 Payment Management: Handle user subscriptions and payments seamlessly.
 Real-Time Alerts: Notify users of profitable arbitrage opportunities.
 User Authentication: Implement secure authentication and role-based access control.
 Data Analytics: Process and visualize data for trend analysis.

2.3 User Characteristics

 Resellers & Arbitrage Experts: Individuals seeking profitable arbitrage opportunities.

 Beginner Online Sellers: Newcomers needing guidance for starting their Amazon
reselling journey.
 Data Analysts: Users interested in detailed trend analysis and data-driven insights.
2.4 Constraints

 Compliance with eBay and Amazon API usage policies.

 Scraping must be optimized to prevent rate limits and bans.
 Adherence to GDPR standards for user data protection.
 Secure handling of financial transactions and user authentication.

2.5 Assumptions and Dependencies

 Continuous internet connectivity is required for real-time updates.

 Access to eBay and Amazon APIs must remain stable and reliable.
 Dependence on third-party services for payment processing and notifications.

2.6 Competitor Analysis & Market Differentiation

2.6.1 Competitor Overview

 Flipmine: Offers basic filtering but lacks advanced AI-driven insights.

 Replen Catcher: Focuses on replenishable products with a high false-positive rate.
 Tactical Arbitrage: Provides extensive features but has a steep learning curve and
high pricing.

2.6.2 OA Hunter Differentiation

 AI-Driven Insights: Advanced filtering that minimizes false positives using historical
data and seller reputation.
 Enhanced Scraping Technology: Utilizes robust proxy rotation and CAPTCHA-
solving mechanisms.
 Custom Alerts: Tailored notifications for profitable deals based on user-defined
criteria.
 User-Centric UI: A modern, easy-to-navigate dashboard compared to competitors.
 Flexible Pricing Models: Competitive pricing with multiple tiers to accommodate
various user needs.
 Amazon Restrictions Checker: Validates product eligibility for Amazon selling prior
to sourcing.
 Efficient Data Processing: Incorporates real-time data processing and analytics
capabilities.
3. Specific Requirements

3.1 Functional Requirements

3.1.1 Web Scraping Module

 Ability to scrape eBay product listings without triggering blocks.

 Automatic retrieval of Amazon pricing and fees using the Amazon SP-API.
 Historical data storage for analytics and trend analysis.
 Implementation of proxy rotation and CAPTCHA-solving mechanisms.

3.1.2 Data Processing & Filtering

 AI-driven filters for assessing ROI, profitability, and brand restrictions.

 Integration with the Keepa API for historical price tracking.
 Automated submission for eBay Best Offers.
 ETL (Extract, Transform, Load) processes for structured data analytics.

3.1.3 User Dashboard

 User authentication via JSON Web Tokens (JWT).

 Dark mode toggle for user interface preferences.
 Comprehensive billing and subscription management interface.
 Data visualization tools for trend analysis and insights.

3.1.4 Subscription & Payment System

 Integration with Stripe and PayPal for payment processing.

 Development of an affiliate tracking system.
 Implementation of a 7-day free trial feature.
 Multi-tier pricing structure catering to different user needs.

3.1.5 Notification System

 Real-time alerts for new arbitrage opportunities via web and email.
 Customizable alert settings for user preferences.

3.1.6 Backend Development

  Framework: Node.js with Express.js.
 Database: PostgreSQL or MongoDB for data storage.
 Caching: Implementation of Redis for performance optimization.
 Message Queue: Use of RabbitMQ or AWS SQS for handling asynchronous tasks.
 Logging & Monitoring: Utilization of the ELK stack, Prometheus, or Datadog for
system monitoring.
 Testing: Jest and Supertest for API testing to ensure reliability.
 Security Measures: Implementation of OAuth2, JWT, rate limiting, and input
validation.

3.1.7 Data Engineering & Storage

 Data Warehousing: Options include AWS Redshift, BigQuery, or Snowflake for data
storage.
 ETL Pipelines: Use of Apache Airflow or AWS Glue for data processing.
 Data Processing Libraries: Implementation of Pandas, PySpark, or Dask for analytics.
 Analytics Dashboard: Integration with Looker Studio or Tableau for visual analytics.

4. Non-Functional Requirements

4.1 Performance Requirements

 The system should support at least 500 concurrent users without degradation in
performance.
 Data retrieval and processing should occur within 2 seconds for optimal user
experience.

4.2 Security Requirements

 All data transactions must be encrypted using industry-standard protocols (e.g., HTTPS,
TLS).
 User data must be protected in compliance with GDPR regulations.
 Authentication mechanisms must prevent unauthorized access.

4.3 Usability Requirements

  The user interface should be intuitive, requiring minimal training for new users.
 Provide comprehensive documentation and help resources for users.

4.4 Availability Requirements

 The platform should achieve 99.9% uptime.

 Regular backups should be scheduled to prevent data loss.

5. Communication

5.1 Communication Channels

 Slack: For real-time messaging and team collaboration.

 Email: For formal communications and documentation sharing.
 Project Management Tools (e.g., Jira, Trello): For task assignments, progress
tracking, and deadline management.

5.2 Meeting Cadence

 Every 2 Days Stand-ups: Short, focused meetings to discuss progress and blockers.
 Weekly Progress Meetings: Review project milestones, timelines, and deliverables.
 Monthly Stakeholder Updates: Present project status, challenges, and next steps to
stakeholders.

5.3 Documentation

 Maintain thorough documentation in a shared repository (e.g., Confluence, Google

Drive) accessible to all team members.
 Update documentation regularly to reflect changes in project scope, requirements, and
technical specifications.
6. Version Control

6.1 Version Control System

 Git: Utilize Git as the version control system for managing code changes.
 Repository Hosting: Use platforms such as GitHub or GitLab for hosting the codebase.

6.2 Branching Strategy

 Main Branch: Stable version of the application, representing production-ready code.

 Development Branch: Ongoing development work; features are merged here before
being promoted to the main branch.
 Feature Branches: Individual branches for developing new features, allowing for
isolated development and testing.

6.3 Commit Practices

 Commit Messages: Use clear, descriptive messages that follow a conventional format
(e.g., feat: add user authentication).
 Frequency: Commit code changes frequently to avoid large, complex merges.

6.4 Code Review Process

 Implement a mandatory code review process via pull requests to ensure code quality
and adherence to coding standards.
 Encourage team collaboration by assigning reviewers from different roles (e.g.,
frontend, backend, QA) to diversify feedback.
7. Milestone Breakdown & Timeline

Senior Full Stack Engineer

Week 1-2: UI/UX Design Finalization

o Activities:

 Collaborate with designers to finalize wireframes and visual designs.

 Conduct user feedback sessions to validate design decisions.

o Deliverables:

 Approved UI/UX mockups.

 User feedback report summarizing findings and design adjustments.

Week 3-4: Backend API Development

o Activities:

 Set up the Node.js environment and Express.js framework.

 Develop APIs for user management (registration, login, role-based
access).
 Implement data retrieval endpoints for eBay and Amazon products.
 Integrate payment processing systems.

o Deliverables:

 Functional user management APIs with documentation.

 Initial integration tests confirming data retrieval functionality.

Week 5-6: Real-Time Notification System Implementation

o Activities:

 Develop the notification service using WebSockets or server-sent events.

 Implement real-time alerts for arbitrage deals based on user-defined
criteria.
 Optimize backend performance through caching mechanisms.
 o Deliverables:

 A fully functioning notification system.

 Performance benchmarks demonstrating improvements.

Week 7-8: Deployment and Security Finalization

o Activities:

 Deploy the application on cloud infrastructure (AWS/DigitalOcean).

 Implement security measures (OAuth2, JWT, rate limiting).
 Conduct comprehensive testing (unit, integration, and user acceptance).

o Deliverables:

 Deployed application with a security audit report.

 User acceptance testing results with feedback for adjustments.
Senior Data Engineer

Week 1-2: Web Scraper Development

o Activities:

 Design and implement web scrapers for eBay and Amazon.

 Establish proxy rotation and CAPTCHA-solving mechanisms.
 Conduct tests for accuracy and efficiency in data extraction.

o Deliverables:

 Functional web scrapers with comprehensive documentation.

 Test results demonstrating data extraction accuracy.

Week 3-4: ETL Pipeline Implementation

o Activities:

 Develop ETL pipelines for real-time data ingestion.

 Store and structure data in PostgreSQL/MongoDB.
 Implement data quality checks throughout the ETL process.

o Deliverables:

 Completed ETL pipelines with documentation.

 Data quality assessment report.

Week 5-6: AI-Based Filtering and Optimization

o Activities:

 Integrate AI algorithms for advanced product filtering.

 Conduct performance optimizations for data processing.
 Collaborate closely with the Full Stack Engineer for integration testing.

o Deliverables:

 An operational AI filtering module.

  Performance optimization report with metrics.

Week 7-8: Data Pipeline Optimization and Analytics Deployment

o Activities:

 Analyze and optimize data pipeline efficiency based on metrics.

 Deploy the analytics dashboard for trend analysis.
 Conduct a comprehensive review of data accuracy and processing
speeds.

o Deliverables:

 Optimized data pipelines with performance metrics documented.

 Deployed analytics dashboard with user access.