Misc Items / Inventory Config
Misc Items lets operators track an inventory of small, miscellaneous physical items on site — things like eye wash stations, first aid kits, smoke detectors, extinguishers, or any other item that needs to be catalogued and periodically inspected. The admin side of misc items has two responsibilities: defining the types of items that can be created, and assigning inspection schedules to those items.
Inventory — organization-Level Rename
Some organizations use this feature as a full inventory management system for parts, consumables, tools, and other equipment rather than a simple site-item catalogue. To better reflect that use case, an org-level setting (misc_item_rename) can be enabled to rename Misc Items → Inventory throughout the entire application — navigation menus, admin pages, reports, modals, and all operator-facing screens.
When the Inventory setting is active, items can be attached directly to tasks and job forms (projects). When a consumable inventory item is consumed on a task or job, EZ Ops automatically deducts the quantity used from the item's stock level, keeping on-hand counts accurate without manual adjustment.
If your organization uses this module for parts or equipment inventory, contact your EZ Ops administrator to enable the misc_item_rename org setting.
Key point: The types you create in admin determine what operators can select when creating an item on site. If a type does not exist, operators can add it on the fly using the + button — but for organizations that want controlled inventories, types should be pre-configured here.
Navigate to Admin → Misc Items (or Admin → Inventory if the rename setting is active) to access the configuration page. This page manages two things:
- Misc Types — the list of item categories operators choose from
- Custom Info Fields — extra data columns you can attach to a type
Inspection schedule assignment happens separately, on each item's record through the location configuration page.
Part 1 — Managing Misc Types
Creating a New Misc Type
- Click Add New Type
- Enter a type name — this is what operators see in the type selector when creating an item (e.g., "Fire Extinguisher", "Eye Wash Station", "First Aid Kit")
- Set the type flags (see below)
- Save
Type Flags
Each type has two flags that control operator behaviour for all items of that type:
| Flag | What It Does |
|---|---|
| User Deactivation | When enabled, operators can deactivate their own items of this type. When disabled, only admins can deactivate items of this type. |
| Is Inspectable | When enabled, items of this type can be assigned inspection schedules. When disabled, the inspection assignment option does not appear for items of this type. |
Both flags are enabled by default on newly created types.
Editing a Type Name
You can rename a type at any time. When a type name is changed, the update cascades automatically to all existing misc items of that type — every item in the system that belongs to the renamed type will show the updated name.
Deleting a Type
A type can only be deleted if no items currently exist for it. If items exist, the delete option is blocked. To remove a type, first deactivate or delete all its items, then delete the type.
Deleted types are soft-deleted and can be restored.
Restoring a Deleted Type
Soft-deleted types can be restored from the same configuration page. Restoring a type makes it selectable again for new item creation.
Part 2 — Custom Info Fields (Extra Info per Type)
Each misc type can have a set of custom data fields attached to it. These appear as extra inputs on the item creation and editing forms for operators. Use this to capture type-specific details — for example, a "Fire Extinguisher" type might have fields for last inspection date, agent type, and pressure rating, while a "Vehicle" type might have fields for licence plate and VIN.
Adding a Custom Info Field
- Open a type on the Misc Items config page and select its Config arrow. The page is headed Edit {type} extra info interface
- Click Add extra info column
- Configure the column:
- Alias — the display label operators see. This is the only part of the column operators ever read
- Internal Column — optional, and only needed when the value has to drive behaviour elsewhere in the product. Leave it unset for a plain data field. See Pricing items for Field Tickets below for the one case where this matters most
- Identifier Order — sets the priority of this field in how items are named and displayed in inspection records and reports. Fields with lower identifier order numbers appear first in the item's identifying label
- Item Component — tick this when the value describes a physical part that can be swapped out, so an inspection's replacement question can update it. See Part 4 below
- Save Changes
Use Active Columns and Deleted Columns to switch between the two lists, and Remove Column / Restore Column to move a column between them.
Pricing items for Field Tickets
There is no price field on a Misc Item. Pricing is carried by a custom info field, and it is the Internal Column that makes it work, not the name you give it. Add the field as normal, then set its Internal Column to rate from the dropdown. The Alias — what operators actually see — can say Rate, Unit Price, $/hr, or anything else.
This catches people out. A field aliased "Rate" with no Internal Column set looks correct on the item record, appears on the import template, accepts a number, and prices nothing. Nothing in the product warns you. If a rate is not pre-filling on tickets, check the Internal Column before anything else.
rate is one of a fixed set of Internal Column values, alongside description, make, model, and serial_number, and a Type can only have one field set to each.
Fill the number in per item on the Misc Items tab, in the field labelled with your alias. In bulk, the import template's column header is your alias rather than rate.
It is only a default; the row's own value is what prices the line and the ticket total, and changing the catalog default later does not reprice tickets already recorded. Whether a crew can overwrite it depends on the screen. On the Job Dashboard the pre-filled rate is editable. On the location or plant Field Tickets panel — the offline path crews use in the field — the Rate box is disabled once a default exists, so the item can only be billed at the catalogue price. Leave the default off any item whose price genuinely varies by job.
This is unrelated to a job asset's Daily cost, which is typed on the Job and is recorded for planning reference only — it does not price anything.
Reordering Fields
Drag and drop fields to set the order in which they appear on the item creation form.
Removing a Field
Fields can be removed from a type. Removing a field hides it from new item creation but does not delete historical data already captured. Removed fields can be restored.
Part 3 — Inspecting Misc Items
Inspection schedules are assigned on individual misc items, not on types. This allows different items of the same type to have different inspection frequencies.
To assign an inspection to a misc item:
- Navigate to Admin → Field Locations or Admin → Plants and open the location
- Find the Misc Items section and click on the specific item
- Click Add Inspection Schedule
- Select the Inspection Form to use
- Set the schedule parameters (due date, frequency, repetition type, warning period)
- Save
Note on rental items: Items flagged as rental when created are never assigned inspection schedules automatically. If an Inspection Handler (auto-assignment rule) is configured for a type, it will skip any item that has the rental flag set.
Modelling a Custom Inspected Asset
EZ Ops has several purpose-built location panels — Plunger, Catadynes, Tanks, Equipment — each of which records a fixed set of details and asks a fixed set of questions. Where you need control over what is recorded and what is asked, an inspectable misc item does the same job and lets you define all of it. This is the usual way to set up a new class of inspected asset, and it is commonly used for plungers as well as for extinguishers, eye wash stations, and vehicles.
The pattern has four pieces:
- An inspectable type. Create the Misc Type with Is Inspectable enabled, and add an extra info column for each static detail you want on the record — plunger type and size, a serial number, a carseal number, a licence plate. Tick Item Component on any column that describes a physical part that can be swapped.
- A questions list. Create a Form with type Inspection and inspection type Miscs — shown as Inventory if your organization renames misc items. Only forms with that inspection type appear in the picker when you attach a schedule, so a form saved with the wrong inspection type will be invisible rather than rejected.
- A schedule per item. Attached on the item as described above, with the standard repetition types — Dynamic, Static, or Window — and a frequency in days, weeks, months, or years.
- Questions that change the record. Two answer types do more than capture a response. They are covered below.
Operators do not complete these from the Misc Items panel. The item is listed there, but the due inspection appears in the location's Inspections panel alongside every other inspection at the site, with Complete Inspection on it.
The frequency-change question
Add a question with answer type inspection_freq to let the operator adjust how often the inspection recurs — useful where the right interval is only obvious once someone has seen the asset.
The operator is shown Current frequency: with the present setting, and enters a New duration:. What they enter becomes the frequency of the next scheduled inspection; the one they are completing is unaffected. Only one such question is allowed per form.
Three limits worth knowing before you add one:
- It is not available during bulk completion, and the form editor warns you about this if Allow bulk is on
- It does not appear on Window schedules set to a
quarteror6 monthfrequency - The change only lands when the device syncs. If the next inspection has already come due first, EZ Ops sends Missed Frequency Update: Inspection Already Completed or Delinquent instead of applying it, so tell crews to sync the same day
The replacement question
Add a question with answer type replacement to let the operator record that a part was physically changed and update the item's details in the same step. This is what makes the pattern worth using for anything consumable — a plunger swapped for a different type, an extinguisher whose serial or carseal number changed.
The operator sees a checkbox labelled with your question text. Ticking it reveals a text input for every column on the type marked Item Component, each labelled with that column's Alias and limited to 255 characters. Saving writes the new values onto the item and retires the old ones — the misc item itself is not replaced, only its component values change, so the item keeps its identity and its inspection history.
Both values remain visible afterwards. The completed form log shows the old value prefixed Old beside the new one, and the Misc Items Changes report lists them as old and new values across every item.
Two constraints:
- Only put one replacement question on a form. The form editor will let you add a second, but the two share one internal flag, so unticking either cancels the item update even when the other is still ticked
- Like the frequency question, replacement is unavailable during bulk completion
If the form has a replacement question but no column on the type is marked Item Component, the operator gets the checkbox with no fields under it and nothing is updated.
Part 4 — Bulk Operations
The Misc Items report and admin pages support bulk operations on multiple items at once:
| Operation | What It Does |
|---|---|
| Mass Deactivate | Sets selected items to inactive. Items remain in history but are excluded from active inventory views. |
| Mass Reactivate | Restores selected inactive items to active status. |
| Mass Delete | Soft-deletes selected items. |
| Mass Restore | Restores soft-deleted items. |
Bulk operations are useful when a site changes, a batch of items is replaced at once, or rental items are returned.
Part 5 — Importing Misc Items (Excel)
Misc items can be bulk imported from an Excel file. This is the fastest way to set up an initial inventory for a new site.
The Import Misc Items tab (Import Inventory when the Inventory rename is on) appears on the Misc Items configuration page for users who have the Can Import user setting enabled. If you do not see the tab, that setting is the reason.
The template is per type, and so is the import. You can only import one misc type per file. A file containing two types will have the second type's rows rejected.
To import:
- Open the Misc Items configuration page and go to the Import Misc Items tab
- Under Import Template, use Filter By Type to pick the type you are importing
- Tick With Data if you want the template pre-filled with the existing items of that type — this is how you bulk edit rather than bulk create
- Click Download Template
- Fill in the rows, leaving the
idcolumn blank on every new item - Choose the file under Import File and click Import
Repeat for each type.
Filling in the template
The template gives you a fixed set of columns followed by one column for every info field configured on that type.
| Column | What to enter |
|---|---|
id |
Leave blank to create a new item. Enter an existing item's ID to update that item instead |
misc_type_id |
The numeric type ID, the same value on every row. See below for where to find it |
active |
1 for active, 0 for inactive |
locationable_id |
The numeric ID of the plant or field location |
locationable_type |
App\Plant for a plant, App\Well for a field location |
quantity, quantity_units, consumable |
Stock fields. Quantity defaults to 1 and consumable to unticked if left blank |
| One column per info field | The item's details, under the alias you gave each info field |
A template downloaded without With Data is column headings only. Nothing is pre-filled, including misc_type_id. The quickest way to get the type ID and see what good data looks like is to create one item of that type by hand, then download the template again with With Data ticked — the misc_type_id on that row is the value to copy down your whole file. Ask the EZ Ops team if the type has no items yet.
Locations are matched by ID, not by name. The location_name column in the template is there for you to read while you work; the import ignores it. Get the numeric ID from the location's admin page or from a template downloaded With Data.
There is no description column. An item's description is built automatically by joining the info fields you marked as identifiers on the type, in identifier order. If your imported items come in with blank descriptions, no identifier info field was set on the type.
Do not delete or rename any info field column. If even one of the type's info field columns is missing from the file, the entire file is rejected rather than just that column being skipped. Column headings are read exactly as written, so keep the spelling, spacing and capitalisation the template gave you.
Columns that do not import
Four columns appear in the template but are not written by the import: rental, vendor, status and alert_quantity. Set these on the item after import, or through a mass edit. The attachable_id and attachable_type columns are also checked but not saved, so an item cannot be attached to a piece of equipment or a tank through the import.
Before you import, make sure the type exists with all of its info fields configured, and that the plant or field location already exists. Both are matched during the import and neither is created by it.
Part 6 — Using Misc Items / Inventory in Tasks and Jobs
When the Inventory org setting is enabled, misc items become first-class participants in task and project workflows.
Attaching Items to Tasks
Operators can attach one or more inventory items to a task from the task detail view. Each attachment records:
- Which item was used
- Quantity used — how many units of that item were consumed on the task
When the task is completed, EZ Ops automatically deducts the quantity_used from the item's on-hand quantity. This means stock levels stay current without any extra manual updates.
Attaching Items to Jobs (Projects)
Misc items / inventory items can also be attached to jobs (projects) as assets. Each attachment on a job records:
- Item, quantity, quantity units
- Assigned date and released date
- Whether the item is consumable (stock is deducted immediately on attachment) or a non-consumable asset (status is set to
assignedfor the duration and returns toavailablewhen released) - Daily cost and rental flag
Job-level attachment reserves the item — it does not cost the job anything. The assigned and released dates mark the item busy for that window so it cannot be picked up by another job. They do not price it. Daily cost is captured on the attachment for planning reference, but no job cost total charges it, and leaving the released date blank does not accrue anything. Actual equipment cost comes only from the item being added as a line on a Field Ticket.
Marking the job Complete releases its open non-consumable assets automatically and backdates them to the job's end date, but nothing else does. In particular, deleting a job does not release its assets: they stay marked assigned and cannot be picked for another job until the job is restored and the assets released by hand.
Two different things can look like the same attachment. An item added to the job is a reservation — it marks the item busy and carries no cost. An item added to a Field Ticket on that job is a billable line priced by rate × quantity, and it does not change the item's status. Only Misc Items can be either — records in the Equipment module cannot be assigned to a job at all, and assigning a misc item to a job creates no equipment utilisation or maintenance history.
Consumable vs. Non-Consumable Items
| Item type | On attachment | On removal / release |
|---|---|---|
| Consumable | Quantity is reduced by quantity_used immediately |
Quantity is restored if the attachment is deleted |
| Non-consumable | Item status changes to assigned |
Item status returns to available |
This distinction is set on the item itself when it is created (the consumable flag on the misc item record). Configure item types accordingly so operators understand which items deplete stock and which are tracked by availability.
Common Issues
"Operators can't find a type when creating an item"
- The type may not exist yet — add it on the Misc Items config page
- The operator can use the
+button to create a new type on the fly if admin settings permit
"Operators can't deactivate an item"
- The type's
User Deactivationflag is disabled — only admins can deactivate items of that type. Enable the flag on the type if operators should be able to deactivate on their own.
"An item doesn't show an option to assign an inspection"
- The type's
Is Inspectableflag is disabled — enable it on the type configuration to allow inspection assignment
"Deleting a type is blocked"
- The type still has items associated with it. Deactivate or delete all items of that type first.
"An import failed with a type not found error"
- The
misc_type_idin the file does not match a type in your organisation. Do not type this value in by hand — download the template for the type you want and use the ID it comes pre-filled with.
"An import was rejected with a missing headers error"
- One of the type's info field columns is missing from the file. A single missing info field column rejects the whole file, not just that column. Re-download the template and re-enter the data rather than editing an older copy, because the columns change whenever an info field is added to the type.
"An import rejected every row after the first few"
- The file contains more than one misc type. Only one type can be imported per file. Split the rows into one file per type and import them separately.
"Imported items have blank descriptions"
- No info field on the type is marked as an identifier. The description is generated by joining the identifier info fields, so with none set there is nothing to build it from. Set identifier order on the type's key info fields, then re-run the import with the
idcolumn filled in to update the existing items.
"Imported items landed with no location"
- The
locationable_idcolumn needs the location's numeric ID andlocationable_typeneedsApp\PlantorApp\Well. A location name in thelocationable_idcolumn will not resolve, andlocation_nameis ignored by the import.
Tips & Recommendations
- Set the Internal Column to
rateon any type you bill from Field Tickets — it pre-fills the rate on the ticket row, which is faster and more accurate than crews typing a price from memory. Set the Internal Column, not just the alias, or the field prices nothing - Leave the default rate off items whose price varies by job — crews working offline cannot type over a default, so a fixed rate on a variable item forces them to record the difference as a freeform expense instead
- Pre-configure types before deployment — give operators a clean type list of pre-configured misc types with all settings and columns set
- Use identifier order on custom fields — the fields with the lowest identifier order numbers form the item's display name in inspection records. Put the most identifying field (e.g., serial number) first
- Disable
Is Inspectablefor types that don't need it — this keeps the inspection assignment option clean and prevents accidental schedule creation on non-inspectable items - Use
User Deactivationcarefully — enable it for consumable or frequently-rotating items; disable it for permanent infrastructure items that should only be retired by admins - Reach for an inspectable misc type before a purpose-built panel — the fixed panels record fixed details and ask fixed questions. A misc type with extra info columns, an Inspection questions list, and a schedule gives you control over all three, plus the frequency-change and replacement questions
- Mark the swappable parts as Item Component while you are building the type — retrofitting it later is easy, but every inspection completed before you did so recorded a replacement with nothing to update