[FEATURE] Link Scanned Barcodes and Medicine IDs to Counterfeit Incident Reports

[dipexplorer]

Which part of SahiDawa needs improvement?

Backend API (apps/api/src/routes/reports.ts) & Frontend wizard (apps/web/components/reports/ReportWizard.tsx)

Description

There is a functional disconnect between scanning a suspicious medicine and filing a counterfeit report:

1. When a user reports a batch using POST /api/verify/batch/report, it associates the report with scanned_barcode and medicine_id (by resolving the batch number), but doesn't take images, descriptions, state details, etc.
2. When a user reports an incident via the Report Wizard (POST /api/reports), they can add description, pharmacy details, and images, but POST /api/reports schema and logic completely ignores scanned_barcode and medicine_id.

If a user gets a suspicious result in the medicine scanner and clicks "Report", the system cannot link the scanned barcode or database medicine entry to the final incident report.

Detailed Implementation Guidance

1. Backend Route (apps/api/src/routes/reports.ts)

• Locate createReportSchema in reports.ts. Extend it with two new optional fields:
  • scannedBarcode: z.string().optional()
  • medicineId: z.string().uuid().optional()
• Update the SQL payload inside supabase.from("counterfeit_reports").insert({...}) to parse and store scanned_barcode and medicine_id columns:

  scanned_barcode: data.scannedBarcode ?? null,
  medicine_id: data.medicineId ?? null,

2. Frontend Wizard (apps/web/components/reports/ReportWizard.tsx)

• Check if the URL contains query parameters barcode or medicineId when the user enters the reporting workflow from a scan details screen.
• Store these properties in the wizard component's state.
• Include scannedBarcode and medicineId in the JSON request payload when sending the report data to the POST /api/reports endpoint on submission.

---

GSSoC 2026

• I am a GSSoC 2026 participant and would like to solve this issue.

---

To get assigned, please reply with your planned approach. Keep it clean and avoid spamming.

---

⚠️ Contributor Instructions (Please Read Carefully)

• Do NOT spam "/assign" or "Please assign me".
• To claim this task, you MUST reply with a brief proposed implementation plan/approach. What files will you touch? How will you solve it?
• Once your approach is reviewed and approved by a maintainer, you will be officially assigned.
• Any PR opened without prior assignment and approach approval will be closed.

[anshul23102]

I can implement the backend portion of this feature. My planned approach:

Backend changes:

1. Extend createReportSchema with optional scannedBarcode and medicineId fields
2. Update the report insert payload to include scanned_barcode and medicine_id columns
3. Ensure null handling for optional fields

This connects the medicine scanner workflow to incident reports, allowing the system to link scanned barcodes and database medicine entries to counterfeit incident reports. Ready to implement the backend logic when assigned.

[anshul23102]

@RatLoopz
/assign

[github-actions]

❌ Request Denied

Hi @anshul23102, to ensure a fair distribution of tasks during GSSoC/Hacktoberfest,
contributors are limited to a maximum of 3 active assigned issues at a time.

You are currently assigned to the following 3 active tasks:

• [TESTS] Implement Backend API Route Tests for Counterfeit Incident Reports #1210 ("[TESTS] Implement Backend API Route Tests for Counterfeit Incident Reports")
• [Bug] Error Handler Leaks Sensitive Information - Stack Traces Exposed to Users #1183 ("[Bug] Error Handler Leaks Sensitive Information - Stack Traces Exposed to Users")
• [Security] Medicine Status Validation Missing - Invalid Status Values Accepted #1182 ("[Security] Medicine Status Validation Missing - Invalid Status Values Accepted")

Please complete your currently assigned tasks before requesting assignment for new ones! 🤝

[github-actions]

⚠️ @anshul23102, friendly reminder!

It looks like there hasn't been any activity on this issue since your last update on Thu, 04 Jun 2026 10:33:51 GMT.
To keep this assignment, please share a progress update or open a Draft PR within the next 21 hours. Otherwise, you will be automatically unassigned to let other contributors have a chance. Thank you! 💙

[github-actions]

⚠️ @anshul23102 has been auto-unassigned due to inactivity for over 3 days.

Per our contribution guidelines, we ask that you share updates or open a draft PR to keep your assignment active. If you'd still like to work on this, feel free to drop a comment and ask to be reassigned! 🚀

[anshul23102]

/assign

[github-actions]

⚠️ @anshul23102, friendly reminder!

It looks like there hasn't been any activity on this issue since your last update on Tue, 09 Jun 2026 12:40:24 GMT.
To keep this assignment, please share a progress update or open a Draft PR within the next 21 hours. Otherwise, you will be automatically unassigned to let other contributors have a chance. Thank you! 💙