Concrete situations in a plant's purchasing, and what Konyx does about each.
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.
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.
Related: Ask Konyx — request intake · Matching against the company's own catalog
Source: konyx-erp — Ask Konyx with photos · Checked 26 September 2026 · Version 1 · use-cases.no-part-number
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.
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.
Related: One RFQ to all the vendors · Purchase orders from a quote
Source: konyx-api — core/supplier-part.ts · Checked 28 September 2026 · Version 2 · use-cases.supplier-part-numbers
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.
Related: Vendor discovery on the open web · Discovered vendors are reviewed
Source: konyx-api — core/discovery · Checked 26 September 2026 · Version 1 · use-cases.rush-part-no-supplier
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.
Related: Purchase history beside every line · Quotes side by side
Source: konyx-api — core/purchase-context.ts · Checked 26 September 2026 · Version 1 · use-cases.last-paid-price
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.
Related: The vendor's quote link · Quotes side by side
Source: konyx-erp — vendor portal and comparison grid · Checked 26 September 2026 · Version 1 · use-cases.quotes-in-pdfs
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.
Related: Roles and permissions · Routing, escalation, notes and notifications
Source: konyx-api — permissions and escalation · Checked 26 September 2026 · Version 1 · use-cases.employee-cannot-send
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.
Related: Sending from the buyer's own email · Email
Source: konyx-erp — own-email sending · Checked 26 September 2026 · Version 1 · use-cases.send-from-own-domain
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.
Related: The savings audit · Baseline — before any contract · How savings are measured
Source: konyx-admin — Audit page · Checked 26 September 2026 · Version 1 · use-cases.business-case-before-contract
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.
Related: Ask Konyx — request intake · Vendors ranked with reasons · Plan limits per company
Source: konyx-erp — Ask Konyx with spreadsheets · Checked 26 September 2026 · Version 1 · use-cases.spreadsheet-of-parts
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.
Related: Routing, escalation, notes and notifications
Source: konyx-erp — request page, notes, notifications · Checked 26 September 2026 · Version 1 · use-cases.tracking-a-request
