Holy ResourceHoly Resource
ModulesInventory

Checkouts And Returns

Record who is using an item, tie it to a ministry or event, scan barcodes, and resolve returns correctly.

The Checkouts page tracks temporary inventory movement.

Use it when an item is leaving storage for an event, service, rehearsal, outreach, classroom, or ministry activity and you need a clear record of who took it, why, and whether it came back.

What The Page Tracks

Each checkout record can include:

  • item name
  • event
  • used by ministry
  • checked out by
  • checked out at
  • expected return date
  • returned or resolved timestamp
  • quantity
  • status

The page keeps both open and resolved records together so teams can review current use and past accountability from the same surface.

Manual Checkout Workflow

Use the manual checkout dialog when staff need to choose a specific item, quantity, event, and ministry in one controlled step.

The form includes:

  • item selector
  • optional event link
  • required ministry field
  • quantity
  • optional expected return date
  • optional notes

Important rule:

  • the ministry field is required

That rule keeps the audit trail more useful later because leadership can see which team actually used the item.

What Happens During Checkout

When a checkout is saved:

  1. the app verifies the item exists and belongs to the current branch
  2. the app checks that enough quantity is available
  3. the app creates a checkout record
  4. the app reduces the available quantity immediately

If the requested quantity is larger than available stock, the checkout is blocked.

Barcode Scanner Workflow

The page also includes a scanner for faster use at storage rooms, production areas, and prep tables.

The scanner supports two modes:

  • checkout
  • return

In checkout mode, staff must choose a ministry before scanning.

In return mode, the system looks for the oldest still-open checkout for that item and resolves it first.

This makes scanning practical for repeated one-at-a-time movement.

One scan means one item

The barcode scanner handles checkout and return one item at a time. If your team is moving larger quantities at once, the manual dialog is usually clearer.

Return Workflow

Returns can be recorded in three ways:

  • returned in good condition
  • returned damaged
  • lost

The return dialog also supports partial returns.

That means if 10 units were checked out and only 6 came back, staff can return 6 now and leave 4 still checked out.

Return Rules That Matter

Good return

If the status is returned:

  • quantity is restored to inventory
  • the checkout gets resolved
  • the return timestamp is recorded

Damaged return

If the status is damaged:

  • quantity is not restored
  • a reason note is required
  • the item condition is updated to damaged

Lost return

If the status is lost:

  • quantity is not restored
  • a reason note is required
  • the record is resolved as shrinkage, not as available stock

These rules matter because the system treats damaged and lost inventory as real operational loss instead of pretending the stock came back.

Partial Returns

Partial returns are useful when:

  • some items came back now and the rest will come back later
  • a team only used part of a multi-unit checkout
  • some units were returned while another unit was damaged or missing

The system keeps the remaining open quantity visible until the rest is resolved.

The event field is optional because not every inventory movement belongs to a scheduled event.

Still, it is worth using when the checkout is event-specific because it gives you better historical context later.

Useful examples:

  • Sunday service equipment
  • youth night setup items
  • outreach supplies
  • conference-room audio gear for a staff meeting

Ministry Accountability

The Used By Ministry field is one of the most important parts of the workflow.

It helps your branch answer questions such as:

  • Which ministry is still using this item?
  • Which team keeps borrowing the same equipment?
  • Should this item stay assigned to that ministry long term?

That same ministry relationship also supports the overview page confirmation queue.

Good Operational Habits

  1. Use the manual dialog for multi-unit checkouts.
  2. Use the scanner for fast one-at-a-time handling.
  3. Record notes when something unusual happened.
  4. Do not mark a damaged or lost item without a real reason note.
  5. Return items as soon as they are back so the available quantity stays trustworthy.

Common Questions

Why is the ministry field required?

Because the system is built for accountability, not just movement. A ministry name makes the record useful later.

Why did a damaged return not increase stock again?

Because a damaged item is not treated as available inventory.

Why did the barcode return resolve the oldest open record first?

The scanner uses a first-in, first-out return rule so repeated scans can cleanly close the oldest still-open checkout.

Was this helpful?

On this page