<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.
Every channel terminates in one order — portal, EDI, marketplace, direct.
A customer portal for self-service order capture, inbound and outbound EDI on the standards each market expects, marketplace integration, and a single order schema underneath. The salesperson, the customer and the operations team work from the same record.
Customer portal
Self-service order capture, order status, invoice history, payment history — single channel, audit-trailed, with the customer's pricing applied.
Inbound EDI
X12, EDIFACT, PEPPOL, custom XML — the protocol the customer demands, parsed into the same order schema.
Outbound EDI
Order confirmation, ASN, invoice, dispute response — emitted in the format each customer's ERP expects.
Marketplace integration
Direct connectors to industry-specific marketplaces; the order arrives in the same schema as a portal capture.
What the channel surface covers
Self-service portal
Customer-side order entry against their own pricing, order tracking, dispute reporting, invoice and payment history, document download, user-management at the customer side.
EDI inbound
ANSI X12 (850 PO, 856 ASN, 810 invoice), EDIFACT (ORDERS, DESADV, INVOIC), PEPPOL, OASIS UBL — translated into the same order schema, with errors routed to the customer-service team.
EDI outbound
Order acknowledgement, ship notice, invoice, credit notes — emitted in the standard each customer expects, with delivery confirmation tracked.
Marketplace connectors
Industry-specific marketplaces (B2B procurement portals, regulated-product exchanges) integrated as channels — orders flow into the same schema.
Channel-specific validation
Per-channel rules — required fields, allowed product range, customer-side credit checks — applied at the channel boundary; channel-clean orders move forward, dirty orders route to remediation.
Channel analytics
Order volume by channel, error rate by channel, average time-to-process by channel — visible to operations for channel-mix optimisation.
Why one schema beats one bridge per channel
A common pattern in ERP integration is a bridge per channel — one transformation for EDI, another for the portal, another for the marketplace, each mapping into a slightly different internal schema. Maintenance becomes a project per channel; adding a new channel touches every downstream consumer.
Axional uses a single internal order schema with channel-specific translators at the boundary. Adding a new channel adds one translator; everything downstream — fulfilment, invoicing, customer service, analytics — sees the same order shape it has always seen.