The latest articles on DEV Community by Niraj Kumar (@niraj-kumar). https://dev.to/niraj-kumar https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4033063%2Fc73bf176-98a7-4979-8a24-9487df3f4a5c.png https://dev.to/niraj-kumar en Niraj Kumar Fri, 17 Jul 2026 04:18:01 +0000 https://dev.to/niraj-kumar/how-i-built-an-ai-powered-compliance-marketplace-for-the-cannabis-industry-1d6p https://dev.to/niraj-kumar/how-i-built-an-ai-powered-compliance-marketplace-for-the-cannabis-industry-1d6p <p>The cannabis industry isn't just another e-commerce business.</p> <p>Every product, every business, and every transaction must comply with strict regulations that vary by state. Unlike traditional marketplaces, selling a product often requires license verification, lab-tested Certificates of Analysis (COAs), age restrictions, and compliance checks before a listing can even become visible.</p> <p>Recently, I worked on a marketplace that solved many of these technical challenges. This article focuses on the engineering decisions behind the platform rather than the business itself.</p> <h2> The Challenge </h2> <p>Building a regulated marketplace meant solving problems beyond a typical e-commerce application.</p> <p>Some of the major challenges included:</p> <ul> <li>Business verification before sellers could access the platform.</li> <li>License validation for different business types.</li> <li>Product approval workflows.</li> <li>AI-assisted Certificate of Analysis (COA) processing.</li> <li>State-specific compliance rules.</li> <li>Secure marketplace transactions.</li> <li>Multi-role dashboards.</li> <li>Product discovery across verified businesses.</li> </ul> <p>The goal was to build a scalable platform where every product entering the marketplace passed compliance checks before reaching buyers.</p> <h2> Architecture Overview </h2> <p>The platform was designed using a modern full-stack architecture.</p> <h3> Frontend </h3> <ul> <li>React</li> <li>Next.js</li> <li>TypeScript</li> </ul> <h3> Backend </h3> <ul> <li>Node.js</li> <li>REST APIs</li> <li>PostgreSQL</li> <li>Prisma ORM</li> </ul> <h3> Cloud &amp; Infrastructure </h3> <ul> <li>AWS</li> <li>Object Storage</li> <li>CDN</li> <li>Background processing</li> <li>Secure authentication</li> </ul> <h2> AI-Powered COA Processing </h2> <p>One of the most interesting engineering challenges was handling Certificates of Analysis (COAs).</p> <p>Instead of requiring administrators to manually review every report, AI was used to extract structured information from laboratory documents.</p> <p>The workflow looked like this:</p> <ol> <li>Business uploads a COA.</li> <li>AI extracts relevant information.</li> <li>Important fields are normalized.</li> <li>Validation rules are applied.</li> <li>Administrators review extracted data.</li> <li>Products move into the approval workflow.</li> </ol> <p>This significantly reduced manual processing while improving consistency.</p> <h2> Multi-Step Product Approval </h2> <p>Instead of allowing products to become available immediately, every product followed an approval lifecycle.</p> <p>Business Registration</p> <p>↓</p> <p>License Verification</p> <p>↓</p> <p>Account Approval</p> <p>↓</p> <p>Product Upload</p> <p>↓</p> <p>COA Validation</p> <p>↓</p> <p>Administrative Review</p> <p>↓</p> <p>Marketplace Listing</p> <p>↓</p> <p>Available for Buyers</p> <p>This workflow ensured that only approved products appeared in the marketplace.</p> <h2> Compliance First </h2> <p>A regulated marketplace requires compliance to be part of the application's architecture.</p> <p>Some examples included:</p> <ul> <li>State-specific business rules.</li> <li>Business license validation.</li> <li>Role-based permissions.</li> <li>Age-restricted access.</li> <li>Administrative approval workflows.</li> <li>Product visibility based on compliance status.</li> </ul> <p>These rules influenced both backend APIs and frontend user experiences.</p> <h2> Lessons Learned </h2> <p>Working on this project reinforced several important engineering principles:</p> <ul> <li>Business rules often become the most complex part of an application.</li> <li>AI should automate repetitive tasks, not replace human review.</li> <li>Approval workflows deserve first-class architectural design.</li> <li>Role-based access control becomes increasingly important as platforms grow.</li> <li>Clean backend architecture makes evolving compliance rules much easier.</li> </ul> <h2> Final Thoughts </h2> <p>This project demonstrated how modern AI techniques, scalable backend architecture, and well-designed workflows can simplify complex compliance processes while providing a better experience for businesses and administrators.</p> <p>It was an excellent opportunity to combine full-stack engineering with AI-assisted document processing, workflow automation, and scalable SaaS architecture.</p> <h2> Read the Complete Case Study </h2> <p>This article provides a high-level overview of the engineering approach.</p> <p>The complete case study includes the project architecture, workflow diagrams, technical decisions, challenges, and implementation details.</p> <h2> Read the Complete Case Study </h2> <p>This article is a condensed overview of the engineering challenges and architecture.</p> <p>👉 <a href="https://www.nirajkumar.in/work/ai-cannabis-compliance-marketplace" rel="noopener noreferrer">Read the full case study on my website</a></p> <p>If you enjoyed this article, follow me on DEV for more content on Full Stack Development, AI Engineering, System Design, and scalable SaaS architecture.</p> ai architecture showdev softwareengineering