Exchange Core Tracking

What an exchange is

An exchange is a transaction in which a supplier ships a serviceable unit to a customer, and the customer sends back their unserviceable unit of the same type. The unit that comes back is the core. The customer pays for the difference in value rather than for a whole new unit, and the supplier keeps the core to repair and sell again.

It is one of the oldest arrangements in the aircraft parts trade and one of the most useful. It is also, from a systems point of view, one of the most awkward transactions in the industry — because the sale finishes long before the transaction does.

How it differs from the alternatives

• Outright — the customer buys the unit and owes nothing back. Simple, and the most expensive option for them.
• Exchange — the customer receives a serviceable unit immediately and returns a core. Fast, capital-efficient, and creates a return obligation.
• Repair — the customer sends their own unit in and gets that same unit back. Cheapest per event, slowest, and the aircraft waits.
• Loan or rental — the customer receives a unit temporarily and returns that same unit. The obligation is to return the specific asset, not an equivalent one.

The distinction that matters operationally is between transactions where a specific asset must come back (loan, rental, repair) and transactions where an equivalent asset must come back (exchange). Equivalence is a judgment, and judgments are where disputes live.

Why exchange programs exist

Exchange survives because it solves a real problem for both sides, and it is worth being explicit about what each party is buying.

What the customer gets

Primarily, time. An aircraft on ground is expensive by the hour, and a repair cycle measured in weeks is not an option when the alternative is a serviceable unit shipped today. Exchange converts a repair turn time into a shipping time. Secondarily, they get price certainty — an exchange fee agreed in advance, instead of a repair quote that will not exist until the unit has been opened.

What the supplier gets

A better return on the same inventory. One serviceable unit can serve many customers over its life, because each exchange returns a core that becomes the next serviceable unit. The rotable pool is the asset; exchange is how the asset earns repeatedly. Suppliers also gain a durable customer relationship, since exchange arrangements tend to be repeat business.

The economics only work if the cores actually come back, and come back in a condition worth repairing. That single dependency is the source of everything difficult about exchange.

What an exchange creates: the core obligation

The moment a serviceable unit ships on exchange terms, three things happen at once. The commercial sale is made. A physical asset leaves. And an obligation opens that will not close for weeks or months.

That obligation is normally described by four values:

• Core valueWhat the returned unit is worth to the supplier as a repairable asset. It is the reason the exchange price is lower than outright.
• Core chargeThe amount the supplier will bill if the core is not returned, or comes back unacceptable. It is security, not revenue.
• Core due dateThe date by which the core must be received. Commonly 14 to 30 days, but entirely contract-dependent.
• ExposureWhat the supplier stands to lose right now across all open cores if none of them came back. This is the number that matters and the one least often visible.

The awkwardness is structural: from the commercial system's point of view, this transaction is finished. The order shipped, the invoice went out, the revenue is recognized. Everything a system of record is designed to care about has concluded. Meanwhile the operationally significant part of the transaction — an asset owed to you, aging, held by somebody else — has only just begun.

Where it gets operationally difficult

The obligation is invisible once the sale closes

This is the root problem and everything else follows from it. Sales consider the order shipped. Accounting considers it invoiced. The warehouse considers it picked. There is frequently no role whose job description includes "notice that this core has not come back," which is why so many organizations discover the problem through a year-end reconciliation rather than through an operational process.

Aging without an owner

Core due dates pass quietly. Nothing fails, nothing alarms, and the unit simply does not arrive. By the time somebody notices, the commercial conversation is harder — the customer's maintenance event is a distant memory, the person who ordered it may have moved on, and asking for a core ninety days late damages a relationship in a way that asking at day twenty does not.

Getting the core back is a customer relationship problem

The core is not lost. It is usually sitting in the customer's shop, in a box, behind other work, waiting for somebody to raise a shipment. Chasing it is collections work performed by operations people, and it is done well by the organizations that do it early, politely and consistently — and done badly by the organizations that only start when the finance team asks.

Receiving a core nobody was expecting

Cores frequently arrive unannounced, poorly labeled, referencing an order number that means nothing to the receiving clerk. Matching an inbound unit to the open obligation it satisfies is genuinely difficult, and a core booked into general stock instead of against its obligation is worse than one that never arrived — the exposure stays open while the asset is already on your shelf.

Inspection and disposition: where equivalence is judged

This is the technically substantive part. The core has to be assessed against what the contract said would come back, and there are more failure modes than people expect:

• Wrong unit. A different part number, or an interchangeable one that the exchange terms do not accept.
• Incomplete. Missing hardware, missing sub-assemblies, missing data plate. A unit stripped for other work before it was returned.
• Robbed. Serviceable components removed and replaced with unserviceable ones, or not replaced at all.
• Damaged beyond the expected condition. Handling damage, corrosion, evidence of an event rather than of normal wear.
• Beyond economic repair. Technically restorable but not at a cost that leaves the core worth anything.
• Undocumented. No removal tag, no reason for removal, nothing establishing that the unit was not involved in an incident.
• Life-expired. A life-limited part with no remaining life is not a repairable asset regardless of its physical state.

Each of these produces a different commercial answer, and each requires evidence that will withstand a customer disagreeing. Disposition is where the money in an exchange program is actually made or lost.

Financial resolution

Once dispositioned, the obligation has to be closed commercially: release the core charge if the core was acceptable, issue partial credit where it was acceptable but degraded, or bill the core charge where it was not returned or not acceptable. This closes the loop — and it is the step most often left incomplete, because it requires the operational judgment and the commercial system to agree, and those usually live in different places.

The other side of the same transaction

Most of the above is written from the supplier's perspective. Every organization that sells exchanges also buys them, and the obligations run the other way.

When you take a unit on exchange from a vendor, you owe them a core. That core is typically the unit you removed, which may currently be in your own shop, at a subcontractor, or waiting on a teardown that has not been scheduled. Missing a vendor's core due date costs real money at their core charge, and it is embarrassing in a market where the same names recur. Organizations that track their outbound cores rigorously and their inbound obligations casually are exposed in a direction they rarely measure.

What organizations should think about

These questions tend to reveal how well an exchange program is actually being run:

• What is your total open core exposure right now? Not last quarter — now. If producing the number requires assembling a spreadsheet, it is not being managed operationally.
• How many open cores are past their due date, and by how long? Aging distribution tells you more than a total. A few very old cores usually means nobody owns the chase.
• Who is responsible for chasing a core on day twenty-one? If the answer is a role rather than a named habit, good. If it is "whoever notices," the program is running on luck.
• When a core arrives, how is it matched to its obligation? And what happens if the paperwork with it is wrong?
• How long between a core arriving and being dispositioned? Cores waiting for inspection are exposure that has already been physically resolved but not commercially resolved.
• How many cores were billed at the core charge last year, and why? A number near zero may mean excellent compliance — or that nobody is enforcing the terms.
• What do you owe your vendors in cores today? The direction most organizations measure least.

How this connects to the Aviation Operating Platform

Exchange cores are the clearest single illustration of why aviation needs something above its system of record.

Nothing about the problem is a data problem. The order exists. The shipment exists. The core charge is on the contract. The due date is calculable. Every fact required to manage an exchange program well is already recorded somewhere. What is missing is a place where those facts are held together as a live obligation — with an age, an exposure, an owner and a next step — rather than as the residue of a sale that the commercial record considers finished.

That is precisely the definition of an Aviation Operating Platform: a system concerned with the state of operational work rather than the recording of transactions, in which an obligation that outlives its invoice is a first-class thing the system understands rather than something a person has to remember. The aviation ERP page explains why a system of record is not the natural home for that kind of state, and aviation inventory software covers the related question of ownership — because an open core is, in the end, an ownership state that has not yet resolved.

Common questions