Operations & Compliance package

Inventory reorder

A daily stock check finds items at or below their reorder point, raises an Approve order / Skip task for each and emails the supplier a purchase order.

OfficialNo integrations neededScheduledIntermediate~15 min setupv1.0.1

Download .utpkg 14 KB How to install

About this package

What it does

Inventory reorder keeps consumables and packaging from running out without anyone watching a spreadsheet. The Stock items table lists each item with its on-hand quantity, reorder point, reorder quantity, unit cost, supplier, supplier email, lead time and whether it is already on order. Sample rows cover packaging, labels, gloves, wipes, paper and toner, three of them below their reorder point.

Every morning at 07:00 the Daily stock check lists the active items and loops over them. Each item at or below its reorder point that is not already on order starts the Raise reorder sub-workflow: it marks the item on order, logs the reorder in the Reorders table with its estimated cost and gives the buyer a task with Approve order and Skip buttons. Approve order lets the buyer adjust the quantity, records the expected delivery date from the supplier's lead time and emails the purchase order to the supplier; Skip records why and releases the item so it comes up again tomorrow.

When anything was raised, the buyer also gets a short daily summary to confirm the stock counts are right before approving orders. No integrations needed.

Scheduled

Daily at 07:00 (Pacific/Auckland). You can also start it any time from the Run dialog, the API or the CLI.

Runs on a schedule (daily, weekly, monthly) in your time zone.

The flow

Step by step

1
Daily check
At 07:00 the schedule lists every active item in Stock items.
2
Find low stock
A loop checks each item: on hand at or below the reorder point and not already on order.
3
Raise a reorder
Each low item runs the Raise reorder sub-workflow: marked on order, logged in Reorders with its estimated cost.
4
Approve or skip
The buyer adjusts the quantity and presses Approve order or Skip (with a reason).
5
Purchase order
Approved orders are emailed to the supplier with the expected delivery date; skipped items come up again tomorrow.
6
Confirm the counts
The buyer gets a daily summary of what was raised and confirms the stock counts or flags a recount.

Every day at 07:00

Run on a schedule

Set title

Set the title for this workflow instance

Active stock items

Query, insert, update, or delete data store rows

list → Stock items

No reorders yet

Store a value

low_count = ƒ 0

Reorder list

Store a value

low_list =

Each stock item

Iterate over a collection

each in items

Done

Each Item

Below reorder point?IF

If/else if/else branching

ƒ IF(item.on_hand <= item.reorder_point, true, false) is_true

Reorder

Else

Count it

Store a value

low_count = ƒ ADD(low_count, 1)

Add to the list

Store a value

low_list = low_list<li>item.sku item.name: item.on_hand on hand …

Raise the reorder

Execute another workflow as a sub-process

→ Raise reorder

Stock is fine

Write audit log

item.sku: item.on_hand

Anything to reorder?IF

If/else if/else branching

low_count gt 0

Reorders raised

Else

Confirm the stock counts

Assign a task to a person and wait for action

Stock check {{=FORMAT_DAT

Counts confirmed

Recount needed

Nothing to reorder

Stop execution immediately

Counts confirmed

Stop execution immediately

Recount needed

Write audit log

Stock recount needed ({{task_d

Recount flagged

Stop execution immediately

Daily stock check — Every morning: find active stock items at or below their reorder point (and not already on order), raise a reorder approval for each through the Raise reorder sub-workflow, and ask the buyer to confirm the counts. The same canvas you get in the designer after installing.

Sub-workflow: Raise reorder

Reorder needed

Triggered by an incoming webhook

Reorder reference

Store a value

reorder_ref = RO-ƒ FORMAT_DATE(NOW(), "YYYYMMDD")-ƒ UPPER(LEFT(GUID(), 4))

Estimated cost

Store a value

est_cost = ƒ ROUND(reorder_qty * unit_cost, 2)

Set title

Set the title for this workflow instance

Mark on order

Query, insert, update, or delete data store rows

update → Stock items

Log the reorder

Query, insert, update, or delete data store rows

insert → Reorders

Approve the reorder

Assign a task to a person and wait for action

Reorder sku name:

Approve order

Skip

Approved quantity

Store a value

quantity = ƒ COALESCE(task_data.quantity, reorder_qty)

Final cost

Store a value

est_cost = ƒ ROUND(quantity * unit_cost, 2)

Expected by

Store a value

expected_by = {{=FORMAT_DATE(ADD_DAYS(TODAY(), COALESCE(lead_time_days, 5)), "YY…

Record: ordered

Query, insert, update, or delete data store rows

update → Reorders

Stamp the stock item

Query, insert, update, or delete data store rows

update → Stock items

Email the purchase order

Send an email via Resend

To: supplier_email

Ordered

Stop execution immediately

Record: skipped

Query, insert, update, or delete data store rows

update → Reorders

Not on order

Query, insert, update, or delete data store rows

update → Stock items

Skipped

Stop execution immediately

One stock item below its reorder point: log the reorder, ask the buyer to Approve order or Skip, email the purchase order to the supplier.

Forms

Inputs and task forms

The inputs a caller passes when it starts a run, and the forms people complete when the process needs a decision.

Start inputs

Daily stock check

Passed by the calling system

Buyer (user id) buyer_id · textOptional: user id of the buyer who approves reorders and confirms the daily summary. Set it as the default after install; empty means the workflow owner.

User Task

Confirm the stock counts

Stock check {{=FORMAT_DATE(TODAY(), "DD/MM")}}: {{low_count}} items to reorder · own header and theme

Checked by * checked_by · text

Notes count_note · textarea

Counts confirmedRecount needed

User Task · Raise reorder

Approve the reorder

Reorder {{sku}} {{name}}: {{on_hand}} left (reorder point {{reorder_point}}) · 2-column grid · own header and theme

Order quantity * quantity · numberPrefilled: {{reorder_qty}}

Note to the supplier supplier_note · textarea

Reason to skip skip_reason · choice

Stock count is wrongOrder already placedItem being discontinuedWaiting for a better priceOther

Approve orderSkip

From your code

Start a run over the API

Every workflow can be started over REST, MCP or the CLI, whatever its trigger, with the sample input below. Runs start straight away on the published version; replace <workflow id> with the id the install created.

REST

shell

curl -X POST "$USERTASKS_URL/api/v1/workflows/start" \
  -H "Authorization: Bearer $USERTASKS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"workflow_id":"<workflow id>","variables":{}}'

CLI

shell

usertasks workflows inputs <workflow id>          # the start form: keys, types, required
usertasks workflows run <workflow id>  --wait

What's included

5 assets, ready to adapt

Type	Name	Details
Email template	Purchase order to supplier	Sent to the supplier when a reorder is approved.
Data table	Reorders	Every reorder the daily check raised: what, how many, the estimated cost and whether it was approved.
Data table	Stock items	Stock you keep on hand: current quantity, the reorder point that triggers a purchase, how many to order and who supplies it. The daily check reads this table.
Workflow	Daily stock check	17 steps — Every morning: find active stock items at or below their reorder point (and not already on order), raise a reorder approval for each through the Raise reorder sub-workflow, and ask the buyer to confirm the counts.
Workflow	Raise reorder	17 steps — One stock item below its reorder point: log the reorder, ask the buyer to Approve order or Skip, email the purchase order to the supplier.

Reorders · 1 sample rows

Reorder referenceSKUItemOn hand when raisedQuantityEstimated costSupplierSupplier emailStatusRaisedDecidedExpected byNote

Stock items · 9 sample rows

SKUItemCategoryLocationUnitOn handReorder pointReorder quantityUnit costSupplierSupplier emailLead time (days)On orderLast orderedActive

Requirements

What you connect it to

Credentials never travel in a package. The install wizard asks for what your environment must provide, or installs it incomplete until you finish setup.

Needs

Email (optional) — Email delivery configured for the instance (EMAIL_PROVIDER), used for notifications.

After installing

Replace the sample rows in Stock items with your stock: on hand, reorder point, reorder quantity, unit cost, supplier and supplier email. Untick Active for items you no longer stock.
Set the default of the "Buyer (user id)" input on the Daily stock check to the person who approves orders; empty means the person who installed the package.
Keep On hand up to date (edit the table, import a CSV or update it from another workflow). When stock arrives, untick On order.
Change the trigger time and time zone if 07:00 Pacific/Auckland does not suit, and set EMAIL_PROVIDER so purchase orders reach suppliers.

Asked for on install

Nothing: it installs complete.

Install

Install it in your workspace

Works on UserTasks cloud and on any self-hosted instance. Installing creates the assets above; nothing runs until you complete setup and start it.

In the app

Download inventory-reorder-1.0.1.utpkg.
Open Automations → Packages and drag the file onto the page (or choose Import package). Browse gallery there lists every gallery package without downloading by hand.
Pick the file. The wizard verifies the checksum, every file hash and the signature, and shows the readme.
Review the changes (what is created) and the data rows.
Fill in the requirements, or tick Keep incomplete and finish later with Complete setup.
Done: the workflow is published and active once setup is complete.

With the CLI

shell

curl -fLO https://usertasks.com/gallery/inventory-reorder-1.0.1.utpkg
usertasks packages inspect inventory-reorder-1.0.1.utpkg       # offline: checksum, hashes, signature
usertasks packages install inventory-reorder-1.0.1.utpkg --dry-run
usertasks packages install inventory-reorder-1.0.1.utpkg       # prompts for each requirement
usertasks packages install inventory-reorder-1.0.1.utpkg --keep-incomplete --yes   # in CI; finish with:
usertasks packages complete inventory-reorder -f values.yaml

Verify the download

File SHA-256: 5be89fe75715fe3d0eec37de3828108a8c24e03c60b7ba917c9dc8dec1394893
Package checksum (what is signed): sha256:9d3dc866a68cd5c23ae682eaebcdbb2f45f03f1ecd53048377a140b16d27d08b
Signer: Unsigned preview build — compare the SHA-256 above

shasum -a 256 inventory-reorder-1.0.1.utpkg should print the file SHA-256. How gallery packages are signed.

Versions

Version 1.0.1

v1.0.12026-10-28Steps for the coordinator who set the package up are assigned to the workflow owner (workflow_owner_id), now that workflow_started_by names the person who started the run.
v1.0.02026-10-28First release.

Installing a newer version upgrades in place: local credentials and requirement values are kept, and changes you made are flagged first. How packages work

More packages

Browse the whole gallery

Inventory reorder

What it does

Scheduled

Step by step

Sub-workflow: Raise reorder

Inputs and task forms

Daily stock check

Confirm the stock counts

Approve the reorder

Start a run over the API

5 assets, ready to adapt

What you connect it to

Needs

After installing

Asked for on install

Install it in your workspace

In the app

With the CLI

Version 1.0.1

Related

Audit evidence collection

Contract renewal reminders

Policy acknowledgement tracker