From emailed PO to booked order

NgageFlow turns emailed purchase orders into orders in IFS or SAP.

Before and after

The same piece of work, as it waits today and once NgageFlow has run it.

Before The PO waits in the orders inbox to be retyped.
Outlook Orders inbox 6 unread

PO 7781, spring stock order

From
Example Marine, buyer@example.com
Attached
PO-7781.xlsx, 9 lines
Wanted
Delivery by 2 December

To do Key into SAP, check prices, confirm to the buyer

NgageFlow Agents run it

Order flow

  1. 1Read the email and the spreadsheetOutlook
  2. 2Check the customer and the partsSAP
  3. 3Book the sales orderSAP
  4. 4Confirm to the buyerOutlook
After Booked in SAP and confirmed. Nobody retyped it.
Slack #sales-ops 1 new

PO 7781 from Example Marine is booked in SAP as order 4100823.

Lines
9 of 9 parts found
Prices
Match the price list
Confirmation
Sent to buyer@example.com

Booked Read, checked and booked by NgageFlow

Illustrative, on a test landscape. Names, numbers and amounts are samples.

What runs between inbox and SAP

Every PO that arrives starts a run like this.

NgageFlow 4 steps

New email in the orders inbox: PO 7781 from Example Marine

  1. 1 Read the email and the spreadsheetPO 7781, 9 lines, by 2 December Outlook
  2. 2 Check the customer and the partsCustomer 2045, 9 of 9 parts found SAP
  3. 3 Book the sales orderOrder 4100823, 9 lines SAP
  4. 4 Confirm to the buyerSent, and posted to #sales-ops Outlook
An illustrative run on a test landscape.
  1. 1

    Read the email and the spreadsheet

    Outlook, the orders inbox

    The agent reads the order and maps each description to a part number.

  2. 2

    Check the customer and the parts

    SAP, customers and materials

    It checks the customer, each part and the price list before booking.

  3. 3

    Book the sales order

    SAP, sales orders

    A clean order is booked. A part it cannot match goes to a person.

  4. 4

    Confirm to the buyer

    Outlook and Slack

    The buyer gets the order number by email. The desk sees one line in Slack.

Runs on IFS and SAP

Customer orders in IFS, sales orders in SAP.

SystemWhat it holdsWhat NgageFlow does
IFS Customers, parts, customer orders Checks the customer and parts, creates the order
SAP Customers, materials, sales orders The same checks, then books the order
Outlook or Gmail The orders inbox Starts a run for each PO
Webhooks A customer portal Sends portal orders through the same checks

IBM Maximo, IFS and SAP are ready today. For any other application, including a homegrown one, we teach Ngage how it works in weeks.

You choose what waits

Clean orders book themselves. The rest wait for a person.

  • Read the PO and match the partsRuns alone
  • Book an order at list priceRuns alone
  • A part it cannot matchWaits for customer service
  • A price change or a credit blockWaits for sales ops

Questions about order intake

Can it read orders in different formats?

Yes. PDFs, spreadsheets and orders typed into the email go to the same agent, which flags what it cannot match instead of guessing.

Can portal orders use the same flow?

Yes. A webhook starts the same flow as the inbox, so every order goes through the same checks.

Who decides on prices and credit?

Your team. A price off the price list or a customer on credit block waits for the person you name, with the PO beside the draft order.

Describe your order intake

Write it the way you would brief a new order clerk.

Or write to hello@ngagesuite.com

Customer service can ask where an order stands, without a hunt through screens. See NgageChat on customer orders

Try one

It runs on

We run it with you, live, in a safe test setup.