Supply Chain Management

Supply Chain Management is the Nashua 360 module that governs the movement of goods and value from first demand signal to final delivery. It owns procurement, purchase order lifecycle, goods receipt and matching, warehousing, and outbound logistics as a single connected discipline, giving the organisation one authoritative view of what has been ordered, what has arrived, what is held where, and what is in transit. The module closes the operational gap that fragments most enterprises, where buying, receiving, storing and shipping are run in separate systems that never reconcile.

Positioned between the plan and the ledger, the module translates production and replenishment requirements into supplier commitments, controls the physical flow through the warehouse, and hands verified financial events to the accounting core. It is the operational spine of the suite: sourcing decisions, inventory positions and delivery performance all resolve here, and every downstream cost and valuation traces back to a transaction the module records.

What the module does

Supply Chain Management delivers the full procure-to-deliver capability set in one place. On the sourcing side it handles purchase requisitions, request-for-quotation cycles, supplier selection, and the creation, approval and dispatch of purchase orders, together with blanket and contract orders, scheduled call-offs, and change order control. Vendor evaluation runs continuously through scorecards that weight price, quality, on-time delivery and responsiveness into a ranked supplier position that informs each award.

On the receiving and financial-control side it performs goods receipt against open orders, records inspection outcomes, and executes two-way and three-way matching that reconciles the order, the receipt and the supplier invoice before any liability is confirmed. Inside the warehouse it manages locations, zones and bins, directed put-away, replenishment, cycle counting, and the pick, pack and ship cycle for outbound fulfilment. Across logistics it manages carriers, rates, shipments and tracking, so every consignment inbound or outbound is visible in real time. Above the transactional layer sits demand and replenishment planning, inventory optimisation, safety-stock calculation and supplier collaboration, closing the loop between what the business needs and what its suppliers commit to provide.

Domain and data model

The module organises the domain around a small number of durable business ideas rather than a sprawl of records. The first is the order commitment: a firm agreement to buy a defined quantity of a defined item, at an agreed price, for delivery to an agreed place and time. Every requisition matures into such a commitment, and every commitment carries its own history of approvals, amendments, receipts and invoices, so the current state of any obligation is always knowable and always auditable.

The second idea is the stock position: the quantity of a given item physically present at a given location, distinguished by whether it is available, reserved against demand, in inspection, or in transit. A position is never a single number but a layered truth, and the module keeps these layers separate so that availability is honest and commitments are never double-counted. Movements, not balances, are the primitive: each receipt, transfer, pick and shipment is an event that shifts quantity from one state or place to another, and the position is simply the sum of those events.

The third idea is the trading relationship with a supplier or carrier, which carries terms, lead times, pricing agreements, performance history and compliance credentials, and which frames every transaction conducted with that party. The fourth is the fulfilment obligation, the outbound counterpart of the order commitment, which drives the picking, packing and shipping of goods to an internal or external destination. These four concepts, commitment, position, relationship and obligation, interlock cleanly, and the richness of the module comes from how faithfully it models the transitions between them rather than from any catalogue of tables.

Principal workflows

The core operational flow is procure-to-receive. A requirement is raised as a requisition, sourced against preferred or newly quoted suppliers, and converted to a purchase order that routes through a configurable approval hierarchy governed by value thresholds, category and budget. The dispatched order is acknowledged by the supplier, tracked to delivery, and closed on goods receipt, at which point inspection confirms quantity and quality and matching validates the eventual invoice against the order and the receipt.

The warehouse flow governs the physical estate. Received goods are put away to directed bins, held and counted in place, and replenished from bulk to pick faces as demand draws them down. Outbound, the module waves and releases work, generates optimised pick paths, consolidates into packed units, and produces the shipment with its carrier, labelling and documentation. The planning flow sits above both: demand is forecast, netted against current and committed stock, and turned into replenishment proposals that respect safety stock, reorder points, lead time and economic order quantity, which planners confirm into new requisitions and orders. Supplier collaboration threads through all three, exposing forecasts, order status and delivery schedules to trading partners so commitments are agreed rather than assumed.

RequisitionPurchase orderGoods receiptand matchWarehouse andshipment
The procure-to-deliver flow that Supply Chain Management governs end to end, from raised requirement to dispatched shipment.

Control, matching and valuation depth

The financial rigour of the module rests on disciplined matching and clean inventory accounting. Three-way matching holds a supplier invoice against both the purchase order and the goods receipt, confirming that price agrees with the order and quantity agrees with what was actually received, within configured tolerances for price variance, quantity and rounding. Two-way matching applies where receipt is not expected, for services or expensed categories. Invoices that fall outside tolerance are held as exceptions and routed for resolution rather than posted, so no unverified liability ever reaches the ledger.

Inventory is valued on a consistent, auditable basis, supporting standard cost with variance capture, moving average, and first-in-first-out, with purchase price variance, freight, duty and landed-cost elements accreted onto the value of received goods. Every stock movement generates the correct accounting event: goods receipt raises the goods-received-not-invoiced position, invoice matching clears it against payables, and issues and shipments relieve inventory to cost of sales or work in progress. Segregation of duties is enforced across requisition, approval, receipt and invoice, delegation of authority is codified in the approval matrix, and a complete, immutable audit trail records who did what and when. Cycle-count reconciliation, tolerance-based write-off control and full traceability of lot and serial through receipt, storage and dispatch round out the control environment expected of a regulated operation.

Fit within the Nashua 360 suite

Supply Chain Management is engineered to operate as one organ of a single body rather than as a bolt-on. It integrates directly with Manufacturing and Operations, where the bill of materials explodes production plans into component demand that drives requisitions and purchase orders, and where completed work orders return finished goods into stock positions the module maintains. Component availability, planned receipts and shortage signals pass between the two continuously, so the shop floor and the buying desk work from one reality.

It integrates with Accounting and Control as the source of truth for payables and inventory value: matched invoices post automatically to accounts payable, goods-received-not-invoiced is reconciled in the general ledger, and inventory valuation, landed cost and variance flow straight into the financial statements without rekeying. The module also underpins the suite's Inventory capability, contributing the movement events, stock positions and warehouse structure on which item availability across every other module depends. Because these connections are native, a purchase raised here, a receipt booked here and a shipment dispatched here are the same records the finance, planning and operations teams see, with no reconciliation layer between them.

AI Workers in the module

The suite is AI-native, and AI Workers act as first-class participants inside Supply Chain Management rather than as an assistant bolted to the side. Through conversational query a buyer or planner can interrogate live module data in natural language, asking which orders are overdue from a given supplier, where a shortage sits against a production plan, or how landed cost has moved on a category, and receive an answer grounded in current records. Workers execute real actions within their granted authority: raising requisitions from replenishment proposals, chasing acknowledgements, drafting purchase orders and expediting late deliveries.

They monitor continuously for anomaly and exception, flagging price variances outside tolerance, receipts that diverge from orders, suppliers whose scorecard is deteriorating, and stock positions drifting below safety levels, and they surface these with the context needed to act. They perform document and data extraction, reading supplier invoices, order acknowledgements and shipping documents and reconciling them against open commitments to accelerate matching. They provide decision support, comparing quotes on total landed cost, recommending reorder timing, and modelling the service and working-capital effect of a safety-stock change. Crucially, a Worker can serve as a named approval or review node in a workflow, adjudicating a match exception or clearing a low-value order against policy, with every judgement recorded in the same audit trail as any human decision, so automation extends the control environment rather than bypassing it.