Starter pack · Factories & production
POs taken, production planned, deliveries notified and daily reports written — without extra headcount
This pack assembles four AI agents for small and mid-sized factories that take orders from business customers (B2B) by email, LINE and phone, then have to re-key them into the ERP, add up production and tell customers when the goods will arrive. It all runs on the factory's existing systems. Fixed scope, live in 2–3 weeks.
Work in
Factories & production+ human approval
To the customer
A person approves before it ever reaches the customer· drag to rotate
A fit if you…
- Factories or producers of 20–150 people, taking POs from regular customers by email, LINE and fax or photo, with someone keying each one into the ERP or Excel
- A planning team or production supervisor of 1–2 people adding up production orders and checking raw materials by hand, who have run out of material because they found out too late
- B2B customers calling or messaging about delivery status so often that sales loses time on the same answers every day, while managers get the production report late or not at all
A day with this pack running
- 06:30The planning agent combines yesterday's POs with the next seven days of production, compares that against raw material stock, and sends what will run short to purchasing and planning on LINE
- 08:15Three POs arrive by email and one as a photo on LINE. The PO intake agent reads the lines, checks them against contract prices and creates three sales orders in the ERP. The fourth has a price mismatch and goes to sales in the approval screen
- 10:40A customer asks on LINE when “the lot ordered on Monday” will be ready. The status agent answers from the production plan and the delivery date in the ERP, with the SO number, and sales never picks up the phone
- 14:00A two-hour machine stoppage pushes the plan back. Planning updates the new delivery dates in the system and the agent drafts messages to the two customers affected, ready for sales to send
- 18:30The reporting agent compares actual output against plan, scrap by line and by cause, and POs still open, and sends a one-page report to the plant manager and the owner on LINE
The output you get
Reads attachments and photographs alike · anything unclear is held for a person to check before it enters the ERP
An illustrative example — the names and figures are invented so you can see the shape of the work; the real thing is built around your business.
Example: Factories & production
LIVE DEMO1 · Work arrives
2 · The AI agent does it
- POs from every channel, keyed in
- Production plan + material alerts
- Delivery status for B2B customers
- Daily output and scrap report
3 · You just approve
POs where the price does not match the contract, or with a new product or a new customer, are bounced back for sales to confirm before they enter the system.
Result
-70 to -90%
Time spent keying POs
What is in the pack
4 AI Agent already assembled
Reads POs from email, LINE, PDF and photos, pulls out product codes, quantities, prices and delivery dates, checks them against that customer's contract prices, and creates the sales order in your ERP or the sheet you use, with the original attached to every one.
POs where the price does not match the contract, or with a new product or a new customer, are bounced back for sales to confirm before they enter the system.
Rolls every sales order into a 7–14 day production requirement, explodes it into raw material needs against the BOM, then compares that with stock and with goods already on order. Every morning it sends what will run short, the date it runs short, and how much to order.
Planning sequences production and purchasing places the orders. The agent only prepares the numbers and drafts the purchase requisition.
Answers customers asking about a PO on LINE or by email, from the real production plan and the ERP, and tells them proactively when the goods are ready, when they leave the factory, or when a delivery date changes, in the wording agreed with the factory.
Anything that affects an agreement, such as a delay, a reduced quantity or a customer asking to expedite, is drafted by the system but sent by a salesperson every time.
Every evening it pulls actual output, scrap, machine downtime and open POs from the system or from photographs of the line record sheets, compares them against plan and against last week, and flags anything unusual, such as a line where scrap has jumped. The manager can ask follow-up questions in the chat.
The report is an observation, not a decision. Every number links back to its source, and the manager is the one who acts on it.
All included
What is in the box
- Email, LINE OA and your existing ERP or Google Sheets connected (any ERP with an API or ODBC)
- One approval screen for POs that need a person, customer messages waiting to be sent, and the purchase requisitions already drafted
- Message templates for customer status updates and a daily report format, adjusted to how the factory writes
- A four-number dashboard: POs entered automatically, keying time removed, materials flagged in time, and time spent on reports
- PDPA paperwork and a data flow map showing where customer data and contract prices live, and who can see them
- One training session for sales, planning and the manager, with a short guide for the cases the system bounces back
Go live
Live in 2–3 weeks
Step 1 / 3 · Collect samples and connect the systems
Week 1
- 1Week 1
Collect samples and connect the systems
We take sample POs from 10–20 of your main customers, the contract prices, the BOM and the old production reports, connect email, LINE OA and your ERP or sheet, and set which POs a person must see first.
- 2Week 2
Run in parallel with the real work
- 3Week 3
Go live and measure
-70 to -90%
Time spent keying POs
From the cases we have done. Most regular customers' POs enter by themselves, leaving people to look only at the ones where the price or the product does not match.
Close to 0
POs keyed with the wrong code or quantity
Because every PO is checked against that customer's contract prices and product codes, with the original attached so you can check back.
1 page at 18:30
Production and scrap report
The manager gets the report at the same time every day with nobody adding anything up, and sees materials about to run short around 7 days ahead.
Price and scope
One price, paid once, for the fixed scope in this pack, plus a small monthly fee covering AI model costs, monitoring and minor rule changes. The total per month usually works out at about what a part-time data entry clerk costs. The real figure depends on how many POs a month and which ERP you run, and we tell you exactly after a free 30-minute call.
Not included
- Connecting an ERP with neither an API nor ODBC, which needs a custom connector (scoped separately as an Implement project)
- Advanced production planning, such as automatic machine scheduling or capacity across several plants
- Customer channels beyond email and LINE OA, such as a large customer's EDI portal
- Deep reporting on cost per piece and profit per order (that is in the cost-reduction bundle)
Where you go when you grow
Once POs are entering the system reliably, most factories go one of two ways: the operations and back-office bundle, so other paperwork such as delivery notes and supplier bills enters the same way; or the cost-reduction bundle, to track scrap, dead stock and leaking purchase prices. If you need a complex ERP connection or several plants, use the Design and Implement services for a custom build.
Safety in this business
- Contract prices and the customer list are commercially sensitive. They stay in the factory's own systems, the agent reads only the records it needs for each task, and there is a log of who or what accessed them and when.
- Messages to customers carry only the PO number and the status. They never reveal prices, another customer's production plan, or anything internal to the factory, and customer contacts are handled under PDPA, with the notice explaining what the data is used for ready to hand out.
- Anything that affects an agreement, such as accepting a PO priced differently from the contract, moving a delivery date or ordering raw material, always goes through a person, and you can trace back what the agent based its decision on.
FAQ for Factories & production
Our ERP is old and not well known. Can it connect?
If the ERP has an API, or exposes its database over ODBC, then yes, within the pack's scope. If it has neither, we will offer options on the free 30-minute call, for example having the agent produce an import file in the format the ERP accepts, or using Google Sheets as a bridge first and connecting properly later as a separate Implement project.
Every customer's PO looks completely different. Can the system really read them?
Yes, because the agent reads for meaning rather than by fixed positions. In the first week we teach it with real POs from your main customers. Anything it is not confident about goes to a person instead of being guessed, and every one keeps the original attached so you can check back.
If the production plan changes mid-day, will customers get the wrong information?
The agent always answers from the latest data in the system, and when a delivery date changes it drafts a message to the affected customers for sales to send. It never sends by itself. Where it does not have enough information, it says a member of staff will get back to them and alerts sales immediately.
The line still writes output and scrap on paper. Can we still get the daily report?
Yes. The line leader photographs the record sheet into LINE at the end of the shift and the agent reads the numbers and adds them up, showing the original photo next to every figure so the manager can check. Plenty of factories start this way and move to forms or scanners later.
Over these 2–3 weeks, what does the factory team have to do?
We need one person from sales, one from planning, and a little of the manager's time, about 2–3 hours a week in total, to send sample documents, tell us which cases a person must see, and check the results during the parallel run. The keelz team does the rest.
Cases from similar businesses
Purchase orders from email and LINE, into the ERP automatically
-25 hrs/week Data-entry hours
See this case Multi-branch retail · Mid-sized · 200 peopleA leadership report at 07:00 every morning, with nobody writing it
0 hrs Time spent on the report
See this casePacks for other businesses
Send us five sample POs, then let's talk for 30 minutes
We will tell you how much of your POs and your ERP fit this pack, what needs adjusting, and what numbers to expect in the first 30 days. Free, no obligation.
Want to see it working first? Open the sample workspace for a business like yours — this exact team of agents is running in it. Sample data, no sign-up.