Release Notes

This page lists recent changes made in Fishbowl Advanced as well as download links for the currently supported versions.

• Click here to jump to the most recent download.
• Instructions for updating Fishbowl are found in the Update Fishbowl article.
• Release Notes and downloads for older versions are found in the Release Notes archive.
• Upcoming features are found in the Roadmap.

​

JUL 14, 2026 - Advanced 26.7

Download - 26.7

• Download Fishbowl-2026.7.exe for Windows
• Download Fishbowl-2026.7.dmg for macOS (Limited support)
• Download Fishbowl-2026.7.sh for Linux (Documentation only)

Highlights - 26.7

• Important Notice: MySQL 8.0 End of Life - Update Optional for Now - MySQL 8.0 reached End of Life (EOL) in April 2026. Oracle will no longer issue security patches, bug fixes, or official support for MySQL 8.0. While we recommend upgrading to MySQL 8.4 LTS, this update is NOT required at this time. Fishbowl will continue to support MySQL 8.0 until the September 2026 release. You can safely use the standard auto-update process for version 2026.7 - it will maintain your current MySQL 8.0 installation. For detailed upgrade instructions, visit: https://help.fishbowlinventory.com/advanced/s/article/MySQL-Update
• Important Notice: If you are upgrading from version 2025.9 or older then this upgrade requires a coordinated installation process. The Fishbowl Server must be updated manually first, followed by client updates. The Fishbowl Client will automatically detect version mismatches and guide users through the update process with a simple "Automatically update your Fishbowl Client" button. If you are upgrading from 2025.11 or later versions this update follows the normal upgrade process supporting auto updating of the server by simply checking for updates.
• Important Notice: Fishbowl 2025.12 and newer versions no longer support MySQL 5.7: If you are still running MySQL 5.7 we recommend migrating to MySQL 8.0 before upgrading to 2026.7. Follow the instructions here to migrate to MySQL 8.0: https://help.fishbowlinventory.com/advanced/s/article/Fishbowl-Advanced-MySQL-Migration
• Important Notice: We are unable to support the Fishbowl Anywhere plugin as part of the 2026.7 release. If you are actively using Fishbowl Anywhere, you should not upgrade beyond the 2025.9 release. We will have Fishbowl Anywhere included in an upcoming release but will provide additional information once available.
• Important Notice: Custom Plugins are not supported in 2025.11 or newer versions. If you utilize any custom Plugins do not upgrade beyond 2025.9. Note that custom integrations are different than custom Plugins. Custom integrations that utilize the REST or Legacy API's will continue to function on 2026.7.
• QuickBooks Online journal entries now carry the customer/job, bringing job costing to parity with the QuickBooks Desktop integration
• QuickBooks Online and Xero connections now stay active automatically, preventing the unexpected disconnects that required a manual reconnect
• Read-Only Location Groups now extends to the Work Orders module
• Fishbowl Payments now refreshes payment credentials automatically to prevent API key expiration
• Quality and reliability improvements across accounting, reports, and bills of materials

New Features - 26.7

• QuickBooks Online — customer/job on journal entries (job costing). Journal entries that Fishbowl posts to QuickBooks Online now include the customer or job when one is specified in Fishbowl, matching how the QuickBooks Desktop integration already works. This ties the cost side of your transactions to the customer or job, so QuickBooks Online job-costing reports reflect the full picture. Jobs map to QuickBooks Online sub-customers.
  • Applies to postings from sales orders, purchase orders and receiving, inventory adjustments (Cycle Count, Scrap, and initial Add), and manufacturing / work orders.
• Fishbowl Payments — automatic credential refresh. Fishbowl now refreshes your payment processing credentials automatically before they expire. Previously, customers who went an extended period (30 or more days) without taking a card payment could have their credentials expire and be locked out until they manually generated new ones. A system option controls how many days before expiration the refresh happens (default 10 days).
• Read-Only Location Groups — Work Orders. The Read-Only Location Groups feature introduced in the previous release now extends to the Work Orders module. Users assigned a location group as read-only can view work orders in that location group without being able to create or edit them, and a lock icon marks those work orders in the search list.
• Part CSV — "Pick in part UOM only" option. The part option "Pick in part UOM only" can now be set and reviewed through CSV import and export, in both the Part import/export and the Part, Product and Vendor Pricing (PPVP) import/export. Previously this option could only be changed one part at a time in the Part module, so customers maintaining parts in bulk can now manage it alongside their other part data. Existing CSV files without the new column import unchanged.
• REST API — create, unissue, and delete transfer orders. Building on the transfer order support added in the previous release, the REST API can now create a transfer order, return an issued transfer order to the Entered status, and delete a transfer order. Access rights, location group access, and status rules are enforced.
  • POST /api/transfer-orders — create a transfer order (Ship and Move types)
  • POST /api/transfer-orders/{id}/unissue — return an issued transfer order to Entered
  • DELETE /api/transfer-orders/{id} — delete a transfer order that is still in Entered status
  • GET /api/transfer-orders/next-number — next transfer order number
• REST API — work order memos. The REST API can now list, retrieve, create, update, and delete memos on a work order, matching the memo support already available for other order types.
  • GET /api/work-orders/{id}/memos — list memos on a work order
  • GET /api/work-orders/{id}/memos/{memoId} — get a single memo
  • POST /api/work-orders/{id}/memos — create a memo
  • POST /api/work-orders/{id}/memos/{memoId} — update a memo
  • DELETE /api/work-orders/{id}/memos/{memoId} — delete a memo
• REST API — get the next sales order, work order, and purchase order number. The REST API can now return the next available sales order or purchase order number based on your auto-numbering settings. Note that requesting a number reserves and consumes it, so the counter advances whether or not you go on to create the order. Auto-numbering must be enabled for that order type.
  • GET /api/sales-orders/next-number — next sales order number
  • GET /api/manufacture-orders/next-number — next manufacture order number
  • GET /api/purchase-orders/next-number — next purchase order number

Fixes - 26.7

General

• Resolved: In some modules (such as Sales Order and Purchase Order) dates were displayed in a different format than other modules, even when the date-format settings were identical. Date formatting is now consistent across all modules.
• Resolved: In the Import/Export dialog, when a user had limited access to .csv imports/exports, the wrong Export/Import would try to run. The Import/Export dialog now exports/imports whats selected correctly regardless of which import/export permissions you have.
• Resolved: Importing the Part Cost CSV failed with an "only the admin can import this information" error for non-admin users, even when they had been granted the appropriate import/export permission. Users with the correct permission can now run the Part Cost CSV import.

Accounting

• Resolved: QuickBooks Online and Xero connections could drop every few weeks with no setting change, and could only be restored by manually reconnecting and re-authorizing. Fishbowl now refreshes the QuickBooks Online and Xero connection tokens automatically before they expire, so connections stay active. A system option controls how many days before expiration the refresh happens (default 10 days).
• Resolved: When an account referenced by an order was inactive or missing in QuickBooks Online, the export reported an error but still posted the invoice and journal entries; once the error was resolved, a second copy was posted. Fishbowl now stops the export for an order as soon as it encounters a missing or inactive account, so invoices and journal entries are no longer duplicated. The same protection applies to Xero.
• Resolved: For customers using 30 Days EOM payment terms, due dates synced to Xero could be incorrect, because Fishbowl did not send a calculated due date and Xero derived it from the transaction date instead. This was especially noticeable in shorter months. Fishbowl now sends the correct due date to Xero based on the order's payment terms.
• Resolved: When cash rounding ("round cash transactions to the nearest $0.05 or $0.10") was enabled, the rounding line was not exported to accounting if payment was taken after the order was fulfilled, causing totals in Fishbowl and the accounting system to disagree. The rounding line is now added and fulfilled correctly when payment is taken after fulfillment.

Purchasing

• Resolved: The Auto PO wizard could recommend purchasing items that were already covered by open transfer orders, because inventory in transit on a transfer order was not being counted. Auto PO now accounts for inventory on open transfer orders, so it no longer recommends unnecessary purchases.
• Resolved: A user with view-only access to the Purchase Orders module — or viewing a purchase order in a read-only location group — could still change a line item's vendor cost using the right-click menu or a keyboard shortcut. These actions are now properly blocked for users without edit access.

Manufacturing

• Resolved: Importing a bill of materials via CSV with a note line set as variable quantity prevented that bill of materials from being added to a manufacture order until the note was manually corrected. Note lines no longer use the quantity fields on import, so the bill of materials works correctly. This applies to both the Part BOM and BOM Details CSV imports.
• Resolved: When a bill of materials was imported via CSV with the finished good marked as a one-time-use item, generating a manufacture order from a sales order with a quantity greater than one produced incorrect component quantities. One-time-use is now ignored on finished good items, so quantities generate correctly. This applies to both the Part BOM and BOM Details CSV imports.

Sales Order

• Resolved: When adding a product to a sales order using the Add Item Wizard (the + button) rather than the product search bar, the product's custom field values were not copied to the sales order line item, even with the option to add custom fields to sales order items enabled. Custom field values now carry over regardless of how the product is added.

Reports

• Resolved: On the Sales Order Summary Export report, the created date was blank until the order was issued. The created date now appears as soon as the order is created.
• Resolved: On the Sales Order, Sales Order (special characters), and Sales Invoice reports, custom field columns were right-aligned while all other columns were center-aligned. Custom field columns now align consistently with the rest of the report.
• Resolved: The Sales Production Demand report calculated its summary totals incorrectly when the part and the product used different units of measure, mixing the two units so the Short total was wrong. The summary now converts units consistently.

REST API

• Resolved: When retrieving a transfer order through the REST API, access could be denied unless the user had access to both of the transfer order's location groups, without accounting for which location group owns the order. Transfer order access now correctly considers ownership, so a user with the appropriate access can retrieve the order.

​

JUN 23, 2026 - Advanced 26.6

Download - 26.6

• Download Fishbowl-2026.6.exe for Windows
• Download Fishbowl-2026.6.dmg for macOS (Limited support)
• Download Fishbowl-2026.6.sh for Linux (Documentation only)

Highlights - 26.6

• Important Notice: MySQL 8.0 End of Life - Update Optional for Now - MySQL 8.0 reached End of Life (EOL) in April 2026. Oracle will no longer issue security patches, bug fixes, or official support for MySQL 8.0. While we recommend upgrading to MySQL 8.4 LTS, this update is NOT required at this time. Fishbowl will continue to support MySQL 8.0 until the September 2026 release. You can safely use the standard auto-update process for version 2026.6 - it will maintain your current MySQL 8.0 installation. For detailed upgrade instructions, visit: https://help.fishbowlinventory.com/advanced/s/article/MySQL-Update
• Important Notice: If you are upgrading from version 2025.9 or older then this upgrade requires a coordinated installation process. The Fishbowl Server must be updated manually first, followed by client updates. The Fishbowl Client will automatically detect version mismatches and guide users through the update process with a simple "Automatically update your Fishbowl Client" button. If you are upgrading from 2025.11 or later versions this update follows the normal upgrade process supporting auto updating of the server by simply checking for updates.
• Important Notice: Fishbowl 2025.12 and newer versions no longer support MySQL 5.7: If you are still running MySQL 5.7 we recommend migrating to MySQL 8.0 before upgrading to 2026.6. Follow the instructions here to migrate to MySQL 8.0: https://help.fishbowlinventory.com/advanced/s/article/Fishbowl-Advanced-MySQL-Migration
• Important Notice: We are unable to support the Fishbowl Anywhere plugin as part of the 2026.6 (Java 21) release. If you are actively using Fishbowl Anywhere, you should not upgrade beyond the 2025.9 release. We will have Fishbowl Anywhere included in an upcoming release but will provide additional information once available.
• Important Notice: Custom Plugins are not supported in 2025.11 or newer versions. If you utilize any custom Plugins do not upgrade beyond 2025.9. Note that custom integrations are different than custom Plugins. Custom integrations that utilize the REST or Legacy API's will continue to function on 2026.6.
• Important Notice: REST API change for kit items. When you retrieve a sales order through the REST API, kit components are now returned nested inside a "kitItems" list on their parent kit item, rather than as separate top-level line items, and the previous parent-reference field has been removed. If you have an integration that reads sales order kit items through the REST API, review and update it before upgrading to 2026.6.
• New Read-Only Location Groups, giving users view-only access to inventory and orders in specific location groups
• Expanded REST API with sales order creation, transfer order issuing, and nested kit items in sales order responses
• New module option to view and control the next customer account number
• Faster Receiving screen for customers with large numbers of locations
• Security improvements, including a configurable read-only database user and an updated logging component
• Quality and reliability improvements across reports, scheduling, accounting, and purchasing

New Features - 26.6

• Read-Only Location Groups. Administrators can now assign a location group to a user as read-only, letting that user see the data in that location group without being able to change it. This makes it possible to give people visibility into warehouses or branches they don't manage, without risking accidental edits.
  • Read-only access is set per location group in the User module, using a new Read Only checkbox on each assigned location group. A user can have any number of read-only location groups.
  • It applies across the Inventory, Sales Orders, Purchase Orders, Transfer Orders, and Manufacture Orders modules. Records from read-only location groups still appear in the search lists, but creating, editing, adjusting, moving, and similar changes are blocked for those records.
  • A lock icon appears next to records in the search lists that belong to a read-only location group, so users can tell at a glance which records are view-only. For transfer orders, the lock appears only when both the source and destination location groups are read-only.
  • Read-only location groups can still be selected and searched in Advanced Search.
  • User CSV import and export now include read-only location group assignments through a new Read Only Location Groups column.
  • The REST API and legacy API can report which of a user's location groups are read-only, so integrations can enforce the same view-only behavior.
• Customer Module: control the next customer number. Customer numbers are now generated from a stored "next number" counter, the same way order numbers work. A new module option shows the next customer number and lets you change it, giving you direct control over the value assigned to the next new customer.
• Server: configurable read-only database user. Administrators can now set a custom password for the built-in read-only database user, or disable that user entirely, from the Server tab of the Database Settings dialog. Previously this account always used a fixed default password. Existing installations are not disrupted: if no password is set, the current default is kept until you change it.
• Advanced Mobile Plugin: custom email subject and body for shipping. The Mobile Plugin's Shipping Options now include Email Subject and Email Body fields, so the email sent from the mobile app can use a custom subject and message. Existing behavior is unchanged when these fields are left blank.
• REST API: The REST API has been enhanced to include new functionality for accessing API Documentation, Sales Orders, and Transfer Orders.
  • Create a sales order. The REST API can now create a sales order and return the created order, following the same pattern as the existing create and update purchase order calls. Customer defaults such as carrier, payment terms, currency, and addresses are applied automatically from the selected customer, and access rights and location group access are enforced. Kit items and drop ship items are not supported in this first version.
    • POST /api/sales-orders — create a sales order
  • Issue a transfer order. The REST API can now issue a transfer order, moving it to the Issued status. Access rights, location group access, and status rules are enforced.
    • POST /api/transfer-orders/{id}/issue — issue a transfer order
  • Kit items nested in sales order responses. When you retrieve a sales order, kit components are now returned nested under their parent kit item instead of appearing as separate top-level line items, making the response easier to work with for kits. Non-kit items are unaffected. (See the Important Notice above — this changes the response shape for existing integrations.)
    • GET /api/sales-orders/{id} — kit components now appear in a kitItems list on their parent kit item
  • Machine-readable documentation. The REST API documentation can now be retrieved in a machine-readable format, making it easier for developers and AI coding assistants to work with the API programmatically.
    • GET /apidocs.json — the full API documentation as structured data
• Legacy API — save a signature image at receiving. The legacy API can now save a signature or other image against a receipt at receive time, supporting workflows that capture a delivery signature when stock is received. The image is identified by the order (purchase order, sales order, or transfer order) and its location group.

Fixes - 26.6

General

• Resolved: The client update process could fail because it did not recognize a new program directory introduced in a recent release. Client updates now complete successfully.

Accounting

• Resolved: When a drop ship item on a sales order was received in more than one partial receipt, the first receipt exported to QuickBooks Online correctly, but the second receipt reused the same document number and failed on export with a "Duplicate Document" error. Each partial receipt of a drop ship item now exports with its own unique document number.
• Resolved: When an export to QuickBooks Online was rejected with a "Business Validation" error, Fishbowl did not record the detailed error information QuickBooks returned, which made some recurring export errors hard to diagnose. Fishbowl now captures the full QuickBooks error detail and Intuit's transaction reference in the Fishbowl Server Log, helping support identify the cause of failed exports faster.

Purchasing

• Resolved: When reorder levels are set by location group, Auto PO did not recognize demand created by out-of-stock items on transfer orders, even when the relevant "From" location group was selected in the Auto PO wizard. The same demand from a sales order generated a PO correctly. Auto PO now recognizes transfer order demand by location group and creates the expected purchase orders.

Purchasing and Receiving

• Resolved: The Receiving screen opened slowly for customers with a large number of locations, and slowed further each time an item was received and the screen refreshed. Receipt details now load much more efficiently, so the Receiving screen opens significantly faster in large configurations.

Reports

• Resolved: The Asset Valuation by Account report calculated FIFO cost incorrectly when run for a past date, so the value did not match the Inventory module's total cost for that date. The report now calculates historical FIFO cost correctly.
• Resolved: The Packing Slip report in the Standard layout did not show all part tracking details for transfer order items that were split across multiple lots or expiration dates; it combined the lines and showed tracking for only the first. The report now lists tracking details for each line, matching the sales order and By Carton layouts.
• Resolved: On the Packing Slip, the option to show or hide order notes had no effect — the notes always appeared. The show/hide notes option is now honored.
• Resolved: On the Purchase Order report, a vendor address that had a country but no city, state, or ZIP displayed a stray comma. The address now formats correctly when those fields are empty.
• Resolved: The Tracking report failed to run for parts whose part number contains an apostrophe (for example, a foot mark such as 40'). These reports now run correctly.
• Resolved: Running the Batch Sales Order Invoice report with the Show Memos option enabled failed with an error when an order included a memo. The report now generates correctly when memos are shown.
• Resolved: After a recent change, several sort options on the Sales Backorder report — Customer, SO Number, Date to Fulfill, and Quantity Needed — sorted by the wrong column. Each option now sorts by the correct field.
• Resolved: After a 26.5 change, the Sales Order Summary and Sales Order Summary Export reports could not be selected when creating a scheduled task. Both reports can be scheduled again.

Database Updates

• Added "readOnly" column to the userToLg table. This column supports the new Read-Only Location Groups feature, which lets administrators give a user view-only access to a location group. The column defaults to false, so all existing location group assignments remain fully editable after upgrade.

​

MAY 20, 2026 - Advanced 26.5

Download - 26.5

• Download Fishbowl-2026.5.exe for Windows
• Download Fishbowl-2026.5.dmg for macOS (Limited support)
• Download Fishbowl-2026.5.sh for Linux (Documentation only)

Highlights - 26.5

• Important Notice: MySQL 8.0 End of Life - Update Optional for Now - MySQL 8.0 reached End of Life (EOL) in April 2026. Oracle will no longer issue security patches, bug fixes, or official support for MySQL 8.0. While we recommend upgrading to MySQL 8.4 LTS, this update is NOT required at this time. Fishbowl will continue to support MySQL 8.0 until the September 2026 release. You can safely use the standard auto-update process for version 2026.5 - it will maintain your current MySQL 8.0 installation. For detailed upgrade instructions, visit: https://help.fishbowlinventory.com/advanced/s/article/MySQL-Update
• Important Notice: If you are upgrading from version 2025.9 or older then this upgrade requires a coordinated installation process. The Fishbowl Server must be updated manually first, followed by client updates. The Fishbowl Client will automatically detect version mismatches and guide users through the update process with a simple "Automatically update your Fishbowl Client" button. If you are upgrading from 2025.11 or later versions this update follows the normal upgrade process supporting auto updating of the server by simply checking for updates.
• Important Notice: Fishbowl 2025.12 and newer versions no longer support MySQL 5.7: If you are still running MySQL 5.7 we recommend migrating to MySQL 8.0 before upgrading to 2026.5. Follow the instructions here to migrate to MySQL 8.0: https://help.fishbowlinventory.com/advanced/s/article/Fishbowl-Advanced-MySQL-Migration
• Important Notice: We are unable to support the Fishbowl Anywhere plugin as part of the 2026.5 (Java 21) release. If you are actively using Fishbowl Anywhere, you should not upgrade beyond the 2025.9 release. We will have Fishbowl Anywhere included in an upcoming release but will provide additional information once available.
• Important Notice: Custom Plugins are not supported in 2025.11 or newer versions. If you utilize any custom Plugins do not upgrade beyond 2025.9. Note that custom integrations are different than custom Plugins. Custom integrations that utilize the REST or Legacy API's will continue to function on 2026.5.
• Improved client connection performance with reduced server communication overhead
• Fishbowl Payments (Powered by Run Payments) ACH-only merchant support
• New Accounting Module options added
• Quality and reliability improvements across accounting, purchasing, inventory, and receiving modules

New Features - 26.5

• Client connection performance improvements. The Fishbowl client connection has been optimized to reduce the number of server round-trips made during normal operation. Clients now check whether server-side updates are available before requesting them, rather than fetching on every interaction. Users on high-latency or slower network connections should notice improved responsiveness.
• Fishbowl Payments (Powered by Run Payments) ACH-only merchant support. Fishbowl Payments now provides an additional payment option for merchants who process with ACH only that does not require a Credit Card merchant ID (MID). Payment routing is handled transparently by Run Payments based on the merchant's ACH MID entered during initial integration, no separate configuration is required.
• New Accounting Module options for Invoice email address. A new module option, "Always send the customer's default address default email on Invoice," ensures the customer's default contact email is used when exporting invoices to QuickBooks Online and other accounting packages, regardless of which contact placed the order. The option is off by default.
• New Accounting Module options for QuickBooks Canada users: New module options for QuickBooks Desktop Canadian tax rounding control and accounting package email override
• QuickBooks Desktop — Canadian tax rounding module option. A new Accounting Module Option on the QuickBooks tab controls whether Canadian tax rounding mimics QuickBooks Desktop rounding behavior. Customers who generate orders outside Fishbowl (e.g., via ecommerce integrations) can now disable this rounding so totals match between their external system and Fishbowl/QuickBooks Desktop. The option is off by default; existing behavior is preserved.
• New QuickBooks Online — Intuit Enterprise Suite (IES) Accounting integration option. A dedicated Intuit Enterprise Suite integration button is now available in the Accounting module, alongside QuickBooks Online. IES customers can connect using the same authorization flow and sync logic as QuickBooks Online; the new entry clarifies compatibility for customers running on the Intuit Enterprise Suite platform.
• Bi Reports and Dashboards:
  • Dashboard updates and performance improvements. Updated versions of the Sales, Inventory, Purchasing, Production Scheduling, and Company dashboards, plus the Inventory Reorder Watchlist BI report, are now included in the release. The updates add async loading on large datasets, refactor tooltips, and resolve a number of dashboard-specific bugs.
  • Added secure REST API access from Bi reports. A new apiFetchAsync function is available to BI report authors. Reports can now call REST API endpoints under the running user's session, so the server enforces the user's access rights automatically. This replaces the prior pattern of calling the legacy socket API, which bypassed access-rights and field validation.
  • Added ability to drill into Picks from a Bi report. openModule("Picking", pickNum) now opens the Picking module and loads the specified pick, matching the existing behavior for Part, Sales Order, and Vendor. Report authors can link from any report row directly to the relevant pick.
  • BI Reports — drill into Receipts from a Bi report. openModule("Receiving", ...) now supports a compact identifier format ("S122" for SO receipts, "P234" for PO receipts, "T456" for TO receipts) that opens the Receiving module and loads the matching receipt. Report authors can link directly into receipts the same way they link into other records.
• New report module features: Added: Cycle count zero-quantity-change entries (inventory log typeid 68, introduced in 26.4) are now available as a filter option on the Part Activity Report. The filter is unchecked by default to preserve existing report behavior.
• Added: Cycle count zero-quantity-change entries are now available as a filter option on the Part Activity Export Report. The filter is unchecked by default to preserve existing report behavior.
• New API Features:
  • Email Report API — custom subject and message body. The legacy Email Report API now accepts optional EmailSubject and EmailMessageBody fields, allowing the mobile product and integrators to send reports with a customer-appropriate subject and body. The existing scheduled-task email behavior is preserved when these fields are omitted.
  • REST API — The REST API now supports core Transfer Order operations: retrieving a single Transfer Order, searching for Transfer Orders, and managing memos on a Transfer Order. Access rights and location-group access restrictions are enforced.
    • The REST API now supports core Transfer Order operations: retrieving a single Transfer Order, searching for Transfer Orders, and managing Transfer Order memos. Access rights and location-group access restrictions are enforced. New endpoints for creating, retrieving, and updating Transfer Order memos.
    • GET /api/transfer-orders — search Transfer Orders
    • GET /api/transfer-orders/{id} — get a single Transfer Order
    • GET /api/transfer-orders/{id}/memos — list memos on a Transfer Order
    • GET /api/transfer-orders/{id}/memos/{memoId} — get a single memo
    • POST /api/transfer-orders/{id}/memos — create a memo
    • POST /api/transfer-orders/{id}/memos/{memoId} — update a memo
    • DELETE /api/transfer-orders/{id}/memos/{memoId} — delete a memo
  • REST API — Get Pick. A new endpoint loads a Pick by ID and returns the full Pick object with all calculated fields populated, matching the behavior of loading a pick in the client. Access rights and location group restrictions are enforced.
    • GET /api/picks/:id
    • Pick items now include source tag information in the response

Fixes - 26.5

General

• Resolved: After upgrading to version 2026.3, the Products module search began returning both active and inactive products by default. The Active Only filter shown in Advanced Options was not being applied on initial load or when clicking the search button. The default search behavior now correctly limits results to active products.
• Resolved: Creating Sales Orders, Manufacture Orders, or Purchase Orders with a value that contained both an underscore and a dash in the same field could cause duplicate records to appear in search results and break several reports. Orders with mixed underscore and dash characters now save as a single record and search and report correctly.
• Resolved: Server update notifications continued to appear in the client even when the server was configured to never notify or to auto-update. The client now correctly honors the server's update notification setting.

Accounting

• Resolved: When manually applying landed costs, entering an incorrect amount that triggered a validation error and then correcting the value would cause Fishbowl to accumulate both the invalid and corrected amounts rather than replacing the prior entry. This resulted in an overstated landed cost total and a "Please balance your debits and credits" error on accounting export. The correction now replaces the prior entry rather than adding to it.
• Resolved: Exporting a Sales Order to QuickBooks Online failed with an "Amount is not equal to UnitPrice * Qty" error when associated pricing on the order had been changed after the order was issued. The unit price was not being correctly carried through to the export calculation. The export now uses the price stored on the sales order line item.
• Resolved: Exporting a Credit Return Sales Order to Xero failed with a line total mismatch error when stock for the return was received in multiple batches (e.g., two receipts of 5 units for a line originally returned as 10). Fishbowl was not correctly apportioning the unit price across split receipts, producing mismatched totals. The export now correctly calculates line totals for split credit return receipts.

Purchasing

• Resolved: Reconciling a Purchase Order after a void-and-re-receive sequence could fail because the inventory log pivot was using incorrect values, leaving the reconcile unable to complete. The pivot is now built from the correct inventory log entries and reconcile completes successfully.
• Resolved: Auto PO did not include parts that were short when the "No ROPs" option was checked and an unrelated reorder point was defined elsewhere in the database. Short parts are now correctly included regardless of unrelated ROP definitions.
• Resolved: The ship-to address on auto-generated Purchase Orders was not being populated correctly in some configurations. Auto-generated POs now use the correct ship-to address.
• Resolved: Vendor Last Cost on a Purchase Order could be recorded as a negative value in certain credit/return scenarios, causing accounting and cost-reporting issues. Vendor Last Cost is now stored as a non-negative value.

Purchasing and Receiving

• Resolved: When receiving stock against a Purchase Order with a backdated Receive Date, the created inventory tag's dateCreated was stamped with the current system date rather than the backdated date entered by the user. This caused the FIFO pick method to select an incorrect tag for lot-tracked parts. Tag dateCreated now reflects the user-entered Receive Date.

Manufacturing

• Resolved: Auto MO did not create a manufacture order when no reorder point was defined for the part, even when the "Include No ROPs" option was checked. Auto MO now correctly creates manufacture orders for parts without reorder points when that option is enabled.

Materials

• Resolved: The Replenish Wizard in the Transfer Order module did add parts to a transfer order when no reorder point was defined for the part, even when the "Include No ROPs" option was checked. The wizard now includes parts regardless of reorder point configuration when when the "Include No ROPs" option is checked.

Reports

• Resolved: The Sales Order Summary and Sales Order Summary Export reports did not differentiate between products that share the same name across different branches of a product tree, causing items from unrelated branches to appear together in the filtered results. The product tree filter now correctly scopes results to the selected branch.
• Resolved: The Sales Order Summary Export report could pull in items incorrectly when filtering by certain date or status combinations, producing extra or unrelated line items. Filtering and item selection now match the configured filters.
• Resolved: The Sales Order Summary Report returned zero results when filtered by a single day combined with the "SO item date fulfilled" filter, even when fulfillments existed for that day. The report now correctly returns matching results for single-day fulfillment filters.
• Resolved: The Work Order Traveler report was not displaying page numbers, making multi-page travelers difficult to track on the shop floor. Page numbers are now rendered on all pages of the report.
• Resolved: The Sales Backorder report did not render correctly in certain scenarios, producing incomplete or incorrect output. The report now generates as expected.
• Resolved: Selecting a value in the Carrier filter on the Sales Order Summary report caused the entire report to return blank. The Carrier filter now correctly narrows results to the selected carrier.
• Resolved: The Packing Slip report appended a time stamp (e.g., "2025-08-29 00:00:00") when displaying custom date fields, even though the client displays them as date-only. Custom date fields now render without the time component.
• Resolved: The Shipping Invoice report's Field Titles area exposed two "FOB Point" labels, and editing the second actually changed the Sales Person title. The second entry is now correctly labeled "Sales Person".
• Resolved: The Reverse Lot History report failed to complete and would load indefinitely on databases that had been upgraded from version 24.7 or earlier. The report now generates as expected.
• Resolved: The Location Barcode and Location Barcode One Off reports printed barcodes shifted to the left of center on the label rather than centered. Barcodes are now centered correctly on the label.
• Resolved: In international databases, toggling off the "Show Cost" option on the Purchase Order Summary report hid the column header but left the cost values and removed the totals. The toggle now hides both the column data and the totals consistently with US databases.

Calendar

• Resolved: On Australian and other non-US system locales, the Calendar module did not display scheduled events or orders in the first row of dates, while events on later rows displayed correctly. Calendar events now render in all rows regardless of locale.

Database Updates

• Added "priceLocked" column to the soitem table. Supports the associated-pricing fix that resolves the QuickBooks Online export error "Amount is not equal to UnitPrice * Qty" when an associated price is changed after a sales order is issued. The new column defaults to false; on upgrade, existing Associated Price line items on Issued (or later) sales orders are backfilled to true so that already-issued orders continue to export correctly.

​

APR 14, 2026 - Advanced 26.4

Download - 26.4

• Download Fishbowl-2026.4.exe for Windows
• Download Fishbowl-2026.4.dmg for macOS (Limited support)
• Download Fishbowl-2026.4.sh for Linux (Documentation only)

Highlights - 26.4

• Important Notice: MySQL 8.0 End of Life - Update Optional for Now - MySQL 8.0 will reach End of Life (EOL) in April 2026. Oracle will no longer issue security patches, bug fixes, or official support for MySQL 8.0. While we recommend upgrading to MySQL 8.4 LTS, this update is NOT required at this time. Fishbowl will continue to support MySQL 8.0 until the September 2026 release. You can safely use the standard auto-update process for version 2026.4 - it will maintain your current MySQL 8.0 installation. For detailed upgrade instructions, visit: https://help.fishbowlinventory.com/advanced/s/article/MySQL-Update
• Important Notice: If you are upgrading from version 2025.9 or older then this upgrade requires a coordinated installation process. The Fishbowl Server must be updated manually first, followed by client updates. The Fishbowl Client will automatically detect version mismatches and guide users through the update process with a simple "Automatically update your Fishbowl Client" button. If you are upgrading from 2025.11 or later versions this update follows the normal upgrade process supporting auto updating of the server by simply checking for updates.
• Important Notice: Fishbowl 2025.12 and newer versions no longer support MySQL 5.7: If you are still running MySQL 5.7 we recommend migrating to MySQL 8.0 before upgrading to 2026.4. Follow the instructions here to migrate to MySQL 8.0: https://help.fishbowlinventory.com/advanced/s/article/Fishbowl-Advanced-MySQL-Migration
• Important Notice: We are unable to support the Fishbowl Anywhere plugin as part of the 2026.4 (Java 21) release. If you are actively using Fishbowl Anywhere, you should not upgrade beyond the 2025.9 release. We will have Fishbowl Anywhere included in an upcoming release but will provide additional information once available.
• Important Notice: Custom Plugins are not supported in 2025.11 or newer versions. If you utilize any custom Plugins do not upgrade beyond 2025.9. Note that custom integrations are different than custom Plugins. Custom integrations that utilize the REST or Legacy API's will continue to function on 2026.4.
• New user rights added for individual Import/Export operations
• Improved user security with automatic password expiration and CSV-based temporary password assignment
• Updated USPS address validation integration
• Quality and reliability improvements across accounting, purchasing, inventory, and receiving modules

New Features - 26.4

• Granular Import/Export access rights. A new set of 114 individual access rights has been added — one for each import and export operation — giving administrators the ability to allow or deny specific import and export operations per user group. The existing Import/Export-View access right continues to control visibility of the Import/Export menu item. All existing user groups are automatically granted the new rights via migration to maintain backward compatibility.
• Inventory: Require Notes on Quantity Adjustments and Inventory Moves. Two new module options have been added to the Inventory module that allow administrators to require users to enter a note when adjusting inventory quantities or moving inventory between locations. Both options are off by default. When enabled, users must provide a note before completing the action, creating a documented record for each inventory change.
• Automatic user password expiration. A new option in the Users module allows administrators to enable automatic password expiration. When enabled, a configurable expiration period (in days, defaulting to 30) is set, and users are prompted to reset their password at their next login after it expires. This improves password security for organizations that require periodic credential rotation.
• Temporary password assignment via users.csv import. A new optional "Password" column has been added to the users.csv import format, allowing administrators to assign a temporary password when creating new users via CSV import. This field applies to new user creation only and cannot be used to reset passwords for existing users. This action is limited to the admin user.
• USPS Address Validation update. The USPS address validation integration has been updated to work with the current USPS API. This feature, which allows users to validate shipping addresses on orders directly within Fishbowl, was previously non-functional due to changes made by USPS.
• REST API: Part tracking data on GET Shipment. The GET Shipment endpoint now returns part tracking information on ship items when tracking data is present, matching the tracking details visible when viewing a shipment in the Fishbowl client.
  • GET /api/shipments/:id - Now includes a tracking object on each shipItem when applicable.

Fixes - 26.4

General

• Resolved: Cost and price fields, line item totals, and order totals on Purchase Orders and Sales Orders now display correctly when the home currency is set to an Arabic currency (e.g., Kuwaiti Dinar, Iraqi Dinar, Omani Rial, Bahraini Dinar). Previously, values displayed using Eastern Arabic numerals instead of standard numerals, and order totals did not appear at all.
• Resolved: Cycle counts that result in no quantity change (where the counted quantity exactly matches the system quantity) are now saved as records. Previously, zero-change cycle counts were discarded with no record retained, making it impossible to report on when an item was last counted or confirm its accuracy at that point in time.
• Resolved: Transfer Order CSV imports now enforce UOM compliance for each line item. Previously, importing a Transfer Order via CSV allowed any unit of measure to be assigned, regardless of whether it was valid for the part, which could corrupt order, pick, and inventory records.
• Resolved: Filtering when exporting via the CSV export wizard now works correctly. Previously, applying a filter in the export wizard would result in a blank error and no file was produced. Exporting without applying a filter was unaffected.

Purchasing and Receiving

• Resolved: Outsourced Purchase Orders can now be reconciled even when one or more receivable line items do not yet have cost history. Previously, the absence of a cost history for any receivable line would prevent the entire receipt from being reconciled.
• Resolved: Purchase Order CSV imports now preserve unit cost values with more than two decimal places. Previously, line item unit costs were incorrectly rounded to two decimal places during import, introduced in version 2026.1.
• Resolved: The Receiving Data CSV import now assigns the correct billed unit cost when a single order line is received across multiple CSV rows. Previously, splitting one line into multiple receive lines resulted in each row receiving a different, incorrect calculated cost (e.g., $10.00, $2.00, $2.50, $3.33) instead of the correct value.

Accounting

• Resolved: QuickBooks Desktop exports now correctly handle tax rounding when Canadian dollars are used as the home currency. Previously, the exported tax amount was rounded up by $0.01, causing a discrepancy between the payment recorded in Fishbowl and the invoice balance in QBD that required manual correction on each affected invoice.
• Resolved: Credit returns on Sales Order lines for non-inventory parts now correctly reverse the COGS entry with a negative cost value. Previously, when duplicating a Sales Order and selecting "Credit Return," non-inventory line items retained a positive cost rather than posting a negative COGS, overstating cost of goods sold.
• Resolved: When duplicating a Sales Order as a Credit Return, tax line items calculated by TaxJar and QuickBooks Online Automated Sales Tax are now correctly converted to negative amounts. Previously, these tax line items remained positive on the credit return, resulting in incorrect tax totals instead of properly reversing the original tax charges

​

MAR 23, 2026 - Advanced 26.3

Download - 26.3

• Download Fishbowl-2026.3.exe for Windows
• Download Fishbowl-2026.3.dmg for macOS (Limited support)
• Download Fishbowl-2026.3.sh for Linux (Documentation only)

Highlights - 26.3

• Important Notice: MySQL 8.0 End of Life - Update Optional for Now - MySQL 8.0 will reach End of Life (EOL) in April 2026. After this date, Oracle will no longer issue security patches, bug fixes, or official support for MySQL 8.0. While we recommend upgrading to MySQL 8.4 LTS before the EOL date, this update is NOT required at this time. Fishbowl will continue to support MySQL 8.0 until the September 2026 release. You can safely use the standard auto-update process for version 2026.3 - it will maintain your current MySQL 8.0 installation. If you wish to upgrade to MySQL 8.4 now, see the "MySQL 8.4 upgrade" feature description below. For detailed upgrade instructions, visit: https://help.fishbowlinventory.com/advanced/s/article/MySQL-Update
• Important Notice: If you are upgrading from version 2025.9 or older then this upgrade requires a coordinated installation process. The Fishbowl Server must be updated manually first, followed by client updates. The Fishbowl Client will automatically detect version mismatches and guide users through the update process with a simple "Automatically update your Fishbowl Client" button. If you are upgrading from 2025.11 or later versions this update follows the normal upgrade process supporting auto updating of the server by simply checking for updates.
• Important Notice: Fishbowl 2025.12 and newer versions no longer support MySQL 5.7: If you are still running MySQL 5.7 we recommend migrating to MySQL 8.0 before upgrading to 2026.3. Follow the instructions here to migrate to MySQL 8.0: https://help.fishbowlinventory.com/advanced/s/article/Fishbowl-Advanced-MySQL-Migration
• Important Notice: We are unable to support the Fishbowl Anywhere plugin as part of the 2026.3 (Java 21) release. If you are actively using Fishbowl Anywhere, you should not upgrade beyond the 2025.9 release. We will have Fishbowl Anywhere included in an upcoming release but will provide additional information once available.
• Important Notice: Custom Plugins are not supported in 2025.11 or newer versions. If you utilize any custom Plugins do not upgrade beyond 2025.9. Note that custom integrations are different than custom Plugins. Custom integrations that utilize the REST or Legacy API's will continue to function on 2026.3.
• Important Notice: Previously the Ebay plugin was not compatible with Java 21. This issue has been resolve and it is now fully functional.
• Improved MySQL 8.4 update process
• New Bi Report
• Enhanced REST API with shipment and payment search functionality
• Improved Sales Order flexibility with kit item type changes
• Quality and reliability improvements across multiple modules

New Features - 26.3

• MySQL 8.4 upgrade option (Optional). For customers who wish to upgrade to MySQL 8.4 LTS ahead of the September 2026 requirement, the Fishbowl installer now includes automatic MySQL 8.4 upgrade capability. This upgrade is completely optional for the 2026.3 release. Here's how it works:
  • Windows users with Fishbowl-installed MySQL 8.0: Simply run the full Fishbowl installer (not the auto-update) over your existing installation. The installer will automatically detect and upgrade MySQL 8.0 to MySQL 8.4.
  • Windows users with manually-installed MySQL: You will need to manually upgrade MySQL 8.4 first, then install Fishbowl Advanced 2026.3. The installer will provide instructions if it detects manually-installed MySQL 8.0.
  • MacOS and Linux users: You will need to manually upgrade MySQL to 8.4 first, then install Fishbowl Advanced 2026.3. The installer will provide upgrade prompts and instructions.
  • If you choose to stay on MySQL 8.0: Simply use the standard auto-update process for Fishbowl 2026.3. Your MySQL 8.0 installation will remain unchanged and fully supported. For detailed MySQL upgrade instructions, visit: https://help.fishbowlinventory.com/advanced/s/article/MySQL-Update
• Fishbowl Payments (Powered by Run Payments). The integration has been updated to continue to help merchants save on credit card processing fees. When you process a payment, Fishbowl automatically sends detailed transaction information to the payment processor, including:
  • Order details like customer PO number, order date, and shipping information
  • Individual line items with product descriptions, quantities, prices, and product codes
  • Accurate tax and shipping amounts By sending this extra information, Fishbowl Payments helps you qualify for the lowest processing fees available for business-to-business transactions. The system automatically handles sending the additional data - you don't need to do anything different when taking payments.
• Inventory Reorder Watchlist BI Report. A new standalone Inventory Reorder Watchlist BI Report has been added to the BI Reports module, providing detailed visibility into parts approaching or below reorder points with drill-down functionality to investigate specific part details, supplier information, and inventory levels across locations to help prevent stockouts and optimize inventory management. Click here to learn more.
• Sales Order kit item type flexibility. A new Sales Order module option "Allow changing kit item types" enables users to change the item type (Sale, Credit Return, Drop Ship) for kit items that have been added to a Sales Order. This option is unchecked by default to maintain backward compatibility. When enabled, users can modify kit item types both inline and in the item edit screen, providing greater flexibility for managing inventory status changes.
• Enhanced auto-update options. A new "Never notify or update automatically" option has been added to the Server Administration page auto-update settings. When selected, Fishbowl will neither notify users about new updates nor automatically update the software, providing complete control over the update process for organizations with strict change management policies.
• REST API shipment management. The REST API now includes new shipment functionality:
  • GET /api/shipments/:id - Retrieves details of a specific shipment by ID with location group access validation
  • POST /api/shipments/:id/pack - Changes shipment status from Entered to Packed, with validation to prevent packing already packed or shipped orders
  • Search functionality - Returns paginated lists of shipments based on filter criteria with proper access rights checking
• REST API payment search. The REST API now supports searching for payments with the ability to return paginated lists of payments based on filter criteria. Documentation has been added to the Payments section of the REST API docs with proper access rights checking.
• REST API product search. The REST API now supports searching for products with the ability to return paginated lists of products based on filter criteria. Documentation has been added to the Products section of the REST API docs with proper access rights checking.
• Updated Remote Assist link for AU databases. Australian database users accessing Help > Remote Assist are now redirected to the correct remote support page (https://apac.fishbowlinventory.com/s/remote-assist/) instead of the booking support page.

Fixes - 26.3

Sales

• Resolved: Kits containing both standard type kit items and variable quantity type kit items can now be added to Sales Orders with the variable quantity item set to 0, as long as at least one standard kit item has a quantity greater than 0. Previously, the system incorrectly displayed an error stating "Invalid Qty: Kit must have at least one item in the kit" even when standard items were present.
• Resolved: Sales Order totals now display correctly when the home currency is UAE Dirham or other non-US currencies. Previously, total values at the bottom of orders would not display, though line item unit prices displayed correctly.

Payments

• Resolved: Fishbowl Payments (Powered by Run Payments), The payment window has been resized to ensure all three payment options (Card Present, Manually Entered (Send to Payment Terminal), and Manually Entered) are visible when connected to a payment terminal, eliminating the need to manually stretch the window.
• Resolved: CloverConnect card processing via terminal continues to function properly after removal of outdated port numbers from integration URLs.

Manufacturing

• Resolved: BOMs with notes can now be properly deleted from partially fulfilled Manufacturing Orders without requiring Knowledge Engineer or Support assistance. Previously, attempting to delete BOMs with notes would generate a null error.

Purchase

• Resolved: When the "Update vendor cost on issue" Purchase Order module option is unchecked, vendor costs are no longer incorrectly updated when issuing orders. Additionally, when multi-currency is enabled and vendor costs are updated, the calculations are now accurate. Previously, changing the currency conversion rate on a Purchase Order could incorrectly update vendor last costs with wrong values for both home and foreign currencies.
• Resolved: Purchase Order totals now display correctly when the home currency is UAE Dirham or other non-US currencies. Previously, total values at the bottom of orders would not display, though line item unit prices displayed correctly.

Accounting

• Resolved: QuickBooks Online can again create new currencies when exporting from Fishbowl if they don't already exist in QuickBooks Online. Previously, exports would fail with an "Operation could not find resource for entity companycurrency is not supported" error when a currency existed in Fishbowl but not in QuickBooks Online.
• Resolved: Xero exports now properly handle part cost journal entries when class tracking (categories) is enabled. Previously, exporting part cost changes would fail with a null error because journal entries did not have a class/category assigned and the system was incorrectly validating these entries.

​

FEB 19, 2026 - Advanced 26.2

Download - 26.2

• Download Fishbowl-2026.2.exe for Windows
• Download Fishbowl-2026.2.dmg for macOS (Limited support)
• Download Fishbowl-2026.2.sh for Linux (Documentation only)

Highlights - 26.2

• Important Notice: If you are upgrading from version 2025.9 or older then this upgrade requires a coordinated installation process. The Fishbowl Server must be updated manually first, followed by client updates. The Fishbowl Client will automatically detect version mismatches and guide users through the update process with a simple "Automatically update your Fishbowl Client" button. If you are upgrading from 2025.11 or later versions this update follows the normal upgrade process supporting auto updating of the server by simply checking for updates.
• Important Notice: Fishbowl 2025.12 and newer versions no longer support MySQL 5.7: If you are still running MySQL 5.7 we recommend migrating to MySQL 8.0 before upgrading to 2026.2. Follow the instructions here to migrate to MySQL 8.0: https://help.fishbowlinventory.com/advanced/s/article/Fishbowl-Advanced-MySQL-Migration
• Important Notice: We are unable to support the Fishbowl Anywhere plugin as part of the 2026.2 (Java 21) release. If you are actively using Fishbowl Anywhere, you should not upgrade beyond the 2025.9 release. We will have Fishbowl Anywhere included in an upcoming release but will provide additional information once available.
• Important Notice: Custom Plugins are not supported in 2025.11 or newer versions. If you utilize any custom Plugins do not upgrade beyond 2025.9. Note that custom integrations are different than custom Plugins. Custom integrations that utilize the REST or Legacy API's will continue to function on 2026.2.New and updated Business Intelligence Dashboards with enhanced data visualization
• Expanded Server Administration capabilities for remote management
• Enhanced REST API for improved performance
• Outsourced Purchase Orders now support parts with tracking
• Quality and reliability improvements across multiple modules

New Features - 26.2

• New Business Intelligence Dashboards. Two new and three updated professionally-designed BI Dashboard reports are now included by default both as Dashboards and in the BI Reports module, providing powerful data visualization and decision-making tools:
  • New Production Scheduling Module - Manufacturing order planning and scheduling optimization featuring an interactive calendar view where manufacturing orders can be moved and rescheduled by dragging and dropping, plus drill-down functionality for detailed work order analysis. Click here to learn more.
  • New Company Dashboard - High-level company performance overview with drill-down capabilities across multiple business areas for deeper insights. Click here to learn more.
  • Updated Sales Dashboard - Comprehensive sales performance metrics and trends with drill-down functionality to explore detailed order and customer information. Click here to learn more.
  • Updated Purchasing Dashboard - Purchase order tracking and vendor performance analysis with drill-down capabilities to view detailed purchase order and vendor data. Click here to learn more.
  • Updated Inventory Dashboard - Real-time inventory reorder watchlist and stock management with drill-down options to investigate part-level inventory details. Click here to learn more.
  • Note: These new BI Dashboard reports must be granted as user rights in the User Group module for users to view them. Each Dashboard has its own unique user right under the access tab and the Bi Reports tab. Administrators should review and assign appropriate access rights to users who need access to these dashboards.
  • Note: If you prefer the previous dashboard experience, you can easily switch back to the Classic Dashboards through the Dashboard customization settings in the Settings module. See the Dashboard customization settings feature description below for more information.
• Dashboard customization settings. A new "Dashboards" tab has been added to the Settings module, allowing administrators to customize the default dashboard experience for each dashboard module. Users can select between Classic Dashboards (maintaining the appearance of the Dashboards from version 26.1) or any available BI Report. This means that Bi Reports can be edited or created in the Bi Editor and then selected as a default for the following modules (Click here to learn more):
  • Inventory Dashboard
  • Sales Dashboard
  • Purchasing Dashboard
  • Manufacturing Dashboard
  • Production Scheduling Dashboard
  • Company Dashboard
• Dashboard module rename. The existing Dashboard module has been renamed to "User Dashboard" to distinguish it from the new Company Dashboard in the General module group. The User Dashboard can be customized by each individual user and the Company Dashboard is a company wide dashboard.
• New Server Administration Module. The Server Administration module now includes powerful remote management capabilities previously only available when directly logged on to the Fishbowl Server(Click here to learn more):
  • Active Connections management - View all connected users with their name, last activity, and client type. Administrators can refresh the user list, log off selected users, and send messages to connected users directly from this module in the client.
  • Connection settings - Configure Client Inactivity Timeout and enforce single-login restrictions (users can only be logged in once).
  • Server restart capability - Restart the Fishbowl Server directly from the Administration module with configurable delay periods to give connected users adequate warning. This feature requires a new "Restart Fishbowl Server" user right (granted to the admin user only by default).
• Outsourced Purchase Orders with part tracking. Parts with tracking (including Lot Numbers, Expiration Dates, Serial Numbers, and custom tracking types) can now be used on outsourced Purchase Orders. This enables manufacturers who outsource production operations to maintain full traceability throughout their outsourced manufacturing process without being forced to remove tracking from parts.
• Automatic backup retention management. Scheduled database backup tasks now support automatic deletion of old backup files. Administrators can configure a retention period (in days) to automatically clean up backups older than the specified threshold, preventing disk space issues without manual maintenance. Setting the value to 0 disables automatic deletion. Create a new or edit your existing Database Backup scheduled task to enable this feature. Default setting is set to 0. Click here to learn more.
• Enhanced Fishbowl Payments (Powered by Run Payments) card entry. When connected to a Run Payments card processing terminal, users now have more flexibility for card not present transactions. A new "Manually Entered" option allows credit card information to be entered directly into the client through the Run Payments iFrame for faster processing, while the existing functionality has been renamed to "Manually Entered (Send to Payment Terminal)" for sending payment processing to the card terminal. Card Present remains the default option.
• REST API memo endpoints. The REST API now supports full memo management for Sales Orders, Parts, and Products with the following new endpoints:
  • getMemoList - Retrieves a list of all memos associated with a specific Sales Order, Part, or Product
  • getMemo - Retrieves details of a single specific memo by its ID
  • deleteMemo - Removes a memo from a Sales Order, Part, or Product
  • updateMemo - Modifies the content of an existing memo
  • createMemo - Adds a new memo to a Sales Order, Part, or Product

Fixes - 26.2

Fishbowl Payments (Powered by Run Payments)

• Resolved: QuickBooks Online automated sales tax is now properly included in Run Payment Links. Previously, QBO estimated tax amounts appeared correctly on the Sales Order and in the manual payment screen but were not included in the payment link total.

REST API

• Resolved: REST API performance and efficiency have been significantly improved for customers with large amounts of orders, customers, and parts. These improvements resolve Java heap space errors previously experienced by customers with larger datasets. The following enhancements have been implemented:
  • Replaced HttpURLConnection with the new HttpClient
  • Enabled HTTP/2 support
  • Removed JSON size limit for API requests
  • Improved file download memory efficiency
  • Eliminated unnecessary base64 encoding to decrease request sizes
  • Avoided double serialization
• Resolved: REST API documentation for search endpoints now correctly indicates that all search filters are optional for Inventory, Location Group, Manufacture Order, Part, Purchase Order, UOM, User, and Vendor.
• Resolved: REST API documentation links have been updated from the old wiki URLs to the new help article URLs. All "Related Guide" links now correctly redirect to the appropriate pages on the help site.
• Resolved: The /api/products/:id/best-price endpoint documentation now correctly indicates that customerid is a required field, and optional parameters (uomId, date, and includePricingRules) are properly marked as optional.

Database Updates

• Added "deleteBackupOlderThan" column to the fbschedule table. This new column enables the new automatic deletion of backups feature in the schedule module.

​

JAN 15, 2026 - Advanced 26.1

Download - 26.1

• Download Fishbowl-2026.1.exe for Windows
• Download Fishbowl-2026.1.dmg for macOS (Limited support)
• Download Fishbowl-2026.1.sh for Linux (Documentation only)

Highlights - 26.1

• Important Notice: If you are upgrading from version 2025.9 or older then this upgrade requires a coordinated installation process. The Fishbowl Server must be updated manually first, followed by client updates. The Fishbowl Client will automatically detect version mismatches and guide users through the update process with a simple "Automatically update your Fishbowl Client" button. If you are upgrading from 2025.11 or later versions this update follows the normal upgrade process supporting auto updating of the server by simply checking for updates.
• Important Notice: Fishbowl 2025.12 and newer versions no longer support MySQL 5.7: If you are still running MySQL 5.7 we recommend migrating to MySQL 8.0 before upgrading to 2026.1. Follow the instructions here to migrate to MySQL 8.0: https://help.fishbowlinventory.com/advanced/s/article/Fishbowl-Advanced-MySQL-Migration
• Important Notice: We are unable to support the Fishbowl Anywhere plugin as part of the 2026.1 (Java 21) release. If you are actively using Fishbowl Anywhere, you should not upgrade beyond the 2025.9 release. We will have Fishbowl Anywhere included in an upcoming release but will provide additional information once available.
• Important Notice: Custom Plugins are not supported in 2025.11 or newer versions. If you utilize any custom Plugins do not upgrade beyond 2025.9. Note that custom integrations are different than custom Plugins. Custom integrations that utilize the REST or Legacy API's will continue to function on 2026.1.
• Enhanced Fishbowl Commerce integration with channel-specific status mapping
• Run Payments ACH-only integration option added
• Quality and reliability improvements across multiple modules

New Features - 26.1

• Fishbowl Commerce channel-specific status mapping. A custom scheduled script is now available that allows operations managers to override the status import behavior for specific e-commerce channels. This enables different status mappings depending on the channel, preventing the need for additional processing of orders. For example, if more than one channels orders are in shipped status in Fishbowl Commerce and is mapped to come in as issued to Fishbowl Advanced, the script can take one of those channels orders an fulfill them. The script takes two parameters: desired status ID and the channel name and runs via the schedule module to automatically perform the steps necessary for additional order processing. If you want to enable this feature reach out to our Support Department at 800-774-7085 ext 3.
• Fishbowl Payments ACH-only support. The Fishbowl Payments integration now supports customers who only have an ACH Merchant ID (MID). When the service provider is integrated using only the ACH MID, only ACH payments are processed through Fishbowl Payments and only an ACH option appears on generated payment links.

Fixes - 26.1

General

• Resolved: Users can now properly revoke access to the MyFishbowl Module through user access rights. Previously, all users could view the MyFishbowl Module regardless of access rights settings.
• Resolved: The Part Activity Report tooltip for the Group By option now correctly describes the grouping functionality rather than showing the same tooltip as the Order By option.

Sales

• Resolved: We have removed the Module Option for "Fulfill Flat Rate discounts with preceding line items on ship" from the Sales Order Module Options. This option will be included in a future release pending some additional development changes.

Purchasing and Receiving

• Resolved: International customers using currencies with commas as decimal separators and vendor part number associations can now be added to Purchase Orders when multi-currency is enabled. Previously, these parts could not be added to a Purchase Order and the cost could not be changed in the vendor's home currency.
• Resolved: Purchase Order CSV imports now enforce the same cost restrictions as the Fishbowl Client. Credit return type line items with positive costs are imported as negative costs, and purchase type line items with negative costs are imported as positive costs, preventing incorrect accounting exports.

Materials

• Resolved: The "All Locations" option in the Part Module's MRP feature no longer assigns reorder points to inactive location groups. Inactive location groups are now excluded from MRP calculations.

Calendar

• Resolved: The Calendar module in international databases now works correctly in all view modes (1 Day, 5 Day, and 7 Day views). Previously, orders would not display in 1 Day and 5 Day views, and selecting 7 Day view would cause an error that prevented other modules from loading requiring a restart of the Fishbowl Client to fix.

Advanced Search

• Resolved: The Advanced Search popup window now properly displays cancel and search buttons at the bottom without requiring window resizing, specifically when many custom fields are present. The dialog now allows scrolling to accommodate a large numbers of custom fields in Part, Product, Customer, and Vendor modules.

Scheduled Tasks

• Resolved: Scheduled tasks no longer remain stuck in queue requiring a server restart to run. Thread management issues related to the schedule module have been addressed, and timeouts have been added to Run Payments API requests to prevent tasks from hanging indefinitely.

Plugins

• The Ebay plugin has been update to be compatible with Java 21 and is not fully functional