Automate order entry in your ERP

An AI agent reads orders and call-offs from emails and PDF attachments, checks them the way your inside sales team does and prepares the sales order in your ERP.

Nothing is created or confirmed until an employee approves it.

Orders orders@your-company.com
  1. PDF Call-off order 4500231877Customer 20417 Call-off from framework agreement
  2. Excel Order list week 43Customer 1042 New order
  3. Text RE: Order 4500229310Customer 3870 Order change
  4. PDF Blanket order 2027Customer 5512 New blanket order

4 draft orders are waiting for your approval

Orders arrive as PDF, Excel or email text and are keyed into the ERP by hand

Every morning there are 30 new orders in the shared mailbox. Most come as a PDF from the customer's system, some as an Excel list, a few as a short email with item, quantity and requested date in the text. Whether you call it order entry, order creation or order handling: your team keys every one of these orders into the ERP by hand.

Much of this is not written down in any system. Often only one or two employees know which customers get an order confirmation only when something differs, or which delivery address runs under its own customer account. When they are on holiday or off sick, orders pile up.

The same check for every line item, by hand
  1. Find the itemby the customer's number
  2. Check for blocksis the item blocked?
  3. Work out free stockon hand minus reserved
  4. Check goods receiptsincluding transport time
  5. Find the framework agreementopen quantity, price and price unit
  6. Create the orderapprove, confirm

Where things have to move fast, mistakes creep in that only show up later:

Duplicate orders

An order change is entered as a new order and the goods go out twice.

Framework quantities that drift apart

A new framework agreement is drawn on although the old one still has quantity open. After that, the remaining quantities in your records and the customer's no longer match.

Dates that cannot be met

The stock looked sufficient but was already reserved for other orders.

How the AI agent enters an order

Typing is only part of the work. Much of it lies in the checks beforehand. The agent takes on both, following the rules of your inside sales team.

The agent does thisYour team decides this

  1. Recognise the order

    Whether it is a PDF from the customer's system, an Excel list or an order as free text in an email: the agent reads the shared mailbox and recognises whether it is a new order, a call-off from a framework agreement, a new blanket order or an order change.

  2. Read the line items

    For each line item it takes the customer's item number and description, quantity, price with price unit and requested date, plus the delivery address, order number and framework agreement number.

  3. Find the item

    It searches first by the customer's item number, then by variant spellings and the description. If several items match, it offers them for selection instead of guessing.

  4. Check like your team

    It checks availability: blocks, free stock and goods receipts, plus the open quantity in the framework agreement and the agreed price. Using your transport times, it works out for each line item whether the requested date can be met and otherwise proposes the earliest feasible one.

  5. Prepare the order

    It fills in the sales order with customer, delivery address, order number, framework reference and a delivery date for each line. If a quantity has to be spread over several dates, it splits the line. It collects notes for the customer for the order confirmation.

  6. Approve, create, confirm

    Your employee sees the order and the draft side by side, with the source of every field and the result of every check. Only after approval does the agent create the sales order in the ERP, attach the customer's order as proof and send the order confirmation.

Customer 20417 Call-off_order_4500231877.pdf
  • New order
  • Call-off from framework agreement
  • New blanket order
  • Order change

Call-off order 4500231877

dated 14 Oct 2026, delivery address Plant 2

Line item 1

Material number 4410023

Bearing bush 20 x 26 x 15

2,400 pcs at €41.50 per 100 pcs

Delivery date 6 Nov 2026

Call-off from framework agreement 118

Line item 2

Material number 4410031

Retaining clip, galvanised

1,200 pcs

Delivery date 6 Nov 2026

Call-off from framework agreement 124

Checks

Framework agreement 118 open 3,000, afterwards 600
Price line item 1 €41.50 per 100 pcs = €0.415 per piece

3,000 pcs in stock, 1,800 of them reserved for other orders. The goods receipt of 5,000 pcs on 27 Oct covers the date.

To Customer 20417

Order confirmation for your call-off order 4500231877

Line item 1300210 Bearing bush 20 x 26 x 152,400 pcs6 Nov 2026
Line item 2300214 Retaining clip, galvanised1,200 pcs19 Nov 2026

Notes

  1. Framework agreement 118: 600 pcs remain open after this call-off.
  2. Line item 2: delivery date 19 Nov 2026 instead of 6 Nov 2026.
sent

Your rule decides whether line item 2 is confirmed with the new date or the whole order waits until it is clarified. In individual cases, your team decides at approval.

Draft order in progress ready for approval created in the ERP
Type
Call-off from framework agreement
Customer
20417
Delivery address
Plant 2
Order number
4500231877

Line item 1StockFrameworkPrice

Item
4410023300210 Bearing bush 20 x 26 x 15found by the customer's material number
Quantity
2,400 pcs
Price
€41.50 per 100 pcs€0.415 per piece
Delivery date
6 Nov 2026
Framework agreement
118

Line item 2new date

Item
4410031300214 Retaining clip, galvanised
Quantity
1,200 pcs
Delivery date
6 Nov 202619 Nov 2026Proposed
Framework agreement
124
Order confirmation
Draft with 2 notes
Customer order attached as proof ApproveApproved

Example with fictional data

Try it yourself: in the online demo you enter an order, from the email to the sales order.

Online demo (opens in a new tab)

Special cases in order entry

An order change, not a new order

If a second email arrives for the same order number, the agent changes the existing sales order instead of creating a second one. If the goods have already been picked or delivered, it prepares the reply to the customer.

Framework agreements

Following your rule, every call-off is booked against the right agreement, for example the oldest open one first. If the customer names a different one, the agent explains the difference in the order confirmation. If the agreement does not cover the quantity, it confirms what is covered and keeps the rest open. If there is no agreement at all, the line item goes to your team.

Requested date not feasible

The agent proposes the earliest feasible date and prepares the message to the customer. If the stock covers only part of the order, it spreads the quantity over several delivery dates.

Blocked items or items not yet released

If an item is blocked, for example because of a complaint, the agent confirms nothing and shows your team the block together with its notes. If the customer has not yet approved the sample, it puts the line item on the list of open cases.

Item numbers with quirks

If a customer writes their numbers with different separators from your ERP, or just says “stainless steel” where the item master says “A2”, the agent still finds the item.

Replenishment under a different number

If the goods receipt for an item is recorded under a different item number, for example as a blank or a kit, the agent checks availability there.

Delivery to a different plant

If deliveries to a plant abroad run under a separate customer account, for example because of the VAT identification number, the agent selects that account based on the delivery address.

Customer-specific rules

Some customers only get an order confirmation when something differs, others round prices to two decimal places. The agent applies these rules and reports only genuine differences.

New blanket orders

The agent creates them with framework agreement number, item, quantity and price and leaves them open. Costing, term and confirmation stay with your team.

How much working time goes into your order entry today

Worked example

If 30 orders reach you every day and your team needs 8 minutes per order, that is 4 hours of clerical work a day, or half a full-time position.

No order and no confirmation without approval

The agent does not create or change any sales order in the ERP that an employee has not approved. Order confirmations and messages to customers also go out only after approval.

The agent proposes delivery dates. They are promised when your team approves them, because the responsibility towards the customer stays with you.

Processing takes place in data centres in the EU under the General Data Protection Regulation (GDPR), with a data processing agreement. The provider of the language model does not use your data for its own training.

Draft order created

Your team

Approve

Sales order in the ERP, Customer 20417 receives the order confirmation

  • A source for every field, for example Quantity: customer order, line item 1
  • A result for every check, for example Goods receipt on 27 Oct covers the date
  • Every action of the agent and every approval is logged

Effort, costs and your ERP

We record your order entry on screen, with the employees who create orders today, using real orders including special cases. That way we also capture the rules that so far exist only in people's heads.

We keep the onboarding fee small and agree it before the start. Even in the test phase, the agent enters real orders, with your approval. After that you pay a monthly fee, set individually and can be cancelled flexibly.

Onboarding

Extra effort for your team2 to 3 days

Test phase

Extra effort for your teamno extra effort

Benefit visible, then subscription

Operation

Your costsmonthly fee priced for mid-sized companies, can be cancelled flexibly

Extra effort for your teamno extra effort

Start step by step

You begin with the order type that takes the most time, such as call-offs, and add more once the first ones are running. Order entry is the first step of order processing. After that, further agents can take over, for example in materials planning and shipping.

No new system, no change for your customers

The agent works through the interface of your existing ERP system. You need neither a new ERP nor your own developers. Your customers keep ordering as before, without an ordering portal and without EDI (electronic data interchange).

Less dependence on individuals

The rules that only certain employees know today are stored with the agent after onboarding. A stand-in can then approve orders too, because the draft shows where every value comes from and what every check found.

Frequently asked questions

Does this work with our ERP system?

The agent uses the interface of your ERP system. Before the start, we check whether it offers everything order entry needs, such as creating and changing sales orders, reading stock and goods receipts, and assigning framework agreements.

Is this software for automated order entry?

Yes, but not software that replaces your ERP. The AI agent works through the interface of your existing ERP system and creates sales orders only once your team has approved them. You do not need an additional program for order entry, and your order management stays in your ERP.

What happens if the agent does not understand an order?

Then it creates nothing. It shows the order to your team and marks what it could not match, such as an unknown item or a missing quantity.

Does our master data have to be cleaned up first?

No. The agent finds items even when they are spelt differently. Where a one-off correction in the item master is simpler than a special rule, we tell you so during onboarding.

What is the difference between a blanket order and a call-off order?

A blanket order fixes quantity and price for a period. With a call-off order, the customer requests part of that quantity for a specific date. One blanket order is often followed by many call-offs. That is why call-offs usually account for most of the entry work.

We call it order intake. Is that the same thing?

Yes. Whether you call it order entry, order intake, order creation, order capture, order handling or order booking: it means the path from the customer's order to an approved sales order in your ERP. Order processing goes further, from incoming order through shipping to invoice. Order entry is its first step.

See in 30 minutes how the agent prepares an order for your ERP

Using a call-off with several line items, we show you how an email and a PDF become a sales order ready for approval, with its order confirmation, and we clarify what this means for your company.