Best Cloud and Multi-Location Inventory Software

Workflow it supports

The dated pricing rows list inventory transfers on Optima and Pro, but not Start. Sales orders, picking/packing, and serial/lot tracking are identified with the Pro plan; do not imply Start includes them.

Capabilities and conditions

QuickBooks Online synchronization is optional; the pricing page also describes standalone inventory use. The technical integration page specifies QuickBooks Online Plus or Advanced when sync is used.

Checks before choosing

The retained plan rows attribute sales orders, picking/packing and serial/lot tracking to Pro; QuickBooks sync depends on Plus or Advanced.

Warehouse and scanner workflows

The product describes stock counts, lot and serial tracking, purchasing, kitting and wave picking. Mobile Barcode WMS is listed under Growth and Enterprise, not established as part of Essentials. Its documented workflows include bin-directed picking and barcode label, lot and expiry handling.

The separate Finale Mobile Scanner is documented for Android 8.1 or later; it does not run on iOS. It requires a Barcode License for installed scanner software. A scanner first downloads data via Wi-Fi, collects operations offline and then uploads them after reconnecting. Synchronisation is manual and each scanner keeps its own downloaded snapshot; automatic cross-device merging or browser offline operation is not established.

Integrations

Finale lists Shopify, Amazon FBA and Walmart, and names QuickBooks Online and Xero. Existing QuickBooks Online documents use inconsistent legacy plan thresholds and a dated US-only statement, so current plan and regional eligibility must be confirmed. API and EDI are listed under Enterprise; this does not establish access in every tier.

Workflow it supports

The mobile documentation lists counts, pick lists, purchase orders and camera-based barcode/QR scanning; check the applicable plan and device requirements.

Capabilities and conditions

Offline mode is mobile-only. Changes stay on the device until sync, so synchronize before disconnecting and reconnect after working offline.

Checks before choosing

The cited offline FAQ supports the mobile-only and sync conditions; the help page lists app requirements, but this release does not assume one device version or plan entitlement for all users.

Workflows and scope

The saved regional page excerpt positions Anchanto for ecommerce and retail warehouse operations and describes warehouse, inventory and fulfillment scope. It does not establish inbound purchase-order receiving or a complete workflow specification for every edition.

The saved excerpt does not establish mobile or handheld workflows, device requirements, offline transactions, interface languages or supported sales countries.

Deployment and pricing

No warehouse-software amount was established from the product check and targeted pricing search; the site's Pricing & Promotions product is a different subject. Unresolved terms include WMS modules, warehouse/user/order allowances, onboarding, integration fees.

Review evidence

The bounded check on 2026-10-28 yielded no readable, dated, attributable review sample for this service. Profile discovery or blocked pages do not provide review content.

Warehouse workflows

Aptean lists receiving and putaway, real-time inventory, order planning and picking, voice picking, reverse logistics and 3PL support. Its page also describes weight, case and serial-level scanning.

For cold storage, the vendor lists traceability and temperature capture. Confirm how the proposed system captures temperature and whether the necessary hardware or interfaces are included.

Operational detail

Aptean describes ProWMS customers ranging from single-site standalone operators to multinationals with multi-site supply chains. Its product page lists reverse logistics, voice picking and scanning at weight, case and serial level alongside order planning. Those details make the handling unit and return process useful points to examine during evaluation.

A scenario to test

Take a mixed case containing serial-controlled goods through receipt, putaway, picking and a customer return. Ask the supplier to show where each serial is captured, how an exception is corrected and what the customer can see. Repeat with the actual handling units and label formats used at your site.

Implementation boundary

Document the scope for each warehouse separately: inventory ownership, customer reporting, scanning hardware, voice equipment and any temperature data. Ask which functions are standard configuration and which require additional interfaces or project work.

Evaluation in practice

For a temperature-controlled 3PL example, prepare two customer-owned products with different storage requirements and an order containing both. Ask the supplier to demonstrate the proposed receipt, location decision, pick and return processes using the customer identifiers and labels your operation actually uses. Include an item with a damaged label and a return whose original serial cannot be found. Record how staff identify the exception and who authorizes a correction. For implementation, distinguish the warehouse transaction from the separate measurement of temperature: identify the physical sensor, the system holding the reading and how the reading is linked to a stock record, if required. Ask for a sample customer-facing report and reconcile it against a known receipt and shipment before accepting the design.

Warehouse workflows and regional editions

The vendor describes receipt with batch and expiry details, quarantine until authorised QA release, first-expiry-first-out allocation, recall tracing and cold-chain logs.

As of 28 October 2026, the vendor described a live deployment at a Dubai drug store, India as early access, Singapore, Australia and the United States as founding-customer pilots, and Saudi Arabia as design-partner stage. Country-specific compliance items may remain in pilot or on the roadmap.

The India edition is described as cloud software accessible through a browser, with phone access for sales and delivery staff. Confirm offline operation, UI languages and the scope and cost of statutory or accounting integrations for the relevant regional edition.

Compare and ask

Compare inventory workflows and deployment choices with Odoo Inventory; the products serve different purchasing requirements.

Ask which regional compliance functions are live, how batch migration is priced, and whether the setup charge is mandatory.

Warehouse operations

The Operations material describes directed inbound and quality checks, cross-docking, lot and date control, replenishment rules, multiple picking methods and sequenced loading. Task direction can use permissions, priorities and proximity.

Operations is marketed on an extensible SaaS platform with APIs for existing systems. Blue Yonder also advertises a Robotics Hub service for automation onboarding; confirm connector scope and licensing.

Operational detail

Blue Yonder’s Warehouse Management Operations material describes configurable inbound workflows, directed putaway, in-line quality assessments and identification of cross-docking opportunities. It also describes task direction using permissions, priority and proximity. These are operational functions within the named Operations material; they should not be taken as proof that every wider suite module is included.

A scenario to test

Use an inbound shipment with one item requiring inspection and another needed urgently for an outbound order. Ask the team to demonstrate the decision points, where exceptions appear, and how work reaches the intended employee. Test a change in priority while work is already in progress.

Implementation boundary

Request an architecture diagram showing the proposed Operations scope and each separately licensed service. Identify the authoritative system for inventory, the interfaces to existing applications, the event exchange and who owns the configuration and testing.

Evaluation in practice

For a further operational test, plan a busy shift with a receipt, replenishment and urgent outbound work competing for the same aisle. Give the vendor your employee roles and priorities and ask it to demonstrate the sequence in the proposed configuration. Change an employee’s permission or availability and examine which work remains unassigned and how a supervisor sees the exception. For the integration design, request examples of the inbound receipt, inventory change and shipment-confirmation messages, including identifiers and error responses. Decide which system owns item, location and order master data, then reconcile a deliberately rejected message. Compare the demonstration with current throughput and handling requirements; a realistic workload and agreed measures will be more useful than a generic list of features.

Workflows and scope

BoxHero documents stock in/out, transfers, counts and barcode scanning. Its Business plan lists purchases and sales, multiple locations, label printing, low-stock alerts, reports, return orders, bundles and team permissions. These features are plan-specific.

BoxHero offers web and mobile access. The Google Play listing for version 3.59.6 requires Android 7.0 or later; the US Apple listing requires iOS/iPadOS 15.5 or later. The account guide lists selectable interface languages: English, Spanish, French, German, Russian, Japanese, Korean, Indonesian, Thai, Vietnamese, Brazilian Portuguese, Simplified Chinese and Traditional Chinese.

Custom Open API access and webhooks are documented for every plan. The documentation does not establish API quotas or named native accounting connectors.

Deployment and pricing

The pricing page observed October 29, 2026 lists Business at $24 per month when billed annually ($288 for a year). The separate pricing guide observed October 28, 2026 lists Business at $30 per month when billed monthly. Both pages show a dollar sign without identifying its ISO currency; rates are per team subscription.

Personal is free. Business add-ons are listed at $5 per member per month, $10 per additional 1,000 item types per month and $10 per additional 10 locations per month. The listed amounts use the same unspecified dollar currency.

Review evidence

The US App Store sample contains three dated BoxHero entries from June 1 to August 28, 2026. The dates and storefront identify the scope of this small sample; they do not establish distinct authors or overall customer sentiment.

Warehouse workflows

Canary7 describes booking stock against purchase orders, capturing batch, serial and expiry information, and directing putaway. It lists single, batch, cluster and zone picking, scan verification, carrier label generation and multi-site, multi-client operation.

The vendor describes a browser interface for scanners, tablets and laptops. Confirm supported devices and browsers for the proposed installation.

The labour-management material describes using scan activity to report picks, putaways and packs by operative, time by shift or task, and client-level labour costs. The pricing matrix reserves advanced labour management for 3PL Advanced and Enterprise; confirm the exact reporting scope in the proposal.

Plan-dependent features

The published plan matrix reserves API access and advanced labour management for 3PL Advanced and Enterprise. Dashboard editing is listed as an add-on for the two lower plans; plan cards and broader inclusion statements conflict, so confirm the proposed entitlement.

Warehouse workflows and connections

Standard WMS guides mobile picking, packing, restocking, putaway and stock lookup for one warehouse location. Unlimited inventory locations on a plan do not by themselves extend this mobile WMS scope. Advanced WMS adds multiple-warehouse workflows, kit picking, time tracking, delivery scheduling and FIFO/FEFO pick-order enforcement; it is a separate entitlement and the Standard card marks it unavailable.

Cin7 names QuickBooks Online and Xero, as well as Shopify, Amazon, WooCommerce and ShipStation. EDI and 3PL connections are described through API and partner solutions; API access is an add-on in the displayed plan. The B2B self-service portal is also an add-on. Confirm applicable plan, partner and integration charges.

Where it fits and how warehouse work moves

Follow one channel order from inventory allocation through warehouse picking and dispatch, and compare that flow with the standard and advanced warehouse functions shown for Omni packages.

Documented functions and operating conditions

• Documented warehouse functions include: Inventory management; Purchase orders; Barcode scanning.

Capabilities and operating conditions

Cybernaptics WMS addresses stock control across warehouse locations and movement to distribution and stores. The vendor describes on-premises and cloud SaaS options.

• Documented warehouse workflow: Warehouse software for stock control across multiple warehouse locations and supply-chain movement to distribution and stores
• Deployment: Standalone on-premises; Cloud-hosted SaaS.
• Supported platform: Not documented in the retained accepted evidence.
• Integrations: Not documented in the retained accepted evidence.
• Offline operation: Not documented in the retained accepted evidence.
• Industries: Wholesale; Distribution; Retail; Manufacturing; Food production.
• Business size: Not documented in the retained accepted evidence.
• Application UI languages: Not documented in the retained accepted evidence.
• Verified country availability: Not documented in the retained accepted evidence.

Pricing, plan limits and additional costs

The retained product page describes deployment choices but no verified price or licence terms.

Review evidence and sample limits

No dated individual review record for the exact product was accepted in the bounded search.

Orders, stock and delivery

The vendor describes AI extraction of customer, purchase-order and line-item data from emails and PDF attachments. Inventory functions include FIFO across warehouses, batch and expiry tracking, low-stock alerts and reorder suggestions. Delivery management covers release orders through dispatch and proof of delivery.

FT-Services lists two-way connections with Odoo, QuickBooks, Tally and Zoho Books for orders, invoices and customer data, as well as APIs. Manufacturing, HR and payroll, POS and e-commerce are described as custom apps or integrations, not standard DOPAS modules. Deployment, supported devices, offline operation and UI languages were not established in the reviewed material.

Warehouse workflows

Documented functions include receiving and matching advance shipping notices, barcode scanning, batch and expiry capture, picking, shipping and multi-warehouse inventory. Check the specific workflow and marketplace connections needed for each site.

Warehouse workflows

Documented workflows include barcode receiving, cross-docking, putaway, stock adjustments, picking and cycle counting. Confirm which capabilities and devices are included in the proposed configuration.

Stock and integrations

The inventory interface distinguishes available, reserved and incoming stock and supports reorder points and low-stock alerts. With the multi-location module, teams can transfer stock and split a sales order across shipping locations. Serial, lot and expiry tracking is separately priced.

Erplain supports QuickBooks Online; its FAQ excludes QuickBooks Desktop and Enterprise. The settings guide says outbound stock is totalled across Erplain locations, while inbound QuickBooks adjustments affect the configured default location; QuickBooks locations do not sync to Erplain. Document sending can be automatic or manual.

The service is cloud-based and accessible through a responsive browser on computers, tablets and smartphones. Confirm version, UI languages and disconnected operation; paid implementation or migration assistance should be scoped separately.

Compare and ask

Compare an open-source parts inventory if self-managed deployment is a priority.

Ask for a configured quote including required modules and dependencies, order overages, migration, taxes and the exact QuickBooks or Shopify sync scope.

Parts and inventory workflows

The documented parts functions include QR-based part lookup and checkout, minimum stock alerts and cycle counting. Multi-site parts visibility and inventory cycle counts should be evaluated against the chosen plan: the pricing analysis places multi-site management and cycle counts in Professional.

Where it fits and how warehouse work moves

The UK Inventory comparison distinguishes Essentials, Growth and Scale: Growth lists pick, receive and ship work, while Scale lists lot traceability and audit features.

Documented functions and operating conditions

• Deployment: Cloud
• Deployment: Fishbowl Inventory is described as cloud-native inventory and warehousing software. Condition: Fishbowl Manufacturing is separately described as cloud-hosted; its deployment choices are not assigned to Inventory.
• UK Inventory Essentials includes stock/SKU tracking, reorder points and mobile barcode scanning. Condition: UK Inventory Essentials block only, not Advanced Warehouse or Manufacturing; app/hardware prerequisites are unresolved.
• UK Inventory Growth lists picking, receiving, shipping/fulfilment, automated reordering, multichannel selling and transfer orders. The same UK comparison marks transfer orders “Coming soon”; confirm release availability before relying on transfers. Condition: Growth card wording; availability is unresolved.
• UK Inventory Scale adds lot forward/backward traceability, audit trails and advanced permissions. Condition: Scale entitlement only. GMP/FDA/ISO document labels do not establish certification or guaranteed compliance.
• Connected systems: QuickBooks Online; Xero Condition: The UK Inventory Essentials card names these connections. Desktop appears in family/Advanced material and is not inherited by Inventory.
• Connected systems: Spark Shipping explicitly connects to Fishbowl Inventory and the separately named Advanced/Manufacturing product. Condition: Requires a Spark Shipping account and supplier/channel/routing configuration; this is a third-party integration, not a built-in Inventory entitlement.
• Through Spark Shipping, supplier feeds update stock/catalogue data, rules route supplier orders and tracking can be written back to Fishbowl. Condition: Only through separately configured Spark Shipping. Sync timing is configurable; typical intervals do not establish zero-lag operation.
• Industry applications: Food and beverage; Chemicals Condition: Named audiences for UK Inventory Scale lot-tracked operations; industry wording does not prove regulatory compliance.
• Supplier-stated business-size fit: Small and mid-market businesses Condition: Inventory-specific supplier positioning. The separate Advanced platform is recommended for manufacturing, 3PL and EDI-heavy operations; this is not a hard employee, SKU or site ceiling.
• Supported platform: Web Condition: The Inventory FAQ describes access from a browser and phone without a local server. No supported mobile OS, browser version, scanner model or offline behaviour is established.
• Fishbowl Inventory is distinct from Manufacturing, Advanced Warehouse and Commerce Suite; family-level Desktop, mobile and EDI material does not establish Inventory support.
• Inventory QuickBooks and Xero scope is separate from Advanced setup; directionality and current connector prerequisites still need confirmation.

Workflow it supports

Use bills of materials and work orders to plan builds, check material availability and follow production inventory through fulfillment.

Capabilities and conditions

The Manufacturing page names QuickBooks but does not establish an Open API for this product edition. Confirm the supported QuickBooks version and any API access with the vendor.

Checks before choosing

Do not assume capabilities or commercial terms from Fishbowl Inventory or Advanced apply to Manufacturing.

Operational detail

The current Fishbowl manufacturing page attributes multilevel bills of materials to Advanced Manufacturing. It distinguishes the separate AI Manufacturing cloud product, which the vendor says currently supports single-level bills and kits. The directory listing requires a confirmed mapping to the current product and edition before applying these claims to a proposal.

A scenario to test

Use a finished product with a subassembly and one missing component. Ask the vendor to show the bill of materials, the resulting work orders, the shortage and the movement from raw material to work in progress and finished stock. Change the order quantity and inspect how the proposed edition handles the change.

Implementation boundary

Request the precise current SKU, product name and deployment model, together with the supported accounting version and any required add-ons. Ask for a written mapping from the directory’s Manufacturing name to the quoted edition; do not transfer a price or Advanced-only feature without that mapping.

Evaluation in practice

For a second evaluation, select an assembly with two levels of components, one subcontracted step and a finished item held in more than one location. Ask the vendor to show which parts of that example are supported by the exact quoted edition, what must be entered manually and how a shortage is reflected before a work order is released. After a partial build, compare component balances and finished quantities with the expected physical result. Ask the accounting owner to trace the resulting transactions into the supported accounting system and reconcile a sample. Before rollout, define ownership of bills of materials, part numbers, inventory locations and opening work in progress. The edition mapping should be included in the proposal and tested with the same workflows.

Workflows and scope

The product page describes service-vehicle stock, warehouse-to-truck transfers, barcode-linked job usage and phone scans queued until signal returns. A separate accepted vendor fact record lists a QuickBooks item-file export, Jobber job-parts CSV and Housecall Pro job-parts CSV; these are file exports, not native real-time integrations. API and webhooks are listed for the Unlimited plan.

The documented offline workflow is limited to phone scans queued until signal returns; other offline actions are not established. Device requirements, interface languages and country/currency availability are not specified.

Deployment and pricing

The pricing page checked 2026-10-28 lists per-subscription annual prices: Starter $129 (1 user; unlimited trucks/parts; email support), Pro $197 (up to 5 users; unlimited trucks/parts; priority support), and Unlimited $249 (unlimited users/trucks/parts; API and webhooks). The page offers a 14-day trial with no card. The dollar symbol is shown, but the ISO currency is not established. The stated terms include auto-renewal after 12 months unless canceled and a 14-day money-back period in the first paid year; these are not monthly invoice prices. Taxes, setup and hardware costs are not stated.

Review evidence

The bounded check on 2026-10-28 yielded no readable, dated, attributable review sample for this service. Profile discovery or blocked pages do not provide review content.

Warehouse workflows and deployment

The vendor describes inward processing on wireless handheld devices, location and SKU movements, pick lists, pick confirmation and delivery notes. Inventory activities include cycle counts, stock adjustments and ownership transfers, with stock and expiry reports.

Focus WMS describes barcode and RFID workflows and integration with ERP modules and third-party systems. Specific connectors, devices and any add-on requirements need confirmation for the proposed installation.

The vendor lists on-premises, cloud and hybrid deployment. Supported platforms, offline behaviour and interface languages should be confirmed for the selected version.

Warehouse workflows and deployment

The documented workflows include receiving and inspection, cross-docking, directed putaway, replenishment, wave planning, picking and packing. Slotting and 3PL billing are optional capabilities, so include them explicitly in the scope if needed.

Generix describes cloud and on-premises deployment and integration with ERP, OMS, material-handling equipment and WCS. Ask Generix to identify supported versions and the work required for each interface.

Operational detail

Generix distinguishes SOLOCHAIN core capabilities from extended capabilities. The latter list includes item traceability reporting, item recall reporting and a 3PL billing engine. Their appearance in the extended list does not establish inclusion in a particular contract.

Test a recall across owners

Create two customer-owned receipts of the same item with different lot identifiers. Ask the supplier to produce the proposed traceability and recall reports for one lot, following it through stock and shipment records. Verify whether returns or value-added steps appear, and compare report totals with the underlying transactions. Record which traceability and recall functions need to be enabled or separately scoped.

Translate work into a 3PL invoice

Use an agreement charging one owner per pallet received and for a special handling activity. Demonstrate how the activity is captured, reviewed and converted to a customer charge, then correct a quantity after the work is recorded. Reconcile the corrected charge against the operational transaction and ask whether the billing engine, customer-specific rules and accounting export are included. Assign responsibility for maintaining rates and approving exceptions.

Workflow it supports

The retained homepage supports ASN receiving, inspection, putaway, bin inventory, wave picking, packing and dispatch. Label printing is not established in that saved source.

Capabilities and conditions

The homepage describes an API and states AGPLv3 licensing with a separate commercial option.

Separate project documentation covers system architecture, prerequisites, deployment and license terms. Verify the supported stack and operating responsibilities against that documentation before implementation.

Checks before choosing

The saved material does not establish label-printing support, exact environment requirements, a production-ready mobile app or offline operation. Confirm each requirement before selection.

Desktop and Android workflows

Documented functions include multi-location inventory, serial and lot tracking, barcode scanning and receiving. One delivery can be received against several purchase orders, with partial quantities left open. Invoice viewing and printing with signatures depend on a Sales licence.

Desktop supports a local Windows or Windows Server installation and Android mobile devices. The published hardware list specifies Android 5.0 or later, a four-inch display and at least 512 Mb of free space, using the vendor’s wording; confirm the unit and current device and scanner compatibility. The Desktop edition is distinct from HandiFox Online, so its iOS support and integrations should not be assumed.

QuickBooks Desktop Pro, Premier, Accountant and Enterprise compatibility is described with regional-version conditions; confirm the precise QuickBooks version and country before purchase. Test the exact mobile transactions and synchronization needed when a connection is unavailable.

Warehouse-to-vehicle inventory

The documented inventory structure tracks parts by warehouse and vehicle, records transfers and compares available quantities with job requirements. It also describes job commitments, usage, returns and replenishment workflows. Ask to see how a technician records each movement and how an office user resolves discrepancies.

Operational detail

HVACSoftware.com describes its AI Dispatcher as placing suggestions in a review queue for a person to apply or discard. The page says proposed assignments consider skill, zone, truck capacity and drive time. It describes assist as the public workflow, while assign-on-create is a later shop setting rather than the illustrated default.

Test the proposed assignment

Enter an urgent cooling call while a qualified technician is already scheduled and the nearest truck lacks a required part. Ask the dispatcher to inspect the proposal, reject or change it and show the job that reaches the field. Separately verify where the part availability is read and how the office records a substitution or transfer; do not assume the dispatch proposal itself reserves inventory.

Reconcile the truck and job

After the visit, compare the part taken from the truck with the job record and the remaining vehicle balance. Include a part brought from the warehouse after the first assignment, and ask who posts the transfer and who resolves an unmatched usage entry. Request a live demonstration with your roles and data: the public example explains the proposed workflow, not an independent proof that every field or inventory integration is configured.

Workflow it supports

The dated product-fact record lists receiving, putaway, picking, packing, dispatch and returns, with serialized stock, FIFO/FEFO, kitting and traceability capabilities.

Capabilities and conditions

The same fact record categorizes Increff as a cloud WMS. Confirm scan-device support, named channel connectors and rollout arrangements for the proposed configuration.

Checks before choosing

The short saved excerpt itself only covers SKU variety, inventory volume and order types. The broader workflow statements above come from separate dated accepted facts; the full page body is unresolved.

Cross-docking and order allocation

Increff describes directing inbound goods to outbound orders without first placing them into normal storage. Its cross-dock description covers box- or item-level plans created through the interface or API, mapping an inbound shipment to one or more outbound orders, and quality control and sorting before the handoff to packing and dispatch.

For a practical demonstration, provide an inbound shipment containing several sizes, with one carton serving two outgoing orders and another requiring inspection. Ask the presenter to show the allocation, what the receiving team sees, and how an exception is resolved if the expected quantity differs from the arrival. Record which decision is made by the operator and which is configured in advance.

Returns as an inventory decision

The product FAQ describes a returns process spanning scan-based gate entry, goods receipt, quality control, reconciliation, restocking, return to vendor and quarantine. It also mentions image and video proof capture. These are vendor-described workflows; the exact steps and evidence requirements must be matched to the proposed implementation.

Bring two sample returns: a sellable item and a damaged item whose identity is uncertain. Ask how a worker distinguishes them, who can override a disposition, and how a correction reaches the selling channel. Check what information is retained for an audit and whether capturing evidence requires particular equipment or an additional service.

Deciding how channels share a warehouse

Increff says one WMS can support fulfillment for direct-to-consumer, marketplaces, wholesale and offline retail. Its product page separately describes cross-dock allocation at box and item level; a buyer should therefore assess both the order channel and the physical unit at which work is controlled.

Use the same SKU in a store replenishment order and a consumer order in the demonstration. Compare how priorities, packing rules and available stock are represented, and request a diagram identifying the systems that send orders and receive dispatch updates. Ask for named connectors, supported versions, error handling and responsibilities rather than assuming that every marketplace connection is included.

A useful acceptance test

The official page describes a combination of multichannel fulfillment, cross-docking and returns. These are separate operational paths, so a successful demonstration of one should not be taken as proof that the other two have been configured for a particular facility.

Before selection, agree a small acceptance script covering a normal inbound, a split cross-dock, a returned unit and a short shipment. Assign a business owner to each expected result and note the master data needed to run it. Compare vendors on the work required to configure and maintain that script, not just on the length of the feature list. Confirm implementation scope, training and any additional costs in the written proposal.

Inventory and integrations

The client matrix places stock counts and reports on Windows and web, rather than the mobile columns; internet access is required for the documented clients.

QuickBooks Online integration is documented for paid Simple Start, Essentials, Plus and Advanced plans in the US, Canada, UK and Australia; the selected inFlow plan must also support integrations. Setup includes mapping accounts and payment methods, and payment synchronisation can be one-way or two-way. Confirm the plan and mapping for your configuration.

Warehouse workflows

The accepted product evidence describes license plates, directed receiving and putaway, cross-docking, wave management, replenishment and kitting. It also lists 3PL billing and labour management; the precise entitlement and configuration should be confirmed with Infor.

Operational detail

Infor describes multi-owner inventory with configurable rotation rules and wave scheduling using filters including line count, weight and final destination. The filters and rules are vendor-described options, not evidence of the exact settings or commercial entitlement at a particular site.

Reconcile a multi-owner shortage

Prepare identical-looking goods owned by two clients, with two expiry dates for one owner. Create an order for the earlier lot and make its bin quantity lower than the record. Ask the team to show whether the proposed allocation respects owner and rotation rules, how the shortage is corrected and what remains available for each owner. Compare the before-and-after bin balances and license-plate totals with the transaction history.

Compare two waves

Use the same outbound orders to build one wave grouped by destination and another constrained by weight or line count. Review which orders are included, what happens to the exception order and how a supervisor releases or amends work. Ask which ERP messages carry owner, lot and shipment identifiers and how a rejected confirmation is reconciled. Agree the comparison criteria before treating a demonstrated wave as the intended production configuration.

Warehouse operations

The Warehouse Management add-on provides a mobile-friendly web client for pick and pack, purchase-order receiving, barcode validation and default bin assignments. Warehouse Operators have dedicated logins and do not see pricing or costs. Enablement and task toggles are required; the documentation says system-generated Unbatched batches cannot be selected for Pick & Pack.

The Warehouse client uses a modern browser and camera-equipped devices with QR and six-digit operator login; it is not a native iOS or Android app. Offline operation and universal scanner compatibility were not established. The language FAQ identifies English as the officially supported language.

Sales and accounting integrations

Shopify setup requires authorisation, mapping each Shopify location to a Katana location and explicit activation. Inventory and fulfilment have separate sync controls. The Free plan’s ecommerce FAQ limits its current ecommerce integration to Shopify.

Katana describes Amazon FBA inventory and delivered-order synchronisation separately from FBM open orders, stock and tracking. It also supports QuickBooks Online, not QuickBooks Desktop: the documented accounting flow includes invoices and bills, but creating Bills requires QuickBooks Online Essentials or higher. That is a QuickBooks subscription prerequisite, not the name of a Katana plan. Confirm which Katana plan and region permit the intended integration.

Plan and location limits

The Free pricing page advertises unlimited locations, while a January 2026 help article describes three locations and different archived-SKU counting. Confirm the current Free entitlement and Warehouse add-on scope before relying on either description.

Workflow it supports

Synchronize marketplace inventory and orders, then manage general picking, packing and shipping.

The Enhanced Warehouse add-on lists kits, FIFO/FEFO lots, serial tracking, a 3PL client portal and wave picking.

Capabilities and conditions

These named warehouse capabilities are associated with the Enhanced Warehouse add-on. Confirm that the add-on is entitled in your subscription and whether it is priced separately; verify channel and shipping connectors for your account.

Checks before choosing

The reviewed page does not establish device-specific or offline warehouse behavior.

Workflows and scope

Logiwa’s reviewed pages describe cloud fulfillment software for 3PL and brand operations. The captured material is a combined site record, so individual claims about automation, AI agents, mobile execution and connectors should be verified against the named product page and quoted plan.

Cloud infrastructure explicitly described; mobile/device/OS and offline specifics not captured. Offline use: Offline mode/device requirements not stated. UI language: UI languages not stated. Availability by country: Supported countries not listed on reviewed page.

Deployment and pricing

Logiwa describes pricing as custom and based on fulfillment volume and complexity. The reviewed pricing material does not establish a universal user, client, integration or implementation entitlement; confirm all included scope in the quote.

Review evidence

No readable SourceForge review record was retained in the bounded review evidence. Search-result discovery alone does not establish that the SourceForge profile had zero reviews.

Warehouse and freight workflows

The vendor describes ASN-driven or blind receiving with barcode capture, directed bin putaway, wave, batch, cluster and single-order picking, and shipping with labels and carrier handoff. Lot, serial and expiry tracking, cross-docking and cycle counts are also listed.

For U.S. customs operations, the vendor describes ACE-related filing and status workflows and controls for held inventory. Confirm filing eligibility, jurisdiction and the exact interfaces included in your implementation; a listed workflow does not by itself establish compliance for your facility.

Logiware lists direct integration with its TMS, EDI 940, 943, 944, 945 and 947, and connections to Cargo Spectre and CubiScan dimensioners. The customer portal lists PayCargo, CargoSprint and card payment options. Confirm availability and transaction or third-party charges in the proposal.

Devices and connectivity

Logiware describes the WMS on Android and iOS tablets and desktop screens, with Bluetooth or USB barcode scanners. It says scans can queue during a connection interruption and synchronise when connectivity returns; this does not establish that every workflow works offline.

Inventory and execution

Manhattan describes a unified inventory view across inbound, yard, reserve storage, pick sites, automated storage and outbound shipments. Its embedded warehouse execution system coordinates human work and automation; the product page describes integration with sorters, put walls, automated storage and robotics.

The vendor also describes fulfillment and slotting control. Its separate Manhattan Active Labor Management module is identified for functions including real-time task prioritization and gamification. Confirm module entitlement, equipment interfaces, device support, offline operation and UI languages for the proposed configuration.

Compare and ask

For an automation-focused execution layer, compare the scope and hardware interfaces with Exotec Deepsky.

Ask which labor, slotting and WES capabilities are included, and how interface changes are priced.

Operational detail

On its current ActiveWarehouse edition comparison, Manhattan lists core receiving and inventory control in Essentials, Enterprise and Enterprise Premier. It lists basic labor and material-handling equipment connectivity in Enterprise and Premier, while embedded WES is listed in Premier. These are current ActiveWarehouse edition descriptions; their relationship to the historical listing and a particular contract must be confirmed.

Choose an edition against actual work

List the work at the first site and the planned automation at the next. Ask Manhattan to demonstrate core receipt and inventory tasks in Essentials, then show the specific equipment-connection and labor requirements that would move the proposal to Enterprise. If embedded WES is needed, request a Premier demonstration of the exact decision boundary with the equipment controller. Record add-ons, excluded implementation work and the edition named in the quote.

Resolve existing-customer mapping

For an existing Manhattan Active Warehouse Management contract, ask the supplier to map the old product and purchased modules to the current edition names in writing. Compare current entitlements, interfaces, configurations and test environments with the proposed offer. Request a migration and regression-test plan, including changes to integrations, release cadence, commercial terms and any functionality that moves to an add-on. Do not infer an automatic upgrade or identical scope from the naming.

Warehouse workflows and modules

Documented functions include receiving, configured putaway and cross-docking, replenishment, stocktaking, picking, packing, labelling and shipping-load confirmation, plus analytics reporting.

Expansion modules are optional and include Multi-Carrier Shipping, Labor Management, Slotting, WMS for 3PL, Automation and Robotics, YMS, Manufacturing, Store Fulfillment, Marketplace Integration and Value-Added Services. Ask for the required modules and their individual terms.

The catalogue describes ERP and other software connections as well as interfaces to automation, RF scanners, RFID, printers, pick/put-to-light and voice devices. Specific models and integration work need confirmation.

Deployment and devices

Mecalux describes cloud SaaS and on-premises alternatives. For SaaS it describes supplier-managed infrastructure, maintenance and updates, and access from internet-connected computers, tablets and smartphones. Mecalux also describes an Android RF application with Smart UI; this is a configured warehouse client, so confirm device compatibility and access rights for the purchased deployment.

The supplier advertises an interface in 14 languages but does not name them in the product description. Confirm the required languages and offline workflows for the selected release.

Operational scope

Microlistics describes multi-client warehouse management and multi-site operations. Ask the supplier to demonstrate the exact receiving, inventory, picking, shipping and customer-specific workflows needed in the chosen configuration; the overview does not establish their detailed entitlement for every edition.

Operational detail

Microlistics says its 3PL WMS includes a third-party billing module and a web portal. The portal is described as providing stock holding, movement and age views and the ability to view and create purchase and sales orders. These are statements about the 3PL offer, not all Microlistics editions.

Reconcile two customer invoices

Set up two hypothetical clients with different receipt and storage rates. Receive the same quantity for each, add a special service for only one, and compare the resulting proposed charges with each agreement. Correct one receipt and ask how that affects the pending bill and its audit trail. Have an accounting user identify any manual charge, rate effective date and approval step before export.

Test portal isolation and data ownership

Sign in as each client and compare stock, movement history and aging for that client against the warehouse operator view. Ask each user to create or view a sample order and verify whether the other client can see it. Confirm who manages access, how a disputed movement is investigated and whether portal and billing are included in the quoted 3PL configuration. Specify the accounting interface and responsibility for mapping customer codes and rate changes.

Workflow it supports

Coordinate receiving, storage, picking, packing and shipping, with client-facing portal and billing workflows described in vendor materials.

Capabilities and conditions

Mintsoft is described as a cloud WMS with a mobile warehouse app and client portal. Confirm device compatibility, integrations and plan limits for the operating model.

The 3PL packages page states that mobile app user licences are separate. Include the required mobile licences when sizing scan-based warehouse workflows.

Checks before choosing

The reviewed product overview does not establish device-specific or offline warehouse behavior.

Inventory and plan differences

The documented stock workflows cover lot tracking, storage locations and warehouse transfers. Serial numbers are listed on Professional; barcode scanning, multiple stocks or sites, and packing are listed on Enterprise. API and webhooks are listed on Unlimited. Check the selected tier before relying on these features.

Capabilities and operating conditions

NetYield connects accounting and inventory records for seafood businesses, including case/pound units, lot history and fulfillment picklists.

• Deployment: Cloud.
• Supported platform: Not documented in the retained accepted evidence.
• Integrations: Not documented in the retained accepted evidence.
• Offline operation: Not documented in the retained accepted evidence.
• Industries: Seafood; Wholesale.
• Business size: Not documented in the retained accepted evidence.
• Application UI languages: Not documented in the retained accepted evidence.
• Verified country availability: Not documented in the retained accepted evidence.

Pricing, plan limits and additional costs

The retained product source and bounded pricing check did not establish a subscription or licence amount.

Review evidence and sample limits

The captured SourceForge listing reported no reviews at its recorded check; this describes that listing only.

Follow the cost of a seafood lot

NetYield describes inventory cost as including product price plus estimated procurement and production costs. It also describes delayed costing, under which product cost on invoices is determined when full procurement costs are known. Its site connects inventory transactions with accounts payable, accounts receivable and general ledger entries.

Ask the vendor to walk through a purchase whose freight or processing cost arrives after the goods are received. Follow the inventory value, invoice and accounting entries before and after the additional cost is known. Agree who can change the estimate, how corrections are approved and what the accountant can reconcile. Use your own cost categories and accounting period rules in the demonstration.

Cases, pounds and commercial quantities

The vendor says quantities and prices can be specified by case or pound, and that inventory shows item-level on-hand and available quantities as well as lot-level attributes. This combination is relevant when a sales transaction and the physical stock are expressed in different units.

Bring an example where cases vary in weight and an order is quoted by the pound but picked in cases. Ask the presenter to show what is entered at receipt, what the salesperson can promise, and what appears on the picklist and invoice. Test an adjustment for a damaged or short case, and check whether the proposed configuration preserves the quantities needed for your own reconciliation.

Test traceability in both directions

NetYield says every lot retains a history of inductions and releases. Its description of available stock and lot attributes offers a starting point for evaluating how seafood transactions are investigated; the site does not by itself establish a particular buyer’s recall procedure or regulatory outcome.

Choose a sample receiving lot and ask the vendor to trace its subsequent movements and customer shipments. Then start from a customer invoice and work back to the source lot. Introduce a partial release and a correction so the audit trail can be examined. Agree the identifiers, documents and output format required by your team, and test whether external warehouses contribute the necessary information.

Assess the system around the warehouse

NetYield identifies itself as cloud-based accounting and inventory software for seafood companies, and describes use by traders, distributors and processors. Its public overview emphasizes industry quantities, costs and lot history. That positioning should guide the evaluation of the surrounding physical warehouse workflow.

Map the handoff between receiving, sales, warehouse picking, invoicing and finance. For a third-party storage location, ask who enters receipts and releases, how frequently balances are reconciled and what happens when records disagree. Request a complete proposal for implementation, training, support, data migration and any required interfaces. Compare that scope with the physical execution tools already used at the site.

Where it fits and how warehouse work moves

Follow a bonded receipt through inventory records, duty or tax documentation and a bond-status report, then verify the site’s warehouse movement steps.

Documented functions and operating conditions

• Documented warehouse functions include: Bonded-goods inventory tracking; Customs document handling; Duty and tax records; Bond-status reports.
• Deployment: Cloud-based system

Operational detail

The vendor describes bond-status and duty-payment reporting together with automated bond release and stock updates. These are product descriptions; authority filing, duty treatment and the applicable procedure must be confirmed for the buyer’s jurisdiction.

Reconcile a partial release

Use one bonded receipt of 100 units and request a release of 30. Compare the proposed release document, bond status and remaining 70 units with the warehouse movement record. Then record a damaged unit and ask how the discrepancy is corrected, who approves the adjustment and whether the report retains the original entry. Have the warehouse and customs teams reconcile the same identifiers rather than comparing only summary totals.

Review the report with the filing owner

Give the responsible broker or customs specialist the sample bond-status and duty report, the authority reference and the underlying release transaction. Ask whether the fields and calculation are appropriate for the actual authorization and location, and who submits, monitors and corrects filings. Identify whether inventory data enters manually or from another system and test a rejected or duplicate release message. Put filing responsibilities and interfaces in the implementation scope.

Inventory and integrations

The documented functions include batch and lot tracking, expiry dates and serial tracking, alongside multi-hub stock and mobile workflows. Ask how these identifiers are captured and followed through your specific warehouse processes.

Omniful describes cloud deployment and an integration API. It does not establish a particular ready-made connector, supported device model or offline capability; confirm those details for your systems.

Workflow it supports

The official features page describes receiving-to-stocktake scanning, batch picking, lot/expiry/serial tracking, and production or kitting workflows.

A dated research note paraphrases a search-result observation of client logins and activity-based billing. The exact result text is not retained, and the 3PL page body was not available; treat these details as leads to confirm directly with the vendor.

Capabilities and conditions

The feature-page record describes APIs and integrations. It does not establish named device/OS requirements, webhooks or every 3PL portal and billing condition. The 3PL detail is only a paraphrase of a reported search observation, not a retained result or page body; confirm the relevant terms and site configuration with the vendor.

Checks before choosing

The 3PL detail is preserved only as a paraphrased research note about a search observation; the exact result text and page body were not retained. Verify client access and billing terms directly with the vendor.

Warehouse workflows and deployment

Oracle describes B2B and direct-to-consumer fulfilment, inventory visibility and material-handling equipment integration. The deployment documentation covers the cloud product; confirm the specific automation, upstream systems and supported integration scope.

Devices, offline data and integrations

The mobile application is documented for iOS and Android and supports compatible hardware scanners; check the specific model. Its My Scans view retains the device’s data offline and synchronises to cloud sheets after reconnection. Shared All data and remote integrations should not be assumed current while offline.

The vendor lists Google Sheets, Microsoft Excel, REST API, webhooks and Power BI integrations. The documented display-language options cover web and mobile, including English, Spanish, French, German, Ukrainian, Japanese and others. Confirm the required connector and permissions for your plan.

Workflow it supports

The Features page lists inbound, storage, cycle counting, waves, labor, yard, kitting and cross-docking workflows.

Capabilities and conditions

SAP groups features into basic and advanced capabilities. The Product Tour presents mobile/desktop, voice/AR, labor and automation workflows; confirm which are licensed and configured for the intended EWM mode.

The saved Features summary does not resolve whether a proposed deployment is embedded with S/4HANA or stand-alone. Confirm the architecture and release with SAP or the implementation partner.

Warehouse workflows

The documented scope includes receiving, cross-docking, multi-owner storage, picking by wave, order or load, inventory counts and dispatch. Confirm the modules and configuration needed for each process.

Workflow and operating use

Senior’s WMS page adds two useful controls beyond the general workflow list: multi-depositor rules and fiscal-document integration. A 3PL should test the exception where the supplier tax identity does not match the depositor or an item lacks an owner mapping. The public page does not say whether this blocks, warns or routes the receipt, so ask the supplier to demonstrate configured behavior and the correction record.

Integration and product boundaries

Senior describes cloud-native microservices and integration through its logistics ecosystem, while the broader suite lists TMS, YMS, tracking and routing as separate products. APIs/connectors for market ERPs, hubs and marketplaces are mentioned, but public material does not enumerate versions or commercial inclusion. Ask whether a fiscal-document change belongs to WMS configuration, ERP mapping or another module, and confirm release, change window and rollback responsibilities.

Buyer evaluation and fit

Demo a valid depositor receipt, then one with a mismatched supplier/tax identity and an item without an owner mapping. Inspect disposition, fiscal record, correction permissions and audit trace before stock is released. This is a buyer test proposal, not a tested result. Confirm the exact Brazilian tax flow and module schedule for the contracted SKU.

Capabilities and operating conditions

SkuVault Core is Linnworks’ warehouse and inventory product for ecommerce. Keep it distinct from Linnworks and its other products in comparisons.

• Multi-warehouse stock visibility
• Barcode pick and pack checks
• Kits and bundles
• Deployment: Not documented in the retained accepted evidence.
• Supported platform: Not documented in the retained accepted evidence.
• Integrations: Not documented in the retained accepted evidence.
• Offline operation: Not documented in the retained accepted evidence.
• Industries: Not documented in the retained accepted evidence.
• Business size: Not documented in the retained accepted evidence.
• Application UI languages: Not documented in the retained accepted evidence.
• Verified country availability: SkuVault Core is currently available in North America.

Pricing, plan limits and additional costs

Core pricing is tailored to order volume, custom needs and extra modules. A shared FAQ identifies Core separately; no numeric rate was verified.

• SkuVault Core: no numeric amount verified. North America only. Exact order allowance, modules, onboarding fee and term require quotation.

Review evidence and sample limits

Three selected historical 2023 accounts come from two contexts: two SourceForge reports about SkuVault and one review of its connected Shopify app. Their onboarding/support experiences differ; this small historical sample cannot establish present platform reliability.

Warehouse and customs workflows

SOFT describes multiple bonded warehouses, entry and exit, tariff records, warehouse documents and invoices. Connections include SOFT ERP, EDI, barcodes and MAVI YGM; confirm the specific interface, jurisdiction and setup required.

A related bonded/export module describes multiple storage locations without automatic allocation. Ask how locations are assigned in the proposed module and configuration rather than assuming automatic placement.

Workflow and operating use

SOFTTRANS describes bonded and export warehouse operations: warehouse entries and exits, multiple facilities, outgoing-unit tracking, warehouse documents, tariff definitions, price calculations and invoices. Its barcode workflow includes item and shelf labels, work orders, location-sorted pick lists and RF-terminal control of exiting goods. It also lists quantity, weight and volume differences across operations. These are specialized customs-linked records; buyers should map them to the goods categories and procedures their authorized operation actually uses, rather than treating the page as proof of regulatory approval or complete compliance.

Integration and product boundaries

The solution page groups SOFTTRANS and SOFTINTERFACE with EDI, barcode and customs integrations and names exchanges with SOFT transport applications and an authorized customs-broker system. It lists standard EDI flows for incoming customer shipment data and return of barcode or exit information. Importantly, the page states that labeled put-away has no automatic allocation. Related transport, container, export and customs products are separate named applications, not necessarily part of the bonded-warehouse purchase. Request module boundaries, interface specifications, sample messages, jurisdiction scope and data ownership.

Buyer evaluation and fit

A demo can trace an inbound bonded consignment through customer data, receipt, barcode labeling, placement, pick work order, RF-controlled exit and outbound customs/broker exchange. Include damaged goods and quantity/weight discrepancies, then ask how corrections are recorded. These are proposed checks, not a test report. SOFTTRANS suits evaluation where bonded/export work and partner exchange matter. A general WMS may better fit ordinary distribution without customs processes. Compare explicit customs workflows and interface dependencies, and have a customs specialist check statutory obligations. Also ask who is responsible for tariff maintenance, barcode label design, partner onboarding and exception correction. These responsibilities can affect both launch effort and daily control, even when the advertised feature list appears to match.

Inventory and accounting

Companion includes one location. Plus adds multiple locations, bins, transfers with shipping, pick tickets, serial and lot tracking, and barcoding. Pro adds work orders, work centres, work in process and job costing.

SOS documents authorised two-way QuickBooks Online synchronisation. Before connecting, compatible items must be prepared and QuickBooks Online inventory tracking disabled so SOS manages inventory; confirm the migration and accounting setup with the supplier.

Capabilities and operating conditions

Stockpit covers stock movement, purchasing, locations, lot numbers and expiry dates. Its core plans and connector pages have different scopes.

• Core Power covers stock levels and adjustments; Smart adds purchasing, multiple locations and delivery/reservation workflows, with 1,000 orders per month on the main-site plan.
• Pennylane Smart adds sales import, purchasing and multiple locations; its Boost connector tier adds kits/assemblies, packaging and lot traceability.
• Sellsy Smart includes purchasing and multiple locations; connector-specific Boost adds kits/assemblies, packaging and lot traceability.
• QuickBooks connector cards distinguish Locations (500 orders/month), Smart (1,000) and Boost (1,000, with kits/assemblies, packaging and lot traceability).

Pricing, plan limits and additional costs

Main site: Power EUR 19/user/month or EUR 190/year; Smart EUR 39/user/month or EUR 390/year, excluding tax. Connector pages have separate prerequisites; do not transfer their limits to core plans. Trial statements are explicit on the connector pages: Pennylane and Sellsy each advertise a free 14-day trial, and the QuickBooks page carries a 14-day trial notice.

• Power — Main site (monthly): EUR 19 per user per month, billed monthly; 1 user included; Stock levels, manual adjustments and valuation. Excludes tax.
• Power — Main site (annually): EUR 190 per user per year, billed annually; 1 user included; Stock levels, manual adjustments and valuation. Excludes tax.
• Smart — Main site (monthly): EUR 39 per user per month, billed monthly; 1 user included; Purchasing, multiple storage locations and delivery/reservation workflows; 1000 orders/month. Excludes tax.
• Smart — Main site (annually): EUR 390 per user per year, billed annually; 1 user included; Purchasing, multiple storage locations and delivery/reservation workflows; 1000 orders/month. Excludes tax.
• Pennylane: Power €19/user/month or €190/user/year; Smart €39/user/month or €390/user/year; Boost €59/user/month or €590/user/year. Prices exclude tax; the annual page advertises two free months. A separate Pennylane Essentiel or Premium subscription is required. Smart and Boost each list 1,000 orders/month; their API option is €30/month, with no API per-user unit stated.
• Sellsy: Smart €39/user/month or €390/user/year; Boost €59/user/month or €590/user/year. Prices exclude tax and the accounting subscription is separate; eligible Sellsy editions are Facturation or Ventes et Facturation. Both tiers list 1,000 orders/month; the €30/month API option is not stated per user. The page also lists an excess-order charge; confirm its billing mechanics before purchase.
• QuickBooks: Locations $9/user/month or $90/user/year (500 orders/month); Smart $39/user/month or $390/user/year (1,000 orders/month); Boost $59/user/month or $590/user/year (1,000 orders/month). Tax is excluded and the separate QuickBooks subscription is additional. The dollar ISO currency is unknown. The API option is $30/month, with no per-user unit stated; Smart or Boost is required for this connector configuration.

Review evidence and sample limits

The bounded check accepted no dated full review account. The exact QuickBooks App Store URL returned an HTTP 200 JavaScript/interstitial shell on the saved 28 October attempt; no identity, aggregate rating or review text was retained. This access limit does not establish that Stockpit lacks a QuickBooks connector.

Inventory and offline work

The vendor describes receiving, selling, moving and counting stock, barcode scanning, low-stock information and team access. Work can continue offline and changes sync when connectivity returns. Android is available through Google Play; the iPhone and iPad version was described as a TestFlight beta in the checked material.

Confirm the supported devices, interfaces to other systems and UI languages for the version you plan to deploy.

The free version limits the database to two stores and excludes money fields; Premium enables those fields and additional stores. Online seat allowances depend on the purchased plans.

Compare and ask

For an open-source parts inventory, compare InvenTree and its hosting requirements.

Ask how many Online seats are included, how conflicts are resolved after offline work, and whether the needed import and pricing features are in the selected plan.

Workflows and integration

The official Protheus integration guidance covers receiving documents and checks, dispatch orders and picking status. It documents a REST API connection; verify the required Protheus version and transaction configuration for your implementation.

Workflow and operating use

The SKU-specific Protheus integration guide says TOTVS WMS SaaS uses REST APIs implemented in ADVPL. For inbound, the ERP must release documents for integration; the guide filters eligible records by document type, stock-controlled transaction and positive quantity. For 3PL customers, the supplier's CNPJ and state registration must match a registered depositor. These rules are more decision-useful than attributing unrelated TOTVS family-page functions to SaaS.

Integration and product boundaries

The guide also describes the WMS returning receipt-check status to Protheus, including finished or divergent checks, and says custom fields such as observation and process subtype require Protheus API customization. This is specific to the documented Protheus integration; it does not establish that other ERP products use the same API or constraints. Confirm the Protheus release, branch mappings and customization responsibility for the project.

Buyer evaluation and fit

Build two integration cases: one eligible inbound document linked to a depositor, and one with a nonmatching supplier registration or missing warehouse-item relationship. Verify which record is withheld, what reason is returned and how the WMS check status updates Protheus. This is buyer guidance, not a performed integration test. Keep other TOTVS product-line capabilities out of the SaaS acceptance scope unless separately documented.

Where it fits and how warehouse work moves

Map receiving and cycle counts into barcode-supported inventory, then follow FIFO/FEFO picking, batching, shipping labels and returned-item quality checks.

Documented functions and operating conditions

• Deployment: Cloud
• Documented warehouse functions include: Receiving; Cycle counting; Barcode scanning; FIFO/FEFO; Picking and batching; Shipping labels; Returns quality checks.
• Industry applications: Ecommerce; Retail

Workflow and operating use

Unicommerce describes configurable facility allocation rules that can consider inventory levels, warehouse capacity and order value. This is a separate decision from the later carrier or manifest step: the chosen facility affects which stock is committed before dispatch planning begins. The product page is ecommerce-oriented and its broad integration totals are vendor claims, so test the specific marketplace, channel and warehouse combination you intend to deploy.

Integration and product boundaries

Ask how rule priority behaves when the preferred facility lacks stock or capacity, and when a multi-line order can be split. The page describes facility routing and centralized inventory visibility, but it does not publish your connector's refresh interval or failure semantics. Confirm when channel availability changes after allocation, cancellation and return, and which system is authoritative if two channels request the same unit.

Buyer evaluation and fit

Use two facilities with different on-hand quantities and one capacity constraint. Run a high-value order and a normal order, then inspect the chosen site, reservation and channel-visible quantity. Repeat after cancellation and a return to check reconciliation. This is a buyer test plan, not an observed outcome. Verify the exact integration and routing rules in the configured Unicommerce edition.

Inventory and fulfilment

Documented functions include purchase orders, bills of materials, production, batch tracking and inventory forecasting. The B2B material also describes online ordering, bulk-unit breakdown, picking, packing and dispatch.

The pricing comparison lists WMS and multi-bin functionality separately; confirm their inclusion, integration scope and device requirements for the selected package.

Warehouse workflows and integrations

Vinculum lists receiving, putaway, picking, cycle counts and shipping, alongside configurable 3PL billing. It describes Android warehouse workflows and desktop or tablet access. Availability and configuration of each function should be confirmed.

The broader Vin eRetail suite describes connections to marketplaces, shipping providers and ERPs including SAP, Tally and QuickBooks. Those suite-level claims do not establish that every connector is included in the WMS agreement. Confirm exact editions, fees, offline operation and UI languages.

Compare and ask

Compare another WMS when the project needs integrated warehouse execution and automation.

Ask how 3PL billing rules are configured per client and which mobile and ERP integrations are included in the implementation.

Workflow and operating use

Vin eRetail's product page lists FIFO, FEFO and LIFO as inventory-rotation choices. For a multi-client warehouse, the relevant test is whether rotation is applied within the correct client's stock pool and whether expiry/batch attributes travel with the selected unit. The page also describes synchronization of marketplace inventory after orders and returns, which makes allocation timing and the stock state sent to each channel part of the decision.

Integration and product boundaries

The same page cites historical Gartner Magic Quadrant recognition for 2017-2022. Treat that as a dated vendor statement about past coverage, not a current ranking or proof of product quality. The current product page combines retail, marketplace and 3PL content; a long list of capabilities does not establish which features or integrations are included in a specific commercial package.

Buyer evaluation and fit

Test two clients holding the same SKU with different expiry dates, then process an order and a return. Check that the intended rotation rule selects stock only from the right client, and that the updated available quantity reaches the intended channel. Ask which record and timestamp are authoritative when synchronization is delayed. This is buyer guidance, not a tested Vin eRetail deployment.

Warehouse workflows

The documented scope includes goods inwards, picking management and dispatch control. For 3PL use, confirm what each client can see and do, how stock ownership is represented and how customer reporting is configured.

Vision Bond adds bonded-warehouse reporting. Confirm its prerequisites, jurisdiction and commercial terms instead of assuming that the base WMS includes it.

Workflow and operating use

An accepted official capture dated 2026-10-28 described the Vision WMS reporting database as available through ODBC, with Excel, Crystal Reports or other ODBC-compatible software named as reporting routes. The same historical text listed built-in report areas including goods-in, stock, goods-out, security audit trails, sales, site operations and customs/excise. The exact reporting page later returned 404; treat this as dated capability evidence, not a current license or support entitlement.

Integration and product boundaries

For a warehouse audit, distinguish direct read access from a supported reporting product: the capture does not specify schema stability, credentials, read-only safeguards, refresh timing, or whether external reports are covered by support. Nor does a report category prove that a customer receives a particular template. Ask for a current data dictionary, access method and permitted extraction pattern before connecting BI tools to operational data.

Buyer evaluation and fit

Choose one reconciliation report, such as stock movement or security audit activity, and ask the vendor to show the source fields, time basis, customer/owner scope and correction history in the proposed release. Confirm whether the report can be exported without direct database access. The retained details are historical supplier text, not a current deployment claim.

Capabilities and operating conditions

Nehlum WarehouseOS joins stock movement from receiving and putaway through picking, packing and dispatch.

• PO-linked receiving and inspection
• Bin-level putaway and slotting
• Returns inspection with restock, quarantine or disposal routing
• Deployment: Not documented in the retained accepted evidence.
• Supported platform: Not documented in the retained accepted evidence.
• Integrations: vendor onboarding and FAQ materials describe ERP, store and scanner connections, including named examples; compatibility, configuration and entitlement need confirmation.
• Offline operation: Not documented in the retained accepted evidence.
• Industries: Not documented in the retained accepted evidence.
• Business size: Not documented in the retained accepted evidence.
• Application UI languages: Not documented in the retained accepted evidence.
• Verified country availability: Not documented in the retained accepted evidence.

Pricing, plan limits and additional costs

Saved product/onboarding/contact/legal pages state no software tariff, licence metric, billing cadence, minimum term or usable trial. Website-use terms are not a software agreement.

Review evidence and sample limits

A bounded exact-product search response was retained on 2026-10-29; it did not establish an independent profile or dated review account. Namesakes and employer reviews are separate.

• This is a bounded public-source check, not an exhaustive survey of every marketplace or proof that no reviews exist. No account access, login, CAPTCHA, vendor contact or form submission was used.
• Search output is discovery only. Publisher crawl/cache age, actual retrieval time and any historical account date remain separate. Supplier testimonials, company/employer opinions and similarly named products are excluded.

Items, assets and orders

Henga describes creating items in different warehouses with SKU, expiry and warranty attributes; assigning assets to people; maintaining access levels; and logging inventory and order activity. Sale and lease orders can record lost or damaged items and checks when leased items return.

Confirm supported integrations, offline operation, devices, application languages and availability for the intended location.

Compare and ask

Compare another inventory tool if team stock counts and offline synchronisation are central to the decision.

Ask how leased items are checked back in, which identifiers are mandatory and how data can be exported.

Workflow and operating use

An accepted official Wezza capture describes filterable and exportable reports for inventory and assets. That makes the report-to-reconciliation step a useful selection question: can the exported view retain the identifiers and dates needed to compare recorded stock or asset condition with a source register? The accepted wording does not establish a particular file format, scheduled export or accounting/WMS connector.

Integration and product boundaries

The homepage itself returned 403 during independent review, so this enrichment relies on retained official-source material rather than a fresh full-page read. Do not infer current plan limits, KES prices, tax terms or availability from earlier page text. Ask the vendor for current documentation and an export sample before comparing its commercial plans or moving records.

Buyer evaluation and fit

Request a sample export for one location with a stock adjustment and one asset whose condition changed. Check whether filters, date ranges and item identifiers persist in the exported file, then reconcile it with the current register. This is a buyer validation step, not a report of a Wezza trial. A separate WMS is still worth evaluating if the operation needs directed warehouse tasks.

Workflows and scope

Transfer orders require at least two warehouses. A transfer can be marked In Transit for later receipt or completed and received immediately; barcode scans can add items and increase quantities. Serial and batch tracking require an eligible plan.

Zoho lists iOS and Android apps. The Android listing for version 2.22.0 requires Android 8.0 or later. The US Apple listing requires iOS/iPadOS 16 or later and lists the Apple client’s supported languages. An administrator can configure the organization interface language; the settings page does not give a complete language list.

QuickBooks Online connection requires an active account, one Zoho organization per QuickBooks organization, matching organization countries and the same base currency. Data modules and synchronization frequency are configurable; some account data syncs daily or manually.

Deployment and pricing

The pricing table captured October 29, 2026 lists a free tier with 50 orders (no period is stated), one user and two locations. Annual-billed paid prices are $29 per organization per month for Standard, $79 for Professional, $129 for Premium and $249 for Enterprise. The displayed dollar sign’s ISO currency is not identified, and the listed rates exclude local taxes.

Those paid tiers list monthly order limits of 500, 3,000, 7,500 and 15,000 respectively. User limits are two for Standard, Professional and Premium, and seven for Enterprise; location limits are two, four, six and ten. Professional adds serial/batch tracking; Premium lists up to 2,000 bins per location and Enterprise up to 5,000.

Review evidence

One TrustRadius account dated April 21, 2022 is marked incentivized. It concerns the web service at that time, not the current iOS app; one historical account is not evidence of current performance or broad customer sentiment.