The procurement bot that messages every vendor before 8am

At Ashwheelz, procurement worked like this. Purchase orders were created and confirmed in Odoo, which is the right place for them. Then somebody had to tell the vendors. Every morning, a staff member opened the day's confirmed POs, copied the details, and messaged each vendor on WhatsApp, one at a time.

It sounds small. It was not. The messages went out late when the person was busy. The format changed depending on who was typing. Vendors occasionally got missed, which meant a delivery did not arrive, which meant a kitchen ran short. And the whole process depended on one person remembering to do it.

The information was already in Odoo. The problem was the last mile.

What we built

A small, focused bot that does the morning routine unattended.

Pull the day's POs from Odoo

The bot connects to Odoo over XML-RPC, Odoo's standard external API, and queries for purchase orders confirmed for the day. It reads the vendor, the order lines, quantities and any notes. Nothing is entered twice. If it is in Odoo, the bot knows about it; if it is not, it does not get sent.

Send each vendor a formatted WhatsApp

For every vendor with a confirmed PO, the bot builds a clean, consistent message: order reference, the items and quantities, and delivery expectations. It sends the message through Green API, a WhatsApp gateway that lets software send messages from a business number without anyone touching a phone.

Because the template is fixed, every vendor gets the same structure every day. There is no variation in wording, no forgotten line items, and no "sorry, sent that to the wrong supplier".

Run every morning on its own

The bot has a built-in scheduler. It wakes up each morning, does the Odoo query, sends the messages, and goes back to sleep. Nobody needs to open it or press a button. If a person is off sick or on leave, the vendors still hear from the company on time.

Ship as a one-click Windows executable

This was a deliberate choice. The client's procurement team works on ordinary Windows PCs and does not have a server team. So we packaged the bot as a single Windows executable. Install it once, enter the Odoo and Green API details, set the morning time, and it runs. No Python environment to maintain, no command line, no dependencies to install.

The result

Two things changed immediately.

**Same-day delivery.** Vendors now receive orders before their working day starts, which means they can plan deliveries for the same day. Previously, a message sent at 11am might mean a delivery the next day.

**Zero manual messages.** The daily routine is gone. Nobody copies POs into WhatsApp any more. The time saved is real, but the bigger win is consistency: no missed vendors, no inconsistent formats, no dependence on one person's memory.

Why this pattern works

We have built a lot of automations, and the ones that stick share a shape with this one.

• ✓**The source of truth already exists.** Odoo already held the POs. We did not create a new place for data; we read from the one the team already trusted.
• ✓**The output goes where people already look.** Vendors live on WhatsApp. Sending them an email or a portal login would have been ignored.
• ✓**It runs without a human in the loop.** A scheduler beats a reminder. The moment a process depends on someone pressing a button, it eventually does not happen.
• ✓**It is packaged for the people who run it.** A Windows executable the team can install themselves is more valuable than a technically elegant service nobody on site can restart.

What it did not require

It is worth saying what we did not have to do. We did not change how the team uses Odoo. We did not ask vendors to adopt anything new. We did not build a dashboard nobody asked for. The bot replaced one repetitive task with software and left everything else alone.

If your team is copying data out of one system and pasting it into a messaging app every day, that is a bot waiting to be written.

Want this for your business? Message us on WhatsApp +92 320 0496154.