An email order reaches your ERP without retyping

The pilot has a fixed price that we confirm before kickoff, once we know how your ERP accepts orders from an external service. There is no hourly rate and no paid analysis. After the pilot you pay a monthly subscription sized to your order volume.

We are starting with Comarch ERP Optima, an ERP widely used in Poland. For other systems, such as Microsoft Dynamics 365 Business Central, SAP Business One or Oracle NetSuite, we first check two things: that the ERP lets an external service create a sales order, and that it exposes the item and customer master data. Some vendors offer that access only in a higher edition or under a separate licence. If something has to be bought, or saving orders is not possible, you hear it before you sign.

Try it first, because it may be enough. Some built-in tools read a clean PDF that an employee uploads. Others, such as the Sales Order Agent in Business Central, watch a mailbox themselves. If the built-in tool copes with your real emails, you do not need the pilot. It earns its place when orders are written in the email body, arrive as spreadsheets or photos, or use the customer's own names instead of your item codes, and the built-in tool leaves those to your team. On the first call we look at a few of your emails and tell you which route is enough.

Your employee approves every order before it is saved in the ERP. In the panel they see what the customer wrote next to what will go into the ERP, and the lines the AI is not sure about are marked for checking. A recognition error does not reach the ERP without a person accepting it.

If after 30 days fewer than 80% of email orders reach the ERP without an employee's corrections, we extend the pilot by another 30 days at no extra charge and keep improving the recognition. We count the share in the approval panel and show it in the report.

Because some customers write emails anyway. The pilot does not replace the B2B portal or the ERP. It takes the orders someone retypes by hand today and leaves customers the way of ordering they are used to.

No. The ERP remains the source of prices, stock and documents. We need a technical account that can save orders and access to one mailbox. Instead of retyping, your team checks and approves orders in the panel.

That is a second stage, outside the pilot. It needs call recording at your switchboard and the callers' consent, so we start with email, where the result shows after 30 days.

A decision on the pilot and one person who approves orders in the panel. Access to the mailbox your orders arrive in. A technical account in the ERP. 30 minutes for the kickoff and 30 minutes for the review after a month. A signature on the data processing agreement we prepare.

You get a report: how many orders arrived by email, how long it took from the email to the document in the ERP, and what share went through without corrections. Then you decide: a subscription, the next process, or the end of the engagement. There is no commitment after the pilot.

Not yet. This is a new service and we are taking on the first pilots now. That is why the scope is narrow, the price is fixed and a person approves every order. What we can show is an AI assistant running on Rader's 3,494-product catalogue, and stores you can open and check: ImpregnatyBC and Alufix.

Before kickoff we sign a data processing agreement that lists everyone involved in the processing. Access is limited to one mailbox and a technical ERP account. When the engagement ends we delete or return the pilot data, as the agreement sets out.