Unleashed software pricing for a two-warehouse team

Your second warehouse is ready to open, and purchasing needs to know what can ship from each location. Unleashed software pricing should be evaluated against that workflow. The US pricing page lists annual base prices of $4,389 USD for Core and $8,019 for Pro. Its inventory feature description limits multi-warehouse management to Core and Pro, so Lite is not the starting point for this two-warehouse comparison.

Evaluate Core when the required inventory workflow fits its included capabilities and confirmed allowances. Consider Pro when its additional capabilities have a defined job in your operation. Keep an existing inventory system if it already handles location-level stock, backorders, and access without recurring manual corrections. A new package needs to solve a specific failure before the migration work is justified.

Hold the users, locations, and order volume constant

Use a proposed US business with three named users: purchasing, warehouse operations, and sales administration. It has two warehouses, 600 product codes, 80 sales orders each month, and one accounting connection. The scope includes receiving purchased stock and partially shipping customer orders. These are evaluation inputs, not an observed customer deployment.

Unleashed’s feature explanation starts Core at three users and Pro at five. Each person needs a license. Both cover the proposed three-person roster without adding users, but the unused Pro seats do not establish a reason to upgrade. Compare the required workflow and the included modules before assigning value to the larger bundle.

The base difference is $3,630 per year. These October 29, 2026 figures use the displayed annual charges, not the rounded monthly equivalents. Taxes, onboarding, added users, optional modules, extra integrations, and usage additions are excluded. The complete first-year total remains unknown until those items are scoped.

Ask sales to put the order allowance and treatment of the accounting connection in the offer for this exact scenario. Do not assume that one shipment, one invoice, and one sales order count as interchangeable events. For a neighboring inventory option, Cin7 pricing also requires matching the order and integration scope before comparing totals.

Identify the work that changes the package price

The US pricing FAQ describes extra-user, integration, storage, API, and sales-order charges. It says exceeding an order allocation can cause an additional allocation to be applied in following months. Ask for the charge, effective date, and removal terms in writing. Keep the entire quote in USD; another regional page may show different amounts or packaging.

Separate a warehouse location from a scanning workflow. Receiving by location may meet the initial requirement, while bin-level picking or device access introduces another configuration to price. Give the vendor the tasks and number of people doing them, and ask which modules and devices the proposed offer includes. Leave that line unresolved until the vendor confirms the scope.

The same discipline applies to manufacturing. If the team assembles finished goods from components, include one bill of materials and an incomplete production run in the demonstration. If the business only buys and resells stock, do not add production requirements to make a higher package look more attractive. Katana pricing covers the separate decision when production is central to the purchase.

Walk through a receipt and a partial shipment

Start with a fictional product, an agreed opening quantity at each warehouse, and a customer order that exceeds the quantity available at the shipping location. Record the units and location before doing anything. Unleashed’s product documentation distinguishes stock on hand from available quantity, which excludes amounts allocated to open sales orders, assemblies, or warehouse transfers.

Have the implementer demonstrate the order allocation, a shipment of the available quantity, receipt of the remaining stock, and the final shipment. The backorder documentation describes leaving unshipped quantities on backorder and creating a purchase order or assembly to fulfill them. Inspect the remaining quantity and location after each step.

The expected result is a reconciled movement history: received stock, dispatched stock, and the amount still owed to the customer. Confirm how invoices and the accounting connection behave at partial dispatch. These are proposed acceptance checks based on current documentation; no hands-on results are claimed here.

Repeat the relevant steps with the warehouse user’s permitted access. Record whether that role can change cost data, reverse a transaction, or export records beyond its job. Ask the implementer to explain any failed requirement before signing off. A correct quantity entered by an administrator does not establish that the everyday role is ready to use.

Where Permute fits: reconciling the inventory report

Permute sells connected business data and custom applications. This comparison reflects our commercial interest. When an inventory export, a warehouse spreadsheet, and QuickBooks disagree, we help define which product records match and which source supplies each value. The original identifiers and dated evidence remain part of the review.

Your rule for available stock or inventory value can be reused in a recurring report or custom app. An operations manager can inspect the permitted records behind an exception and see whether it comes from an allocation, a delayed feed, or an unresolved product match. The report should distinguish an unknown from an amount that has been reconciled.

Keep operational and analytical responsibilities explicit

We do not sell Unleashed licenses or promise a native Unleashed connector, automatic stock adjustments, or an inventory forecasting engine. Source access and permitted actions need a defined implementation scope. The inventory system remains responsible for the operational transactions you have assigned to it, while a connected report needs a clear refresh and reconciliation process.

Agree the opening-stock process before the cutover

Unleashed’s product import documentation says its opening stock-on-hand template is for products that have never held stock in Unleashed. It cannot change existing stock quantities. Rehearse the setup before loading live balances, and agree how corrections will be made if the imported result differs from the signed-off count.

Keep a cutover record of products, units of measure, warehouse balances, batch or serial details, open orders, and values approved by finance. Preserve the original exports. The same import instructions warn that an imported update cannot be reversed and that templates accept plain text rather than images. Treat files and historical supporting records as a separate migration task.

Reconnect the accounting integration only within the agreed cutover sequence, so historical documents are not created twice. Compare the opening balances and first completed order before handing the system to the whole team. Inventory reconciliation describes how to keep the differences attributable to their source rather than adjusting a total without an explanation.

Approve the inventory workflow and the annual commitment together

Core and Pro provide different annual starting points for the same two-warehouse team. Select the package after the receipt, partial-shipment, and access checks show what the operation needs. Add the confirmed services and usage terms before calling the budget complete. Keep the existing system when it meets those requirements and a migration would add work without fixing an identified problem.

Questions about an Unleashed inventory budget