Stock levels, purchase orders, shop orders and delivery runs are linked tables, so each one updates the others. An AI agent raises the reorder, follows up what is late and tells the team each morning what needs attention.
Items, locations and movements in linked tables, checked by a stock count form.
A purchase order is raised when an item drops below its reorder level.
Purchase orders on a calendar by due date, and a follow-up when one is late.
Shop orders on a board from To pick to Dispatched, with the shop updated.
The day's drops in order, a text to the customer and proof of delivery.
Late orders, low stock and failed drops in one message each morning.
Every item is a row with its SKU, its location and a reorder level. Each movement between locations is recorded with who moved it and when, so the quantity on hand is worked out from the movements. A stock count form checks the shelf against the table.
Each item has a reorder level. When the quantity on hand drops below it, a workflow raises the purchase order with the supplier and the quantity filled in. An agent tells whoever orders it, and an order above the agent's limit waits for a person to approve.
Purchase orders appear on a calendar by the date they are due. When one is late, an agent drafts the message to the supplier and tells the buyer. When the goods arrive, the order is marked as received and the stock is added to its location.
Orders from the shop and marketplaces are synced to a shared table and shown as a board, from To pick to Dispatched. When an order goes out, the fulfilment is written back to the shop, so the customer sees the update there.
A delivery run lists the day's drops in order, with a driver and a vehicle. A workflow texts the customer when the van is an hour away. The driver records proof of delivery on a form, with the name of whoever signed and a photo, so a question is answered by looking at the record.
A digest agent opens the day in team chat with what needs attention: purchase orders that are late, items below their reorder level and drops that failed yesterday. Dashboards show the same rows, so the numbers match what the warehouse sees.
A supply chain agent watches stock levels, drafts purchase orders, follows up late suppliers and writes the morning digest. It cannot change a stock count, and orders above its limit wait for a person.
Items, locations and movements from the template.
A purchase order when stock drops below its level.
The day's drops, with proof of delivery.
What is late, in team chat each morning.
From the connector library. Webhooks and a REST API cover the rest.
Messenger
LINE
Google Sheets
Google Calendar
Slack
Google ChatYes. Upload a CSV or an export and start from that, or pick a base template and paste the data in.
Shopify, WooCommerce, BigCommerce, Adobe Commerce, Squarespace, Etsy and Amazon Seller are in the connector library. Webhooks and a REST API cover the rest.
Only inside its limit. Every agent has a spending limit, anything above it waits for a person, and the approval is recorded.
Free for up to twenty people. Set up this team now, and add the others as needed.