Does this require custom SAP development?

We don't have a native SAP connector yet. It moves to the top of the build queue when a customer commits to a pilot. In the meantime we post each approved order to a webhook URL your team owns. Some customers wire that into SAP themselves through their existing iPaaS, others wait for the native connector.

Will it match customer part numbers to our SAP items?

Line items are extracted and surfaced for review. The matching to your SAP item master happens during your import step (for IIF) or in your downstream wiring (for webhook). Per-customer SKU aliases are still recorded so the reviewer's corrections improve future extractions deterministically.

What if an order can't be matched cleanly?

It routes to an exception queue with the flagged field and the source document side by side. A CSR resolves it in seconds and the order becomes available to download / re-emit to your webhook, nothing is ever guessed into SAP.

On the roadmap

SAP sales order automation

When the SAP connector lands, validated orders will post into S/4HANA or ECC without per-customer EDI onboarding. Today, we deliver them to a webhook. We don't have a native connector for this ERP yet, it lands when our first customer using it commits to a pilot. In the meantime we can deliver orders to a webhook of your choice (JSON), and you can wire that into your ERP however your team already integrates other tools.

On roadmap

native SAP connector

0

templates to maintain

1-2 weeks

onboarding

Why SAP teams still re-key orders

SAP is built to manage orders once they're in the system, but it can't read the PDF a customer just emailed. So a CSR opens the attachment, finds the customer and items in SAP, and types the order in by hand, line by line.

OrderPier closes that gap. It reads the inbound purchase order, matches it to your SAP records, and posts the validated order to a webhook you wire to your ERP, so the document arrives as a ready-to-fulfill order, not a task in someone's inbox.

How a roadmap ERP works in the meantime

Capture the PO from a forwarded email or shared mailbox.
Extract every field and line item with confidence scoring.
Push approved orders as JSON to a webhook URL you provide (we POST the validated sales order. You handle the last hop).
Once you commit to a pilot, we prioritize a native SAP connector.

SAP questions

Does this require custom SAP development?: We don't have a native SAP connector yet. It moves to the top of the build queue when a customer commits to a pilot. In the meantime we post each approved order to a webhook URL your team owns. Some customers wire that into SAP themselves through their existing iPaaS, others wait for the native connector.
Will it match customer part numbers to our SAP items?: Line items are extracted and surfaced for review. The matching to your SAP item master happens during your import step (for IIF) or in your downstream wiring (for webhook). Per-customer SKU aliases are still recorded so the reviewer's corrections improve future extractions deterministically.
What if an order can't be matched cleanly?: It routes to an exception queue with the flagged field and the source document side by side. A CSR resolves it in seconds and the order becomes available to download / re-emit to your webhook, nothing is ever guessed into SAP.

First in line for the SAP connector

Try extraction on your own POs free today. Commit to a pilot and the native SAP connector moves to the top of the build queue.