Capabilities
Every format and method, in one place
ProcuLink takes orders in however your buyers send them and delivers them in exactly the format and channel each supplier needs. Here's the full picture — and we keep it honest: nothing is marked Supported unless it works in production today. Don't see yours? It's very likely Configurable or On request — just ask.
SupportedWorks today — set it up yourself in the app.
ConfigurableWorks today; we switch it on with you in a quick setup.
On requestNot built yet, but straightforward — we'll add it for your rollout.
PlannedOn the roadmap.
Get data in — methods
How orders reach ProcuLink.
SupportedManual upload (drag-and-drop / browse)
Drop a file straight into the app.SupportedREST API
POST orders as JSON with an API key — Zapier, Make, or your own code.SupportedEmail inbox polling (IMAP)
We poll your mailbox for order attachments. Integration plan.SupportedSFTP folder pull
Point us at an SFTP folder; we import new files. Integration plan.SupportedS3 / R2 bucket pull
Watch a bucket prefix for order files. Integration plan.ConfigurableHosted inbound email address
Forward orders to your orders@… address; we set up the receiving domain.On requestAS2 / PEPPOL network receive
Through a certified access-point partner.Get data in — formats we read
What an incoming order file can be.
SupportedCSV
Delimiters and common column aliases auto-detected.SupportedExcel (XLSX)
First worksheet, header row.SupportedPDF (text-based)
Text layer read, then AI structured extraction. Deterministic fallback when no AI key.SupportedPDF (scanned / image)
No text layer — read by AI vision extraction. Assisted: every line is flagged for review.SupportedcXML 1.2
OrderRequest documents.SupportedUBL 2.1 / Peppol BIS
Order documents.SupportedSAP IDoc ORDERS05
SAP's ORDERS05 purchase-order IDoc, sent as XML.ConfigurableEDIFACT ORDERS
D96A — core segment coverage today; we verify your message files with you during setup.SupportedANSI X12 850
004010 / 005010.SupportedJSON
Via the REST API order shape.Get data out — delivery channels
How the finished order reaches each supplier.
SupportedHTTPS webhook (POST / PUT)
Auth: API key, bearer, basic, or OAuth2 fetch-token.ConfigurableSFTP
Password or private-key. Configure it yourself; we verify it with you on a real folder before go-live.ConfigurableFTPS
Explicit TLS. Configure it yourself; we verify it with you on a real folder before go-live.ConfigurableEmail (SMTP)
The order is sent as an attachment. Configure it yourself; we verify your mail server with you before go-live.ConfigurableErply (ERP connector)
We switch it on with you against your Erply account before go-live.ConfigurableDirecto (ERP connector)
We switch it on with you against your Directo account before go-live.On requestMore ERP connectors
Fortnox, Visma, e-conomic, Dynamics 365 BC, NetSuite, SAP…On requestAS2 / AS4 / PEPPOL access point
Through a certified partner.Get data out — formats we produce
What we transform each order into. Set per supplier.
SupportedCSV
Configurable columns.SupportedXML (generic)
SupportedcXML 1.2
SupportedUBL 2.1 / Peppol BIS
SupportedANSI X12 850
SupportedJSON
On requestEDIFACT ORDERS
Outbound EDIFACT transformer on request.Don't see your format or method?
Tell us your supplier's requirement. Most formats and channels are already supported or a quick configuration away.