Automate purchase orders without replacing your ERP

You can automate purchase-order preparation without replacing an ERP by connecting the existing demand, supplier and approval records, then automating repeatable checks and drafts around them. Keep the ERP as the system of record and require a person to approve the final purchasing commitment.

An ERP replacement is not a prerequisite for improving procurement. The useful starting point is a workflow where teams still move details between work orders, BOMs, email, spreadsheets and the purchasing system. Automate the handoffs that are clear, while leaving sensitive decisions with their current owners.

A safe design avoids creating another disconnected list of orders. It links a request to its source, shows what has been checked, records who approved it and updates the existing process only through an agreed integration or controlled handoff.

Practical steps

1. 01Choose a repeatable purchase workflow with a visible problem, such as quote follow-up or routine replenishment. Define its start, the required source records and the decision that makes a draft ready for review.
2. 02Connect the minimum information needed: work order, BOM item, quantity, required date, supplier status, open orders and purchasing rules. Start read-only where possible and document which system owns each value.
3. 03Write down the checks before automating them. Define duplicate detection, price or quantity exceptions, supplier eligibility and required approvals. Send missing or conflicting information to a person instead of allowing a guessed value into a draft.
4. 04Generate a PO draft with traceable supporting records. Show the proposed supplier, part, quantity, price, delivery terms and source quote. The designated approver reviews the draft and makes any change through the normal authority process.
5. 05Return approved information to the ERP through an agreed connector or operator handoff. Monitor rejected drafts, missed updates and supplier changes, then adjust the workflow before extending it to other categories.

How Achilles does this

Achilles works alongside an existing ERP. It reads work-order and BOM context, supplier responses and open purchasing information, then prepares a PO for approval. This helps procurement act on current job needs without requiring a rip-and-replace project.

The ERP remains the purchasing record, and a person approves the order. The workflow can be introduced around one process, with the integration and write-back limited to what the manufacturer approves. Teams can expand only after the first workflow is useful and controlled.

Start by agreeing which records the workflow may read and which fields, if any, can be written back. A draft can remain outside the ERP until an authorized person approves it; after approval, the system can use the agreed handoff to create or update the purchasing record. Keep a visible exception when a write fails, so a retry does not create a second order and a person can resolve the mismatch.

A focused rollout also needs a named owner for access, supplier data and approval rules. Test routine cases alongside exceptions such as a missing part number, changed quantity or supplier substitution. Confirm that the ERP still reflects the approved transaction and that users know where to find the source and audit trail. Expand the connection only when people can explain the process and trust its controls.

Before broadening access, check that the workflow preserves the ERP's required fields and does not bypass existing segregation of duties. Document who can change a supplier, edit a draft and approve a release. These boundaries make automation useful without confusing a prepared purchase with a committed one.