Best ERP and MRP Software with Warehouse Workflows

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.

Warehouse work inside the ERP

The native WMS covers receiving and putaway, barcode scanning, location movement, picking, packing and shipping. Mobile scanning and automated workflows connect warehouse actions to Acumatica Cloud ERP.

• The Inventory Management page describes quantities, availability, allocations, movements and replenishment across warehouse locations in the connected system.

Confirm the licensing boundary

The cited WMS page presents warehouse management as part of Acumatica Cloud ERP. It does not establish a standalone WMS license or a WMS-only price; the accepted pricing record keeps that price unknown.

Operational detail

Acumatica’s feature guide treats Warehouse Management as a licensed feature group. When it is included in the license, an administrator can enable individual functions used in the warehouse configuration. Receiving supports receipt and putaway using handheld barcode scanners; Inventory Operations covers issuing, receiving, transferring and counting with scanners or mobile devices.

A scenario to test

Use a receipt with a short shipment and a transfer between two locations. Ask the partner to show the documents and stock balances before and after each scan, then correct an entered quantity. Record which features must be enabled, which device is used, and who can reverse an error.

Implementation boundary

Agree how open pick lists and receipts will be finished before changing feature settings. Have the partner identify the licensed features, document ownership, scanner setup, and the responsibilities of the ERP implementation team.

Evaluation in practice

For a second test, use a wave containing several shipments for the same SKU but different destinations. Ask the partner to show how workers identify the correct shipment and location and what happens when the physical count is lower than expected. Follow the discrepancy through a correction and a subsequent inventory count. Give the team both a barcode that matches the item and one that does not, and record the actual response on the proposed scanner. Before rollout, assign ownership of item identifiers, locations and opening balances, then reconcile a small migrated sample to the old system. Ask how the partner tests user permissions and returns a transaction to a usable state after a mistake. Compare the resulting work with the present paper process and identify any additional manual handoff.

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.

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 and ordering workflows

The documented warehouse functions include barcode scanning, lot and expiry tracking, serialized equipment and quarantine of suspect stock. Confirm how these functions work with your receiving, picking and recall procedures.

The B2B ordering portal describes customer-specific prices, online orders flowing into the ERP, and order history and status. Confirm whether the portal is included in your proposal and which customer-facing functions are configured.

Workflow it supports

Coordinate inventory and order management with shipping, fulfillment, purchasing forecasts and retail analytics across sales channels.

Capabilities and conditions

Brightpearl is presented as a retail operating platform rather than a warehouse-only tool. Its integrations navigation names ecommerce, accounting and payment services; confirm connector and feature availability for your edition.

Checks before choosing

The reviewed product overview does not establish deployment options or offline warehouse behavior.

Maintenance scope

Dematic identifies equipment condition monitoring and maintenance scheduling as Sprocket capabilities. Ask for a demonstration using your asset types and maintenance procedures, including how data is collected and how work is scheduled.

Operational detail

Dematic describes Sprocket as asset management software that tracks equipment condition and schedules maintenance with standard operating procedures and compliance procedures. The vendor associates this product with equipment health and maintenance, a distinct scope from its WMS, WES and WCS offerings.

A scenario to test

Choose one conveyor motor or other representative asset and ask to see its condition record, a scheduled maintenance task and the procedure attached to that task. Follow the job through completion and ask where the maintenance history is available. Include an overdue task and a condition finding that requires follow-up.

Implementation boundary

Prepare an asset hierarchy, maintenance intervals and existing procedures for the demonstration. Confirm how equipment data enters the product, who approves changes, how records are exported and which capabilities belong to Sprocket in the quoted configuration.

Evaluation in practice

For a second maintenance scenario, provide an asset with a recurring inspection, a spare part and a safety procedure. Ask the supplier to show the asset record, the planned task, the person responsible and the history after the task is completed; ask separately how spare parts would be represented in the proposed scope. Introduce an overdue inspection and request a demonstration of the escalation process, recording which steps are automatic and which are manual. Before rollout, clean and import a small asset hierarchy and compare it with the existing maintenance register. Define ownership of procedure revisions, access permissions, data retention and export. Request a separate interface design for condition data rather than assuming every machine can report directly into Sprocket. Also request an example of the completed maintenance record and agree who can amend it after review.

Capabilities and operating conditions

Dolibarr is an ERP and CRM application with stock and warehouse management in its distribution. Administrators enable the stock module; it is not a standalone WMS.

• Warehouse stock movements
• Stock corrections and transfers
• Replenishment
• Optional lot and serial tracking
• Deployment: Self-hosted; stock management is included in the distribution.
• Supported platform: the official README describes standalone and web-application use; supported operating systems and offline operation are not established.
• 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: Multi-language support is documented; the full language list and translation coverage are not specified.
• Verified country availability: Not documented in the retained accepted evidence.

Pricing, plan limits and additional costs

Dolibarr is GPL version 3 or later and can be self-hosted. Community help, commercial partners and hosted services have separate terms.

• GPLv3-or-later distribution: no numeric amount verified. No monetary zero is inferred solely from the open-source license.
• Hosting or commercial partner support: no numeric amount verified. Separate provider choice and terms; no representative amount adopted.

Review evidence and sample limits

Two dated SourceForge accounts (2025-04-14 and 2023-06-22) discuss the Dolibarr ERP/CRM project broadly. Neither identifies warehouse use; the small project-wide sample cannot establish sentiment about the stock module.

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.

Where it fits and how warehouse work moves

Map the required location and license-plate flow, then verify receiving, putaway and picking behavior in the applicable release. The second retained Microsoft excerpt says only formula processing is supported for catch-weight products; surrounding licensing and unsupported-combination detail is not preserved here.

Documented functions and operating conditions

• Short retained Microsoft excerpt: “tracks inventory down to the individual location and license plate.” Dated accepted analysis also lists directed work, receiving, putaway and picking, but the full overview page body is not retained.
• Short retained Microsoft catch-weight excerpt: “Only formula processing is supported for catch weight products.” The original surrounding paragraphs are not retained, so the exact license, handling-policy and unsupported-combination details require confirmation against the target release.

Stock workflows

The stock documentation lists purchase receipts, delivery notes, stock entries and reconciliation alongside batch and serial-number records. It also indexes picking lists and putaway rules. Check the documentation for the deployed version and configure the workflow to match your operation.

Self-managed deployment is available for ERPNext. The available material does not establish offline operation, every supported device or a complete set of interface languages.

Self-hosting

ERPNext is offered for self-hosting under GPL-3.0. Running and maintaining the server and arranging implementation or support are separate decisions.

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.

Returns and deployment

A returned item can be tied to the original order; a serialised item can be checked for warranty coverage, and a repair or replacement can be sent on a linked warranty order. Reason and status codes help identify returns awaiting inspection. If inspection finds no problem, the item can be returned to stock and a fixed or percentage restocking fee deducted from customer credit.

The vendor lists cloud and customer-hosted Premise arrangements. In modifiable cloud, changes are made by the Fitrix team on multi-tenant hosting, or by Fitrix or the customer team on single-tenant hosting.

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.

Capabilities and operating conditions

FreshByte is food-distribution ERP with seafood-oriented actual-weight inventory and traceability through processing or repacking.

• 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: Seafood; Food and beverage; 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 seafood page and bounded pricing search did not establish a current tariff.

Review evidence and sample limits

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

Workflows and scope

The ERP page describes handheld scanning for lot/pallet inventory and actual-weight capture, customer-owned inventory, and billing based on warehouse activity. Feature availability depends on system configuration; confirm these flows on the proposed system.

The reviewed page does not establish supported devices, offline operation, interface languages or sales countries.

Deployment and pricing

The official Inspired Portal ERP source describes customer/order/inventory functionality, but no verified vendor monetary tariff or package contract was located in this bounded check. Unresolved terms include Base ERP and warehouse/inventory module fee, Users/sites and required accounting/integration components, Deployment, implementation, support and training cost, Invoice/minimum/renewal, tax and trial.

Review evidence

Two dated SourceForge review records for Inspired Portal were present in the bounded metadata check. The review bodies were not reread for this revision, so the records do not support a new thematic summary here. The sample covers named product reports, while releases and configurations may vary.

Parts, stock and purchasing

The project describes parts management, stock control, supplier records and external integrations or custom plugins. Its purchasing documentation includes suppliers and purchase orders. Confirm the capabilities and plugins supported by your installed version.

InvenTree is open source; deployment, backups and operational support require an explicit hosting arrangement. The reviewed sources do not establish offline operation, all UI languages or country-specific service coverage.

Compare and ask

For van-based counts, compare Hoardo; check whether supplier ordering and deployment flexibility matter to your team.

Ask your hosting provider about upgrades, backups, plugin maintenance and support charges.

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.

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.

Capabilities and operating conditions

OpenStock is the TMBeaver Python/Flask application backed by SQLite. The retained repository documentation describes self-hosting; it does not establish whether a managed offering is available.

• Goods receipts
• Stock transfers
• Production bills of materials
• Deployment: Self-hosted Python/Flask application backed by SQLite.
• 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: Not documented in the retained accepted evidence.

Pricing, plan limits and additional costs

The exact TMBeaver repository carries an MIT licence; hosting, implementation, hardware and support remain separate.

• MIT software license: published amount 0 per software license. Permission free of charge under MIT; this is not a hosted-service or implementation price.

Review evidence and sample limits

The bounded search surfaced an editorial security review, not an attributable customer account; its result headers are discovery evidence only.

Workflow it supports

The full page describes lot tracking from receipt to shipment, receiving and shipping scans, FIFO, and catchweight production scheduling.

Capabilities and conditions

The saved page presents warehouse, inventory and production functions together. It also describes PF Quality as optional; confirm whether that quality module is in the proposed scope.

Checks before choosing

The full page is retained, but the reviewed material does not establish hosting or device/OS requirements.

Operational detail

Advantive describes ParityFactory production management as generating ingredient and finished-goods picklists and tracking inventory through work in progress. It separately describes PF Quality as a quality module; the proposed package and any equipment connections require confirmation.

Trace ingredients through one batch

Create a sample recipe with two ingredient lots and a planned finished quantity. Ask the supplier to show the ingredient picklist, record a substitution and follow consumption into work in progress and the finished-goods picklist. Reconcile expected versus actual ingredient quantities and finished yield. Introduce a missing or incorrect lot label and ask how the operator corrects it without obscuring the original entry.

Decide whether quality scope is needed

Repeat the batch with a quality hold and a measured result that needs review. Ask the team to identify what is available in the base proposal and what requires PF Quality, a scale interface or another system. Trace who records the result, who releases or rejects the batch and how the decision appears in the lot history. Specify the quality module, devices, implementation work and reporting requirements in the written offer.

Capabilities and operating conditions

Part-DB manages electronic components across locations with BOM-linked withdrawals, barcode labels and inventory history. It is an open-source web app installed on a server.

• Assign electronic parts to categories, footprints, manufacturers, tags and multiple storage locations; attach datasheets or images and filter by component parameters
• Use project BOMs to calculate buildable quantities and withdraw needed components; record inventory/user changes and revert older part versions
• Generate part, lot and storage-location labels using reusable profiles, WYSIWYG/HTML content and data placeholders
• Deployment: Self-hosted on a web server; the main documentation lists MySQL, SQLite and PostgreSQL database backends.
• Supported platform: Web.
• KiCad 8+ connects through Part-DB’s HTTP library using an API token; the integration is read-only. Usable EDA metadata controls normal visibility, while Force visibility can override it and force parts or categories visible or hidden.
• Optional SAML single sign-on can connect an existing LDAP or Active Directory service through an intermediary such as Keycloak.
• The main documentation also describes an API for other applications and import/export tools for data exchange.
• Offline operation: Not documented in the retained accepted evidence.
• Industries: Electronics and components.
• Business size: Hobbyists; Makerspaces; Small companies; Universities.
• Application UI languages: German; English; Russian; Japanese; French; Czech; Danish; Chinese.
• Verified country availability: Not documented in the retained accepted evidence.

Pricing, plan limits and additional costs

Part-DB uses AGPL-3.0-or-later. Self-hosting is possible; server and maintenance costs are separate from the licence.

Review evidence and sample limits

The bounded search retained no dated independent customer-review sample; no rating or theme is inferred.

Workflows and scope

The official PRISM by Intelik page captured on 2 November 2026 describes distribution, inventory visibility, sales and procurement. It describes batch tracking, expiry alerts and purchase orders through batch-level receipt. The page does not establish the full edition matrix; confirm entitlements and deployment.

The 2 November official page does not establish supported devices, deployment, offline operation, interface languages or availability outside Pakistan. Confirm these requirements with the supplier.

Deployment and pricing

A limited check of the official homepage and its Pricing control on 29 October did not reveal a software tariff. A free-trial invitation appears on the 2 November official page, but its conditions were not established. Ask for a written quote with currency, billing, modules and term.

Review evidence

The 2 November vendor page contains testimonials; these are not independent reviews. Review-based fit remains unassessed.

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 field work

The vendor describes warehouse and truck stock, vehicle par levels, replenishment alerts, purchase receipts and technician material usage. Device platforms, offline workflows and accounting or field-service integrations should be confirmed for the selected subscription.

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.

From parts to production

The vendor describes stock by location and lot, supplier lot references and holds. Planning uses bills of materials, stock, open purchase orders and work orders to identify shortages and draft purchase orders or planned work orders. Shop-floor staff can update routing steps on a phone.

TrackFinch says it is not accounting or payroll software and does not have a QuickBooks or Shopify connection. The vendor describes CSV import and export; confirm other integrations and the supported device and offline requirements for your workflow.

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.