Skip to content
Editor goes to an ingredients page and sees the Upgrade screen instead of the cost information.
User Navigates to Plans PageUser request “Contact Us”Note: User can request 1 time per sessionRequest Sent To:Account OwnerSlack Channel: #bot-devices-upgrades
Updating the Percentage amounts on ingredients in recipes using Standard or Bakers Percentage does not change the quantity of the ingredientBaker Percentage updates recipes correctly
From the team page, the user clicks “Manage Devices” to view the device list. This link is only visible to Owner and Editor/Manager Role TypesOnly available on Starter and Scale PlansNote: Free Plans do not have access to the Team Page
User clicks remove on a device,That device is logged out immediately
If a user belongs to an organization that is at its limit that is 2 or more devices, they will be able to request additional devices via an in-app teaser. On button click an email and slack will be sentEmail: devices@getmeez.comUsers are allowed to request 1 time per login attempt. After they request, they can then move forward by logging out a user and entering meez or returning to the login screen. They are not required to request additional devices to move forward
Navigate to the owner user account in Django AdminOpen User Detail Page and Scroll to User SettingsUpdate Value of Maximum Device sessions-1 = Unlimited AccessEmpty/Null = Feature is disabled/unlimited devices>=1 = Numeric Value that represents the maximum number of active devicesDevice Info - i.e Mac, iPhone 12,Global IP AddressDevice IP AddressBrowser
PIT hangs and loads continuously on filter. We improved the PIT to better handle pagination and multi location UoM Definition that was creating infinite load time and zombies Recipes can be restored even if an ingredient was also deleted, The ingredient will be restored as well
Unhandled API error for device tracking in store/user/api to avoid endless spinning at login When a user is redirected to a details page (recipe/ingredient/menu/etc) after login, the < back icon should take them to home page and not create a new token
Product Release Notes
5.9.0 September 29, 2025
Lets try this again, we caught some bugs in the final stages of QA that we were not comfortable with releasing, but now we are ready to go.
While this release of only 29 tickets may not seem flashy, it directly resolves 5 customer-reported bugs. Additionally, we've implemented valuable updates to our infrastructure, the Bulk Recipe AI tool, and refined the user experience.
Customer Enhancements:
5.8.0 September 9, 2025
We are on a roll! This release is highlighted by the introduction of the new request Scale flow from the plans page. We also included some enhancements to the Bulk Recipe Upload work flow and cleaned up some bugs.
Automated Inbound From Plans Page - No More Email Client!
Additional Enhancements
5.7.0 September 2, 2025
The releases keep coming! This release is highlighted by fixes to the new backend printing process to address issues voiced during the team meeting including: opening recipe In a new tab vs window, using fractions instead of decimals, aligning hero images to the right and removing the added default header to prep step to save vertical space. Additionally, we addressed issues related to the ai recipe uploader, the ability to remove menu section values and some further clean up on plans and active devices.
Finally, we are releasing the last portions of the home page refactor. This work is all behind a feature flag so there will be no impact to customers until we turn it on.
Printing Updates & Menu Category Improvements
Here is quick walkthrough -
https://www.loom.com/share/42bcf2ab624640af81994b35451a6ad3?sid=f8bbb75e-77d9-45cc-b77d-028165f849f5
Cost Input Field Consistency
When customers are manually entering cost, the fields on the recipe page and the ingredient page are in different orders for Purchase Cost, Purchase Unit. We have now created consistency that it will show at Cost then unit on in those areas.
Recipe & Old Ingredient Cost Forms
New Ingredient:
Additional Enhancements
5.6.0 August 20, 2025
This release is the first of a new cycle where we will be trying to release at the end of our two week sprints. This release will be highlighted by introducing the ability for owners and editor/managers to manage the devices that are currently logged into an organization's accounts. Additionally, we are deploying the last pieces of the Recipe AI uploader so we will now be able to enable that feature for internal and service use. We had a handful of bugs and enhancements that are going out.
Active Device Management
We have created a new view that allows owners and managers the ability to view the devices that are currently logged into their organization. The owner will have the ability to remove a device, which will force a log out of that users. The owners will be able to see the device, browser, email and last active date for each device. This view matches the view when users hit the device limit for their page
Team Page View
Device List View
Additional Enhancements
5.5.0 August 12, 2025
This release is a small bug fix release. The primary bug that we are addressing is an issue where freemium users are not able to upgrade to the team plan in the app if their trial was on a legacy plan type. We additionally fixed another handful of bugs. Highlights below.
Additional Enhancements:
5.4.0 August 5, 2025
This release we will be introducing the next phase of active device restrictions and a round of significant clean up on how we create and manage device sessions. With this release, we will begin to enforce device limits on any users that purchases a new or modifies a plan, starts a trial or gets downgraded to the free version of the app from a plan or trial with a device limit. This will not impact any existing users that are on legacy plans or plans that were purchased with active device restrictions listed. THIS IS JUST FOR NEW PURCHASERS/TRIALIST after the release is live.
FAQ - Now that restrictions are live:
Will a user get blocked if they reached the limit?
For users in organizations that have reached their limit, they will get blocked on login. They will be required to remove an active session or upgrade to a higher plan.
What happens when a user requests additional devices:
How do I manually update an organization's device limit:
Device Fingerprint Improvements:
To minimize the number of duplicate tokens being created and to tie session more closely to the device, we have made the session fingerprint more closely associated with the device you are on. We are now creating a device id on the following parameters:
Additional Enhancement:
5.3.2 July 2, 2025
Another follow up release to address updates to the pricing model and some active device duplicate token creation. See below for details
Ticketlog:
5.3.1 June 19, 2025
This is a quick follow up release that improves our management and logging of active device activity. These issues were identified prior to 5.3.0 release but the fixes didn’t make the cut off for release.
Ticketlog:
5.3.0 June 16, 2025
In this release, we introduce the concept and tracking of active devices. As part of our new pricing model we will begin tracking and then restricting the number of devices that a single organization can have active at one time. This release introduces all of the code for this feature, but it will initially be turned off except for the tracking of active devices. We will monitor organization devices usage over a few weeks period to understand if our limits are correct and if the technology is working as expected.
Additionally, we are rolling out enhancements to our Plans Page, Inventory Management, and our Data Infrastructure.
Active Device Tracking
What is an active device:
An active device is logged, when a user logs into meez. We are tracking active devices based on the user id, device type and browser. For example, if user: logs in on their mobile device via safari, that will log one device. If the same user then logs in on their desktop computer via chrome, that would be active device 2. You can see a full list of test cases here -
What is not an active device
We have exclusions in place to not count devices for users that have an @getmeez email address or if a customer account is logged in via Django admin. Once we enable device restrictions, this will be critical so as not to take up any seats from an organization by an internal user or service team member.
What This Release Means For Customers
Nothing happens for our customers immediately after this release. On Sunday June 22, we will run a script to reset all user tokens. This means customers will need to log in post the deploy. We will post a message in the app starting Friday June 20th. After that initial login, users should see no impact from the new device restrictions and they will continue on as normally as if there are no device restrictions.
What This Means for Meez:
We will now be logging all devices and begin monitoring usages across our customers. We will provide Sigma reports that will show the active device counts for each organization. These values will help us determine what is typically usage for an organization as well as identify customers that use a large amount of devices and could be severely impacted by the new restrictions and pricing model.
What Comes Next:
After we build confidence that the technology and our business logic is working appropriately, we will start rolling out device limits to production. At that point, customers will begging getting blocked from access meez if they are at the company's allowable count. Users of organizations that are at their limit, will have the ability to log out another active session so continue into the app. We will additionally have functionality that allows customers to request more devices directly with Sales and CS. As we get closer to enabling this we do additional training and education.
Inventory Count Status Update Tool
Django Admin Tool To Update Count Status:
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.