QAD Adaptive Warehousing: Real-Time WMS Built for Manufacturers

Key Takeaways

• QAD Adaptive Warehousing is an ERP-native WMS that connects inventory, production, and shipping in real time without spreadsheets or disconnected systems.
• Warehouse algorithms automate putaway, picking, and shortage clearance decisions, replacing manual location selection with rules-based routing.
• Material Routings define the physical path inventory follows through each warehouse area, from receiving through storage to shipping.
• Tenneco Wuhan replaced SAP WMS with QAD Adaptive Warehousing in under 3 months, with Arista Consulting raising and resolving more than 40 QAD product tickets to certify the solution before go-live.
• Arista Consulting designed a QAD equivalent for SAP COGI, an error-correction process for failed goods movements, as part of the Tenneco Wuhan implementation.

In October 2025, QAD released its Adaptive Warehousing and Automation Solution functionality. By January 5, 2026, Tenneco's Wuhan, China manufacturing site was live on it, having migrated from SAP WMS in under 3 months. During that window, Arista Consulting raised and resolved more than 40 QAD product tickets to certify the solution for production use, and designed custom QAD equivalents for critical SAP processes the site depended on.

QAD Adaptive Warehousing is built to deploy fast in manufacturing environments where waiting is not an option. This guide covers how the system works, what separates it from basic inventory management, and what a real implementation looks like.

Inventory Management and Warehouse Management Are Not the Same Thing

These two capabilities are often used interchangeably, but they address different problems. Understanding the distinction matters before choosing or configuring either.

Inventory management focuses on capturing, monitoring, and tracking inventory movements. It handles purchase receiving for raw materials, picking and packing for finished goods, cycle counting for adjustments, and issuing and receiving in production across raw materials, work in progress, and finished goods.

Tools like QAD AS and Eagle support barcode scanning for real-time transactions. The primary goals are minimizing excess stock, managing shortages, and maximizing efficiency across production and distribution.

Warehouse management addresses a different set of problems. It manages high-volume inventory movements across defined physical areas, storage zones, bins, and shelves. It optimizes storage through bin size and capacity constraints.

It drives labor efficiency through predefined rules for putaway, replenishment, and picking, real-time monitoring, and analytics on warehousing activity. It also integrates with external equipment and systems.

Inventory management tells you what you have. Warehouse management tells workers where to go, what to do, and in what order.

What Is QAD Adaptive Warehousing

QAD Adaptive Warehousing is an ERP-native warehouse management system designed for manufacturers. It is built directly into QAD Adaptive ERP, meaning warehouse operations share the same data foundation as production planning, procurement, finance, and shipping. There is no middleware, no file sync, and no delayed reporting.

The system organizes warehousing through a defined hierarchy. A site can link to multiple warehouses within the same domain. A warehouse can be linked to multiple sites within the same domain.

Within each warehouse, there are warehouse areas, which are physical spaces where specific actions are performed. Areas can be functional, such as Shipping or Receiving, or non-functional, such as long-term storage locations.

Below areas sit storage zones, which are sub-elements of an area where movement rules are defined. Within zones are warehouse locations (aisles, racks, shelves, bins) and work zones, which group sections of the warehouse that share common activities by labor or device type. Examples of work zones include Receiving and RM Storage, or Production and RM Storage.

This hierarchy is what makes rules-based automation possible. Every movement decision in QAD Adaptive Warehousing is made with reference to this structure.

Warehouse Jobs and Warehouse Tasks

QAD Adaptive Warehousing separates warehouse activity into two levels. Warehouse jobs are groups of actions that need to occur together.

Examples include picking a production order picklist, picking a sales order pre-shipper, and putting away inventory received from a supplier against a specific PO Receiver. Jobs represent the complete unit of work triggered by a business event.

Warehouse tasks are the lower-level individual actions that occur within a job to move inventory. Tasks are categorized into types, prioritized, and assigned to specific users for efficient completion. A single job typically generates multiple tasks routed to different workers based on their equipment, work zone, and task type assignment.

Task types in QAD Adaptive include Putaway, Replenishment, Picking (covering Sales, Distribution, and Production Orders), Count (Cycle Count), Inspect (Inspection), Recount (Cycle Recount), and Transfer. Each task type carries a confirmation mode of either Manual or Auto depending on how it is configured.

Warehouse Task Type Assignments define the priority sequence and queue order for each warehouse user. A Forklift Driver user might be assigned Queue 1 with Putaway Auto and Transfer Auto, Queue 2 with Replenishment Auto and Picking Auto, and Queue 3 with COUNT Auto and RECOUNT Auto.

This ensures the right work reaches the right person in the right order without a supervisor manually directing traffic.

Material Routings and Routing Assignments

Material Routings define the physical path inventory takes through the warehouse for a given transaction type. Each routing is a sequence of steps, with each step specifying a task type and a destination area.

Three common routing patterns appear frequently in QAD Adaptive deployments. A Putaway routing runs in two steps, first moving inventory from the Receiving Area, then placing it into the Storage Area.

A Sales Order Picking routing also runs in two steps, picking from the Storage Area and then moving to the Shipping Area. A Multi-Step Sales Order Picking routing runs in three steps, picking from the Storage Area, moving to Packing and Staging, and then moving to the Shipping Area.

Routing Assignments link a specific transaction type to a material routing for a given combination of site, warehouse, item, address, from-area, from-zone, from-location, and destination location.

This granularity means different items, customers, or areas can follow entirely different physical paths through the same warehouse without any manual override.

Warehouse Algorithms and How QAD Decides Where to Put and Pick

When putting stock away in functional and non-functional areas, the system uses different routines. These routines are called algorithms. Algorithms remove the decision burden from individual workers and enforce consistent, optimized inventory placement and retrieval.

QAD Adaptive Warehousing includes the following algorithm types.

Warehouse Algorithm Assignments link a specific algorithm sequence to a transaction type, site, warehouse, item, and address.

A putaway transaction on a specific site might first try algorithm 104 (same item and lot), then 103 (same item), then 102 (first empty location), then 101 (first storage location).

A customer-specific picking transaction can use a dedicated picking algorithm while all other customers follow the standard sequence.

Real-World Implementation at Tenneco Wuhan

Tenneco's Wuhan, China, manufacturing site was running SAP ECC with SAP Warehousing functionality that had been implemented a couple of years prior.

The site had developed unique processes built on custom SAP warehousing functionality, which meant a migration to QAD Adaptive required designing QAD equivalents rather than a straightforward configuration exercise.

According to Nilay Dashondi, Business Partner and Principal Consultant at Arista Consulting with more than 20 years of ERP experience, the project faced two compounding challenges.

The first was a very tight timeline. The second was the need to build QAD equivalents for critical SAP processes that had no standard out-of-the-box counterpart in QAD Adaptive.

QAD Adaptive with Warehousing and Automation Solution functionality was available from October 2025. The target go-live was January 2026, leaving approximately 3 months from feature availability to production deployment.

Arista extensively tested the Warehousing and AS functionality and certified it for use at the Tenneco Wuhan site. During that process, more than 40 QAD product tickets for bugs and issues were raised and resolved.

Two custom processes were designed and implemented specifically for Wuhan.

1. QAD Equivalent for SAP COGI

COGI is an SAP transaction code used to process and correct failed automatic goods movements during production confirmations, particularly when the Backflush indicator is set.

It acts as an error log, synchronizing inventory and production order data by identifying issues such as missing stock, wrong storage locations, or incorrect batches.

Common uses include resolving failed goods issues, correcting errors, managing batch discrepancies, and clearing pending failed transactions before month-end financial close.

Because Tenneco Wuhan relied heavily on backflush processing, a QAD equivalent was a firm requirement. Arista designed an automated COGI process in QAD Adaptive that runs in six steps.

1. BOM Explosion. The system determines all required raw material components and quantities from the bill of materials.
2. Shortage Identification. Required BOM quantities are compared against WIP stock to identify shortages.
3. COGI Controlled Supply. Shortage materials are sourced from the COGI location using a special batch number.
4. Material Transfer. Required quantities move from the COGI location to the WIP location before production booking.
5. Stock Availability at WIP. WIP stock is updated to ensure sufficient raw materials are available for production.
6. Backflush Processing. The system consumes materials from the WIP location during production confirmation and receives finished goods.

When the automated process results in negative quantities in the COGI location, a manual reconciliation process runs in six steps.

First, COGI records are identified by reviewing all negative quantities in the COGI location. Second, warehouse inventory locations are verified to check whether the negative quantity components are available elsewhere. Third, shortage quantities are transferred from warehouse locations to the COGI location to match the negative quantities.

Fourth, the COGI balance is cleared by adjusting quantities to zero. Fifth, reconciliation checks confirm that inventory postings match production consumption. Sixth, root cause analysis is conducted to prevent the same errors from recurring.

2. Supermarket Picklist Creation and Transfer for the Mixing Process

Tenneco Wuhan operates a mixing process for raw materials that required a custom Supermarket Picklist workflow built on FEFO (First Expiry First Out) logic. The user enters a Mixing Parent Item, designated as a valid MIXES item, and the quantity to produce.

QAD explodes the bill of materials for the Mixing Parent Item and creates a component list with corresponding quantities. The system checks stock at the WIP location first, then the Supermarket location, then WH Storage Locations, restricting results to active packs with no loose quantity. A QRF Picklist is printed in Wuhan format. Wuhan operates with one reserved location for mixes raw material.

During picklist transfer, the user scans serial IDs to move Serial Units from their current location to the production backflush location. If a Serial Unit has leftover quantity after the required amount is removed, a second transfer moves it from the Production Backflush location to the Supermarket Location.

If the transfer fails, the system returns an error message with the Serial Unit number.

Best Practices for QAD Adaptive Warehousing Implementation

Based on the Tenneco Wuhan experience and broader QAD Adaptive deployments, Nilay Dashondi of Arista Consulting recommends the following.

• Map current warehouse processes before configuring the system. Identify every manual workflow and every custom process built on the legacy system. The Tenneco Wuhan project succeeded because every SAP custom process was documented before a single QAD configuration decision was made.
• Design Material Routings and Algorithm Assignments before going live. These are the rules that govern every movement in the warehouse. Getting them right during configuration prevents costly corrections in production.
• Plan for the gap between feature availability and the go-live date. QAD Adaptive Warehousing launched in October 2025 and Tenneco Wuhan went live in January 2026. That 3-month window was used entirely for testing, bug resolution, and custom process design. Build adequate buffer into the timeline.
• Use Warehouse Task Type Assignments to route the right tasks to the right workers automatically. Labor optimization is one of the strongest ROI levers in warehouse management, and it requires deliberate queue design upfront.
• Integrate with equipment and external systems from the start. QAD Adaptive Warehousing supports integration with barcode scanning via AS and Eagle, label printing via LPS, and broader integration through Qxtend and BOOMI. These integrations should be in scope from the beginning, not retrofitted after go-live.

FAQ

Inventory management captures, monitors, and tracks inventory movements across receiving, production, and shipping. Warehouse management adds the layer of optimizing where inventory is stored, automating how workers move it, and enforcing rules for putaway, replenishment, picking, and shortage clearance. QAD Adaptive supports both, but the Warehousing module adds the algorithm-driven, location-optimized capability that basic inventory management does not provide.

Algorithms are system routines that determine where inventory is placed or retrieved based on predefined rules. Putaway algorithms run in a priority sequence. A typical configuration might first try to find a dedicated location with the same item and lot (algorithm 114), then a dedicated location with the same item (113), then any available first storage location (101). Picking algorithms control how stock is selected, by expiry date, by lot, by commission date, or by pick level. Algorithm Assignments link these routines to specific transaction types, sites, warehouses, and items, so the rules are applied consistently without relying on worker judgment.

COGI is an SAP transaction code used to process and correct failed automatic goods movements during production confirmations. When backflush processing fails due to missing stock, wrong storage locations, or incorrect batches, the error is captured in COGI so production can continue and the discrepancy is resolved separately. QAD Adaptive does not ship with a native COGI equivalent, but Arista Consulting designed a custom QAD process for Tenneco Wuhan that replicates the full COGI workflow. The process covers BOM explosion, shortage identification, COGI-controlled supply from a designated location, material transfer to WIP, and backflush processing.

Yes, though the complexity depends on how much custom functionality has been built on top of standard SAP WMS. Tenneco Wuhan completed the migration in under 3 months, but that timeline required Arista to extensively test newly released QAD functionality, raise and resolve more than 40 product tickets, and build custom processes for COGI equivalence and the Mixing picklist workflow. Organizations with simpler SAP WMS configurations will have a more straightforward path. The key is documenting every custom SAP process before beginning QAD configuration.

Yes. The system supports a site-to-multi-warehouse and warehouse-to-multi-site architecture within the same domain. Tenneco's broader deployment covered 8 plants across 3 continents, including Europe, Asia Pacific, and North America, all on QAD Adaptive. Each site can have its own warehouse configuration, algorithms, routing assignments, and task type priorities while operating within a shared ERP data environment.

Process Design Determines the Outcome of a WMS Migration

QAD Adaptive Warehousing is built into the same data layer as production, procurement, and finance, which means every warehouse movement is visible to the rest of the business in real time.

Algorithms remove the guesswork from putaway and picking. Material Routings enforce consistent inventory paths. Task Type Assignments put the right work in front of the right person automatically.

The Tenneco Wuhan project shows what that looks like in practice. A site running custom SAP WMS processes went live on QAD Adaptive in 3 months. The path there required careful process documentation, intensive testing, and custom development for processes SAP handled natively.

It also required a team willing to raise 40+ issues with the vendor and see them through. That is what a serious WMS migration looks like, and it is what QAD Adaptive Warehousing is designed to support.