Use case · after-sales

    Quote an obsolete spare part during the call, not the next day.

    A stopped machine, a 12-year-old reference, a customer waiting on the phone. An after-sales agent identifies the part, walks its replacement chain and writes the answer into the request, with the reason and the stock. Your after-sales team keeps the customer and the decision.

    Simulated scenario made by Koddex · the figures are the film's

    The three questions behind every old reference

    Replaced how many times since 2014?

    Which supplier still makes it, under which name?

    And why this part rather than another?

    Step by step

    01Step 1 · Identify

    The reference becomes a known part

    The customer reads B7014-C-T-P4S on the failed spindle bearing. The agent normalises the reference, matches its FAG, SKF and NSK aliases and resolves the canonical item: spindle bearing 70×110×20, angular contact 15°, P4. The given reference has been obsolete since 03/2018, and a successor exists. Supplier data conflicts are caught when the data is compiled, not on the phone.

    The agent's plan

    • Normalise the referenceB7014CTP4S
    • Match supplier references3 aliases · FAG, SKF, NSK
    • Resolve the canonical item
    • Check data consistency0 conflicts
    The after-sales agent identifies the part.
    The after-sales agent identifies the part.
    One part, three supplier names, one item in Koddex.
    One part, three supplier names, one item in Koddex.

    02Step 2 · Trace

    The replacement chain is precomputed

    An obsolete part points straight to its current successor: the 2014 reference, the sealed variant of 2018, then the 2022 part with hybrid ceramic balls. Two hops, 0.8 ms. Every hop carries its reason and its date, and the agent checks compatibility (dimensions, contact angle, preload, speed) and stock: 3 units in Lyon.

    The agent's plan

    • Load the precomputed replacement chain
    • Walk the successors2 hops · 0.8 ms
    • Verify compatibilitydimensions · contact angle · preload · speed
    • Check stock3 units · Lyon
    2014 → 2018 → 2022, each hop explained.
    2014 → 2018 → 2022, each hop explained.
    Every hop has a reason and a date.
    Every hop has a reason and a date.

    03Step 3 · Answer

    Not just which part. Why this part.

    The explanation, the chain, the stock and the quote line are written into the request. The after-sales engineer reads the explanation, checks one point with the customer and sends the quote: one HCB7014-C-2RSD-T-P4S, €412, ships today.

    Lookup time

    0.8 ms

    Replacement hops

    2

    Stock

    3 units

    Lookup, chain, stock and explanation in the request.
    Lookup, chain, stock and explanation in the request.
    The engineer confirms with the customer and sends the quote.
    The engineer confirms with the customer and sends the quote.

    04Traceability

    The agent does the lookup. The engineer keeps the call.

    Every action of the agent and every decision of the after-sales team sits on the request's activity, from the identified part to the quote sent.

    Every action is traced.
    Every action is traced.

    What it changes

    From a 12-year-old reference to a sourced quote, during the call.

    Your spare parts catalogue, supplier references and replacement history sit in one graph in Koddex, compiled from your ERP, so the answer is ready before the customer hangs up.

    Answer during the call

    The replacement chain is precomputed: the lookup takes milliseconds, not a search through old files.

    One part, every supplier name

    FAG, SKF and NSK references resolve to the same item, with its characteristics.

    Obsolete is not a dead end

    Every replacement hop is dated and sourced, so the successor comes with its reason.

    Your team keeps the customer

    The agent prepares, after-sales decides, and every action is traced.

    A 20-min demo. Your first use case live in 1 month.

    Bring an old reference your after-sales team struggled with. We trace it in Koddex in the demo.