In manufacturing sites, sudden shortages of components or unexpected equipment failures increase the risk of production line stoppages. For manufacturing bases in Thailand, when considering the implementation of a manufacturing emergency procurement approval system, it is essential to design for both speed and approval traceability. This article details the entire process from emergency order requirements definition, approval workflow, ordering, receiving, and reconciliation, incorporating actual system design and key operational decision points.
Challenges Addressed by Implementing a Manufacturing Emergency Procurement Approval System
The introduction of an emergency procurement and order approval system in Thai manufacturing sites primarily aims to solve the following challenges:
- Minimizing the Risk of Line Stoppages Due to Component Shortages or Equipment Failures
When there is a stockout of critical components or a shortage of spare parts for equipment, the system accelerates the entire process—from immediate procurement requests, approval, ordering, delivery, receipt, to invoice reconciliation—minimizing downtime.
- Clear Distinction from Regular Orders
Unlike changes to unit prices on existing POs or adjustments for partial deliveries, emergency orders create new purchasing commitments. The recommended control is to either record approval by an authorized person, or allow automatic approval/approval omission only if the order matches pre-approved conditions. Since approval routes and omission criteria differ by product, approvals should not be skipped unconditionally just because an order is labeled “emergency” (Microsoft Learn, Purchase requisition workflow; Oracle Fusion Cloud Procurement, Using Procurement).
- Difference from Production Plan Rescheduling
Emergency procurement is a separate decision-making process from reprioritizing existing production plans (rescheduling) or regular PO management (price or delivery date changes). Emergency orders focus solely on the approval and execution of new orders.
First, Define the Boundaries of Urgency and Authority
The first step in designing an emergency procurement and order approval system is to set boundaries for “what situations are considered emergencies” and “who has approval authority and to what extent.”
Example Criteria for Determining Urgency
- Inventory Remaining
Example: Critical component inventory is expected to run out within 24 hours.
- Time Until Line Stoppage
Example: No substitutes available, risk of production stoppage within 2 hours.
- Substitutability
Example: No possible substitutes in other components or processes.
- Lead Time
Example: Standard procurement cannot meet the required delivery date.
- Cost Impact
Example: High loss amount per hour of line stoppage.
These are reference examples for system design and should be adjusted according to each company’s actual situation. Legal definitions of emergencies and approval obligations differ by country and industry, so definitions must be aligned with internal regulations and applicable items.
Key Points in Authority Design
- Four-Eyes Principle
Even in emergencies, at least two people (requestor + approver) must be involved to prevent fraud or erroneous orders.
- Monetary Thresholds and Exception Approvals
Orders below a certain amount can be immediately approved by the site manager; higher amounts require additional approval from department heads or executives.
- Delegation of Authority and On-Call System
Set up on-call approvers for nights and holidays to prevent decision delays during emergencies.
- Scenario Branching
– Imminent line stoppage: Immediate approval workflow
– Procurement needed within 24 hours: Shortened approval workflow
– Standard procurement possible: Standard approval workflow
Linking Events from Shortage/Failure to Ordering with a Single ID
The system design proposed in this article enables tracking from the discovery of shortages or failures through to PO issuance and receipt, all under a single request ID. The GS1 Global Traceability Standard covers critical tracking events (CTEs) related to the movement of goods, such as receiving, and the key data elements (KDEs) that describe who, what, where, when, and why. The act of purchase approval itself is not considered a GS1 CTE. At the time of receipt, the GS1 approach is referenced to link the request, PO, and receipt reference numbers (GS1 Global Traceability Standard).
Key Events in the Emergency Procurement Process
| Event | Responsible Party | Evidence/Record | Next Gate |
|---|---|---|---|
| Detection of Shortage/Failure | On-site Staff | Equipment alarms, inventory reports | Request Initiation |
| Emergency Procurement Request Initiation | On-site/Production Management | Work order, component code, quantity | Inventory/Substitute Check |
| Inventory/Substitute Check | Procurement/Engineering | Inventory reconciliation, substitute evaluation | Technical/Quality Approval |
| Technical/Quality Approval | Engineering/Quality | Substitute approval, risk assessment | Supplier Selection |
| Supplier Quotation | Procurement | Quotation, delivery/price comparison | Order Placement Decision |
| Order Approval Application | Procurement | Approval application, evidence log | Approval Workflow |
| Approval | Authorized Person | Approval record, snapshot at approval | PO Issuance |
| PO Issuance/Notification | Procurement | PO number, supplier notification record | Delivery/Receipt |
| Delivery/Receipt | Warehouse/On-site | Delivery note, receipt record, lot info | Invoice/Reconciliation |
| Invoice/Reconciliation | Accounting/Procurement | Invoice, receipt/PO reconciliation | Completion |
Each event is linked by request ID, leaving an audit trail of decisions. In Oracle Fusion Cloud Procurement, an ’emergency requisition’ can reserve a PO number upon submission. In contrast, simply specifying ‘urgent’ on a standard requisition does not reserve a number. This is a product specification of Oracle and is not behavior common to all ERPs (Oracle Fusion Cloud Procurement, Using Procurement). Microsoft’s purchase requisition workflow handles statuses from draft to approval and the approval route. In addition to this, at implementation, you should also design for the occurrence time of each event and references to the PO (Microsoft Learn, Purchase requisition workflow).

Approval Workflow: Faster for Exceptions, Stronger for Records
When designing the approval workflow for emergency procurement, it is essential to achieve both rapid exception handling and strict record-keeping.
Approval Authority and Exception Handling
- Authority Matrix
Define approvers by amount, item, and urgency. For example, emergency orders to trusted (existing) suppliers may require approval from the site manager and procurement manager, while new suppliers or high-value cases require additional approvals.
- Price Ceiling and Premiums
Even if price premiums are allowed in emergencies, set upper limits and require reasons to be recorded for later review.
- Separation of Duties
Separate the roles of requester, procurement staff, and approver to reduce fraud risk.
- Escalation and Deadline Management
If approval is not completed within a set time, automatically escalate to a higher authority. On-call approvers handle nights and holidays.
- Prohibition of Post-Facto Approval
Even for emergency orders, “backdating approval records” is not permitted; approval records must always be created in real time.
Evidence and Audit
- Immutable Audit Trail
The system must retain edit histories so that approvers, the version of the quotation at the time of decision, reasons for changes, and order numbers can be traced later. Microsoft’s purchase requisition workflow is an example where approval routes can be set, and the method of retaining audit trails should be checked according to the system and settings (Microsoft Learn, Purchase requisition workflow).
- Clear State Transitions
Clearly manage the status and timestamps for each stage—request, approval, PO, receipt, and invoice. This makes it easier to trace causes and respond to audits if problems arise later.
By implementing an emergency procurement and order approval system, manufacturers can achieve both rapid response to exceptions and strict record management, thereby reducing risks and strengthening governance on the shop floor.
Simultaneously Reviewing Price, Supplier, and Quality Risks in Emergencies
When implementing a manufacturing emergency procurement approval system, the most critical factor is balancing “speed” with “risk management.” This is especially true for local factories in Thailand, where emergency procurement due to material shortages or equipment failures can lead to orders being placed without evaluating price, quality, or supplier risks if the approval workflow is skipped.
Therefore, even in emergency orders, it is essential to establish at least minimal review gates and operate a process that checks the following aspects simultaneously:
- Approved Vendor List (AVL)
When procuring from existing approved suppliers, the standard procurement management system workflow can be streamlined.
- Conditional Approval for New Suppliers
If using an unregistered supplier, temporary approval from the head of procurement or the quality assurance department is required.
- Approval of Substitute Parts for Compatibility and Quality
If part numbers or specifications differ, compatibility confirmation by the engineering or quality department is mandatory.
- Spot Buy Price Comparison
Even in emergencies, if possible, compare multiple quotations and evaluate total costs, including shipping, customs duties, and exchange rate risks.
- Risks of Single Quotation or Supplier Promises
When only one quotation is available or a supplier verbally promises “immediate delivery,” always record the exception reason and ensure the approver explicitly assumes the risk.
- Priority Determination
Depending on the risk of production stoppage or impact on customer delivery deadlines, decide whether to shorten the approval flow or add extra review gates.
Practical Decision Table for Emergency Procurement Review
| Case | Required Review Gate | Exception Record / Audit Trail | Attachments / Version Control |
|---|---|---|---|
| Approved Supplier & Existing Part | Approval by Head of Procurement or Site Manager | Record of Emergency Reason | Attach Latest Quotation |
| Use of New Supplier | Head of Procurement + Temporary QA Approval | Reason for Supplier Selection | Registration Application & Quotation |
| Use of Substitute Part | Approval by Engineering or QA Department | Record of Compatibility Evaluation | Specification Sheet & Approval Email |
| Single Quotation / Immediate Delivery Promise | Approval by Department Head or Higher + Explicit Risk Acknowledgement | Exception Reason & Risk Record | Quotation & Delivery Proof |
In this way, even during emergencies, exception reasons and audit trails (such as quotations, approval emails, and specification sheets) are attached and version-controlled in the system, maintaining a state that allows for future audits.
Additionally, it is recommended that the approval workflow be designed to allow routing by “document” or “line item,” as in Microsoft Dynamics 365. Approvers can be automatically determined based on spending limits and risk levels (Microsoft Learn).
Linking Rapid Ordering and Receipt After Approval
Once emergency procurement is approved, it is crucial to clearly distinguish each stage from purchase order (PO) issuance to receipt and visualize progress.
In particular, the system should track each status—PO issuance, supplier receipt, shipment, arrival, quality inspection, and inventory allocation—and be designed to handle exceptions such as the following:
- Distinguishing PO Issuance and Supplier Receipt
Record separately the point when the PO is issued and when the supplier formally receives and accepts it.
- Delivery Date Response and ETA Changes
Any delivery date responses or ETA (Estimated Time of Arrival) changes from the supplier should be recorded in the system each time and notified to relevant parties.
- Partial Deliveries, Substitutes, Lot/Serial Management
For partial deliveries or substitute items, separate each receipt by lot and record lot or serial numbers.
- Quarantine, Inventory Allocation, and Duplicate Prevention
Clearly indicate quality inspection pending (quarantine) and inventory allocation status, and prevent duplicate receipts for the same PO. Any PO modifications must always go through a review.
Notably, in Oracle Fusion Cloud Procurement, the “emergency purchase request” feature allows a PO number to be reserved at the time of submission for emergency orders. In contrast, simply marking a regular request as “urgent” does not reserve a number (Oracle Official Documentation). When designing your system, refer to such implementation examples and clearly define “when PO numbers are reserved” and “whether POs can be issued before approval.”
Returning to Standard Receiving, Invoicing, and Costing Processes
After emergency procurement items are received, revert to the standard procurement management process and ensure thorough audit trails and cost management.
- Goods Receipt
Upon physical receipt, attach delivery notes and inspection records to the system, and record the receiver, time, quantity, and lot information.
- Invoice Matching
In Microsoft Dynamics 365, the configured three-way matching policy allows comparison of PO, receipt, and invoice prices and quantities. Whether approval is required for allowable variances or discrepancies is determined by company settings (Microsoft Learn).
- Exception Handling and Premium Cost Management
Additional costs from emergency procurement, such as premium freight or special charges, should be managed with dedicated cost codes and clearly identified during cost calculation and monthly closing.
- Provisional Invoices and Unreceived Items
Manage provisional invoices for undelivered goods and detect missed receipts in the system to prevent duplicate postings.
- Audit Trail and Traceability
Apply GS1 principles to receipt tracking design, recording “who, what, when, where, why” for each receiving and inspection event, and link related supporting documents (GS1).

Example of a system design where delivery notes, inspection records, invoices, and approval history for emergency procurement items are linked in the system at the time of physical receipt, enabling future audits and cost analysis.
Note that partial deliveries against existing POs (standard operation) and receipts from new POs created for emergency orders should be clearly distinguished in terms of audit trails, cost, and approval history management.
Defining Responsibility Boundaries Between ERP, MES, and WMS
When implementing a manufacturing emergency procurement approval system, it is essential to define responsibility boundaries and data integration design among ERP (Enterprise Resource Planning), MES (Manufacturing Execution System), and WMS (Warehouse Management System).
| Management Area | System of Record | Main ID / Integration Key | Redundancy / Resend Design | Timestamp Management | Quality / Inventory Status Management |
|---|---|---|---|---|---|
| Ordering & Approval | ERP | PO Number, Purchase Request No. | Resend / Idempotency | UTC + Local Time | – |
| Receiving & Inspection | WMS | Receipt Number, Lot Number | Resend / Idempotency | Receipt Time | Quarantine, Pass, Fail |
| Manufacturing Input | MES | Work Order No., Part Number | Resend / Idempotency | Input Time | Usability Status |
- Responsibility Boundaries
This table shows an example where ERP handles ordering and approval, WMS handles on-site receiving, and MES handles manufacturing input. In practice, designate a single system of record for each area according to your existing systems.
- Integration IDs and Idempotency
Integration between systems should be managed with unique IDs such as PO or lot numbers, and idempotency must be ensured to prevent duplicate registrations upon resending.
- Timestamps and Time Zones
Record all events in both UTC and local time to meet audit and traceability requirements.
- Quality and Inventory Status
Explicitly manage quality statuses such as quarantine, pass, or fail, as well as inventory allocation eligibility, to prevent incorrect use before MES input.
For more detailed comparisons and practical guidance on inventory management system implementation, please refer to Inventory Management System Comparison and Inventory Management System Implementation in Thailand.
Three Cases for Delegating Emergency Purchases to On-Site Judgment
Let’s consider a case of component stockout. Even if the book inventory is sufficient for the required components in a manufacturing order, the actual stock on the shop floor may be lacking. If you submit a purchase request simply stating “stockout,” you risk overlooking inventory in other warehouses, quality-hold items, or unrecorded incoming shipments. The application screen should display book inventory, actual shelf count, items pending inspection, transferable quantities at other sites, and the next scheduled production input time. Before forwarding the request to procurement, the warehouse manager should verify the cause of the discrepancy and, if a transfer can resolve the issue in time, reduce the purchase quantity accordingly. Only the shortfall that cannot be covered should be submitted as an emergency request, clearly indicating which manufacturing order the purchase is intended to fulfill. In this example, what needs to be expedited is not the omission of data entry, but the time it takes for all responsible parties to see the same shortage quantity.
In the case of equipment failure, even if the maintenance team finds a “similar part,” it does not necessarily mean immediate procurement approval. You must confirm the equipment number, failure location, manufacturer part number, specification version, replacement procedure, and warranty conditions. If using an alternative part, determine in advance which responsible party—design, quality, or maintenance—will decide on its usability. The decision to purchase an alternative part should be separated from the decision to install it and resume operation. Even if the urgently delivered part is received in the warehouse, it should be placed on quality hold until compatibility is confirmed. The purchase request should be linked to the maintenance work order for the stopped equipment, ensuring traceability for “why this part was chosen at this price.” If the root cause of the failure is found to be different after ordering, a separate task should be created to contact the supplier and confirm whether cancellation is possible.
For supplier selection, suppose approved vendors have slow delivery, while new vendors can deliver faster but at a higher price. The system should not display only unit prices side by side, but also show expected arrival, shipping method, currency, taxes, alternative specifications, quality documentation, and transaction terms on the same comparison screen. If only one quote is obtained, do not leave the comparison fields blank; instead, record the “reason only one supplier could be selected” and the approver who accepted this decision. If the new supplier registration is incomplete, define in advance the conditions under which a PO can be sent. The decision to accept a price premium should be compared against the effect of avoiding production stoppage, using the same currency and period, and if the rationale is unclear, retain the option to revert to the standard route. This screen is not intended to always justify the premium cost.
Even for the same case, the significance of timing differs among stakeholders. For the shop floor, the “required time” is when the component is to be used, while for procurement, the “delivery date” is not sufficient if it only refers to the supplier’s shipping time. The warehouse requires time for receipt, inspection, and transfer to storage locations, and quality requires time for inspection and release. Therefore, record each event separately: application deadline, PO issuance, supplier acceptance, shipment, factory arrival, receipt, quality release, and production input. Even if the supplier’s ETA is updated, do not automatically change the outlook to “on time” until quality release is confirmed. If approvers change during night shifts, it is important to be able to reproduce which authority table was applied, including time and time zone.
In partial delivery cases, only the first-arrived portion of an emergency PO may be delivered, with the remainder arriving the next day. The warehouse receives the quantity and lot of the first-arrived portion, leaving the undelivered portion as pending. Whether the shop floor can use the first-arrived portion depends on inspection results and the required quantity for the process. Even if the supplier sends a single invoice, do not consider the entire quantity as received. Match the invoiced quantity to each receipt detail, and link the remainder to subsequent receipts. If it is a partial delivery of an existing PO, manage it as a normal outstanding order; this is not a reason to issue a new emergency PO. Only when placing a new order for the shortfall with another supplier should you record the relationship between the new request/approval and the undelivered portion of the original PO. This provides the basis for preventing double procurement.
Boundaries are also necessary for post-approval changes. At the time of approval, specific quantities, prices, suppliers, and expected arrival dates were reviewed. If the procurement staff changes only the price and sends the order as is, the conditions seen by the approver will differ. The system should compare before and after changes and determine, based on the authority table, which changes require re-approval. On the other hand, if the supplier only corrects the contact for receipt confirmation, it may not be necessary to re-approve the PO amount each time. Do not process all these as the same “change” button; instead, classify changes affecting order conditions, corrections to contact information, delivery date updates, and receipt record corrections as separate event types. In all cases, ensure that the changer, time, notification recipients, and the canceled old information can be referenced.
During post-receipt reconciliation, do not confuse physical receipt with payment eligibility. If the delivery note part number differs from the PO, the quantity is excessive, the item fails inspection, the lot is missing, or the invoiced price differs from the approved amount, each issue has a different owner. The warehouse handles physical quantity, quality handles conformity assessment, procurement handles PO conditions, and accounting handles invoice matching. The system should not lump discrepancies into a single “error,” but display what each party needs to confirm to proceed. While on quality hold, items should not be allocated to production even if they are in stock, and if only the invoice arrives first, do not fabricate receipt records—leave them as unmatched. At month-end, output lists that distinguish between ordered/unreceived, received/uninspected, and inspected/uninvoiced items.
Finally, even successful emergency procurement is not “complete just because it arrived.” Confirm whether the original stockout or failure has been resolved, whether additional regular orders are needed, which project the premium cost should be allocated to, and whether the alternative part should be treated as approved for future use. Do not automatically elevate exceptions to permanent rules; reflect them in the master only after evaluation by engineering, quality, and procurement. If emergency requests for the same component are repeated, do not just speed up approvals—review safety stock, demand fluctuations, inventory discrepancies, maintenance plans, and supplier delivery responses. The emergency procurement system should serve both as a channel for exceptions and as a record base to feed the reasons for exceptions back into regular planning.
Even when using pre-approved exception rules, narrowly define the scope where human judgment is not required. For example, only auto-approve when all of the following match: approved supplier, part number, price conditions, quantity limit, and validity period; if any differ, route to the responsible person. For auto-approval results, retain the applied rule version and decision input, and ensure traceability of who approved the rule and when. If the rule has expired, revert to normal approval workflow and do not display as ordered on the shop floor screen. If urgency alone is set as the auto-approval condition, cases with the weakest justification may be ordered fastest, creating a reversal. Conversely, if too many approval steps are added, you risk missing the production line deadline. Clearly define which risks require human review, and design the system to separate low-risk routine cases from those involving unregistered suppliers, alternative parts, or high-cost shipping.
Requirements for RFP When Implementing a Manufacturing Emergency Procurement Approval System
When introducing a “manufacturing emergency procurement approval system” in Thailand’s manufacturing sector, there are numerous requirements that should be clearly specified in the RFP (Request for Proposal).
First, regarding functional requirements, it is essential to design a purchase request and approval workflow that supports both regular and emergency procurement. According to Microsoft Learn, purchase requests should allow for branching approval routes at the document or line-item level, with mechanisms to automatically determine approvers based on amount thresholds or department (see Microsoft Learn, Purchase requisition workflow).
For emergency orders, in the case of Oracle Fusion Cloud Procurement, submitting an emergency purchase request allows you to reserve a PO number at the time of application. In contrast, marking a regular request as “urgent” does not reserve a PO number. Therefore, it is necessary to clearly define the “conditions for securing a PO number during emergency orders” at the requirements definition stage (see Oracle Fusion Cloud Procurement, Using Procurement). Additionally, even with Oracle’s auto-generated POs, if prices or other terms have not been pre-negotiated, approval is still required. Be sure to clarify your company’s exception conditions and the design of approval records (see Oracle Fusion Cloud Procurement, Using Procurement).
For non-functional requirements, the following aspects are important:
- Mobile and On-call Support: UI/UX design that allows field staff and approvers to submit, approve, and check status from smartphones or tablets.
- Multi-language Support: Ability to switch between Thai, Japanese, and English, with language settings retained per user.
- Multi-currency and Local Currency Support: Transaction, display, and reporting functions in multiple currencies, including THB (Thai Baht).
- Access Control: Role-based access management (RBAC), with temporary access rights for external vendors or auditors.
- Audit Trail and Logs: All requests, approvals, changes, and cancellations are recorded chronologically, searchable, and exportable.
- Attachment Retention Policy: Flexible management of attachment of quotations, delivery notes, and supporting documents, including retention period, auto-deletion, and archiving settings.
As for scope boundaries, the RFP should clearly state the coverage, such as “This system covers the process from purchase request to order, receipt, and invoice processing, and does not include detailed functions for inventory management, production planning, or financial accounting.” Also, specify interface requirements with external systems (ERP, MES, WMS, etc.) and error retry/duplication prevention design for API integration.
Do Not Mix “Request” and “Order” Data Items in the RFP
Simply creating a single screen for emergency requests makes it impossible to track what was actually ordered after approval. A purchase request should include the requester, originating site, the item or equipment that is stopped or out of stock, required time, required quantity, unit, whether substitutes are allowed, and the timestamp of the inventory inquiry that serves as the basis. For equipment spare parts, reference the equipment number and maintenance work order; for materials, reference the production order and item/specification version. If the purchasing staff obtains a new quote, do not overwrite the original request—instead, add the quote version and candidate suppliers. Approvers must be presented with a snapshot at the time of application, including amount, currency, handling of freight and taxes, expected arrival, and quality risks.
The purchase order is a separate record created from the approved conditions. Distinguish between request ID, approval ID, PO number, and PO line number, and link these through to the subsequent receipt ID and invoice ID. For example, if a single shortage request is split into orders to two suppliers, there is one request but two POs. Conversely, if regular items are added to the same PO, it becomes unclear how to aggregate emergency costs. In the RFP, require the ability to record one-to-many orders, split deliveries, cancellations/reissues, and price revisions as history, and have vendors demonstrate this both on screen and in the data. Corrections to records must not delete the original event; instead, require that the corrector, reason, and target version are retained.
Validate the Approval Matrix by Time, Amount, and Supplier
An approval route such as “department head for emergencies” is insufficient. Separate cases for the currency conversion timing of approval amounts, nighttime proxies, when the applicant and approver are the same person, when an approved supplier cannot meet the delivery date, when using a new supplier, and when substitute parts are needed. Design the authority master with effective dates so that applications referencing outdated authority tables do not remain after approvers change. If the quoted amount increases after approval, determine the need for re-approval not only by the price increase but also by changes in freight or quantity. If the supplier’s delivery response changes, notify purchasing and production management, as production impact may change even if the amount does not.
Even in companies that allow nighttime phone approvals, do not substitute a phone call for an approval-completed flag. Separate who, when, and under what conditions oral consent was given, and who recorded it in the system, and record the times of formal approval and order notification separately. Define in internal regulations the permissible scope for post-event record entry, and design the system so that approvals cannot appear to have been backdated. If a proxy approver is absent, escalate to the next in line; if no one has authority, keep the status as “pending approval” and present alternative mitigation measures such as inventory transfers or production sequence adjustments to the shop floor. Require vendors to demonstrate this stop behavior on actual equipment.
Integration Specifications Must Describe Business Processes for Failures
Integration tables for ERP, WMS, and MES should specify not only the normal transmission destinations but also the owner of events when transmission fails. If the approval screen shows success but the ERP does not have the PO, either prevent sending a firm order to the supplier or require the purchasing staff to check via an exception queue. If communication is interrupted before the ERP responds, require the system to re-query using the same request ID and idempotency key, ensuring that duplicate POs are not created. If the price changes during the communication outage, do not resend the order with the old approved version; instead, re-examine the differences.
Even if a shop floor terminal can save a request offline, approval and ordering are not complete at that point. The terminal should display statuses such as “unsent,” “received,” “pending approval,” and “ordered,” and allow confirmation of which events have synchronized upon recovery. On the receiving side, if there is a delay between WMS receipt completion and ERP inventory posting, decide which system will display the inventory as available. Parts on quality hold should not be included in available quantity even if physically on the shelf, and quality release approval should be a separate event. These measures support explainability when shop floor and accounting figures temporarily differ.
Also Record Decisions to Lower Urgency
Emergency requests should not proceed to the end based solely on the initial sense of crisis. If information emerges—such as finding stock of the same specification in another warehouse, equipment being restarted after repairs, or the required time being extended due to changes in production order—then the purchasing and production control teams will re-evaluate the required quantity and delivery deadline. If a PO has not yet been sent to the supplier, the request can be returned to the normal approval route or the order itself can be withdrawn. If the PO has already been sent, check the supplier’s acceptance status, cancellation conditions, and shipping arrangements, and compare the potential cancellation costs with the expected surplus inventory. The system should not be designed so that the requester can remove the emergency flag and erase the history on their own.
When re-assessing urgency, both the initial shortage forecast and the new inventory or production information must be retained. For example, even if stock is found, it should not be counted as available if it is on quality hold. If an alternative item is approved, the setup time required for the switch must be included in the delivery calculation. Even if the supplier promises early delivery, do not display it as a confirmed delivery date until a written response is received. With these distinctions, you can later explain why extra shipping charges were paid or why an emergency order was canceled. Cases where urgency was lowered should not be removed from KPIs; instead, keep the final status and reasons for changes so you can review whether early detection was effective or if there were many false alarms.
30-Day, 60-Day, and 90-Day Pilot Plans and Acceptance Testing
For the implementation project of an emergency procurement approval system, establishing phased pilot plans—such as 30-day, 60-day, and 90-day stages—minimizes operational impact while ensuring solid adoption. The following is a representative example and should be adjusted according to each company’s situation.
| Period | Main Activities | Example Acceptance Test Scenarios |
|---|---|---|
| 30 days | Requirements definition, initial setup, user training | Emergency order due to material shortage, spare parts order during equipment failure, proxy approval when approver is absent |
| 60 days | Partial operation start, API integration testing | Vendor delivery date change, unapproved substitute item request, duplicate API retry, offline request submission |
| 90 days | Company-wide rollout, month-end closing, operational stabilization | Month-end processing, over-receipt/partial receipt, handling expired quotations, cancellation processing |
For acceptance testing, set up concrete scenarios such as:
- Emergency Procurement Due to Material Shortage or Equipment Failure: Emergency requests from the field proceed through the approval flow and result in immediate PO issuance.
- Unapproved Substitute Item Requests: Prevent ordering or moving to usable inventory until the design/quality department completes conformity checks. For approver absence, verify proxy approval and escalation as separate scenarios.
- Vendor Delivery Date Change: When delivery dates change after ordering, determine whether system notification and re-approval are required.
- Over-Receipt and Partial Receipt: Even if deliveries are split into multiple shipments, ensure proper three-way matching between PO, receipt, and invoice (see Microsoft Learn, Vendor invoices overview; Microsoft Learn, Accounts payable invoice matching overview).
- Expired Quotations and Duplicate API Retries: Resending and duplication prevention in cases of expired quotations or API communication failures.
- Offline and Month-End Processing: Saving requests during network outages, and automatic notification of pending items at month-end closing.
- Cancellation Processing: Ensuring that order cancellations after approval are properly recorded and notified.
The acceptance criteria are that “the expected business flows for each scenario can be reproduced in the system, and stakeholders can confirm operations and results.” Set numerical targets such as processing times based on actual factory measurements, and verify observable reproducibility of business processes in each test.
In FAT, Reproduce Approval Rules and Data Changes on Paper
In FAT (Factory Acceptance Test), prepare test data with anonymized real part codes, authority tables, supplier master, inventory balances, and quote versions. First, process a standard case; then, for the same item, move up only the shortage time to check if the urgency changes. Next, input cases one by one for approver absence, amount overage, application and approval by the same person, unapproved suppliers, and expired quotes. Passing criteria are not simply that an “error appears.” Check on screen and in logs which condition stopped the gate, to whom it was reassigned, whether both the original and resubmitted quotes remain, and whether the order notification has been sent. Also test that when an approved request is sent back, the old approval cannot be reused for the new conditions.
For PO creation tests, intentionally resend the same API request and confirm that only one PO number is issued. If the response times out, the system must not immediately decide it “failed,” but allow querying the result by the original request ID. Changes to ordered PO quantity, price, supplier, and cancellations should each be separate scenarios, and compare the versions before and after the change, whether re-approval is required, and whether the supplier is re-notified. Also confirm that simple due date changes or split deliveries on existing POs are not mistakenly counted as new emergency purchase cases. Attach input data, expected state transitions, actual screens and integration messages, and the evaluator to the test results.
In SAT, Observe Cases Where Physical and Information Flows Are Out of Sync
In SAT (Site Acceptance Test), actual warehouse, purchasing, quality, manufacturing, and accounting staff follow the same test cases. Test real-world sequences such as not moving substitutes into available inventory until quality inspection is complete even if they arrive first, keeping receipts in a pending state if the delivery note arrives before PO integration, and not doubling the received quantity if the same box is scanned twice. For split deliveries, separate the received quantity and lot for each shipment, and if invoices are consolidated, link them to the receipt details. Decide in advance whether to stop acceptance or require exception approval for over-shipments, and avoid leaving such decisions to implicit on-site judgment.
During trials, cross-check not only pre- and post-order screens but also the physical shelves, holding locations, and book balances. If the supplier responds with a delivery delay immediately after PO issuance, recalculate not only the ETA but also the line stop forecast, and check if production management can consider alternatives. If POs remain unbilled or unreceived at month-end, show the list to accounting and the reconciliation procedure for the following month. When actuals and book figures differ, it is important to be able to trace which events are unsent, duplicated, or pending cancellation before the site adjusts the quantities. Acceptance criteria require that the person in charge can reproduce the process using the procedure manual, and that the owner and resolution deadline for exceptions are clear.
Do Not Leave Incomplete Cases Behind When Switching to Production
When switching from trial to production, it is not necessary to migrate all cases to the new system at once. However, before the switch, list by status all requests created but not yet approved, approved but not yet ordered, POs ordered but not yet received, split deliveries, items on quality hold, and unbilled cases, and decide case by case in which system to complete them. Match old and new numbers, and confirm that POs are not sent twice to suppliers. In the first monthly closing after migration, purchasing, warehouse, and accounting should reconcile emergency cost codes, receipt variances, and outstanding provisional receipts.
For the first few weeks, record not only approval wait times but also the reasons for rejections and for any detours via phone or chat. If screen entry is too lengthy, look for fields that can be auto-filled from equipment numbers or part codes before removing required items. If approvals are slow, do not simply relax thresholds across the board, but check under which risk conditions cases are stalled. Also use the same dashboard to check that only the result, not the process, of quality inspection is being accelerated, and that unprocessed accounting reconciliations are not being pushed back. If the emergency flow becomes a loophole for the standard flow, review the basis for urgency and the exception rate, and restore the ability for the shop floor to explain the decision before ordering.

KPIs to Measure Effectiveness and Post-Failure Review
To objectively evaluate the effectiveness of system implementation, set the following KPIs (Key Performance Indicators):
- Approval Lead Time: Time required from purchase request to final approval. Measure separately for emergency and regular cases.
- Procurement-Related Downtime: Record of equipment downtime due to delays in material or spare parts procurement.
- Exception Rate: Number of exceptions such as missed approvals, unapproved orders, incorrect orders, and duplicate orders.
- Premium Procurement Costs: Number and amount of extra costs incurred due to emergency procurement.
- Three-Way Match Discrepancies: Number of mismatches in amount or quantity between PO, receipt, and invoice (see Microsoft Learn, Accounts payable invoice matching overview).
- Open Aging of Pending Items: Distribution of elapsed days for unapproved, unreceived, or uninvoiced items.
- Data Integrity: Presence of required attachments, supporting documents, and audit trails for each procurement case.
Compare these KPIs before and after implementation, using the same scope and period, to quantitatively assess the degree of business improvement. In case of failure or unmet targets, conduct Root Cause Analysis to identify whether issues lie in process, operations, or system—such as frequent approver absence, misoperation of emergency flows, or undetected API integration errors—and implement preventive measures.
Frequently Asked Questions
How much does it cost to implement an emergency procurement approval system?
Implementation costs vary greatly depending on the scope of integration with existing systems, number of users, customization requirements, and local support structure. For cloud-based systems, initial costs can be minimized with monthly subscription fees, but on-premises or advanced workflow designs may incur additional costs. It is important to clarify requirements at the RFP stage and obtain quotes from multiple vendors.
Can emergency procurement approval be handled by ERP alone?
Major ERPs (e.g., Microsoft Dynamics 365, Oracle Fusion Cloud) come standard with purchase request and approval workflow functions. However, emergency procurement-specific flows (e.g., immediate PO number reservation, approval skip conditions, proxy approval, attachment retention policies) may require additional configuration or extensions (see Microsoft Learn, Purchase requisition workflow; Oracle Fusion Cloud Procurement, Using Procurement). It is essential to organize requirements that fit actual field operations.
What is the difference between “emergency” and “urgent”?
The distinction is determined by each company. In Oracle’s product specifications, submitting an emergency purchase request allows you to reserve a PO number, whereas simply marking a request as “urgent” does not. In the system, set special approval routes or PO issuance conditions for the “emergency” flag, and treat “urgent” as prioritized processing in the regular flow. Clear operational rules are necessary.
Is it possible to issue a PO before approval?
In Oracle Fusion Cloud Procurement, you can reserve a PO number when submitting an emergency requisition, but reserving a number and issuing an approved PO are separate states (Oracle Fusion Cloud Procurement, Using Procurement). Whether you may commit an order to the supplier before approval is determined not only by product settings but also by your company’s authority regulations. Do not treat the existence of a number as proof of approval; instead, separately record the time sent to the supplier and the approval history.
What happens if substitute parts are not approved?
Unapproved substitute parts should be designed so that ordering or transfer to usable inventory is halted until conformity is confirmed. If the approver is absent, proxy approval or escalation routes are necessary. If the process proceeds without approval, there is a risk of matching errors or payment holds in subsequent steps (receipt, invoice processing).
How are receipt and invoice processing handled?
After recording receipt, the system matches PO, receipt record, and invoice according to the configured matching procedure. Even if deliveries are split or quantities exceed the order, the system can handle partial receipt and variance management (see Microsoft Learn, Vendor invoices overview). For invoice processing, the system automatically checks for consistency with PO price and received quantity, and routes discrepancies to an exception handling flow (see Microsoft Learn, Accounts payable invoice matching overview).
Conclusion
Implementing a manufacturing emergency procurement approval system in Thailand’s manufacturing sector is crucial for balancing on-site responsiveness with strengthened controls. Clearly defining functional and non-functional requirements, optimizing for field operations through phased pilots and acceptance testing, and measuring effectiveness with KPIs—along with continuous improvement through post-failure reviews—are key to true adoption and results.
If you have questions about system implementation, requirements definition, or evaluating suitability for local operations, please feel free to contact us. We can help you review emergency procurement criteria and approval routes in the context of your existing ERP and on-site procedures.