Skip to content

Tenders

A tender is an incoming LV (Leistungsverzeichnis / bill of quantities) or RFQ: the customer demand Mercura matches against your article catalogue and prices into an offer. Tenders are one of the two entry points of the procurement workflow (the other is orders).

Creating a tender

POST /tenders is the programmatic twin of forwarding an LV / RFQ email to anfragen@lv.mercura.ai: send the same files you would attach to the mail and Mercura runs the identical intake pipeline — same parsers, same matching, same landing states. Accepted files: GAEB (.d81/.d83/.d94/.p81/.p83/.p93/.p94/.x81/.x83/.x93/.x94/.onlv), .xlsx, .csv, .docx, .txt, .pdf, images, and .eml. Max 50 MB per file, 100 MB total, 20 files. Mercura picks the file that drives parsing (GAEB before spreadsheet/CSV/DOCX/TXT before PDF before image); at least one file must be parsable.

Use the optional context field to pass anything that helps Mercura process the tender — the original email body, delivery notes, or guidance for article matching. An unresolvable customer_id / customer_email is not an error: the tender is created without a customer, exactly like an email from an unknown sender.