Question 1

What happens when a PO has a part number we've never seen?

Accepted Answer

It gets flagged, not guessed. The agent shows the line exactly as the customer wrote it, ranks the closest matches from your catalog, and waits for a person. Once you pick one, that mapping is remembered for that customer — the same line resolves on its own next time.

Question 2

Does this change anything in our ERP automatically?

Accepted Answer

No. The agent hands your team a validated, import-ready sales order; your team reviews it and brings it in. It holds no credentials to your ERP and cannot post an order on its own.

Question 3

Which ERPs does this work with?

Accepted Answer

The agent produces structured, import-ready order data. Whether that reaches your ERP as a file import, through an API, or via a custom connector depends on your environment, and it is something we build with each design partner rather than something we ship pre-certified. Bring your ERP and its import spec to the call and we'll tell you honestly whether it's a fit.

Question 4

What about scanned POs, faxes, and orders pasted into the email body?

Accepted Answer

All three are handled. Scans and faxes go through character recognition before extraction, and body-of-email orders are read straight from the message. Accuracy tracks the quality of the source, and anything low-confidence is flagged rather than guessed.

Question 5

How does it handle contract pricing and customer-specific pricing?

Accepted Answer

The agent reads the price the customer put on the PO and compares it to the price your system expects for that customer. When they disagree, the line is flagged with both numbers side by side. It doesn't decide which one is right — that's a judgment call with margin attached, and it stays with your team. Price validation is configured per design partner, since it depends on your pricing data.

Question 6

Who can see our customers' purchase orders? Do you train models on our data?

Accepted Answer

Access is limited to the people supporting your account, and documents can be deleted on request. Data handling, retention, and model-provider arrangements are agreed in writing with each design partner before any documents are processed — we'd rather put that in your contract than make a blanket claim on a web page.

Question 7

What happens when it gets something wrong?

Accepted Answer

You catch it in review, because every order stops there before it reaches your ERP. Each extracted field links back to the region of the source document it came from, so verifying a line takes seconds. Corrections feed the mapping for that customer, so the same mistake doesn't recur.

Question 8

Does this replace my order entry team?

Accepted Answer

No — it removes the typing. The people who know your customers and catch the problems are the reason this works at all. The agent hands them a validated draft instead of a blank screen, so the same team absorbs more volume and spends its attention on the exceptions instead of the keyboard.

Question 9

How long does onboarding take, and what do we need to provide?

Accepted Answer

About a week. We need a catalog export, roughly 30 recent purchase orders to calibrate against, and an hour with whoever does order entry today. We do the mapping work.

Question 10

What happens after the 30 days?

Accepted Answer

You decide whether to continue and we agree pricing then, at design-partner rates you keep. If it isn't working, we part company and you keep the catalog mapping we built.

Question 11

Do our customers have to change how they send us orders?

Accepted Answer

No. That's the point. They keep emailing purchase orders exactly as they do today.

Security

Where things stand

Engineering principles

Your ERP stays yours

Agreed with each design partner

Reporting a vulnerability