The starting point
Help facility teams compare physical inventory reality with Metrc records, investigate variances, document resolution, and prepare reconciliation evidence while preserving the operator's responsibility for verification and reporting.
A public-source portfolio case study for a facility-scoped reconciliation workspace that compares physical inventory with Metrc records, documents variance investigation, and prepares reconciliation evidence. Internal thresholds are advisory rather than regulatory allowances, and operators remain responsible for verification and required reporting. All listed service opportunities are proposals, not shipped functionality.
What’s implemented
- Public landing/pricing/legal/contact routes and authenticated protected workspace with entitlement checks
- Encrypted facility-scoped Metrc integrator/user API-key storage, Oregon Basic auth, timeouts, inventory/sales/lab pulls
- Persistence for facilities, memberships, connections/syncs, inventory/testing snapshots, physical logs, discrepancies, reports, notifications, billing, and contact requests
- Physical count, damage/discard, and lab-result logging
- Deterministic discrepancy rules and severity tiers
- Investigation state, likely causes, filters, resolution notes/timestamps, dashboard risk/status views
- Facility-scoped PDF/CSV reconciliation reports with validation, metadata, and advisory disclaimer
- Stripe Checkout/customer portal and plan/entitlement gating; notification events with email dependent on Resend configuration
- Route/service tests and accessibility/verification scripts
Technical approach & boundaries
Technology
- TypeScript, React 19, Vite, Tailwind CSS 4, shadcn/Radix UI, Wouter, TanStack Query, Recharts
- Node.js, Express 4, tRPC 11, Zod, Vitest, Supertest, esbuild
- Drizzle ORM on MySQL/TiDB-compatible runtime with pnpm; PDFKit
- Axios Metrc HTTP integration
- bcrypt/Jose/session cookies
- Stripe SDK
- Optional Resend and AWS S3 SDK
Limitations & readiness
- Early validation / first-customer-discovery phase. A launch package lists a Q4 2026 target; its uptime, latency, success-rate, status-page, customer, and compliance statements remain unverified planning copy.
- No verified production deployment, clients, paid pilots, uptime, or operational metrics
- POS/cultivation connectors, generic webhooks/APIs, native mobile/offline/photo/SMS/Slack, and multi-location enforcement are planned rather than evidenced
- Email needs Resend configuration; Stripe/hosting depend on managed secrets
- API contract calls for rate limiting and CSRF hardening before public exposure
- Runtime is MySQL/TiDB-compatible; PostgreSQL is a documented portable reference
- Launch package includes unsupported OLCC-compliant, SOC2/HIPAA/GDPR, performance/uptime, and status-history claims that are not evidence
- Operational thresholds are internal advisory rules
Inside the idea.
Public project notes and a separate visual interpretation.
Statusin developmentCategorysystems
Stack
- TypeScript, React 19, Vite, Tailwind CSS 4, shadcn/Radix UI, Wouter, TanStack Query, Recharts
- Node.js, Express 4, tRPC 11, Zod, Vitest, Supertest, esbuild
- Drizzle ORM on MySQL/TiDB-compatible runtime with pnpm; PDFKit
- Axios Metrc HTTP integration
- bcrypt/Jose/session cookies
- Stripe SDK
- Optional Resend and AWS S3 SDK
Implemented notes
- Public landing/pricing/legal/contact routes and authenticated protected workspace with entitlement checks
- Encrypted facility-scoped Metrc integrator/user API-key storage, Oregon Basic auth, timeouts, inventory/sales/lab pulls
- Persistence for facilities, memberships, connections/syncs, inventory/testing snapshots, physical logs, discrepancies, reports, notifications, billing, and contact requests
- Physical count, damage/discard, and lab-result logging
- Deterministic discrepancy rules and severity tiers
- Investigation state, likely causes, filters, resolution notes/timestamps, dashboard risk/status views
- Facility-scoped PDF/CSV reconciliation reports with validation, metadata, and advisory disclaimer
- Stripe Checkout/customer portal and plan/entitlement gating; notification events with email dependent on Resend configuration
- Route/service tests and accessibility/verification scripts
Repository links
Conceptual provenance. The alternate view is an original portfolio diagram based only on this public project record. It is not a product screenshot, live data, or a claim about a shipped interface.
BEYOND THE ORIGINAL PROJECT
What this could become for you.
These are proposed client adaptations—not claims that they have already been delivered.
Potential engagements & deliverables
- compliance-workflow MVP build with staging, schema/migrations, connector, count forms, discrepancy rules, exports, tests, and handoff
- Metrc integration hardening with credential review, retry/idempotency controls, sandbox fixtures, observability, runbook, and failure-path tests
- audit-evidence reporting package with configurable PDF/CSV templates, timeline, archive workflow, retention/export specification, and acceptance checklist
- SaaS access/billing implementation with entitlements, trials, webhooks, owner/admin flows, staging configuration, and a billing runbook
- launch-readiness and claims review with capability matrix, synthetic-data demo, prioritized POS-adapter scope, marketing-copy validation, and release checklist
Related work
- Generic SaaS overlap only; repository references a Manus OAuth/runtime scaffold. No literal AppArchitect identifier is observed.