Live order board
- Before
- Staff rerun the same reports all day to see what's late.
- After
- One screen shows open orders, backorders and anything stuck, on a monitor, tablet or phone. It only reads from Jiwa.
Jiwa add-ons and automation · Auckland
Make Jiwa do the typing.
I build add-ons for New Zealand distributors and importers who run Jiwa. Live order boards. Customer POs that turn into sales orders. Supplier confirmations booked straight in. Your team checks and approves, and stops retyping.
Order inboxSample data
purchasing@harbourelectrical.co.nz · 9:42 am
PO 4471: 3 lines, deliver to Penrose
| Line | Qty | Check |
|---|---|---|
| Inductive sensor, M18, PNPmatched to your part code | 4 | Price OK |
| Cordset, M12, 5 mmatched to your part code | 4 | Price OK |
| Tower light, 3 tiercustomer price is lower | 1 | Check price |
A person checks it and presses Save.Open in Jiwa
What I build
The jobs your team does twice
Every distributor on Jiwa has the same few time sinks. These are the ones I fix, built around the way your team already works.
Customer POs into sales orders
- Before
- Someone retypes every emailed purchase order.
- After
- Each PO is read, matched to your parts and prices, and laid out in Jiwa. A person checks it and saves.
Supplier confirmations into POs
- Before
- Order confirmations arrive as PDFs and scans, and get keyed in by hand.
- After
- They're read, scans included, matched to your part codes and currency, and set up as purchase orders to check.
Product data that's right first time
- Before
- Half-finished parts: no datasheet, wrong category, a $0 price.
- After
- New parts arrive complete, with specs, datasheet and image, and every import is checked before it goes in.
Jiwa plugins
- Before
- Small gaps in Jiwa that cost a minute on every order.
- After
- Plugins built in Jiwa's own .NET framework that close the gap, tested on a copy of your data first.
Answers from your own data
- Before
- Staff dig through catalogues and spreadsheets to answer a product question.
- After
- An assistant that searches your own products and stock, and shows where each answer came from.
How I work
Your system stays safe
Jiwa holds your orders, stock and money. These rules apply to every job.
- Read-only firstMost tools only read from Jiwa. Nothing changes until we agree it should.
- Test copy firstAnything that writes to Jiwa is built and proven on a copy of your data.
- A person approvesAutomation prepares the work. Your staff check it and press Save.
- Nothing goes out on its ownNo email or order reaches your customers without someone sending it.
- Backups before bulk changesEvery bulk update gets a snapshot first, so it can be put back.
- You own what you pay forThe work I build for you is yours, with notes your next person can follow.
How a job starts
Four steps
No long proposal. A conversation, a look at how your team works, then a fixed price.
- Chat15 minutes, free. Tell me which job your team hates most.
- LookI spend an hour with your team and see how Jiwa is used day to day.
- QuoteA written scope and a fixed price, so there are no surprises.
- BuildBuilt on a test copy, approved by you, then switched on. Support after.
About
Hi, I'm Jared
For nearly three years I've worked in sales and systems at an Auckland industrial automation distributor that runs Jiwa. I started on the order desk and ended up building the tools the business runs on: a live order board, automated order entry, supplier confirmation scanning, a part creator that reads datasheets, and a product assistant for staff.
So I know Jiwa from both sides: the database and plugins, and the busy counter at four o'clock when three orders need to go out. Forge Automation is my own business, and I build every job from scratch for the client.
- Jiwa SQL and plugins (.NET)
- Python
- OCR for scanned documents
- Web dashboards
- AI with checks
- Based in Auckland
Why Forge?
Code is my iron.
The computer is my anvil.
I've always been hands-on. I like taking programs that were never meant to work together and making them work as one. When I was choosing a name, "Forge" stuck. Making good software is a lot like making a blade: you heat the metal, shape it, test it, and keep working it until it's right. I treat code the same way. To me, writing it well is a craft, close to an art: clean, strong and built to last. Every job is made for the business it's for.
Contact
Which job does your team hate most?
Phone022 319 2144
Happy to visit anywhere in Auckland, or talk on the phone if you're further away. The first chat is free.