{
  "catalog": {
    "name": "Konyx Knowledge Catalog",
    "version": "1.0",
    "updatedAt": "2026-10-02",
    "owner": "Konyx Industrial Intelligence",
    "contact": "ceo@konyxai.com",
    "site": "https://konyxai.com",
    "description": "The structured, versioned facts about Konyx — industrial procurement software for MRO and indirect spend — that konyxai.com and AI assistants answer from. Every record names its source and the date it was last checked against the product; a capability says whether it is live, planned or not offered.",
    "formats": {
      "html": "https://konyxai.com/knowledge",
      "json": "https://konyxai.com/api/knowledge",
      "markdown": "https://konyxai.com/llms-full.txt",
      "index": "https://konyxai.com/llms.txt"
    }
  },
  "domain": {
    "slug": "use-cases",
    "name": "Problems and solutions",
    "description": "Concrete situations in a plant's purchasing, and what Konyx does about each.",
    "question": "What problems does Konyx solve?",
    "url": "https://konyxai.com/knowledge/use-cases"
  },
  "records": [
    {
      "id": "use-cases.no-part-number",
      "domain": "use-cases",
      "slug": "no-part-number",
      "name": "The technician does not know the part number",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — Ask Konyx with photos"
      },
      "summary": "Problem: a coupling has failed and the technician knows the machine, not the part. Konyx: they photograph the nameplate or the part and say what it is for; Konyx drafts the line, asks the one question that matters (size, material, seal type — with answers to tap), matches it against the catalog and purchase history, and ranks the vendors who carry it.",
      "body": [
        "What the buyer receives is a structured request with the catalog match, the last price paid and the candidate vendors — not a phone call to decode."
      ],
      "audiences": [
        "technicians",
        "buyers"
      ],
      "related": [
        "capabilities.ask-konyx",
        "capabilities.catalog-matching"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#no-part-number"
    },
    {
      "id": "use-cases.supplier-part-numbers",
      "domain": "use-cases",
      "slug": "supplier-part-numbers",
      "name": "The same gasket has a different number at every supplier",
      "verifiedAt": "2026-09-28",
      "version": 2,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/supplier-part.ts"
      },
      "summary": "Problem: one gasket is 101-100-234 at one distributor and LSV-BV-200 at the next; a document with the wrong code gets the wrong part shipped. Konyx: each vendor's copy of the RFQ and the purchase order carries that vendor's own item number, resolved from the item master, a lead list, that vendor's catalog or — for a vendor found on the web — their own product page, and left blank when there is no confident match.",
      "body": [
        "The manufacturer's part number sits under the manufacturer on every document, so nothing is lost. Purchase-order lines snapshot the supplier code at issue, so a reimported catalog can never change a filed PDF."
      ],
      "audiences": [
        "buyers",
        "vendors"
      ],
      "related": [
        "capabilities.rfq",
        "capabilities.purchase-orders"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#supplier-part-numbers"
    },
    {
      "id": "use-cases.rush-part-no-supplier",
      "domain": "use-cases",
      "slug": "rush-part-no-supplier",
      "name": "A rush part with no known supplier",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/discovery"
      },
      "summary": "Problem: a niche part nobody on the vendor list carries, and the line is down. Konyx: after the company's own vendors and the Konyx network have answered, it searches the web, reads the candidates' contact pages, and shows a Found on the web section with contacts, reasons and a score. The buyer picks who to ask; nothing is emailed until they do.",
      "audiences": [
        "buyers"
      ],
      "related": [
        "capabilities.vendor-discovery",
        "control.discovered-vendors-reviewed"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#rush-part-no-supplier"
    },
    {
      "id": "use-cases.last-paid-price",
      "domain": "use-cases",
      "slug": "last-paid-price",
      "name": "What did we pay last time?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/purchase-context.ts"
      },
      "summary": "Problem: a quote arrives and nobody has the last invoice to hand, so it is accepted as it is. Konyx: the price paid last time — from imported history, earlier quotes and earlier requests — sits under the request line and beside every quoted line, and the contract price appears where a contract exists.",
      "audiences": [
        "buyers",
        "finance"
      ],
      "related": [
        "capabilities.bought-before",
        "capabilities.quote-comparison"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#last-paid-price"
    },
    {
      "id": "use-cases.quotes-in-pdfs",
      "domain": "use-cases",
      "slug": "quotes-in-pdfs",
      "name": "Quotes come back as PDFs and email threads",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — vendor portal and comparison grid"
      },
      "summary": "Problem: six vendors answer in six formats and the buyer retypes them into a spreadsheet to compare. Konyx: vendors price each line through a no-login link, quotes land as comparable lines in one grid with the lowest highlighted, and revisions are kept rather than overwritten.",
      "audiences": [
        "buyers",
        "vendors"
      ],
      "related": [
        "capabilities.vendor-quote-portal",
        "capabilities.quote-comparison"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#quotes-in-pdfs"
    },
    {
      "id": "use-cases.employee-cannot-send",
      "domain": "use-cases",
      "slug": "employee-cannot-send",
      "name": "An employee who may raise a request but not send an RFQ",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — permissions and escalation"
      },
      "summary": "Problem: the plant wants anyone to be able to ask for a part, but only procurement to talk to vendors. Konyx: request.create and rfq.send are separate permissions. An employee's request routes to the first person up their supervisor chain who can act; an employee calling the RFQ endpoint directly gets a refusal, not a hidden button.",
      "audiences": [
        "IT and security",
        "buyers"
      ],
      "related": [
        "capabilities.roles-and-permissions",
        "capabilities.request-routing"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#employee-cannot-send"
    },
    {
      "id": "use-cases.send-from-own-domain",
      "domain": "use-cases",
      "slug": "send-from-own-domain",
      "name": "Vendors must hear from the plant's own domain",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — own-email sending"
      },
      "summary": "Problem: policy or vendor relationships require RFQs to come from procurement at the company's own address. Konyx: the buyer switches the send screen to their own email; Konyx prepares each vendor's message, the buyer sends it from their mail app and ticks who they sent; the record shows it and the quotes still come back through the link.",
      "audiences": [
        "buyers",
        "IT and security"
      ],
      "related": [
        "capabilities.own-email-sending",
        "integrations.email"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#send-from-own-domain"
    },
    {
      "id": "use-cases.business-case-before-contract",
      "domain": "use-cases",
      "slug": "business-case-before-contract",
      "name": "Proving the case before signing anything",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-admin — Audit page"
      },
      "summary": "Problem: finance wants a number before a pilot, and vendor claims are not evidence. Konyx: the company sends one export of its purchasing history; Konyx computes the price gaps, cycle times and buyer hours from that file and writes the findings up. The baseline is the company's own data, before any contract.",
      "audiences": [
        "finance"
      ],
      "related": [
        "capabilities.savings-audit",
        "pilot.baseline",
        "proof.savings-audit-method"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#business-case-before-contract"
    },
    {
      "id": "use-cases.spreadsheet-of-parts",
      "domain": "use-cases",
      "slug": "spreadsheet-of-parts",
      "name": "A shutdown list of thirty lines in a spreadsheet",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — Ask Konyx with spreadsheets"
      },
      "summary": "Problem: a turnaround list arrives as a spreadsheet and each line would be a separate request. Konyx: drop the file into Ask Konyx; every row becomes a line on one request, matched against the catalog, with vendors ranked by how many of the lines they cover — then one RFQ goes to all of them.",
      "audiences": [
        "buyers",
        "technicians"
      ],
      "related": [
        "capabilities.ask-konyx",
        "capabilities.vendor-ranking",
        "capabilities.plan-limits"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#spreadsheet-of-parts"
    },
    {
      "id": "use-cases.tracking-a-request",
      "domain": "use-cases",
      "slug": "tracking-a-request",
      "name": "Where is my request?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — request page, notes, notifications"
      },
      "summary": "Problem: the technician who asked for the part has to phone the buyer to find out what happened. Konyx: the request page shows where it is, who it is with and every step on its timeline; notes go back and forth on the request; the bell announces a note, a quote or an order; and the requester can change the request themselves before anything goes out.",
      "audiences": [
        "technicians"
      ],
      "related": [
        "capabilities.request-routing"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#tracking-a-request"
    }
  ]
}