AI-first cannabis ERP
Talk to your ERP like you talk to your team.
Say what happened and it is recorded, costed and ready for an auditor.
Cultivation, manufacturing, distribution, retail and medical — on one set of records.
A system of record tells you what happened. You need one that tells you what to do.
The good systems of record are genuinely good at their job. They store what your team entered, when, and who entered it. But that is a different job from running the operation: reconciling three sources, catching the batch that is missing a record, and knowing what is due before it is late.
That gap is why operators who like their software still keep a spreadsheet beside it.
Records what happened
- You enter it, it stores it
- You build the report to find the problem
- You remember what is due
Tells you what to do next
- You say it, it records and costs it
- It finds the problem and tells the right person
- It raises the work before it is late
Say it. The system writes the record.
Anything a person can do through the interface, they can say instead. No screen-hunting, no learning where a form lives, no training a new hire on menu structure.
It works the same records the rest of the platform works, so what it writes is costed, audited and ready to report the moment it lands.
fig. 1 — illustration. Scripted. Not a live demo.
An agent writing to regulatory records should worry you. It would worry us too, on a system where a mistake is permanent. This one is not.
Because nothing it does is permanent.
A grow room is messy. The scale was not tared, the room was logged wrong, someone keyed 42 where they meant 4.2. Corrections are not an exception in this industry. They are Tuesday.
Every action — yours or the assistant's — is correctable, voidable and fully audited. The operator fixes it themselves, in the system, without waiting on anyone. The original is never deleted, because deleting it is what makes a number impossible to explain a year later.
ledger · batch B-2214 · complete lineage
- 09:14:02ops.mrodriguesharvest.wet_weight42.00 kg
- 09:41:55ops.mrodrigues
harvest.wet_weight42.00 kgvoidreason: scale tare not zeroed
- 09:42:10ops.mrodriguesharvest.wet_weight4.20 kgsupersedes the voided entry at 09:41:55
- 09:42:10reconcile.autolot mass balance closed
- 09:42:11report.period_dirty2 records changed since draft
fig. 2 — illustration. Not a product screenshot.
That is the substrate. It is what makes the assistant safe to trust with your regulatory records, and everything after this depends on it.
It watches, and it tells the right person.
Most systems will report a problem if you build the report. Tracert One goes looking and notifies whoever can fix it.
Work that is coming due
Cycles, holds and rest periods are tracked against the calendar, so the next action surfaces before it is late rather than after.
Numbers that do not agree
The system continuously checks its own records against what is physically there and what has been reported, and raises the divergence.
Records that are missing
A batch that reached a stage without a required result on file, or a package that does not appear in the last reported period.
Costs that never landed
An input consumed against a batch and never costed to it, so your cost per gram does not quietly drift from the truth.
fig. 3 — illustration
Reports are checked before they leave.
The useful work happens before the file exists. Tracert One validates the period, surfaces anything that will not reconcile and tells you what to fix, so the report you file is one you have already checked rather than one you hear about afterwards.
Operational control, not just a record of it.
The same records that satisfy an auditor are the ones that run the floor. Cost, access and workforce are not separate products bolted on the side — they read and write the records everything else does.
Cost, down to the input
Every input consumed is costed to the batch that consumed it — materials, packaging and the labor booked against the work.
- Cost per unit derived from records, not allocated after the fact
- Cost pools and build-up you can open and follow to source
- Purchase orders, invoices and credits on the same ledger
Who can do what
Role-based access down to the permission, so an operator, a QA lead and a controller each see the system their job needs and nothing else.
- Roles composed from a permission matrix, not fixed tiers
- Scoped per facility across a multi-site organization
- Every action carries the person who took it
Work, training and sign-off
Tasks are assigned, dependent work is sequenced, and the SOP a person signed off on is the version they were trained against.
- Task templates, dependencies and shift recording
- SOPs authored in the system, versioned and signed
- Training tracked against the versions in force
Gates you configure, not gates we chose for you
Every controlled step carries a gate, and each one is set on two independent axes. A facility running to a pharmaceutical standard and one running to a lighter obligation use the same platform, configured differently — rather than one of them fighting defaults built for the other.
Signature
How many people have to put their name to it- noneRecorded, no signature required
- singleOne authorized person signs
- dualTwo, and never the same person twice
Enforcement
What happens when the rule is not met- mandatoryThe step cannot complete until it is met
- warn onlyIt proceeds, and the exception is recorded
- disabledNot in force for this facility
Across a multi-site organization, policy can set a floor: a facility can be stricter than the standard its parent imposes, never looser. The setting shows which policy put the floor there, so an auditor asking why a step is configured that way gets an answer from the system.
What is on the same records
Every stage below is built, and every one writes to the same records. There is no boundary between cultivation and finance, or between packaging and the filing, where numbers have to be reconciled between two systems.
Production chain
Propagation through destruction, in order.14 builtpropagation
Cut counts per mother plant by cutting date, with the mother's own lineage back to the seed lot or source culture. Tissue culture vessels tracked as their own container class rather than as plants.
veg and flower
Plant counts by room and position, with canopy area measured against the site's authorized limit and a stage clock per batch. Moves between rooms are recorded as transfers, not edits.
nutrient management
Recipes with per-tank concentrations and EC and pH targets, alongside what was actually recorded, and every batch charged for the fertilizer it consumed.
water management
Source, volume, and destination per irrigation event, with runoff recorded against the room.
harvest
Wet weight captured per plant or per lot at the scale, with the operator on the record.
post-harvest
Dry cycle with room conditions; wet-to-dry loss calculated per lot rather than assumed. Trim, stem, and waste fractions weighed separately so the mass balance closes.
processing
Input lots to output lots with yield and loss per run, and every output carrying the full set of contributing input lots.
QA and lab testing
Certificates of analysis attached to the lot they belong to, with analyte results, method, lab, and sample date, and a packaging block on any lot missing a required result.
sanitation and hygiene
Cleaning scheduled per room and per equipment item, recording product used, contact time, operator, and sign-off. Overdue tasks surface against the room.
packaging and SKU runs
Bulk lot into finished SKU with unit count, unit weight, and packaging materials consumed, and every unit tracing back to its source lot.
medical sales
Patient registration and the authorising document on file, with product and quantity dispensed against the authorized limit and the remaining balance carried forward.
shipments and fulfilment
Shipping documents by package with destination, carrier, and quantity, and discrepancies at receipt recorded against the shipment rather than silently absorbed.
destruction and waste
Reason, method, weight, and witness on every destruction event, with the waste stream it went to.
regulatory reporting
Period-based report generation, with the period validated and anything that will not reconcile surfaced before the file is produced.
Operating modules
Running on the same records, not alongside them.6 builtfinance and costing
Every input consumed — nutrients, media, packaging, labor — costs to the batch that consumed it, so cost per gram is derived from records rather than allocated afterwards.
workforce
Tasks assigned by room and shift. SOPs authored in the system with version numbers, sign-off recorded per person per version, and training records tied to the versions that person is signed off on.
fleet
Vehicles, drivers, and trips tied to the shipments they carried, so a delivery traces back to the vehicle that moved it and when it left the site.
dispensary
Store-level inventory drawn from the same package records as the production side.
point of sale
A sale decrements the same package that the shipping document and the filing see.
ecommerce
Orders draw on the same inventory, with no separate stock file to reconcile.
Regulatory reporting
The platform is the same everywhere. Cultivation, post-harvest, processing, QA, sanitation, finance, workforce, fleet, dispensary, point of sale, the audit trail and the assistant do not change based on where your facility is. What is specific to your regulator is the last step: the file you submit, or the system you push to.
Where this stands today
Reporting is live and runs on the same records the rest of the platform writes. The period is validated before the file is produced, so what you file is something you have already checked. Where a regulator takes a push into a track-and-trace system rather than a file, that is on the build list — it draws on the same records, so it extends this rather than sitting beside it.
Ask about your jurisdiction on the call and you will get a straight answer, including if the answer is not yet.
Which jurisdiction and which integration we build next is decided by who is in the room. Founding partners have direct input on that order.
Founding partner terms
Tracert One is pre-launch. That is the offer, not a caveat attached to it. We are taking 10 founding partners and designing the next year of the product against real facilities.
- 01Founding rate: from US$420 per month for a micro facility — 65% of list price, scaled by licensed canopy.
- 02That rate is locked for 24 months from signing.
- 03After 24 months you move to 85% of list price as it stood on the day you signed — roughly 30% above the founding rate, and it does not move again.
- 04No implementation fee, and no per-seat pricing — unlimited users on every tier.
- 05Direct input on build order, including which regulatory reporting ships next.
- 06Direct access to the founder, not a support queue.
Founding rate
From US$420
per month for a micro facility — 65% of list, scaled by licensed canopy
What we get
A real facility to design against, and a case study once you are live. That is the trade, stated plainly, because a founding partnership that only runs one direction is not one.
Direct answers
Will migrating break my compliance reporting?
This is the right thing to worry about, and it is why migration is not a switch you flip. You run your existing reporting route through at least one full period while your records are in Tracert One, and you compare the two before you rely on ours. If the numbers disagree, that is a finding we fix before you file from here, rather than after.
You are new. Will you be here in 18 months?
Fair question. What we can put in writing, we have: the 24-month rate lock and the list-price term above are contractual, and we publish no dates because we do not make promises we cannot keep. The platform is built — what this page describes exists today, not a plan — and the fastest way to judge us is to spend thirty minutes inside it.
We are happy with our current system.
Then the question is not whether it is good. It is whether it tells you what to do next, or only logs what you already did. A system that records entries leaves every shortage, every overdue cycle and every missing result for a person to notice first. The other test is simpler: do you still keep a spreadsheet beside it? If it tells you what to do next and there is no spreadsheet, we are probably not useful to you yet.
Whether this fits, by the size of your operation
The platform does not care where you operate — your records live here either way, and the honest test is simpler than geography: has your operation outgrown the spreadsheet? The one thing that does depend on your regulator is the final filing step, and the reporting section says plainly where that stands.
A fit now
You are a fit if tracking the operation by hand has started to cost you. Batches you cannot trace back without asking someone who was there. Numbers you cannot explain a month later. A week of rebuilding records before every inspection. Whatever your regulator asks of you, the records that answer it are the ones you are already struggling to keep.
Not a fit yet
You are not a fit yet if the operation is still small enough that a spreadsheet is doing the job. If one person holds the whole picture and nothing has gone wrong because of it, you do not need this. Come back when it starts to hurt.
Tell us about your operationApply as a founding partner
Six fields. Licensed canopy matters most — it tells us whether you have outgrown the spreadsheet yet. Jurisdiction shapes which report we show you on the call.
- 30 minutes, with the founder
- A live walkthrough of the system, not a deck
- We tell you plainly if you are not a fit yet
30 minutes, live walkthrough with the founder, no deck.
These details are used to prepare your call and to decide whether Tracert One is useful to you now. How we handle your data