<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.
Localisation released on the engine's cadence — by the engineers who built it.
The traditional ERP localisation model relies on partner-maintained country packs released on a different cadence than the core engine. The Axional model implements localisation in the engine itself, released by the same engineers, on the same release calendar.
Same release cadence
Localisation changes release with the engine — no separate partner-pack calendar, no synchronisation problem.
Same engineers
The engineers who built the engine own the localisation. There is no second-tier of partner developers maintaining country variation.
Regulatory pace
When the regulator changes the rules, the engineers change the engine. The customer's deployment inherits the change through the regular update process.
Audit posture
Compliance evidence is auditable directly from the engine's journal. The auditor sees the same trail for localisation behaviours as for any other behaviour.
What the engine-level approach changes
Release synchronisation
Engine and localisation are one release stream. No version-incompatibility between engine v23 and partner pack v22; no regression risk from the synchronisation.
Ownership accountability
One team owns the engine and its localisation. When a regulation changes, the responsibility for delivering the change is unambiguous.
Customer-facing predictability
The customer's compliance posture moves on a predictable cadence. Regulatory changes are scheduled releases, not partner-pack project deliverables.
Audit-trail consistency
Localisation behaviours produce the same audit-trail discipline as the rest of the engine. The compliance review and the operational review share one trail.
Depth where it counts
The home market is implemented to home-market depth; emerging-demand markets to commercial-demand depth. The engineering effort follows the customer commitment.
Total cost of localisation
No partner-pack licence cost layered on the engine licence cost. The customer's localisation depth is part of what the engine licence includes.
Why the partner-pack model is a 1990s economics decision
The partner-pack model emerged when ERP vendors had global ambitions and limited local engineering capacity. Delegating localisation to partners let the vendor grow the country list without growing the engineering team. The trade-off — release-cadence lag, ownership ambiguity, audit-trail fragmentation — was acceptable when regulators moved slowly.
Regulators no longer move slowly. SII, TicketBAI, Verifactu, SUNAT, DIAN all release changes on cadences measured in months. The partner-pack model that was acceptable in the 1990s is fragile in the 2020s. Axional's engine-level approach reflects the regulatory reality the customer actually lives in.