New Mexico NMS2S Harvest Dual Entry

Until NMS2S publishes inventory API documentation, harvesting runs in both systems. Flourish remains your operational record for weights, drying, packaging, labels, COAs, and invoicing. NMS2S is the compliance record of truth. This guide will be updated as we work through harvests with operators; sections marked Verify have not yet been confirmed against a completed NMS2S harvest.

Work in Flourish first, then commit to the state once

The instinct during dual entry is to enter the state system first because it is the compliance record. For harvest, do the opposite.

NMS2S harvest entry behaves as a final action. There is no undo, and its date window only accepts entries within about a day of today, so an incorrect entry cannot be corrected later, unlike a Flourish record.
Flourish is where the numbers get built. Weigh by tote, log container by container, and let Flourish sum the totals. You are staging a figure, not committing one.
Flourish runs on mobile. Harvest logging happens on the Android app at the point where the material is being weighed. NMS2S has no mobile app and no barcode scanning at all, so anything done there is a desk task typed from notes.

Get the harvest right in Flourish, then transcribe one correct set of figures into NMS2S. That sequence turns the state entry into a single deliberate action rather than a running log you cannot revise.

Before you can harvest, get the plants into the right rooms

The state migration placed every plant into a single vegetative room. Room assignment and life stage were not carried over, and the migrated birth date reflects the transplant date rather than the date the clone was cut. You cannot run a clean harvest until the plants you are about to harvest are isolated in the correct room.

Work backward from your next scheduled harvest rather than reorganizing the whole site first. Locate and move the plants that are coming down next, then continue with the rest.
NMS2S has no barcode scanning, so plants are located by searching the 16-digit ID. Plan for this to be slow; operators are reporting roughly a day per greenhouse.

Capture plant IDs the moment they are created

NMS2S has no export. When you promote clones to vegetative and the system mints plant IDs, use the Copy All control on the grid and paste the result into a spreadsheet before you navigate away.

That file is what makes plant tag printing and later reconciliation possible. Keep one per promotion, broken out by strain and group where you can. Do this every time, as there is no second opportunity to pull the list.

See this help document for more information.

Weighing: keep the process you already have

Nothing about NMS2S requires you to change how you physically weigh. Keep filling and weighing totes, subtracting tare, and logging container by container in the Flourish harvest log. Flourish sums the total for you.

Verify. Based on the state's training videos, the NMS2S harvest action lets you select a group of plants and enter a single set of figures for the selection rather than per-plant weights:

Harvest date
Wet weight in grams appears to be the total for the selected plants
Waste weight in grams produces the waste package
Expected dry weight an estimate required at harvest time, before you have real dry weights
Yield of trim optional, and not knowable until the end of your process. Recommendation is to skip this and handle trim downstream.
Seeds is left blank unless you are harvesting seeds

Confirm this behavior on a small harvest before committing a large one. If NMS2S turns out to require per-plant weight entry, that changes your labor estimate substantially and is worth raising with CCD.

The dual-entry sequence

Weigh and log the harvest in Flourish as you normally would, container by container.
Select the same plants in NMS2S and enter the harvest date, wet weight, waste weight, and expected dry weight.
When the material is dry, create packages from the Flourish drying screen — enter dry weights, choose the item, review and confirm.
Create the corresponding inventory in NMS2S.
Copy the NMS2S 16-digit ID into Reference Field 1 on the matching Flourish package.
Print the label from Flourish.

Do steps 4 and 5 side by side with both systems open rather than completing everything in one system and returning to the other. Nothing syncs, so there is no waiting, but there is also nothing to catch a mismatch later. Working in tandem is what keeps the two records aligned.

Log harvests the same day

NMS2S rejects dates outside a narrow window: one day before to one day after the current date. You cannot backfill a harvest from last week.

This is the single most consequential constraint on harvest dual entry. Flourish can absorb a late entry; NMS2S cannot. If a harvest comes down on a day nobody can get into the state system, you have a gap that cannot be corrected after the fact. Assign the NMS2S entry to a named person for every harvest day, and treat it as same-day work.

Curing

Verify. The finalize-cure step appears to operate plant by plant, which would be impractical on a harvest of any size. A combine or merge action exists in the interface. Test this on a small harvest and confirm the correct path before your next large one.

Decide your output categories before you harvest

NMS2S is more specific about harvest output than BioTrack was, and some of these decisions have to be made before the material exists.

Deli Style Cannabis. If a customer intends to sell flower deli-style, it must be manifested to them as Deli Style Cannabis. That means asking the customer their intent at order time, and it may mean carrying both a bulk and a deli item for the same product.
Fresh Frozen. An approved alternate to Dry Flower for legacy Flower Lot. If you run fresh frozen for extraction, make sure those items exist rather than sitting under a generic flower item.
Collected Trim. The state recognizes trim and has no separate concept of shake, though your customers may treat them as different products. Decide how you will name these before the labels print.
Unpackaged Pre-Rolls. You cannot go directly from dry flower to a packaged pre-roll. Pre-rolls must first exist as Unpackaged Pre-Rolls, be tested with the COA attached at that stage, and only then be converted to Packaged Pre-Rolls. That means a bulk unpackaged pre-roll item for every strain you roll.

These categories and items can be bulk-created in Flourish. Coordinate the item build with your implementation contact ahead of the harvest, not during it.

Labels

NMS2S label printing is not usable for most operations.

The workaround is to keep printing from Flourish. Your implementation contact duplicates your existing package label and swaps the package identifier field for Reference Field 1, so the state's ID prints on the label you already use. Because the state ID is copied in at package creation, the label is ready to print immediately.

Plant tags are still an open item. Flourish has no plant reference field, so the state plant IDs captured through Copy All have to be imported and swapped in. Work with your implementation contact on this ahead of a cutting cycle rather than during one.

COAs and lot numbers

Test results do not sync back from NMS2S. Upload the COA in Flourish, attach the results to the lot number, and set the lot to inherit on splits so the COA stays attached to child packages. This is also the strongest argument for maintaining a real lot number rather than reusing a state ID, since the state ID changes on every split.

Keep a parallel record

Until the integration exists, keep your own record of harvest weights by container, package counts, the full 16-digit inventory and plant IDs, and your Copy All capture files. If a state-side entry has to be reconstructed or a migration error corrected, that record is what makes it possible.