<media type="image" src="…"/>
as a child of <hero>, switching this page to the
full-bleed dark variant.
Recommended : 1920 × 1080 px (16:9)
Formats : PNG · JPEG · WebP · SVG
Off-spec uploads are rejected — aspect ratio outside 16:9 ±2 %, dimensions outside 800 × 450 … 3840 × 2160.
From requisition to firm order — with approval, scoring and contract context.
A purchasing engine that takes a requisition through the right approval path, runs an RFQ where the category demands it, scores supplier responses against price, lead-time and performance history, and emits the firm order against the right framework contract.
Requisitions
Operational requesters raise needs against catalogues, free text or framework contracts. Approval path determined by category, amount and entity.
RFQ workflows
Multi-supplier solicitation with structured response templates. Responses compared on price, lead-time and total-cost-of-acquisition; supplier performance history weighed into the score.
Multi-level approval
Configurable approval chains with parallel and serial steps, delegation, out-of-office handling, full audit trail of who approved what and when.
Blanket and framework orders
Pre-negotiated price and volume umbrella, with release orders drawn down against the umbrella by the operations team.
What the purchasing engine covers
Requisition
Free-text, catalogue, framework or stock-replenishment requisitions. Required-field controls by category. Visible budget impact at the point of capture.
RFQ
Multi-supplier solicitation, structured response capture, blind-bid options for sensitive categories, scoring matrix configurable per category.
Approval engine
Amount thresholds, category overrides, segregation-of-duties checks, delegated approvers with auto-fallback, audit trail by approver and action.
Firm PO emission
Standard, framework-release, blanket, stock-replenishment and project-specific PO types. EDI-out where supplier supports it; PDF and email where not.
PO change control
Quantity, price, delivery-date and ship-to changes tracked against the original PO. Audit trail preserves the change history.
Buyer dashboard
Open POs by status, ageing-against-due-date, supplier-side acceptance state, expedite candidates, all visible on one screen.
Why the framework contract is the anchor, not the PO
Most procurement engines treat the PO as the primary commercial object — a one-off agreement that exists only between requisition and goods receipt. The framework contract underneath, where one exists, is a reference document at best.
Axional inverts this. The framework contract is the primary commercial object; the PO is a release against it. Price, volume commitments and discount tiers live on the framework; the PO inherits them. When the operations team raises a release, the engine knows whether the volume threshold for the next discount band has been crossed; when the contract expires, every open PO is flagged for renegotiation, not silently re-priced.