Skip to content
Receiving spare parts at the workshop warehouse
Maintenance & safety

What enters the workshop is documented like what leaves it

A receiving log for equipment parts: the part’s source, its condition, the old part it replaced, and the receiving technician — linked to the relevant maintenance report.

Before

What happens today without this module

  • 01The part reaches the site with no written trace of who received it or for which machine
  • 02The replaced old part disappears without its condition documented
  • 03No link between the received part and the maintenance report it was used in
Capabilities

Exactly what this module does

  • The part’s source

    A market purchase or an inventory issue — every receipt has its source.

  • The old part’s condition

    Scrap, serviceable, or repairable — documented at replacement.

  • Linked to the maintenance report

    Every receipt is assigned to the relevant maintenance report and the receiving technician.

  • A supplier trail

    A log linking each receipt to its supplier and the receiving location.

Inside the service

How it actually works in your company

A part arrives at the workshop on the back of a truck, someone takes delivery, it goes into some machine — and a month later nobody remembers who received it, where it came from, or where the old part went. This module is a documentation register built for exactly that moment: every incoming part is recorded with its source, its receiver, the benefiting machine, the maintenance report it served, and the condition of the old part it replaced. Its limits are stated openly: it documents receiving to an auditable standard; it does not claim to manage purchasing or move stock balances.

01

An entry with every element

The technician records the part by name, number, quantity, unit and receiving date, and declares its source: a market purchase under the supplier's name, or an issue from internal stock. He records the receiving location, the receiving technician, the benefiting machine and his notes. A moment that used to pass verbally becomes a written entry with an owner and a date — and every registration leaves a trace in the system's activity log under the name of whoever made it.

02

The old part cannot vanish

At replacement, the old part's condition is documented as one of three states: scrap, usable, or repairable — together with naming the replaced part itself. This one field closes a familiar door in workshops: old parts with resale or repair value disappearing unquestioned. Once everyone knows the old part gets recorded with its condition and its receiver's name, behavior around it changes before any audit even begins — declared documentation is prevention before it is evidence.

03

One screen for every receipt

The register is not limited to manual entries: parts documented inside fault-report work orders — externally purchased parts received, stock parts used, and old parts returned with their condition — all appear in the same register, tied to their report and technician. The reviewer filters by machine, period or source to reach what he needs, and the reports hub carries a dedicated receiving report with spreadsheet export for sharing or archiving.

04

Honest and declared limits

The module does not run a purchasing cycle or financial approval, and recording a receipt here does not change inventory balances — balances move through their own approved gates in work orders, tires and oils. The separation is deliberate: the documentation register stays an independent witness to what entered the workshop, something the manager checks supplier invoices and stock movement against, not a party to the count itself — which is exactly what makes it citable in a dispute.

The flow

How the process runs end to end

  1. 01

    Arrival

    Record the incoming part and its source

  2. 02

    Documentation

    Quantity, condition, and the replaced old part

  3. 03

    Assignment

    To the machine, the maintenance report, and the technician

  4. 04

    Review

    An auditable receiving report

After rollout

What actually changes

No promises built on numbers we don’t know about your company. What follows is the structural difference of wiring this module into the rest of the platform.

A backed receipt
with its receiver’s name and its source
Old parts don’t vanish
their condition on record
Supplier performance
visible in the log

Limits of this module

A standalone documentation log: it doesn’t manage the purchasing and financial approval cycle, and it doesn’t update inventory balances automatically — stock moves through its own gates (work orders, tires, and oils).

Try Parts Receiving on your own assets — not a generic example

We tailor the demo to your operation, starting with the module that blocks your team today.