From any purchase order to a delivered supplier document
Six stages, one workflow. Here's exactly what happens when an order is sent to the supplier.
Receive in any format
Buyers send POs however they like — a PDF email attachment, an XLSX export, cXML posted to your REST endpoint, EDI dropped on SFTP. ProcuLink ingests all of it through one inbox. Upload and the inbound API are on every plan; email, IMAP, SFTP and S3 pickups are Growth plan and up.
Read it into one standard order
Every order is parsed into one neutral structure — the canonical order. PO number, parties, line items, terms and totals each become a field with a confidence score and visible provenance.
Resolve issues with AI
When a buyer item code doesn't match the supplier catalog, an LLM proposes the right code with its reasoning and source. Your team confirms or rejects — nothing is auto-applied without confidence you can see.
Validate before anything leaves
Built-in checks run on every plan and cannot be switched off: an order needs a PO number and a currency, every line needs a quantity above zero and a price that is not negative, and a line whose supplier item code is still unresolved holds the order back instead of being sent blind. Your own rules for a supplier — an accepted currency list, a required ship-to or incoterm, a value range — are a versioned acceptance profile, and authoring or activating one is Enterprise plan and up.
Transform & deliver
The canonical order is transformed into the exact format the supplier requires and delivered over their channel — webhook on Growth plan and up, SFTP or email on every plan, or an ERP connector on Enterprise plan and up. cXML output is Operations plan and up; the other formats are on every plan. Every attempt is recorded with its response code and a SHA-256 fingerprint of the bytes sent.
Walk through a real delivery
Watch a single upload become a delivered supplier order — parsed, mapped, validated, and sent.