Send shipping notices and reconcile receipts
Send shipping notices through each retailer's Web-EDI, then reconcile next morning's receipt data. AI suggests causes of quantity differences; staff confirm.
- Runs on your own PCs and servers
- Use Azure OpenAI, Amazon Bedrock, Google Vertex AI, or an in-house model
- Its engine is Descarty's open-source Dagu (GPL-3.0)
The problem today
Shipping notices must reach each retailer's Web-EDI by its deadline, and receipt data arrives the morning after delivery. Staff check every difference between shipped and received quantities before querying the retailer or issuing corrections, and finding the cause takes time.
In depth: Collecting orders from each customer's Web-EDI in one list
The workflow in Kitewell
- Build shipping notices per retailer from warehouse shipment recordsAutomatic
- Send shipping notices through each retailer's Web-EDIWeb
- Next morning, download receipt data from each Web-EDIWeb
- Extract differences between shipped and received; AI suggests likely causesAI judgment
- Staff review differences and decide whether to query or correctHuman task
What AI does
Suggests causes such as shortages, mis-deliveries, or receipts not yet recorded from the quantities, items, and past patterns, with a confidence for each.
Where people decide
Staff confirm the cause and decide whether to query the retailer or correct records.
Prove Kitewell on your own systems
Try it free for 14 days on your own PC. To see it working first, ask for a 30-minute demo. There is also a one-month onboarding (¥500,000 before tax), where we build your first job together.
What to check when you try this work
- Whether sending notices and downloading receipts run reliably on each Web-EDI
- Whether shipment records are ready early enough for each sending deadline
- Whether suggested causes match the categories you use
How the onboarding runs
- Week 1Requirements and success criteria
- Weeks 2 to 3Build
- Week 4Verify on production screens
- Final dayReport
One-month onboarding
- Length
- One month
- Cost
- ¥500,000 (tax excluded). Your staff build, with the developer beside them
- If you go on to a license
- The onboarding fee is credited to the first year's contract
- Without the onboarding
- At Team scale, start on Team monthly (¥14,800 per computer a month, tax excluded), and cancel in any month
You can try it first on your own PC, in the free 14-day trial.
Frequently asked questions
- Do our documents and screens leave the company?
- Kitewell runs on your own PCs and servers, and Descarty never receives your business data. You choose the AI model: a cloud API, or an in-house or local model with an OpenAI-compatible API. With an in-house model, no data leaves the company. With a cloud model, what the AI reads is sent to the model's provider.
- What if the AI misreads something?
- A person checks what the AI produced before the work goes on. In a sheet, every value the AI reads shows the quote it came from, and rows below your confidence threshold go to a person. Reviewers can send work back with notes on what to fix, and who approved what is kept in the run history.
- What happens when a screen changes or a run stops?
- When a screen changes, the AI reads it again, relearns the step, and carries on. The relearned step is saved, and later runs repeat it. If a run still stops, ask the assistant right there, and it finds the cause and proposes a fix. A proposal is not saved until a person applies it.
- What happens to the RPA and systems we use today?
- Keep them. Kitewell operates screens the way a person does, so it works with systems that have no API. Move the robots that keep stopping and the work you gave up automating because it needs judgment, and leave fast, fixed processing in your current RPA.
- What does it cost?
- ¥14,800 per computer per month, or ¥148,000 per computer when paid yearly, before tax. A computer costs the same whether it builds or runs. You can try it free for 14 days. The one-month onboarding, where we build your first job together, is ¥500,000 before tax, credited to the first year if you go on.
Related use cases
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.
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.
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.
See this work in a demo
A 30-minute demo shows this workflow running. The 14-day free trial lets you check it on your own systems.