Zudo WorksHow the system fits together
The system blueprint (Settings → System blueprint) draws this as a flowchart you can switch between Simple, Detailed and Animated views. In words:
Setup ──▶ Masters ──▶ Stock ──▶ Sales ──▶ Purchasing ──▶ Production ──▶ Low-code ──▶ Admin
company items receipts customers vendors BOMs forms users & roles
units costing issues & sales purchase jobs workflows billing
warehouses transfers orders orders work centres dashboards API keys
team balances procurement & reports webhooks
audit logWhat syncs with what
- A posted movement writes ledger entries, updates balances and the item's moving-average cost, and feeds the dashboard.
- Receiving a purchase order posts a stock receipt (linked to the PO line) and marks the PO received when the last quantity arrives.
- Issuing material to a job posts a
JISmovement valued at the moving-average cost; a return posts aJRTmovement credited at the same rate. Both update the job cost. - Confirming a sales order reserves stock per line; confirmed lines become demand for procurement.
- Procurement = (confirmed sales order lines, exploded one level through released BOMs, + open job material) − (on hand + sent purchase orders) = what to buy / what to make.
- Saving a custom record fires the form's workflow rules (e-mail, create/update records, call a URL); a report button can fire a workflow over the report's rows.
- Every create / update / delete / lifecycle move writes the audit log and, for jobs, sales orders and purchase orders, notifies webhooks and the notification centre.
Mandatory before anything else: company details (set at signup), at least one unit of measure (seeded), at least one warehouse (seeded as MAIN), and an item. A job additionally needs a released bill of materials for its item.
Last updated