Self-Hosting

Free Warehouse Management Software: Stock Control and WMS Limits

•8 min read•By Inventoros Team

A receipt adds units to a storage bin, an internal transfer moves units between bins, and an outgoing order removes units from the warehouse boundary.

Free warehouse management software can record stock without charging a licence fee, but that does not establish a complete warehouse execution workflow. Inventoros covers inventory records, locations, transfers and purchase receiving. It does not provide pick lists, picking waves or zones. If directed picking is essential, start with that requirement before comparing prices.

The useful distinction is what happens between an order arriving and a parcel leaving. A stock record can be correct while the team still needs a separate process for selecting, checking and packing the goods.

Define the warehouse work first

Walk through one receipt and one outbound order with the people doing the work. Identify where quantities are counted, where storage locations are chosen, who resolves a discrepancy and which system records the result.

A warehouse might need simple shelf-level stock control, or task assignment across many pickers and shifts. Those are different purchases even when both are described as a WMS. A product name does not establish support for the second operation.

Write requirements as observable outcomes. “Receive forty of a hundred ordered units without pretending the rest arrived” is testable. “Advanced receiving” is too vague to reveal whether a candidate fits.

Include the exceptions that create extra work: a supplier sends the wrong variant, a carton is damaged, or a worker finds stock in an unlabeled overflow area. A perfect receipt of one simple product will not expose those requirements.

Four meanings of free

Offer What to establish before relying on it
Open-source core Licence terms, installation requirements and maintenance ownership
Hosted free tier User, warehouse, item and transaction limits, plus the first paid step
Time-limited trial Expiry date and whether a usable export is available
Marketplace-funded service How the service is paid for and which transactions carry fees

These are categories, not equivalent offers. A free tier may suit a small operation. Open-source code may fit a team that needs control of its data and integration. Compare the operating arrangement rather than treating “free” as a common feature set.

If the service becomes your stock record, test an export before importing everything. Check product identifiers, quantities, locations and transaction dates. An export of product names alone cannot reconstruct a warehouse balance.

What Inventoros covers

The following boundaries describe the core product and the workflow an operator supplies around it.

Warehouse requirement Inventoros scope
Product and variant records Core product records and identifiers
Warehouse balances Quantities tracked per warehouse
Storage locations Location records and product/location stock
Movement between warehouses Stock transfers
Purchase receipts Receiving against purchase orders, including partial receipts
Stock corrections Adjustments and stock audit workflows
Outbound order quantity Stock deducted when the order is created
Purchasing edits Draft purchase orders are editable; receiving is separate

Immediate order deduction matters during a floor pilot. Staff must understand which balance represents the order commitment, rather than waiting for shipment to deduct the same quantity again. A reservation is a separate plugin hold, not the ordinary sales-order lifecycle.

The Locations screen provides storage cards and a QR-label action. Use consistent physical codes so the location in the software matches the label somebody can see at the shelf.

Cropped Inventoros Locations screen with storage cards, location codes and the QR-label action, with account and user details excluded.

Reconcile a complete movement example

Use a hypothetical product with fifty units in warehouse A and twenty in warehouse B. Receive forty into A, transfer ten from A to B, and create an order for twelve units from B. Assume no plugin holds or other movements.

Opening total                      50 + 20       = 70
Receipt into A                     50 + 40       = 90 in A
Transfer A to B                     90 - 10       = 80 in A
                                   20 + 10       = 30 in B
Order created from B                30 - 12       = 18 in B
Closing total                      80 + 18       = 98
Independent check                  70 + 40 - 12  = 98

The transfer changes distribution, not the total. The receipt increases the total and the order decreases it. Reconcile both warehouse balances and the organization total. A correct global total can conceal ten units assigned to the wrong warehouse.

Count the physical goods after receiving and transferring. After order creation, B can still physically contain thirty units until twelve leave for dispatch, while the recorded balance is already eighteen. Reconcile the twelve units awaiting dispatch separately and avoid deducting them again. If staff move goods before recording a transfer, define who owns that temporary mismatch.

Use the same product and warehouse identifiers throughout the test. Similar names, duplicate SKUs or mixed units can produce a plausible-looking total while referring to different goods. Record the expected result before the person performing the count sees it.

Receiving needs exception rules

Start with a purchase order for one hundred units and record a first receipt of forty. Inspect the outstanding quantity and stock increase. Receive the balance separately and confirm the purchase order completes only when the required quantities are received.

Inventoros only allows editing a draft purchase order. A partly received order cannot be cancelled, and there is no close-short action. If a supplier permanently fails to deliver the remainder, the buyer needs an explicit procedure for that exception.

Landed cost and supplier-invoice matching are outside the purchasing flow. Keep freight allocation and invoice reconciliation in the appropriate purchasing or accounting process. The purchase order workflow explains state transitions and partial-receipt limitations.

Three-year cost including staff time

Compare a hypothetical subscription charging $40 per user per month with a self-hosted system whose core licence fee is zero. This is a budget example, not a quote for a named vendor.

Assume sixteen setup hours at $50 an hour, $30 monthly for infrastructure and backups, and four maintenance hours a month at $50. Common warehouse labor, scanners, printers and training are excluded from both sides. Recurring technical effort is assumed constant as users are added.

Setup                           16 × $50                    =   $800
Monthly infrastructure                                      =    $30
Monthly maintenance              4 × $50                    =   $200
Three-year self-hosted total      $800 + 36 × ($30 + $200)   = $9,080

Subscription, four users          4 × $40 × 36               = $5,760
Subscription, twelve users       12 × $40 × 36               = $17,280
Break-even users                 $9,080 / ($40 × 36)        = 6.31

The subscription is $3,320 cheaper at four users. At twelve, the self-hosted budget is $8,200 lower. Seven is the first whole user count above break-even.

Add integration development, outside support and extra operational coverage when required. A system needing custom picking development is not cheaper merely because its licence is free. Compare it with a product already supporting that workflow and include the cost of maintaining the customization.

Double maintenance hours in the example and the three-year cost rises by 4 × $50 × 36 = $7,200. That change moves the decision much more than saving a few dollars on a server each month.

Install on isolated infrastructure

Inventoros is AGPL-3.0 licensed and has no core item or user caps. Its application requires PHP 8.4.1 or later; the documented Linux installation needs at least 1 GB of RAM, with 2 GB recommended. The Linux installer provisions a Docker-based deployment on the selected server.

Download and inspect the script before running it on a dedicated test server:

curl -fsSL https://inventoros.com/install.sh -o install.sh
less install.sh
sudo bash install.sh

The Linux installation instructions describe the environment and prompts. Keep the pilot isolated from unrelated applications until restore, access and integration tests are complete.

Import a representative catalogue first. Include a variant product, two warehouses, storage locations and a partial purchase receipt. Use barcodes that distinguish products from locations and confirm staff can find the correct record. The barcode inventory setup covers that workflow.

Check integration and recovery boundaries

Inventoros exposes REST, a subset GraphQL surface and webhooks. Those interfaces allow integration work; they do not establish a ready-made connection to every storefront or carrier. Use the API documentation to identify the operation and permission needed.

Design retries around the inventory consequence. If an outside order arrives twice, the integration must recognize the duplicate before creating a second movement. Reconcile receiving and order totals during the pilot rather than assuming a successful HTTP response proves the whole process is correct.

Backups must include the database, required configuration and uploaded assets. Restore to another test environment and compare product and warehouse balances. Protect secrets and verify recurring work after the restore. Record the age of recovered data and the time until staff can work again.

I would use Inventoros for a stockroom or warehouse needing inventory records, purchasing, locations and transfers, with an operator for the application. The inventory tracking product page explains the balance and transaction boundaries.

Choose a warehouse execution product with demonstrated picking capabilities when task-directed picking determines the purchase. Odoo Inventory describes receipt, storage and picking workflows; OpenBoxes describes its supply-chain and warehouse scope. Test the actual edition and workflow before choosing either.

Questions before choosing

Is an open-source WMS free to operate?

The core licence can be free while hosting, maintenance, integration and equipment cost money. Include those costs over the expected operating period.

Can inventory software replace a WMS?

For simple stock control it may cover the work. If the operation depends on task-directed picking or other execution features, verify those directly before replacing anything.

What should a pilot prove?

Correct quantities through a receipt, transfer, order and count; appropriate access; usable exports; and a tested restore. Add the difficult exceptions your warehouse handles every week.

Prices and requirements as of November 2026.