Construction material tracking software: procurement, receiving or inventory?

Choose the question before choosing the system

“Where are our materials?” can describe four different problems. A project manager may mean the supplier has not confirmed a manufacturing date. A foreperson may mean only part of an order arrived. A warehouse lead may know it arrived but not which shelf or job received it. An accounts-payable specialist may be missing evidence for a billed quantity. A single feature label does not resolve those differences.

Write the question in the language of the person doing the work. For example: “Before assigning the install crew, I need to know whether the full required package has physically arrived at the correct location.” That statement defines a state, a location and a decision. It is more testable than a general request for real-time visibility.

Identify the authoritative source for each answer. The purchase order records what was ordered; supplier correspondence may record a commitment; a receiving account records what someone observed. The invoice records what was billed. Keep those meanings separate even if one platform displays them together. A tracking system becomes misleading when it presents a promise or a financial document as proof of physical availability.

Compare four material workflows

Procurement tracking follows the item from request through quotation, order, release and supplier commitment. Receiving records the actual delivery, including shortages, damage and location. Inventory tracks stock balances and movements after receipt. Invoice matching connects billed quantities and prices to purchasing and receiving records. Your shortlist should reflect the workflows you need rather than assume every product covers them equally.

Existing products already address substantial parts of this work. Kojo advertises material procurement for trade contractors alongside tools, prefab and invoice workflows. Its invoice-matching description explains comparison of invoices with purchase orders and delivery records. Those advertised capabilities are a reason to evaluate the exact workflow; they are not independent performance findings or proof of compatibility with your configuration.

A controlled register can still be useful when the volume is small and one person maintains the state. An existing project or accounting system may cover part of the process. A dedicated material platform may be appropriate for repeated purchasing and stock movements. A custom coordination workflow can help gather missing confirmations around those records. Compare the operating process and ownership required by each approach.

Sources: Kojo official material management overview; Kojo: introducing automated invoice matching

Give the item enough identity to follow it

Define the project, order, order line, item description, supplier reference, unit of measure and intended receiving location. Include the relevant revision, substitution or approved selection when it affects what can be used. A short nickname such as “valves” may be understandable in conversation but insufficient when several sizes or specifications appear on the same order.

Decide how packages and components relate. A system that tracks only the order header may show delivery complete even though one required component is missing. Conversely, a package containing several boxes should not become several independent purchased quantities merely because each box has a shipping label. Ask the evaluator to show the relationship between the purchasing unit and the physical receiving units.

Capture source and timestamp with the state. “Expected Friday” needs the supplier's communication and the date it was confirmed. “Received” needs the receiving person, observed quantity and location. “Available for installation” may require another project-specific check. A consistent item record should help the next user understand how the team knows the status, not just display the latest word someone selected.

Run the same partial-delivery pilot

Use a fictional order for 100 identical fittings, purchased and received in individual units. In the pilot, 60 arrive at the correct bay, 40 remain on backorder and five of the received fittings are set aside for review because of visible damage. This produces 60 physically received, 40 not received and 55 apparently undamaged units awaiting whatever acceptance your process requires. Do not label all 100 available.

Ask the receiver to enter the result on an ordinary device, attach the delivery slip and identify the exception. Then ask the project manager to answer whether the full 100-unit installation package is ready. The answer should remain no. The pilot checks whether the system preserves the distinction between an order, a receipt and the quantity the team can actually rely on.

The figures are illustrative test data, not a prescribed inventory method. Your process must define how rejected, quarantined, returned and accepted quantities are represented. The key acceptance criterion is that the users can reconcile the same physical event without silently overwriting it or treating a partial delivery as completion.

Test supplier promises before the truck arrives

Ask how the workflow records an original requested date, the supplier's current promised date and the last confirmed source. Include a supplier reply that provides only a ship date. The project manager should be able to see that arrival remains unconfirmed. A planned departure, estimated transit time and delivery appointment are different pieces of information.

Change the commitment during the pilot. Have the supplier move the outstanding 40 units to a later date, with one unanswered question about the receiving appointment. Observe whether the previous commitment remains in history and whether the right project person receives a useful exception. An automatic date update is less useful if it hides the change or presents an unverified estimate as a firm promise.

Connect the follow-up to the actual installation decision. Ask which activity depends on the missing units, who needs to know and when they will review the impact. A material tracking tool can expose a changed commitment and route the information. It should not claim that a new supplier date has automatically produced a reliable project schedule or that the delivery is guaranteed.

Make receiving workable at the point of delivery

The receiver needs a short path to identify the order, record the observed quantity, note the location and capture an exception. Test the task with the device and connection conditions the team actually encounters. A workflow that requires the foreperson to return to the office before entering every receipt may leave purchasing and finance waiting for information that already exists on site.

Include a delivery without a clear order number. Ask how the team resolves the identity while preserving the original slip and the receiver's account. Do not encourage the user to guess the order simply to clear a required field. An unmatched receipt should become a visible action for the person who can identify it, not disappear into an apparently completed transaction.

Also test a duplicate submission of the same slip. Determine whether the system recognizes the duplicate or gives a reviewer enough information to resolve it without inflating received quantity. Keep the source and correction history. The goal is a reliable receiving record that another person can inspect, rather than the fastest possible path to a green completion indicator.

Follow transfers, returns and substitutions

Once material arrives, its location can change. In the pilot, move ten undamaged fittings from the receiving bay to a named installation area. Ask a second user to locate them and explain whether the move changes the total on hand. A location transfer should not be confused with a supplier return or installation consumption. Each event answers a different question.

Return two damaged units using a separate return reference. Record the physical movement and keep the expected credit or replacement as its own unresolved commercial action. Sending material back does not prove the supplier issued a credit or that a replacement arrived. The purchasing and finance users should be able to reconcile those later events to the same original receipt.

Test a proposed substitute with a different item reference. Ask how approval is recorded and how the original requirement remains visible. Do not let a receiver's text description silently approve a technical substitution. The responsible project process needs to establish whether the item can be used, while the tracking workflow preserves the proposal, decision and resulting material identity.

Trace the invoice to the receiving evidence

Introduce an invoice for all 100 units while only 60 have physically arrived. Ask the evaluator to show the discrepancy and the source records behind it. The system should support the authorized reviewer in applying your actual purchasing and payment terms. A quantity difference is a reason to investigate; it does not by itself prove an invoice is invalid under every commercial arrangement.

Test units of measure deliberately. If purchasing uses cases and receiving uses individual units, the conversion must be defined and visible. Avoid converting based on a model's guess or a free-text description. Add freight, tax and a credit scenario to understand which components are compared and which require review. Record tolerances and approval roles in the proposed configuration.

Kojo's published invoice-matching explanation is an example of an established purchasing-to-finance workflow. In your own evaluation, require the specific accounting destination and supported fields to be demonstrated. Confirm what happens when a transfer fails or an invoice is corrected after export. A general integration claim is weaker evidence than a reconciled transaction in the configuration you plan to buy.

Sources: Kojo: introducing automated invoice matching

Compare evidence, adoption and total operating cost

Score candidates against observable tasks: identifying the partial receipt, locating transferred material, preserving a changed supplier promise, resolving an unmatched slip and tracing the invoice discrepancy. Have the actual field, warehouse, purchasing and finance users perform their tasks. Record vendor assistance separately so a heavily assisted demonstration is not mistaken for ordinary independent use.

Request a written commercial scope. Include setup, catalog migration, accounting connections, external access, mobile use, training, support and ongoing administration. Identify the authoritative system for each field and the person who maintains it. A lower subscription can still create substantial work if the team must reconcile duplicate item catalogs or manually repair every failed transfer.

Set a baseline from your own process. Measure how long it takes to answer the material-availability question, find missing receiving evidence and reconcile exceptions. Track data quality alongside time. Faster entry is not enough if the resulting record overstates available stock. Avoid treating vendor marketing statistics as a forecast for your business; use the pilot to test your specific workflow and assumptions.

Start with the handoff your team can define

Choose one material class and one receiving path for the first rollout. Confirm identifiers, units, locations, receiving responsibilities and exception owners before expanding. Keep an opening snapshot and reconcile physical quantities with the responsible team. Otherwise, an initial cleanup may look like software-created inventory improvement when the starting data was simply inaccurate.

Review the first exceptions with the users. A missing supplier confirmation, unidentified slip, damaged delivery and accounting mismatch need different next actions. Make those paths easy to see and maintain. Expand when the team can explain the current state from its source records without relying on one person's memory or a private spreadsheet.

For a Buildalytic demo, bring a redacted order, a partial delivery example and a supplier message that left a date uncertain. Its custom-workflows offering provides a starting point for discussing confirmation and exception follow-up around existing tools. Ask the demo to show the proposed ownership, source preservation and human review steps, then confirm the configuration and implementation scope.

Sources: Buildalytic custom workflows