Comply with Michigan Cannabis Tracking Laws HB 4209, 4210
Ensure your Enterprise Township, Michigan Cannabis Business is Compliant with Michigan Cannabis Tracking House Bills 4209 and 4210
As a result of the 2017 Michigan state House Bills 4209 and 4210, a state proposal for development of a seed to sale software and tracking database was issued. Consequently, in mid March 2017, Franwell METRC was awarded the contract to supply the state tracking system. In accordance with the law, Michigan cannabis vendors must be able to access and supply regulated information to the state tracking system. As such, there are specifics of these laws that affect cannabis vendors in Enterprise Township, Michigan.
Top 10 Law Changes Affecting Cannabis Vendors in Enterprise Township, Michigan: Grow Facilities, Dispensaries, Processors, Manufacturers, Secure Transporters and Testing Labs
In light of Michigan cannabis tracking laws, cannabis vendors must be in compliance with HB 4209 and 4210 by December 17, 2017. At this point, cannabis vendor operations must comply with the Department of Licensing and Regulatory Affairs (LARA) new internet-based, statewide database and regulatory monitoring software. Furthermore, the state software must track all medical cannabis products in commercial trade and upload the transactions to the state database.
Moreover, LARA is implementing and requiring the Cannabis vendors to link to a statewide excise tax system for the purpose of electronic tracking of all cannabis product sales.
Cannabis vendors must track, store and provide LARA access to its orders and order transports, including transferee, transporter, date, quantity, and price.
Out of Specification (OOS) product test results must be identified and reported to LARA. Additionally, the cannabis vendor must identify any threat to patient health from a particular batch of medical marihuana product. Likewise, the health threat must be reported to LARA.
Cannabis vendors must make a determination of whether a particular product sale or transfer transaction is properly labeled and captured in a transportation manifest. Furthermore, the vendor must prevent patient sales from exceeding the permissible product limit.
Cannabis vendors must retain all cannabis transaction records. This includes the date, time, quantity, and price of each sale or transfer of cannabis patient. Likewise, for a registered primary caregiver, concentrates processor and provisioning center.
Cannabis vendors must monitor seed-to-sale transfers, receipt and integration of information from inventory control and tracking system.
Furthermore, cannabis vendors must store and provide LARA access to data that verifies employee status. Employees of Cannabis vendors must possess a current, valid registry identification card. ID cards must not be suspended or revoked in order for the employee to enter and work within the facility.
In addition, cannabis vendors must purchase a compliant software and database solution to achieve quick and automated compliance. Cannabis compliance software enables automated linkage with the LARA statewide monitoring system and leaves more time for core business needs.
Equally important, cannabis vendor compliance software and database must electronically achieve all the requirements listed in 2-10 above. Additionally, vendor must ensure such software is compliant with HIPAA Privacy Rule requirements.
How you can Comply with Michigan Cannabis Tracking Laws in Enterprise Township, Michigan (See Below)
Motagistics’ Grow Facility Management and Dispensary POS Software is Compliant and Validated to Connect with the Franwell METRC State Cannabis Monitoring Software
Not only are all Motagistics features fully integrated with an inventory management, product tracking & e-commerce software, but they’re also fully compliant with Michigan state regulations:
Visit the Motagistics home page to sign up for a Motagistics Software Demo and additional information fully detailing all seed to sale core functionality and available add-on modules.
Or email your request to firstname.lastname@example.org