AERONEXUM
Request a Demo

AERONEXUM Operations

Core Exchange Process Flow

How AERONEXUM keeps the exchange sale, the returned unit, the financial exposure and the supporting evidence connected as one operational backbone.

What the flow protects

An exchange is two obligations running in opposite directions at once: a unit going out, and a core coming back. They are agreed at different moments, settled at different moments, and are easy to lose track of separately. This flow keeps them as one thing.

  • One flowSource, return, inspection, resolution and evidence stay connected rather than living in separate systems.
  • One next actionBlocked work points to the exact task needed to move the core forward.
  • One record of truthEach task saves back to the right operational record for audit and customer follow-up.
  • One explainable outcomeWhether the core is returned, waived or charged, the reason and the financial result are recorded together.

The flow

Four phases, read top to bottom. The main path runs down the center. Where a phase can stall, the exception is shown to the right of the step that raises it.

The path of an exchange core from sale to closure, in four phases A vertical flow in four phases. Phase one, source, creates the exchange sale carrying the core expectation, confirms the exchange source, and confirms the core terms including due date, policy and exposure basis. Phase two, return, asks whether the core was returned within the agreed window; if not, follow-up and exposure stay visible, and if so the return is received into intake with carrier, tracking, warehouse and location. Phase three, disposition, inspects the unit and verifies condition, part number and serial before setting accepted, repair, scrap or vendor return, then asks whether the core obligation is satisfied; if not, the exposure is resolved by waiving, charging or partially charging, with the reason recorded. Phase four, closure, closes the core obligation with an explainable financial outcome and preserves the evidence packet. Beneath, four supporting panels describe how blocked work is moved forward. PHASE 4 Closure PHASE 3 Disposition PHASE 2 Return PHASE 1 Source Exchange Sale Created The sales order or invoice carries the core expectation Confirm Exchange Source Customer, part, quantity and source line Confirm Core Terms Due date, policy and exposure basis Saved directly to the core terms Core returned within the window? Measured against the agreed due date Follow Up / Exposure Customer communication and aging stay visible NO Receive Return Intake Carrier, tracking, warehouse and location Inspect and Disposition Verify condition, part number and serial Set accepted, repair, scrap or vendor return Satisfies the core obligation? Judged against the terms agreed at sale Resolve Exposure Waive, charge or partially charge Reason and invoice outcome are recorded NO Close Core Obligation The financial outcome is explainable Preserve Evidence and Print Packet Documentation stays attached to the record HOW BLOCKED WORK IS MOVED FORWARD Guidance Action Opens the exact task needed Needs Attention Card Explains the blocker and the next step Task Dialog Save without leaving the core workflow Exception Handling Repair, reject, vendor return or charge
The core is not a separate errand that runs alongside the sale. It is part of the same obligation, and it stays attached to the sale until it is closed, waived or charged.

How to read it

Rectangles on the center line are steps. Highlighted panels are the questions that decide whether the flow continues. The muted panels on the right are what happens when the answer is no — each one returns to the flow once it is resolved, rather than ending it. A core is never simply dropped; it is closed, waived or charged, and the reason is recorded either way.