Spare Parts Exception Procurement Authorization Software
A machine waiting on a part that isn't on the approved list or in stock still needs an authorized purchase, fast, and on record. Kissflow runs that exception as a structured workflow tied to the work order that triggered it, with a sourcing and compatibility risk check built in before approval.
Trusted by energy operators worldwide
One authorization path for the spare part that isn't in the plan
The part number in the ERP shows zero on hand, the machine that needs it does not care, and someone has to authorize buying outside the approved parts list, sometimes from an alternate supplier instead of the OEM, before the shift ends. That decision, urgent and usually made under pressure, deserves a record just as much as a routine purchase order does: what triggered it, who approved it, what it cost, and whether the substitute part was actually compatible. Most plants make that call over the phone and reconstruct the paperwork afterward, if at all.
Kissflow runs that authorization as a structured exception workflow, tied to the work order that needs the part. A maintenance lead submits the part, the triggering work order, and the reason standard sourcing doesn't apply, stores confirms genuine unavailability, and OEM and alternate options surface before approval. Routing follows cost and urgency, with escalation so a line-down request doesn't wait on one approver, and a non-OEM substitute triggers a documented compatibility check. Every exception ties back to the work order, and spend rolls up by equipment and part, showing where the approved list needs updating.
A spare parts exception with no structure is a decision nobody can trace later
Requests happen by phone call
A maintenance lead calls a buyer directly to authorize an urgent out-of-list part, with no record of the request until the invoice arrives.
No link to the work order
The exception purchase happens disconnected from the work order that triggered it, so there's no record of why the part was needed.
OEM vs. alternate sourcing isn't documented
Choosing an alternate, non-OEM part under time pressure happens without a documented risk or compatibility check.
No spend visibility until month-end
Exception spend against the maintenance budget only becomes visible when finance reconciles it weeks later.
Six modules. Configurable to your spare parts sourcing policy.
Every module ships with default forms, approval logic, integrations, and dashboards. Configure each one to your operating model in the visual builder.
Exception request intake
Captures the part, the triggering work order, and the reason the standard sourcing process doesn't apply, in one form.
Stock and sourcing check
Confirms the part is genuinely unavailable in stores and surfaces OEM and alternate supplier options before approval.
Authorization routing
Routes the exception for approval based on cost and urgency, with delegation and escalation so a line-down request doesn't wait.
Alternate part risk flag
Flags when an alternate, non-OEM part is being proposed, requiring a documented compatibility check before approval.
Audit trail
Ties every exception request, approval, and sourcing decision back to the work order that triggered it, for audit.
Exception spend reporting
Rolls up exception procurement spend and frequency by equipment and part, showing where the approved parts list needs updating.
From request to system of record in four steps
Submit
A maintenance lead submits the part, the triggering work order, and why the standard process does not apply.
Review
Stores confirms the part is not available, and OEM and alternate supplier options are surfaced with a sourcing and compatibility risk check.
Approve
The request routes for approval based on cost and urgency, with escalation so a line-down request is not left waiting.
Record
The approved purchase is logged against the work order and rolled into exception spend reporting.
What changes when spare parts exceptions run on Kissflow
| Process | Before Kissflow | On Kissflow |
|---|---|---|
| Exception request | Authorized by phone call with no record until the invoice arrives | Submitted through a structured form tied to the work order |
| Stock check | Assumed rather than confirmed before buying outside the list | Confirmed against stores before the exception is approved |
| Alternate sourcing | Chosen under pressure with no documented compatibility check | Flagged and documented before approval |
| Approval | Whoever picks up the phone signs off | Routed by cost and urgency to the accountable approver |
| Spend visibility | Surfaces at month-end reconciliation | Visible in real time as exceptions are approved |
| Record | No link between the purchase and the work order that needed it | Every exception tied directly to its triggering work order |
Connects to the CMMS, ERP, and procurement systems you already run
.svg){kind=logo}
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
Built for how a spare parts exception actually happens
Fast enough for a line-down decision
Routing and escalation are built for a decision needed now, without skipping the documentation an audit will ask for later.
Alternate sourcing risk flagged, not skipped
Choosing a non-OEM part under pressure still requires a documented compatibility check before it's approved.
Live in weeks, not a re-implementation
Configure approval thresholds and sourcing checks in the visual builder, without a change request against your ERP.
Exceptions that inform the approved parts list
Recurring exceptions for the same part show up in reporting, flagging where the standard parts list should be updated.
Tied to the work order, not a standalone purchase
Every exception traces back to the maintenance event that triggered it, not just a line on a purchase order.
Made for cross-team accountability
Maintenance, stores, and procurement see the same exception record with their own view of it.
Related apps
Emergency Procurement & Spot-Buy Exception Authorization Management System
Authorize an urgent purchase for any line-down material, not just a spare part tied to an open maintenance work order.
Emergency Maintenance Orchestration Workflow
Coordinate the breakdown response whose parts check can trigger this app's exception procurement.
Maintenance Work Order Coordination (EAM-Lite)
Coordinate the work order this app's exception purchase is tied to, alongside every other open work order.
We help maintenance and procurement leaders authorize urgent spares without losing the record
.gif)
“If a company cannot enable everybody to use AI, they will never get the true benefit of AI. Platforms like Kissflow allow us to put that capability in the hands of our users in a safe way.”
Vagesh Dave
GVP & CIO at McDermott International, Ltd
See The Full Story
“Advanced automation of all processes is easy to set up. I cannot imagine how to manage workflows without this software.”
Tanay Tiwary
Global Head - Digitalization & Business Improvement
See the Full Story
“Kissflow supports rapid application development by building a working application prototype in the shortest amount of time.”
Maria Theresa Cabigon
CIO, SN Aboitiz Power Group
See The Full Story
See what Kissflow can do for you
Talk to usGot questions? We're here to help.
Get SupportEmergency Procurement covers any urgent, off-plan material purchase for a line-down risk. This app is specific to spare parts tied to an open maintenance work order, with a stores check and an OEM-versus-alternate sourcing flag built in.
Any part needed for a maintenance work order that isn't on the approved parts list, isn't in stock, or requires sourcing outside the standard purchasing process.
Routing is configurable by cost and urgency. Typically a maintenance supervisor for lower-cost parts and a plant manager or procurement lead for higher-cost or alternate-sourced parts.
No. Your CMMS and procurement system stay the record of the work order and the purchase order. Kissflow runs the authorization workflow that connects the two.
Yes. Process owners configure forms, routing, and thresholds in the visual builder, and the AI Builder can generate a working app from a plain-language description.
Through APIs and integration connectors, under single sign-on and role-based access, with every action written to an audit log.
Configuration and AI generation move delivery from weeks to days, without a multi-year platform program or an engineering backlog.
Kissflow is certified to SOC 1, SOC 2, SOC 3, ISO/IEC 27001, HIPAA, GDPR, and CCPA, hosted on Google Cloud with data residency in the US, EU, APAC, and Oceania.
