Order processing, before and after.

Four manual order tasks at an electrical distributor, what replaced each one, and what changed. Open a row to follow one order from the incoming PO to the ERP.

=DELETE(manual work)

Manual taskRetyping PO emails and PDFs into the ERP line by lineWhat replaced itRuntara reads the PO and enters the sales orderOutcomeInside sales reviews only the lines that fail a check.

  1. 1 / Incoming

    A PO arrives by email

    The customer sends the purchase order as a PDF to your orders inbox, as they do today.

  2. 2 / Extracted

    Runtara reads the order

    The customer number, PO number, lines and total become fields on the run.

    Runtara's details for the Read the purchase order (AI) step of a run for order PO-58215: completed in 1.66 seconds, with the fields it read: customer number, lines, PO number and total.

  3. 3 / In the ERP

    The sales order is created

    An order that passes every check goes in with no one involved. The run keeps the sales order number.

    Runtara's run page for purchase order PO-58221 from Quillfen Electric Inc.: the stage is Entered in ERP, no requests are waiting for an answer, and sales order SO-10484 was created for the $8,141 order.
Manual taskChecking part numbers and units of measure by handWhat replaced itCustomer part numbers and units are matched to your catalogueOutcomeAnything unclear is flagged for review before entry.

  1. 1 / Incoming

    The customer writes it their way

    The line names the item in the customer's words and unit, not yours.

    PO-60417 · 200 FT 3/4" EMT CONDUIT

  2. 2 / Extracted

    Runtara matches item and unit

    The description is matched to your item and feet are converted to 10 ft sticks.

    EMT-075-10 · 20 EA

  3. 3 / In the ERP

    The line lands in your terms

    The order line is entered under your item number and unit of measure.

Manual taskChecking each price against the contract before entryWhat replaced itEvery line price is checked against the contract priceOutcomeOrders over contract wait in one queue for approval.

  1. 1 / Incoming

    One line is priced over contract

    Five lines of the order agree with the ERP. Line 4 does not.

    PO-58213 · line 4 · LED-HB-150W-50K · $412.00

  2. 2 / Extracted

    Runtara holds the order

    The contract price is $386.00, so the order waits in the queue with the difference shown.

    Runtara's Price exceptions queue with seven purchase orders held for approval. PO-58213 from Quillfen Electric Inc. is at the top: line 4 at $412.00 against a contract price of $386.00, $312.00 over contract, with Approve and Reject buttons on every row.

  3. 3 / In the ERP

    The approval creates the order

    Inside sales approves or rejects in one click. An approval becomes the sales order in the ERP.

Manual taskTyping order acknowledgements by handWhat replaced itThe confirmation is generated from the ERP orderOutcomeIt is ready to send as soon as the order exists.

  1. 1 / In the ERP

    The order exists

    The sales order created from the PO is the source for the confirmation.

  2. 2 / Generated

    Runtara writes the confirmation

    Lines, quantities and prices come from the ERP order, not from the PO.

  3. 3 / Ready

    The confirmation is ready to send

    It goes to the customer who placed the order.

Bring us one process.

Start with a paid pilot of one real process, such as order intake into your ERP. Our team builds and runs the workflow, live in two weeks once access is in place.

Book a call