Purpose
The syllabus case study is a group project (at most three members), not a 15-minute classroom vignette. You either (A) study a real e-commerce web or app or (B) propose a new e-commerce application for an organisation you researched.
Use this brief as the assignment sheet. The short case studies on this site are teaching examples only; they are not the project report.
Tracks
Track A — Analyse an existing product. Pick a live site or app (Nepal or global with Nepal operations). Cover products or services, features, payments, security, marketing, and operations.
Track B — Propose a new product. After studying an organisation (shop, NGO, campus unit, B2B supplier), propose an e-commerce application: problem, users, model, features, payments, and go-to-market.
Suggested Nepal starting points (you may choose another with the instructor’s OK): Daraz, Sastodeal, Hamrobazar, eSewa/Khalti merchant checkout, Foodmandu or similar delivery, a D2C Instagram brand that also has a store, a B2B materials or FMCG distributor portal.
Group rules
- Maximum three students. All names on the cover page.
- One shared report and one presentation. Split work, but every member must be able to answer questions on the whole report.
- Do not copy teaching cases from this site as if they were your fieldwork.
Required report sections (map to units)
Write in your own words. Use screenshots you took, dated. Typical length: 2,500–4,000 words (Track A) or a comparable proposal pack (Track B).
- Introduction and type of e-commerce (Unit 1) — Pure vs partial; B2C / B2B / C2C / m-commerce.
- Business model (Unit 2) — Value proposition, revenue model, market, competitors; B2C or B2B model name.
- Infrastructure (Unit 3) — Web vs app, hosting/CDN if visible, mobile experience, key services (search, chat, notifications).
- Security and payments (Unit 4) — HTTPS, login/2FA if any, wallets/cards/COD, PCI scope if cards; policies you can observe (privacy notice, refund).
- Marketing (Unit 5) — SEO, ads, email, analytics clues (pixels, campaigns).
- Social, mobile, local (Unit 6) — Social presence, app/SMS, location or GBP if relevant.
- Networks, auctions, or portals (Unit 7) — Only if relevant (Marketplace, auction, portal vs store).
- B2B / supply chain (Unit 8) — Required for B2B products; optional one paragraph for pure B2C (how fulfilment works).
- Conclusion — What works, what you would change, exam-style link back to theory.
Track B: replace “what they do” with “what you would build,” but keep the same unit headings.
Deliverables
- PDF or DOCX report with cover, contents, references (URLs + access dates).
- 8–10 minute presentation (slides). All members speak.
- Optional appendix: feature table, payment methods screenshot collage, competitor one-pager.
Rubric (100)
| Criterion | Marks |
|---|---|
| Coverage of required unit sections | 30 |
| Evidence (screenshots, URLs, observation—not guesswork) | 25 |
| Nepal / organisation context and honest limits | 20 |
| Theory used correctly (model names, security, payments) | 15 |
| Writing, structure, citation, presentation | 10 |
Failing the integrity rule below scores 0 for evidence.
Academic integrity
- No fabricated screenshots, fake user counts, or invented payment partnerships.
- Quote the site’s own terms/privacy page; do not invent legal claims.
- AI tools may help outline language, but facts must come from the live product and your notes.
- This page is teaching material, not legal or investment advice.
