Warehouse & distribution
- Receiving and put-away log
- Cycle counts and discrepancies
- Pick, pack and ship board
- Returns and damage reports
For warehouses, labs, production lines and kitchens
ezship is where operations teams build their own tracking apps with AI. Explain a process in plain words, and an agent builds a precise, working app on one shared database that your whole team signs in to. You don't need developers, and you don't need the spreadsheet only one person understands.
No card needed. Sign up with your email and start building in minutes.
We receive pallets at docks 1 to 3. Log the supplier, lot number and temperature on arrival. Anything over 5°C goes on hold for QA.
Built a Receiving log with a check-in form, an automatic hold over 5°C and a QA queue. It's using your existing suppliers table. Take a look in the preview.
Add a photo of the delivery note, and make lot number required.
Done. Photos attach to each delivery, and the form won't save without a lot number. Publish to your team?
| Lot | Supplier | Dock | Temp | Status |
|---|---|---|---|---|
| L-24-0918 | Valley Dairy | 2 | 6.4°C | QA hold |
| L-24-0917 | Greenline Produce | 1 | 3.2°C | Accepted |
| L-24-0916 | Coastal Seafood | 3 | 1.8°C | Accepted |
| L-24-0915 | Valley Dairy | 2 | 4.1°C | Accepted |
| L-24-0914 | Hearth Bakery | 1 | — | Accepted |
What you can build
ezship is made for operational record-keeping: the logs, queues, checklists and boards that keep a physical business running. Some of the apps teams start with:
Plus inspections, work orders, asset tracking, training records, IT requests and approvals: anything with people, records and a process.
Sound familiar?
Someone types it up at the end of the shift, if they remember. When something goes wrong, the record you need is in a binder.
It works because one person knows which tabs not to break. Ten people edit copies, and nobody is sure which one is current.
The big system covers most of the job, but changing a single field takes a vendor ticket or a six-month IT project. So the workarounds pile up around it.
ezship replaces those gaps with small, connected apps that the people who run the process can build and change themselves.
How it works
You describe the work. The agent builds it. You try it on real records and ask for changes until it's right, and then you publish it to your team.
Tell the agent who does what, what gets recorded and what should raise a flag. Paste in the columns from the spreadsheet you use today. Plain language is enough.
A live preview runs against your actual data. Click through it, then ask for what's missing: "make temperature required", "add a photo", "show me only my shift".
One click puts it live. Invite people by email. They sign in from the tablet on the line, the phone on the floor or the desktop in the office.
Processes change, and now your app can change with them. Every save is a version with a name and a time on it, and a failed update never takes the running app down.
The studio
Everything happens in one browser window at studio.ezship.dev: the agent, the app it's building, and the data behind it.
| lot | product | qty | location | status |
|---|---|---|---|---|
| L-24-0918 | Whole milk 4L | 120 | QA-1 | hold |
| L-24-0917 | Romaine, case | 48 | C-04 | stocked |
| L-24-0916 | Salmon fillet | 36 | F-02 | stocked |
| L-24-0915 | Greek yogurt | 200 | C-11 | picked |
History · L-24-0918
Why ezship
A general-purpose AI coding tool can make anything, and that's the problem. Each app comes out different, with its own database, its own login and its own surprises. ezship gives the agent a framework built for one job, operational record-keeping, and holds every app to it. The result is apps you can trust with the records your business runs on.
Every app is built the same way, from the same parts. The tenth app is as dependable as the first, and anyone, person or agent, can pick up where the last one left off.
The framework's rules, a type check and a full build run on every publish. If anything fails, the running app stays exactly as it was.
Live tables, lot and ticket numbers that never collide, photo and document attachments, and updates that succeed or fail together. These come built in, so they're never improvised.
Sign-in, roles and access control belong to the platform, not to code an agent wrote. Every app gets them, and none of them can get them wrong.
Apps can't reach out to the internet, install add-ons or store data anywhere else. What the agent builds is what you see.
Each app keeps a written record of its purpose, its users and the decisions behind it, so the next change starts from what the last one learned.
One operation, one source of truth
Each app does one job well, but they all share one database, one set of people and one look. The receiving log and the inventory board read the same lots. Quality sees what production logged a minute ago. Because everything you've already built is there to reuse, each new app comes together faster than the last.
For the person who gets asked for the numbers
Data from scattered spreadsheets has to be cleaned before you can use it. ezship keeps records structured from the moment they're entered, in one place, with the full story behind every change.
Ready for your IT team
These apps hold real operational records, so ezship treats every one as sensitive from day one, whether it's one team's checklist or a hundred people across three shifts.
Got developers?
The apps your team builds in the studio are plain React and TypeScript. Developers can open the same
apps from a terminal with the ez command, keep them in git, and work with Claude Code,
Codex or Cursor. The rules and checks are the same either way, so ops and engineering can share the
work without stepping on each other.
$ ez clone northside
pulled 7 apps into northside/
$ cd northside/receiving
$ claude "add a weekly supplier scorecard"
$ ez push && ez deploy
✓ rules ✓ types ✓ build
✓ live for 38 members
Start with the clipboard that bothers you most. The free trial includes your own private ezship and $5 of AI credit to build with.