NMS2S Update: CCD Releases Q&A Videos

Between September 10th and 11th, the New Mexico CCD released two Q&A videos addressing questions collected from operators during the first weeks of NMS2S. The videos covered everything from testing and manufacturing workflows to migrated inventory, printer setup, API issues, access problems, and the growing list of situations where a support ticket is still the only real answer.

Finished Product Testing

Testing follows the form of the finished product. Tested flower converted into pre-rolls must be tested again because pre-rolls are treated as a separate product category. The cleaner workflow is to manufacture the final unpackaged product first, test it once, then package it for sale.

Pack and Sack

If tested bulk concentrate is simply divided into smaller retail packages without additional processing, ingredients, or a change in product form, another full test is generally not required. The important distinction is whether the product itself changed, not whether the container did.

Manufacturing Sequences

NMS2S calculates manufacturing yield based on the source quantity and finished-unit weight, and the source deduction must reconcile with what is created. Once certain manufacturing actions are completed, including conversion to Deli Style, they cannot currently be undone, so operators need to verify the source inventory, quantities, and product type before committing.

Test Batch Limits

NMS2S cannot increase flower testing batches from 15 to 50 pounds because the limit exists in rule, not in the software. Any increase would require formal rulemaking rather than a system setting.

Migration Corrections

Legacy BioTrack inventory can be corrected through the migrated-inventory correction tool, including product type, name, quantity, expiration date, representation, and package information. If the necessary correction is not available there, operators need to submit a support ticket rather than create replacement inventory to force the numbers to match.

Bulk Actions

Plants can be harvested in bulk only when every selected plant is mature and has the exact same strain name. Inventory splits and adjustments still have to be completed one record at a time, which becomes a serious operational burden when large numbers of migrated records need cleanup.

Integrations

Some folks asked about when services like Inscribe or Dutchie would get access, still no timeline. POS and other integrated systems only satisfy reporting requirements when the transactions successfully reach NMS2S. Operators are still responsible for daily reconciliation and verifying that inventory, sales, and other regulated activity made it into the state system correctly.

Access Requirements

Initial access is tied to the primary controlling person listed in NM Plus. If NMS2S is unavailable, operators must report the issue, maintain complete records during the outage, and enter the activity once access is restored; transfers are restricted while track-and-trace access is unavailable.

Labeling

NMS2S currently supports standard printers and properly configured Zebra printers. Plant tags do not have to be system-printed, and handwritten track-and-trace identifiers are acceptable as long as they are legible, accurate, and remain attached to the correct plant. In the meantime, both myself and inscribe have provided compliant label printing alternatives for license holders but requires manual export.

Support Tickets

Missing migrated IDs, account problems, API failures, unavailable corrections, and other issues that cannot be resolved through the available tools must be escalated to support. CCD is asking operators to include detailed information such as the affected record, POS provider, error message, failed step, and API-token status.

The broader lesson

NMS2S is enforcing a much more explicit relationship between inventory lineage, manufacturing state, testing, and finished-product form. The system can handle the core workflows, but operators have to pay much closer attention to sequence, naming, reconciliation, and irreversible actions because there are still plenty of places where the software gives you very little room to recover from a bad click.

Nightcrawlers

At the same time, operators have been stress-testing the system themselves, poking at workflows, correcting migration errors, and figuring out what NMS2S can actually do beyond what was covered in the official guidance. Between the CCD’s answers and what is being learned in the field, a much clearer picture of the system is starting to emerge.

Do The Splits

One important discovery is that inventory tags can now be merged. When the parent lots originate from the same tested batch, the merged inventory appears to retain the existing testing status.

From The Deli

The flower workflow also has more flexibility than it first appeared. Dry flower can be converted to Deli Style, then to Collected Trim, and from there into Prepacked Flower while retaining the existing test results. Pre-rolls remain the exception: converting flower into pre-rolls creates a new finished-product form and requires new testing.

Finding Nemo

The global search bar at the top of NMS2S is also more useful than it looks. It can quickly locate inventory across different rooms, which makes navigating large inventories considerably easier.

Sears Catalog

One persistent limitation is the lack of a true product catalog. Product names are not being centrally managed or automatically inherited the way many operators are accustomed to. During splits and conversions, product names may need to be manually updated, creating another point where naming inconsistencies and bad master data can creep in.

There was also significant concern among extraction operators after migrated rosin inventory appeared to have lost or broken testing relationships. In several cases, the problem was not a new testing requirement at all. The underlying issue was incorrect migrated inventory data, and correcting those migration records restored the expected workflow.

Taken together, the emerging picture is that NMS2S has considerably more functionality than was obvious at launch, but much of it is being discovered through trial and error rather than through clear documentation. The system can preserve testing through several inventory transformations, search across rooms, and support more complex lineage than initially assumed. At the same time, weak master-data controls, migration errors, and small interface quirks continue to make otherwise straightforward workflows harder than they need to be.