All releases

Release v2.6.0

Inventoros 2.6.0

This release adds exchange rates for purchase orders in a supplier's currency, tax rates per line on sales and purchase orders, and Mark as Sent for purchase orders placed outside Inventoros. It can be installed with Composer, and it includes a large set of security fixes, several of which change behaviour. Read the Upgrade section before updating. It includes every change since 2.5.0; the full list is in the changelog.

Exchange rates for purchase orders

  • A purchase order in a currency other than the organization's stores the exchange rate for its order date and its totals in the organization's currency. The rate can change while the order is a draft and locks when it is sent or marked as sent; later rate updates never change it.
  • Receiving books costs in the organization's currency at the locked rate. The PDF, REST, GraphQL, MCP and the report builder show both currencies.
  • Settings > Exchange rates chooses the provider (Frankfurter, the ECB reference rates, by default, or manual rates), an optional fallback, the stale limit, the currencies to keep and automatic synchronization, and shows the sync status. exchange-rates:sync runs hourly from the scheduler.
  • Two new permissions: manage_exchange_rates and override_purchase_order_exchange_rate (enter or confirm a rate by hand).
  • Plugins can add providers with register_exchange_rate_provider().

See exchange rates. (#420, #424, #450)

Tax per line

  • Products have a tax rate, and the product form a "Selling price incl. tax" field. The selling price itself stays net.
  • Sales order and purchase order lines have a tax rate, pre-filled from the product. The server computes each line's tax: an order discount is shared across the lines before tax, and tax is rounded once per rate, so the tax per rate matches what a VAT summary shows. The order tax is the sum of the line taxes.
  • Order and purchase order pages, the invoice and purchase order PDFs and the supplier email show net, tax and gross per line and the tax per rate.
  • REST, GraphQL and MCP accept tax_rate per line and return tax_breakdown per order. The product export adds Tax Rate and Price Incl. Tax columns, and the import reads tax_rate.
  • Orders without line rates keep their order-level tax exactly as before, and API clients that send only tax amounts get the same totals.

(#416, #425, #426)

Purchasing

  • Mark as Sent. A draft purchase order can be marked as sent without emailing anyone, for orders placed by phone or on the supplier's website, and then received as usual. The same checks as Send to Supplier apply, including approval. Also available as POST /api/v1/purchase-orders/{id}/mark-sent and the MCP tool mark_purchase_order_sent. (#423)
  • Supplier costs keep their currency. Each supplier cost on a product records its own currency, defaulting to the supplier's, and changing a supplier's currency no longer re-denominates costs already entered. The product page shows supplier costs and price history in their own currency, with the amount in the organization's currency underneath at a stored rate. A new purchase order line only takes a cost or price that is in the purchase order's currency; otherwise it starts at 0. (#438)
  • Currency defaults. A supplier without a currency bills in the organization's currency, and the New Product form starts on the organization's currency instead of USD. (#421, #441)
  • Approval and exchange rates. With purchase order approvals on and a threshold set, the threshold is compared in the organization's currency. A purchase order in another currency with no rate recorded, or with a rate entered by hand, needs approval. (#447)

Search

Search ignores apostrophes and quotes, straight or curly, in both the search and the stored text: "Players Handbook", "Player's Handbook" and "Player’s Handbook" all find each other. Every other character, including %, _, hyphens, slashes and dots, is matched literally, so % and _ are no longer wildcards. A number sent as a JSON search term to the API or MCP works again. (#435, #440, #448)

Install with Composer

Inventoros is on Packagist as inventoros/inventoros:

composer create-project inventoros/inventoros inventoros --no-dev

Composer copies .env, generates APP_KEY and prints the remaining steps: build the frontend, then finish in the web installer. 2.6.0 is the first release with this post-create step; older tags still carry the Laravel skeleton's. See Install with Composer. (#427)

Interface

  • Sales orders, purchase orders and stock transfers use one searchable product picker on both the create and the edit pages. It searches product and variant names, SKUs and barcodes and works with the keyboard. Transfers show the stock available at the chosen source location. (#413, #444)
  • Long forms (products, orders, purchase orders, transfers, audits) keep Save and Cancel in reach and link a validation summary to the fields. (#398, #414)
  • The dashboard replenishment panel shows minimum-stock rulers, and Review stock is a clearer decision sheet. Reports have their own pictograms. (#401, #402, #403)
  • Empty lists tell "nothing yet" from "no matches" and offer Clear filters. Settings, import/export, approvals and plugin pages use accessible section tabs. (#404, #405)
  • Receiving and warehouse stock are usable on phones, work order creation explains how to set up an assembly, and translated labels damaged by an encoding step are restored. (#406, #410, #411, #415)

Security

Accounts and sign-in:

  • Two-factor sessions are bound to the user who passed the challenge, and the session id is renewed after the challenge and after enabling two-factor. (#354, #412)
  • Two-factor codes work only once, and 5 wrong codes in 15 minutes lock an account's authenticator codes for the rest of that window. Recovery codes still work during a lockout. (#371)
  • Changing your email, enabling two-factor and creating an API token in Settings ask for your current password. (#391)
  • An emailed password reset, or an administrator setting a user's password, revokes that user's API tokens. (#387)
  • The forgot-password page and the API login no longer reveal whether a staff account exists. (#386)
  • The web installer of a new install asks for a one-time setup token. (#385)
  • A sole administrator cannot delete their own account; fixture seeders with known passwords refuse to run outside local and testing. (#357, #412)

Permissions and data access:

  • Scoped API tokens are limited by their abilities in role assignment, user management, permission sets and report data sources, not only at the route. (#360)
  • Global search, the settings and role pages, payment fields, invoices, the customer lookup and the product and order exports only show data the user's permissions cover. (#352, #358, #373, #377)
  • Role deletion respects the delegated manager's permissions, and built-in roles can no longer be matched by an organization's own role. (#389, #392)
  • The product import needs product permissions, and its stock changes follow manage_stock, approvals and warehouse assignments. XLSX uploads have decompression limits. (#376, #383)
  • Warehouse assignments now apply to work orders, transfer completion, stock reservations, cycle count schedules, order approval, product opening stock and location moves. A restricted user can no longer widen their access by removing their last warehouse assignment. (#359, #361, #363, #366, #367, #368, #370, #395)
  • SKU generation and GraphQL validation only see the caller's organization, and GraphQL sorting is limited to the documented columns. (#364, #378, #390)

Orders, approvals and stock:

  • Order statuses only move forward on every surface. (#353)
  • Editing an approved order's terms sends it back for approval, and the user who changed it cannot decide it. (#355, #388)
  • With stock adjustment approvals on, stock audits require variance review and a new variant's opening stock follows the approval rules and needs manage_stock. (#351, #375)
  • Stock audits measure variances when each line is counted, so movements during a long count are not booked twice. (#408)
  • Voiding a refund cannot silently overpay an order, and purchase order cancel, edit and send re-check the order's state under a lock. (#362, #365, #372)

APIs and outbound requests:

  • GraphQL mutations over GET are refused, a mutation request holds at most 10 root fields, and orders and purchase orders accept at most 500 lines over the API. Page sizes below 1 give the default page. (#356, #374, #393)
  • Organizations other than the administrator organization can only send mail through SMTP hosts with public addresses, or hosts the operator allows. (#369)
  • Webhooks carry a timestamped signature, the test delivery goes only to the webhook being tested, and the outbound host checks for webhooks and carrier labels are stricter. (#380, #381, #382, #412)
  • MCP tools email invoices and purchase orders only to addresses on file or to users of the organization, and mark free text that other people can edit as untrusted. (#384, #449)
  • Exchange rate lookups are limited to supported currencies and dates, throttled, and never show provider error details to purchase order users. (#450)

Updates and deployment:

  • The updater refuses to install a release that is not newer than the installed one, and backups are readable by their owner only. (#379, #412)
  • The production Docker image keeps application code read-only to the web process, and the development stack's database, Redis and Mailpit listen on localhost only. (#409)

Updater

The updater now removes its downloads and extracted files on every exit, including failed and rolled-back updates, and backups no longer include storage/app/temp or the framework caches. php artisan update:clean-temp removes leftovers on demand, and the scheduler sweeps them nightly. (#422)

The updater also checks that it can write the application files and the web root before it enables maintenance mode, and stops with a message when it cannot, instead of failing halfway and leaving the site in maintenance mode. This protects updates from 2.6.0 on; the upgrade to 2.6.0 itself runs on the 2.5.0 updater. (#451)

Dependencies

  • Vite 8 and laravel-vite-plugin 3 build the frontend. The default browser targets rise to Chrome and Edge 111, Firefox 114 and Safari 16.4. (#434)
  • laravel/mcp 1.2: the MCP server speaks protocol revision 2026-07-28. (#436)
  • rebing/graphql-laravel 10.2, with the GraphQL schema unchanged. (#437)
  • Minor and patch updates, including Laravel 13.43, Sanctum 4.5 and Inertia 3.7. (#432)
  • Development only: PHPUnit 13 and concurrently 10. (#433, #439)

Upgrade

Requirements are unchanged: PHP 8.4.1 or newer, MySQL 8.0+, PostgreSQL 13+, or SQLite for development; Node.js 20.19+ or 22.12+ to build the frontend. Back up the database, .env, APP_KEY, uploads and installed plugins before upgrading, and restart queue workers afterwards. UPGRADE.md has the same steps in short form.

Migrations

This release adds migrations. They:

  • create the exchange rate tables (shared rates, per-organization rates and settings) and add the rate snapshot and converted totals to purchase orders, and a currency to supplier price history. Existing purchase orders are left with no rate recorded;
  • add product_supplier.cost_currency and fill it with the supplier's currency, else the organization's, else the install default;
  • set suppliers with a blank currency to their organization's currency and drop the column's USD default;
  • add products.tax_rate, order_items.tax_rate and purchase_order_items.tax_rate (nullable; existing orders keep their tax);
  • add users.two_factor_last_used_timestep and orders.approval_requested_by;
  • grant manage_exchange_rates and override_purchase_order_exchange_rate to the system Administrator role, and override_purchase_order_exchange_rate to the Purchasing Agent permission set. Custom roles and sets are left alone;
  • on PostgreSQL, add trigram indexes on the quote-free form of the searched product, order, customer, supplier and purchase order columns. They are built without CONCURRENTLY, so on large tables writes to those tables may wait while the migration runs. The pg_trgm extension must be installed or creatable by the database user, as before.

Two-factor authentication

  • Everyone signed in with two-factor is asked for a code once more after the upgrade, because sessions verified by earlier versions are not accepted.
  • The first code after the upgrade works as usual. From then on each code works once: signing in again within the same 30-second window, for example in a second browser or through the API, is answered with "This code was already used; wait for the next one." That is not counted as a failure.
  • After 5 wrong codes in 15 minutes, authenticator codes are locked for the rest of that window (the API answers 429 with Retry-After). A recovery code still works and lifts the lock. An administrator can clear it with php artisan inventoros:2fa-unlock user@example.com. The count is kept in the default cache store, so installs with several app servers need a shared cache (Redis or the database) for the limit to apply across them.

Behaviour changes to check

  • Current password. Changing the sign-in email, enabling two-factor and creating an API token in Settings ask for the current password (disabling two-factor already did). A changed email is stored lowercase and must be verified again. POST /api/v1/tokens is unchanged.

  • API tokens and password resets. An emailed password reset, or an administrator setting another user's password, revokes that user's API tokens. Integrations using them need a new token. Changing your own password while signed in keeps them.

  • Scoped API tokens. Managing administrators or managers needs a token created with every permission selected, and running a saved report needs the data source's view_* ability. See UPGRADE.md.

  • Order status. Statuses only move forward: a cancelled or delivered order cannot change status, and a shipped order can only become delivered. Goods that come back go through a return. A shipped or delivered order cannot be cancelled or have its lines changed. Orders moved back from shipped by earlier versions (status pending or processing with shipped_at set) are treated as shipped. To find them before upgrading:

    SELECT id, organization_id FROM orders WHERE status IN ('pending','processing') AND shipped_at IS NOT NULL;
    

    If one never actually shipped, clear its shipped_at. An administrator can move an order marked shipped by mistake back with POST /api/v1/orders/{order}/revert-shipment.

  • Order approval. With order approval on, editing the customer, discounts, tax, shipping, currency or lines of an approved order with no shipment yet sends it back for approval.

  • Saved reports API. GET /api/v1/reports is paginated like the other lists: 15 reports by default, up to 100 with per_page, with links and meta beside data. Clients that expected every report in one response need to follow the pages.

  • API limits. Orders and purchase orders accept at most 500 lines over REST and GraphQL. A GraphQL mutation request holds at most 10 root fields; raise GRAPHQL_MUTATION_MAX_ROOT_FIELDS if an integration needs more. GraphQL mutations sent with GET are refused; send them with POST.

  • Webhooks. Every delivery also carries X-Webhook-Timestamp (Unix seconds) and X-Webhook-Signature-V2, a hex HMAC-SHA256 of {timestamp}.{body} with the webhook secret. X-Webhook-Signature is still sent with its old value, so existing receivers keep working; check the V2 signature and the timestamp to refuse replays.

  • MCP. The server speaks protocol revision 2026-07-28. Clients that open with initialize on 2025-11-25, 2025-06-18 or 2025-03-26 keep working. Requests with a browser Origin other than APP_URL or localhost are refused. MCP can email invoices and purchase orders only to addresses on file or to users of the organization.

  • Imports. Importing products needs create_products or edit_products as well as import_data. Stock changes in a product import need manage_stock and are skipped, with a row warning, when stock adjustment approvals would hold them.

  • SMTP hosts. Organizations other than the administrator organization can no longer use an SMTP host on a private or local address, or one that does not resolve. A host saved earlier fails only when mail is sent. Run php artisan inventoros:check-smtp-hosts after upgrading, and allow a trusted internal relay with INVENTOROS_SMTP_ALLOWED_HOSTS. See UPGRADE.md.

  • Exchange rates. Existing purchase orders keep "no rate recorded". With purchase order approvals on and a threshold set, a purchase order in another currency without a rate, or with a rate entered by hand, needs approval; that includes existing unapproved drafts. Suppliers stored as USD stay USD, because an explicit USD cannot be told apart from the old default: review them. A supplier currency stored in lower case, such as chf, is left as it is in the suppliers table, while its supplier cost links get CHF.

  • Browsers. The frontend now targets Chrome and Edge 111, Firefox 114 and Safari 16.4 or newer.

Docker and Coolify

Pull the 2.6.0 image and recreate the app, worker and scheduler with the existing configuration and volumes; the app applies the migrations on start. With a pinned image, set INVENTOROS_IMAGE=ghcr.io/inventoros/inventoros:2.6.0 first. In Coolify, change the image tag to 2.6.0 and redeploy.

Never use the in-app updater in a container. In 2.5.0 images it can leave the site in maintenance mode. If that happened, remove the marker from the storage volume:

docker compose -f docker-compose.prod.yml exec app rm -f storage/framework/down

Linux installer

sudo bash install.sh --version 2.6.0

cPanel and the in-app updater

Use Admin > Update as usual. Set PHP's memory_limit to at least 256M first. The 2.5.0 updater runs this upgrade, and it can include leftovers from earlier failed attempts in its backup and run out of memory: if a previous attempt failed, delete the extracted_* folders (and any update_*.zip) in storage/app/temp before retrying. From 2.6.0 on the updater cleans up after itself.

Source installs (git)

git fetch --tags && git checkout v2.6.0
composer install --no-dev --optimize-autoloader
npm ci && npm run build
php artisan migrate --force
php artisan optimize
php artisan queue:restart

Composer create-project installs

2.6.0 is the first release whose create-project step copies .env, generates APP_KEY and leaves setup to the web installer; earlier tags also created and migrated a SQLite database. Update an existing Composer install from Admin > Update, as above, not with composer update or another create-project.