Spare Parts Reorder Levels: Stocking Rules That Hold When One Part Changes

Thirty part numbers, one budget and a history spread across work orders

Setting reorder levels for a maintenance storeroom looks like arithmetic. Each part's min covers consumption during its lead time, its reorder point adds a buffer, and critical spares get more cover because a missing seal kit can stop a line for days. Some parts have been superseded by a new number, some are obsolete, and some are stocked at zero and bought only when a job needs them.

The inputs never sit together. Consumption comes from maintenance work orders in ClickUp, lead times come from supplier quotes in Salesforce, the parts table lives in Airtable, and the stocking policy and the month's budget are documents in Google Drive. Changes arrive in Slack from reliability and maintenance. A change to one part usually affects others, and that is the step a busy planner skips.

Who works in the room

The storeroom runs one room for planning. Fin is the default agent and owns the run, so a planner's message about a new quote or a criticality change goes to Fin without a mention. Nova works only on the buyer's sheet. When the buyer posts a new draft, Fin mentions Nova in the thread with the approved run attached, and Nova leads the review until the list of disagreements is back with the buyer.

The monthly reorder run

The rules are the same every month, and so is the order of the work. Nothing is written or ordered until a person approves it.

One part changes, and the parts around it move too

Most changes name a single part. A supplier quotes a longer lead time for a spindle bearing. Reliability marks a seal kit critical after a press stoppage. An engineer reverses a supersession because the new coupling does not fit the older drives. Fin treats the named part as the start of the re-check. A new critical part competes with every other critical part for the same budget, so all of them are re-run. A reversed supersession brings the old part back to active, clears its successor link, and may put it into this month's PO run.

A consumption correction is the widest change. When maintenance finds that a set of work orders logged the wrong part number, usage moves from one part to another. Fin re-runs every affected part and re-confirms each part set aside as superseded, obsolete or zero min, because a corrected history can bring one of them back. Each changed row gets a short note saying which correction moved it.

What the checks catch

• A draft PO line with the wrong quantity, for a part not at its reorder point, outside this month's range, or listed twice
• A part due for reorder that is missing from the draft PO sheet
• Every part already critical re-run when another part joins the critical tier
• A reversed supersession that leaves the successor link in place or skips the PO run
• Superseded, obsolete and zero min parts re-confirmed after a consumption correction

What stays with people

• Approving levels and the PO run before Airtable changes
• Placing purchase orders, which stays with the buyer
• Deciding criticality, which stays with reliability engineering
• Signing off the month's run against the spares budget

Integrations in this workflow

Kylon is not an inventory or maintenance management system, and it is not a replacement for either. It sits across the storeroom's tools and holds the coordination that usually lives in one planner's head. Fin reads ClickUp and Salesforce through a lasting grant the maintenance manager approved for this room, and writes to Airtable only after the planner approves.

• Airtable
• ClickUp
• Google Drive
• Salesforce
• Slack

• Airtable holds the parts table: levels, status, supersession links and the PO run
• ClickUp holds maintenance work orders, which give each part its consumption history
• Salesforce holds supplier accounts and the quotes that carry each part's lead time
• Google Drive keeps the stocking policy, the month's budget and the buyer's draft PO sheet
• Slack is where reliability and maintenance post criticality and supersession changes

Where to start

Take one storeroom and one block of part numbers. Connect the Airtable parts table and the ClickUp work order list, schedule an automation that opens the run on the first Monday of the month, and write one rule in the room guidelines: when a part changes, Fin re-runs every part the policy ties to it, and the planner approves the whole list before Airtable changes.

“When one part changes, the list of parts that moved with it is already in the thread.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.