NMS2S Updates: Tips and Tricks
These are a few things learned while working in NMS2S as of September 23, 2026. These are not official SOPs, compliance interpretations, or regulatory guidance. They are simply observations, workarounds, and lessons picked up from using the system in real operating environments.
Multi-Instance
NMS2S generally keeps you signed into one account per browser session, which can be frustrating for operators managing multiple licenses. One simple workaround is to open a second session in an incognito or private browsing window. That allows you to keep two different accounts open at the same time without constantly logging in and out. For multi-license operators, it can save a surprising amount of time when comparing inventory, manifests, rooms, or activity between locations.
Rooms Cannot Be Deleted
Once a room is created in NMS2S, it currently cannot be deleted. It can be renamed or modified, but the room itself remains in the system. Rooms are tied to unique room IDs, so my assumption is that this is related to preserving historical records and preventing older transactions from losing their reference point. Whatever the reason, the practical lesson is simple: slow down before creating rooms, use consistent naming conventions, and double-check spelling before saving.
Clone Transfers
Plants can be transferred between licenses, but there is a specific path required to get them onto a manifest. The plants first need to be in Clone status, then moved into an Inventory room, and from there they can be added to a manifest for transfer. Once you understand the sequence, the process is fairly straightforward: Clone → Inventory Room → Manifest.
Shoutout to Showroom Cultivation for confirming!
Data Entry Matters
Small data-entry mistakes can become much bigger problems downstream. Strain names are no longer editable once entered, and when products are split, the child packages inherit the parent batch name. That means a typo, inconsistent abbreviation, or sloppy naming convention can follow the product through multiple transactions. More than ever, it is worth slowing down, checking spelling, and copying exact names whenever possible before saving a record.
Flower Conversions and Testing
One useful production workflow we tested was converting tested Dry Flower into Deli Style Flower, then into Collected Trim, and finally into Packaged Flower. Through that path, the test results carried forward, allowing the flower to be packaged into grams, eighths, quarters, and other packaged sizes without requiring another round of testing. The same does not appear to apply when converting Collected Trim into Unpackaged Pre-Rolls, which requires testing again. This is one of those areas where understanding the conversion path before starting can save a lot of unnecessary work.
Zebra Browser Print Issues
Printing directly from NMS2S remains one of the more inconsistent parts of the experience. Between Windows 10, Windows 11, different browsers, different Zebra models, printer drivers, Zebra Browser Print, and label sizing, there are a lot of variables involved. In one case on my own computer, a print process became stuck in a loop and continued consuming CPU resources until the laptop became noticeably hot. That may have been a one-off issue with the local printer environment, but it is still worth watching for. If your computer suddenly starts running hot after printing, check Task Manager and make sure Zebra Browser Print or the Windows Print Spooler is not continuing to run unnecessarily.
Space Farms
Between cultivation, manufacturing, and retail, the grow side often feels the most disconnected from the software. There are a lot of reasons for that. Grows are frequently located in rural areas where internet connectivity may be limited, and an agricultural environment is not exactly designed around having a workstation sitting nearby.
There is also a mismatch between the physical workload and the digital workload. Crops are alive, which means nearly every physical change creates another digital task: a plant dies, log it; new tags are created, log them; plants move rooms, log it.
That burden gets even heavier because the reality is that many growers JUST want to grow. They did not get into the business because they wanted to configure printers, troubleshoot browsers, or spend their day entering data into a tracking system. Any process that reduces those administrative steps without sacrificing accuracy is going to matter.
There is still a lot to learn, and most of the best tricks are probably being discovered by the people actually using NMS2S every day. What have you learned that saves time, prevents mistakes, or makes the system easier to work with?
