ARIA is the software platform by IOMA, an IT/OT industrial integrator based in Turin

ARIA/Warehouse
Warehouse · AMR fleet

ARIA Warehouse.
Warehouse management, integrated with the line too.

WMS software for warehouse management and internal logistics, on its own or with the line.

It is complete, standalone warehouse management software, a production WMS: it handles movements, locations, orders, stock, and material traceability.

It works on its own or integrated with ARIA MES/SCADA and ARIA AMR: where production and the warehouse live in the same plant they share the same backend — no sync between MES and WMS, same master data, same history, and a single view of the process — and warehouse moves become missions for the mobile robot fleet. Without ARIA MES/SCADA, integration with an existing MES or ERP is assessed case by case.

It also supports multiple warehouses (multi-warehouse) on the same data, with real-time updates.

CompatibilityIntegrated WMSReal-timeMulti-warehouseAMR fleetBatch traceabilityOn-prem · cloud
ARIA Warehouse — isometric warehouse plan with racks RACK-A1, A2 and A3 and, on the right, the front view of RACK-A1 with each bin state and the contents of bin P03: stainless steel, batch, 80 kg in stock, with the actions withdraw, move, adjust, and AMR transport
ScreenStructure and slot contents
Strengths

Why ARIA Warehouse.

  • Same source of truth as the field — No nightly sync between MES and WMS — same master data, same history, same real-time. Warehouse and line breathe together.
  • Configuration, not code — New warehouse entities (movements, orders, locations) are added via configuration. No green-field development for every customer.
  • AMR missions with ARIA AMR — With ARIA AMR, warehouse moves become missions for the mobile robot fleet, with warehouse locations bound to the map nodes. Navigation stays with the vendor's fleet manager; here you decide what moves and where to.
  • Stock that follows the move — On mission completion the transfer is written into the warehouse: stock stops chasing the material. Enabled in stages — you start in observation only.

What it does, concretely.

  • Configuration, not code: new warehouse entities in a few lines
  • Receiving against purchase orders, with incoming QC quarantine
  • Lots with expiry, FEFO picking, waves, and packing
  • Cycle counting, replenishment, and low-stock alerts
  • Spatial warehouse map, with a rack-block editor
  • From the bin: find, pick, move, adjust; QR placards
  • AMR mission dispatch on lift, roller, CTU, and forklift
  • Warehouse locations mapped to fleet-manager nodes
  • AMR moves as an automation action, triggered by a line event
  • Multiple warehouses on the same data
  • Same master data and traceability as SCADA — no double truth
AURA

AURA, inside the warehouse.

"What is below minimum stock?" AURA reads the stock and answers with items, bins and shortfall; on confirmation it checks the open purchase orders for those items. Under every answer, the source it read. Real answers on real data; the wait is shortened for the video.

ScreensIn production · live

In production, not on slides.

3 main ARIA Warehouse screens with technical captions. They are real screenshots captured on a live plant — what you see here is exactly what the shift lead sees.

ARIA Warehouse — movements ledger with four open receipts from a purchase order, the from-to route, the dispatch state, the row actions, and counters for open, awaiting and failed movements
Screen · 01

Movements and dispatch

The ledger of open movements, each with the origin that created it: a receipt from a purchase order, a shipment, a release from quality control. Every row carries the product, the route — from where to where —, the dispatch state toward the vehicle that has to run it — requested, running, failed, not dispatched yet — and who is running it; on the right, the actions: confirm arrival, send to an AMR, take it manually, close. The counters up top say how many movements are open, how many are waiting for dispatch, and how many failed: this is the warehouse work queue, not an end-of-period report.

  • Origin tracked: receipt, shipment, QC release
  • Route from → to and dispatch state on every row
  • Counters for open · awaiting dispatch · failed
  • Filters by status, dispatch, and origin
ARIA Warehouse — purchase order list with supplier, warehouse, status (draft, confirmed, completed) and expected date, plus counters for purchase, sales, open and completed orders
Screen · 02

Purchase and sales orders

Purchase and sales orders in one place, each with its state: draft, confirmed, completed. The bar up top says how many orders are waiting for an action: two here, both purchase. The day starts there rather than in an inbox. Every row carries the supplier, the destination warehouse, how many lines it holds, and the expected date; from the top you update an order's state and record a receipt, which opens the put-away movements toward the racks.

  • Purchase and sales in one view, with the totals
  • State per order: draft · confirmed · completed
  • How many orders await an action, up top
  • Supplier, warehouse, lines, and expected date
ARIA Warehouse — isometric warehouse plan with racks RACK-A1, A2 and A3 and, on the right, the front view of RACK-A1 with each bin state and the contents of bin P03: stainless steel, batch, 80 kg in stock, with the actions withdraw, move, adjust, and AMR transport
Screen · 03

Structure and slot contents

The warehouse as you walk it: on the left the isometric plan with racks coloured by state, on the right the path zone › rack › bin. Pick a bin and you get the front view of the rack — every bin colour-coded: available, below minimum, held by quality control, free — and below it the contents: stock, committed, available, item, code, and batch. From there you withdraw, move, adjust, send a transport to an AMR, or print the label. Up top, search finds an item, a batch, or a location.

  • Isometric plan with racks coloured by state
  • Path zone › rack › bin
  • Front view of the rack, bin by bin
  • Bin contents and actions: withdraw, move, adjust, AMR
Plans and pricing

One price per warehouse, not per user.

A perpetual usage licence, with five years of support, maintenance, and updates included. The price counts warehouses, not users or locations: more people on the floor do not raise the bill. ERP integration, scanners, printers, and the server are excluded.

Each warehouse has its own licence. The price does not change with the number of users or locations.

warehouses

× €5,850 /year

It is switched on for the whole warehouse, not part of it: either the warehouse has it, or it does not.

€750 per warehouse per year · €675 paid upfront

What AURA is and what it can answer

Upfront payment: A single payment at kick-off, 10% off the licence. It is the shape that suits a capitalized investment (CAPEX) and the assessment of the 2026 capital-goods incentives, subject to the applicable rules and your company's situation: check it with your accountant.

From year 6

The software is yours

The licence does not expire. ARIA keeps running on your plant server, with your data and your configuration. The only decision left is whether to keep the service active.

  • You renew maintenance: support and updates carry on.
  • You don't renew: the installed version stays in production and keeps working. It no longer receives updates or support.

Service renewal · 30% of the yearly list-price instalment

€1,950 /year

Indicative prices

This is the price list. The quote we write on your warehouse.

The numbers above are the public price list, but your figure depends on the perimeter: the warehouse structure, the master data to load, the ERP integration. Commissioning is the line that moves the most. One call frames it; the site survey settles it.

Get an accurate quote

Before you sign

The price list
Yearly fee per warehouse, in the two payment formulas, excluding VAT.
fee · per warehouse, per year
yearly payment · list priceupfront payment · −10%
Per warehouse€6,500€5,850
AURAadd-on module · per warehouse€750€675

Turnkey commissioning. €6,000 per warehouse, one-off. Travel costs, if any, are excluded.

AURA. It is switched on for the whole warehouse, not part of it: either the warehouse has it, or it does not. The server that hosts the model is the customer's and is sized at the site survey.

Turnkey commissioning

One-off, for each warehouse: installation, the warehouse structure (zones, locations, map), loading the master data, testing, commissioning, and training the people who use it. Travel costs, if any, are excluded.

Terms and notes
  • Prices exclude VAT. The usage licence is perpetual and includes five years of Standard 8×5 support, maintenance, and updates.
  • Each warehouse has its own licence and pays the same fee: the price does not change with the number of users or locations.
  • ERP integration, quoted on the case, and hardware (scanners, printers, server) are not included.
  • From year six, renewing the service costs 30% of the yearly list-price instalment. Without renewal the software stays installed and working, and no longer receives updates.
  • AURA, the AI assistant, is an add-on module and not part of the licence: it is added to the warehouse at a yearly fee per warehouse. The server that hosts the model is excluded.
Questions · scope · cost

Let's assess ARIA Warehouse on your case.

Let's see whether ARIA Warehouse fits your case: what connects to the systems you already run, what changes for the people using it, and what it costs at your scale.

Do you resell or refer industrial software? See the IOMA Partner Program

You might also be interested in

Guides that go deeper on these topics.