Next Restaurant 6.1.0: move your data in, run payroll, and connect other systems Next Inventory 6.2.0: a REST API and webhooks for your other systems Next DB 6.1: Auto-Updating Tables, Printing, Phone Layout and SEO Next Task 6.0.0: a task manager for Joomla Next Inventory 6.1.1: smoother Check Out, no more list limits, and much faster PHP2Shell: Is Your Joomla Site Safe? What to Do Today Introducing Next Boards: Kanban project and task boards for Joomla Building the Future of Joomla Extensions
NextSoftware
Back to Next Inventory changelogs
Next Inventory

Next Inventory

v6.2.0 stable
Released 20 changes
Joomla 4 Joomla 5 Joomla 6
New Features 18
  • REST API. Another system (an ERP, a web shop, a bespoke back-office tool) can now read and change Next Inventory at `/api/index.php/v1/nextinventory`. It covers items, barcode and SKU lookup, categories, warehouses, recipients, units, stock movements (check in, check out, add, remove), transfers, adjustments, the transaction ledger and the reports. Every change goes through the same permissions, validation and stock rules as the screens, and lands in the ledger.
  • REST API page (Configuration → REST API), with Tokens, Settings, Health and Usage tabs. Create a token for each integration and tick the scopes it may use. A token acts as the user who created it and never does more than that user's role allows. It can expire (30, 60 or 90 days, 6 months, 1 year or a chosen date), be disabled or revoked, and its secret is shown only once.
  • Each site serves an OpenAPI 3.1 description of the API at `/media/com_nextinventory/openapi.yaml`, for Postman, Swagger UI or a generated client.
  • Item images and custom fields through the API: upload or remove an item's image, read custom field definitions and values.
  • Webhooks (Configuration → Webhooks). Next Inventory POSTs a signed message to your system when stock changes in any way, when an item falls to its low-stock threshold, when a movement, transfer or adjustment is finalized, and when an item, warehouse or recipient is created, edited or deleted. Failed deliveries are retried by the "Next Inventory: Retry webhook deliveries" scheduled task, created automatically when the first webhook is saved.
  • App Manager has a new Integrations group with API Tokens and Webhooks. Switching an app on switches its plugins on; a plugin switched off by hand is flagged with a one-click repair. Switching API Tokens off refuses every token request at once.
  • Safe retries: a write sent with an `Idempotency-Key` header runs once, and a retry with the same key gets the first answer back.
  • Concurrent edits: records return an ETag, and a change sent with `If-Match` is refused (412) if the record changed in the meantime.
  • REST API → Health: numbered setup steps with the next one highlighted. Checks that the web server passes the Authorization header to PHP (with the fix for your server), that the API plugins are on and that the site uses HTTPS. On sites with an active token, a problem that stops every integration is shown as a banner to users who manage settings.
  • REST API → Usage: copy-paste `curl` examples with your site's address filled in.
  • REST API → Settings: reads and changes per minute per token are limited separately (300 / 120 by default; 0 = no limit), and every answer carries RateLimit-Limit, -Remaining and -Reset headers.
  • Protection against token guessing: more than 20 unknown tokens from one address in 5 minutes are answered 429 until the window ends. A valid token is never refused by it.
  • API tokens, webhooks and the API settings are recorded in Joomla's User Actions Log, without ever logging a token or a secret.
  • Webhooks page with Endpoints, Deliveries, Health and Usage tabs. Each webhook's signing secret can be copied or replaced, and Health lists any receiver that may not have its secret yet.
  • Webhooks also carry the Standard Webhooks headers (webhook-id, webhook-timestamp, webhook-signature).
  • Webhooks: failed deliveries are retried over about a day and a half (1 minute up to 24 hours, 8 attempts); a receiver answering 410 Gone is not retried.
  • Webhooks: the delivery log filters by status, refreshes itself while open, can resend any delivery and can be cleared (pending deliveries are kept). Retention is a setting (30 days by default).
  • Webhooks → Health warns when deliveries are more than 15 minutes overdue and offers Retry due now.
Changes 2
  • Finalizing a warehouse transfer, or a damage or subtraction adjustment, now checks that each item has enough stock, as stock movements always have. Before, it could take an item below zero.
  • Each update now removes the JavaScript files of the release before it. Previously every update left the old ones behind, about 20 MB a time.

Explore Next Inventory

Product details, the full release history and documentation.

View product All releases Documentation

All Extensions