Collect orders and due dates from supplier portals
Every morning, collect new orders and delivery date changes from several customers' supplier portals and, after review, record them in the sales system.
The problem today
Staff sign in to a different portal for each customer, check orders and delivery date changes, and copy them into the sales system. RPA automated this, but the robots stop whenever a portal's screens change, and only the person who built them can fix them.
The workflow in Kitewell
- Sign in to each customer's supplier portalWeb
- Collect the order list and delivery date changesWeb
- AI identifies what changed since the last runAI judgment
- The owner reviews changed ordersApproval
- Record them in the sales system and post the result to TeamsAutomatic
What AI does
Compares with the previous run to identify new orders, quantity changes, and delivery date changes, and summarizes them.
Where people decide
The owner reviews only changed orders before they are recorded in the sales system.
Features used
What a PoC checks
- Whether sign-in and order collection run reliably on each portal
- How far the workflow keeps running without changes when a screen changes
- How to record orders in the sales system: screen, API, or CSV import
Discuss a PoC for this work
We check whether this workflow runs on your own work and screens.
Related use cases
Enter an Excel list into a web system
For each row of an Excel list of orders, AI enters it into a web system and writes the receipt number back into the row. Only failed rows are redone.
Enter records into a desktop accounting app
For each row of an Excel list, AI enters the record in a desktop app. A person approves before it is saved, and the slip number goes back into the row.
Read Excel purchase orders from email and enter them
AI reads Excel purchase orders in each customer's own layout, checks them against the product master, and enters them. A person checks orders that do not match.