MySQL E-Commerce Database Build
Budget: ₹37,500 – ₹75,000 INR
I need a clean, well-structured MySQL database that will act as the backbone for an e-commerce application. Its sole purpose is to handle transactional data—orders, payments, inventory changes, customer records—quickly and reliably.
Here is what I expect:
• A relational schema that reflects common e-commerce entities (customers, products, orders, order items, payments, shipping, etc.) with proper normalization.
• All table-creation scripts, keys, indexes, and constraints supplied as executable .sql files.
• Seed data scripts for a small demo dataset so I can test the integrity of foreign-key relationships and run sample queries.
• Performance-oriented touches where appropriate: sensible indexing on high-traffic columns, consideration for partitioning or read replicas if future scaling demands it.
• Brief documentation (markdown is fine) that explains the schema, assumptions you made, and how to import everything into a fresh MySQL instance.
Acceptance criteria
1. I can import the SQL scripts on a blank MySQL 8.x server without errors.
2. Core business queries—placing an order, updating stock, retrieving order history—return correct results on the provided demo data.
3. No orphan records or redundant fields when I inspect with standard integrity checks.
Let me know if you need clarifications on any business rules or naming conventions, and feel free to suggest enhancements that could make future reporting easier.
Here is what I expect:
• A relational schema that reflects common e-commerce entities (customers, products, orders, order items, payments, shipping, etc.) with proper normalization.
• All table-creation scripts, keys, indexes, and constraints supplied as executable .sql files.
• Seed data scripts for a small demo dataset so I can test the integrity of foreign-key relationships and run sample queries.
• Performance-oriented touches where appropriate: sensible indexing on high-traffic columns, consideration for partitioning or read replicas if future scaling demands it.
• Brief documentation (markdown is fine) that explains the schema, assumptions you made, and how to import everything into a fresh MySQL instance.
Acceptance criteria
1. I can import the SQL scripts on a blank MySQL 8.x server without errors.
2. Core business queries—placing an order, updating stock, retrieving order history—return correct results on the provided demo data.
3. No orphan records or redundant fields when I inspect with standard integrity checks.
Let me know if you need clarifications on any business rules or naming conventions, and feel free to suggest enhancements that could make future reporting easier.
Related categories:
SQL
Oracle
MySQL
Database Programming
Database Development
Database Design
Data Modeling
Data Management