Skip to main content

  • Few improvements on the table scroll
  • [fix] Enterprise: chance for failing to fetch workspaces after successful login

  • This release brings a much faster implementation of tables. Being a very table-intensive app, this means the app should also perform better overall.
  • Columns in tables can now be pinned (to the left of the table) so they are always visible when scrolling horizontally.

Your current table configurations won't be used with this new implementation. This means all columns will be visible by default and with a default size. For every table make sure to select the View previously being used or to hide columns that you don't need to have displayed. Even though this implementation is much faster, the use of table Views is still recommended.

  • This is the first release that brings support for the upcoming ENTERPRISE plan. Similar to the TEAM plan but it allows you to host everything yourself (users and Team Workspaces), keeping the app 100% offline if needed as it comes with an offline license so it doesn't need to touch our servers at all. The offline license can also include access to multiple Team Workspaces. If you'd like to try this out, please get in touch.

    Documentation on how to set up and use the ENTERPRISE plan is available here: enterprise.bomist.com

  • Releases for macOS are now universal (they run natively both on Intel and ARM processors)

  • [fix] Chance for planned inventory not to be removed and stock not updated after creating production builds

  • Backport of v2.9.26 release (see changelog)
  • Parts can be added into purchase lists from the Pricing & Availability table and the Order Qty is assumed by default
  • On Pricing & Availability table, missing inventory can be checked through Stock Balance instead of Stock Available

  • Some improvements on data sync (Team Workspaces)
  • Small UI improvements
  • [fix] Go-to issue when issue type filter is selected

  • Backport of v2.9.25 release (see changelog)

  • Barcode labels (detailed format) now include a second barcode which encodes the text that is printed on the label as a title. For example, for Part labels that represents the Part Number, while for Storage labels that represents the storage location's name.


  • Parts can now be added straight into purchase orders. You can pick an existing purchase order on the desired supplier or create a new one. When adding parts straight into purchase orders you'll have to manually set prices for each line (if needed).

  • When moving quoted parts on a purchase list to purchase orders, you can now opt to add those into existing open purchase orders or to create new ones. Previously, a new purchase order would be created for every selected supplier.

  • Beta versions of the app now always backup daily and on a different backup folder, so the main one is not clogged with beta backups which could be eventually deleted due to the rolling backups.

  • Procurement settings added under Settings - Workspace - Procurement

  • Backport of v2.9.24 release (see changelog)
  • Only for sale parts can be added into sales orders and sales-only suppliers
  • When manually creating a part, a lot can be created along with the initial inventory
  • API: deliveryDate on sales orders has been deprecated, expected.deliverBy should be used instead (please check API documentation)
  • Some other small UI and UX improvements

  • Backport of v2.9.23 releases (see changelog)
  • Parts autocompleter in the Part dialog: results sorted by name's length
  • Small charts with some statistics added to purchasing, production builds and sales

  • BOM: Assign to first match option is now enabled by default
  • API: production plans and units of measure endpoints added
  • [fix] Add to... menu always disabled under the Parts tab

  • Role-based permissions: you can now create custom roles with detailed permissions

  • Inventory ID code and Date code can be set when receiving items on a PO
  • Inventory Date code can be set when finishing a production build
  • [fix] Failing to autocomplete part's data (integration with Nexar API)

  • New feature: role-based permissions (Team Workspaces only)
  • The app is now using the new Nexar API (formerly Octopart API)
  • [fix] Procurement picking the wrong product revision
  • [fix] Input not accepting the minus symbol (-)

Role-based Permissions​


This release introduces role-based permissions. Right now you can pick from 3 basic roles:

  • Admin: can add other users, has access to all features
  • Member: cannot add other users but has access to all features
  • Observer: has access to all the features but in read-only mode (data cannot be changed)

The role can be set when adding a Team Member (only through the app), or through the Account & Team dialog.

Soon you will also be able to create custom roles with detailed permissions.