AIstap

Use case · Wholesale

Stop retyping orders from email.

Your customers order by email, and your order desk retypes every line into the order system (ERP). The automation prepares the order lines. Your order desk checks them, sorts out the exceptions and approves.

ERP: the system that holds your orders, stock and invoices.

Show us your process See the difference

Free · 30 minutes online · one process · no obligation After that: pilot from €2,450 · monthly package from €295 · excl. VAT

How the work runs

  • Email
  • PDF
  • Spreadsheet

AIstap

the automation

  • Reads
  • Validates
  • Prepares

Your ERPFICTIONAL EXAMPLE

Order customer 10482 · 3 linesDraft order

Customer
Customer no. 10482
Line 1
200 × item 201040
Line 2
500 × item 201183
Line 3
25 × item 31040625 × item 770193?

In doubt? To your team first.

Item number 770193 is not in your ERP. Your order desk picks the right item.

Sound familiar?

  • Monday: the mailbox is full

    On Monday morning the order desk's mailbox is full of orders.

  • Hunting for the right item

    A customer uses their own description, and someone looks up the right item number.

  • Your customer waits for confirmation

    Your customer is waiting for an order confirmation while the order is still unread in the mailbox.

Today. And with AIstap.

Today

4 steps by hand

  1. Email, PDF or Excel
  2. Open and read
  3. Look up the items
  4. Retype lines into the ERP
  5. Ask about what is unclear

With AIstap

1 step for your team

  1. Email, PDF or Excel
  2. The automation reads
  3. Check on item and quantity
  4. Your order desk approvesyour team
  5. Order final in your ERP

Possible impact

  • Less retyping
  • Less chance of wrong item numbers
  • A clearer view of open orders
  • Better follow-up on open questions

Possible impact, not a promise: what it brings depends on your process.

What AIstap can build.

An example. What we build for you is agreed upfront.

  • Connected to your mailbox

    Sees which orders arrive.

    A connection to the mailbox the orders arrive in.

  • Reads email, PDF, Excel

    Customer, item and quantity per line.

    Reading email text, PDF and Excel: customer, item and quantity per line.

  • Checks every order line

    Unknown item? To your order desk first.

    A check: lines without a known item number or quantity go to your order desk first.

  • Prepared in your ERP

    Final only after your order desk approves.

    Preparing the order lines in your ERP; final only once your order desk has approved them.

Checked by your team.

The automation prepares. Your people approve and decide when something is unclear.

The automation

Your order desk

  1. DetectThe automation sees what arrives.
  2. PrepareReading, checking and getting it ready.
  3. ApproveSomeone on your team approves, or decides when in doubt.
  4. ExecuteAfter approval it is final in your system.
  5. Follow upWhatever is open stays in view.

Your team stays in control.

  • Try it yourself

    Order customer 10482 · 3 linesDraft order

    Line 325 × item 770193?

    Which item does the customer mean?

    In doubt, your order desk decides

    A line the automation is not sure about stays open. Your order desk sees it with the email attached.

  • The automation

    • Reads
    • Validates
    • Prepares

    Your team

    • Agreeing a price
    • A substitute item
    • Rush promises

    Your team agrees things with customers

    A different price, a substitute item or a rush delivery: your order desk arranges that. In this set-up the automation promises nothing.

  • No final order without your approval

    The order only becomes final when your order desk approves it. In this set-up the automation does not send a confirmation to your customer.

In the systems you already have.

Which connection is possible is something we look at in the free analysis.

The mailbox the orders arrive in and the ERP your order desk works in. In the free analysis we look at whether and how your ERP can be connected.

  • Mailbox (In this example)
  • Order system (In this example)
  • Planning software
  • Spreadsheet
  • Accounting
  • Customer portal

In this example

What it costs to start.

From mailbox to ERP: one process, two systems. The size of a pilot.

  1. STEP 0

    Free analysis

    €0

    You show us one process.

    • 30 minutes online
    • A one-page summary
    • Free, no obligation
  2. STEP 1 Recommended first step

    Pilot

    from€2,450

    One working automation.

    • Max. 2 systems
    • 1 to 2 weeks
    • Fixed price, upfront
  3. ONGOING · AFTER A PILOT

    Monthly package

    from€295/month

    We keep it running.

    • Hosting and monitoring
    • Fixes and AI costs
    • Cancel any month

Prices excl. VAT

All prices and steps

Questions about this use case.

What if a customer uses their own item numbers instead of ours?

If those numbers are stored per customer in your ERP and the automation can see them, it uses them. If the item is uncertain, the line goes to your order desk first.

Does the automation take our price agreements per customer into account?

Only if the automation can see those agreements in your ERP. Whether it can is something we look at in the free analysis. In this set-up the automation does not change prices.

Does this work with our ERP, and does our IT partner need to do anything?

We check in the free analysis whether your ERP can be connected. For the pilot you arrange an account or a test environment, or your IT partner joins in briefly.

More use cases.

Supplier price list to Your ERP

Stop retyping supplier price lists.

New purchase prices, prepared in your order system (ERP). Your buyer decides.

Wholesale Manufacturing

See all use cases

Step 0 · free

Show us your process.

  1. We call or emailTo schedule a time
  2. You show us30 minutes online
  3. You get a summaryOne page

Free, no obligation

Prefer to email directly? [email protected]

All fields are required. We will call or email you back.