Knowify inventory moves need quantity-and-custody proof

Record the movement as a two-sided event

Knowify describes moving inventory among warehouses, vans, projects, and service jobs while updating counts and costs. Each movement should identify the item or controlled lot, catalog and manufacturer identifiers, description and unit of measure, quantity, source and destination locations, project and phase or service job, purchase-order and receipt references, requestor, issuer, carrier or transferrer, receiver, event time, condition, reason, and evidence. The sending record and receiving record must agree before the movement is closed.

Use pending, dispatched, partially received, received, disputed, canceled, and reconciled states rather than overwriting one location field. Preserve split quantities, shortages, damage, wrong parts, substitutions, returns, and corrections as new events. A mobile allocation can say what a user recorded in the field; it does not prove the material left the van, reached the named job, remained usable, or was incorporated into the work.

Reconcile quantity, custody, and cost separately

Three balances can diverge. The system quantity is the transaction ledger. Physical quantity comes from an observed count with location, counter, method, time, and variance. Financial quantity and cost come from purchasing, receipts, invoices, inventory policy, job-cost rules, taxes, freight, returns, and accounting periods. A clean software balance cannot resolve an uncounted van, an invoice mismatch, a damaged item, an unposted receipt, or a material charged to the wrong project.

Set control points for purchase authorization, supplier receipt, warehouse storage, van issue, interlocation transfer, project allocation, return, scrap, and period close. For each, name the person who may initiate, approve, receive, count, adjust, and post the cost. Record the approved variance threshold and escalation. Keep cost-code mapping and contract billing outside the custody fact until the authorized commercial and accounting records accept them.

Do not collapse allocation into installation

Allocated, delivered, staged, issued, consumed, installed, tested, accepted, billed, paid, returned, and scrapped are different events. A part can be assigned to a phase yet remain in a warehouse, delivered but rejected, installed and later removed, consumed in temporary work, or accepted without being billable under the current contract. Each state needs its own actor, time, location, quantity, supporting document, inspection or acceptance where applicable, and superseding correction.

Link serial or lot identity when warranty, traceability, recall, calibration, safety, commissioning, or owner handover requires it. Otherwise retain a defensible aggregate unit and batch method. Photos, delivery tickets, foreman notes, scans, and invoices support different facts and should not be treated as interchangeable proof. If a field user cannot identify the exact item or quantity, retain an unresolved exception rather than inventing precision.

Demonstrate one material through the full custody chain

A buyer test should purchase a controlled quantity, receive a shortage, place stock in a warehouse, transfer part to a van, allocate part to a project phase, issue a substitute, return an unused item, record damage, install a serialized item, and close the period. Reconcile the movement ledger to physical counts, purchase and invoice records, job cost, remaining stock, return or scrap evidence, and the installed or handover record. Repeat offline and after a late correction.

Contractor Systems Index reviewed Knowify's registered homepage and linked official inventory page on September 16, 2026. The sources support the provider's statements about multi-location inventory, transfers, project or service allocation, job-cost impact, count updates, and journey reporting. They do not establish any contractor's physical count, custody, valuation, contract entitlement, installed quantity, acceptance, billing, payment, accounting treatment, loss prevention, or outcome.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Contractor Systems Index will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.