<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 quote to firm order — with the contract, the credit limit and the margin in view.
Multi-line quotations with validity windows, conversion tracking, multi-level approvals, blanket and framework orders, change control. The salesperson sees the contract, the credit limit and the margin before confirming the order, not in a follow-up report.
Quotation engine
Multi-line quotations with validity windows, version control and conversion tracking. The same engine produces a PDF for the customer and a record the salesperson can revise.
Approval at the right level
Discount-driven approvals (the larger the discount, the higher the approver), category overrides, segregation-of-duties checks, audit trail by approver and action.
Order types
Standard, blanket, framework, project-bound, consignment, repair, exchange — each with its own commercial logic, all in one schema.
Change control
Order changes (quantity, delivery date, ship-to) tracked against the original. Audit trail preserves who changed what and when.
What the order surface covers
Quotation life-cycle
Draft → presented → accepted → converted. Validity windows enforced; lost quotes captured with reason; conversion analytics by salesperson, customer, product.
Approval workflow
Configurable approval matrices by discount band, customer segment, product line, geography. Out-of-office delegation with auto-fallback.
Order types
Standard sales order, blanket umbrella, framework release, project-bound (linked to PS module), consignment, repair, exchange, sample — each routed through the right operational pipeline.
Pricing and margin at entry
Pricing engine applies the right tariff at the line; standard cost surfaces alongside; margin visible before confirmation; floor-below approval routing.
Credit check inline
Customer credit exposure checked at order entry and at delivery. Hard block prevents post; soft block routes for override with documented justification.
Order audit
Every confirmed order traceable to the requirements, the approvals, the credit decision and the pricing rule. The auditor opens an order by clicking a row.
Why one order schema for every channel
Some ERPs maintain separate order schemas for direct sales, B2B portals, EDI feeds and marketplace integrations. The argument is fit — each channel has its own quirks. The cost is reconciliation: the same product sold through two channels appears as two different records, with the customer-360 view depending on a nightly aggregation job.
Axional uses one order schema for every channel. The channel is an attribute of the order, not a separate object. The reconciliation happens at the moment the order lands, not in a downstream warehouse. The customer-360 view is a query, not an aggregation.