Batch-Based Bud Safety
BBBUDS is built around one simple idea: batch-level information should be easy to find. A QR code or printed batch/package identifier can link consumers, retailers, inspectors, and labs to COAs, documentation, and recall notices associated with a specific batch.
Verify a batch or package
Enter a batch number (medical) or a source/package identifier (adult-use) to open the public verification page.
How it works
Each batch is assigned a stable public path, for example: /verify/1A4FF0100000022000000123
- Verification page can show COA files, lab info, and packaging fields.
- Recall checks can happen at scan time (batch match).
- Works with short QR payloads (URL + ID) or optional JSON payloads.
What BBBUDS provides
- Stable, scannable verification URLs
- COA links and document caching
- Recall visibility at scan time
- Human-readable pages and API-style JSON endpoints
For producers & retailers
Reduce friction around compliance information by giving each batch a stable public reference point.
- One QR per batch (simple ops)
- Can coexist with existing packaging
- Recall matching can be automated
QR-seeded Conway preview
This box starts as a QR-seeded pattern for one minute, then evolves slowly using Conway’s Game of Life. If it becomes stable for 30 seconds, it reseeds automatically.
API shape
Keep it dead-simple on shared hosting:
- Public page: /verify/<id>
- Static JSON record: /verify/data/records/<id>.json
- Optional: a lightweight PHP router can load JSON + render HTML.
Next steps
- Wire a “recall batches” JSON source (state-hosted would be ideal).
- For adult-use, match METRC “source tag”/package to your verification ID.
- For medical, accept internal batch numbers with the same page format.