Take in orders from retailers' Web-EDI

Each morning, sign in to each retailer's Web-EDI, download orders, and convert them for the core system. Staff check unusual quantities before import.

  • Wholesale & consumer goods
  • Operations & orders

The problem today

With retailers not connected by the industry EDI standard, orders come through each retailer's own Web-EDI. Every morning, order staff sign in to each Web-EDI, all built differently, download orders, convert them, and import them into the core system. RPA automated this, but robots stop whenever a Web-EDI screen changes, and some days orders miss the cut-off.

The workflow in Kitewell

  1. Sign in to each retailer's Web-EDI and download ordersWeb
  2. Convert each retailer's format into the core system's import formatAutomatic
  3. AI flags orders whose quantities or items differ sharply from past ordersAI judgment
  4. Order staff confirm flagged orders with the retailer and approve the importApproval
  5. Import into the core system and post orders that failed to TeamsAutomatic

What AI does

Compares with past orders by retailer and item to find quantities with suspect digits or items never ordered before, and explains why.

Where people decide

Order staff confirm only unusual orders with the retailer before approving the import.

Features used

What a PoC checks

  • How each Web-EDI handles sign-in security such as one-time passwords or client certificates
  • Whether each Web-EDI's terms allow automated screen operation
  • Whether conversion and import finish reliably before the order cut-off

Discuss a PoC for this work

We check whether this workflow runs on your own work and screens.