Field service software: 4 tools compared on stock and forms

• Frappe: A Stock Entry lets you record Item movement between Warehouses Frappe Documentation.
• Odoo: In the Min field and Max field, leave the values set to 0.00 Odoo.
• Microsoft: Create inspections and add them to work orders for Field Service technicians to fill out online Microsoft.
• Housecall Pro: Add a name for the checklist (this is the name you and your employees will see when adding and viewing checklists to jobs and estimates) Housecall Pro.

The table below maps each publisher to the specific stock control or job form capability described in its own documentation. Use it to verify which platform documents the setting you need before configuring it.

To apply this comparison, identify whether your next setup task requires a quantity restriction, a permission-based inspection workflow, or a structured checklist with photo storage. Then locate that specific documented setting in the tool you are currently using. If your team needs to track warehouse movements, review the Frappe documentation for Stock Entry records. If you are configuring automatic replenishment triggers, check the Odoo reordering rules for the Buy route configuration. For teams assigning digital forms to technicians, verify that your user roles match the Microsoft Field Service permissions for creating, assigning, and viewing inspections. Finally, if you rely on visual evidence during a visit, confirm that your checklist photos remain attached to the checklist itself rather than migrating to job attachments, as documented by Housecall Pro. This ensures each piece of field data lands in the location your software actually supports.

Frappe Documentation describes the serial and batch bundle feature introduced in version 15 to handle stock transactions for serial number or batch items. When recording a Stock Reconciliation entry, users select Item Code, Warehouse, Quantity, and Valuation Rate fields. The system also derives transaction quantities directly from entered serial numbers; for instance, adding serial nos A001, A002, and A003 sets the quantity as 3 in the transaction.

Frappe outlines a receiving tolerance example where ordering 100 units with a supplier sending 120 units allows receiving 110 units if the percentage is set to 10%. This example illustrates how percentage-based limits function in Stock Settings but does not establish a universal receiving limit for every business. Additionally, from version 15, users cannot make negative stock transactions for serial or batch items even though Allow Negative Stock has enabled in the Stock Settings. This restriction applies specifically to serial and batch item types regardless of the general negative stock setting status.

Illustrative example: moving serial-tracked stock

Suppose a crew moves 10 serial-tracked units between warehouses and records each serial number on the transaction. If the serials are entered, the transaction quantity should equal the number of serial numbers, as in the Frappe behavior described above. Run a test entry in your own system before you rely on it.

Odoo documents an item configured with a 0/0/1 reordering rule that uses the Buy route. In this specific configuration, the Min and Max fields are both 0.00, and the rule is written as 0/0/1. Presenting these values as a documented example prevents treating them as a universal truck-stock recommendation for all service vehicles.

Check your current software settings to see if they match these documented examples before adjusting your workflow.

The Checklists Overview documentation explains how to structure the items a technician completes during a visit. You can add sections to organize different checklist items, which lets you group related tasks under clear headings rather than listing every step in one unbroken block (Housecall Pro). This organization applies to the checklist itself, so each section holds its own set of items as defined by your setup.

Photo storage follows a specific rule that distinguishes checklist evidence from general job records. Photos uploaded to a checklist will be stored and viewed on the checklist; they will not appear in the attachments section on jobs or estimates (Housecall Pro). This means if a technician takes a picture while completing a checklist item, that image remains associated with that specific checklist entry. It does not automatically populate the broader attachments area found on the job ticket or any estimate documents.

When planning your workflow, consider where you need to review these images later. If you rely on checking job attachments to see all visual evidence from a visit, checklist photos will not show up there. They stay within the checklist context. To view them, you must open the specific checklist where they were uploaded. This separation keeps checklist-specific observations distinct from other file uploads attached directly to the job record.

For service managers reviewing completed work, this distinction matters when verifying what was captured. A photo taken during a checklist step is part of that step’s record. It is not a generic job attachment. When auditing field observations, open the checklist where the photos were uploaded rather than searching the job's main attachment list. This ensures you are reviewing the correct evidence tied to the specific task performed.

If your team uses checklists to document condition reports or safety inspections, remember that the visual proof lives with the checklist. Photos uploaded to a checklist will not appear in the attachments section on jobs or estimates. Plan your review process accordingly by navigating to the relevant checklist to access the stored photos. This keeps your audit trail precise and aligned with the specific items completed by your technicians.

The "Use inspections in work orders - Dynamics 365 Field Service | Microsoft Learn" documentation assigns specific responsibilities to three distinct roles. The Field Service-Administrator role holds the permission to create inspection setups and associate them with service task types, according to Microsoft. This setup step separates inspection design from daily dispatch operations. An administrator defines what gets inspected before any technician sees it. You must map this creation duty to a user who understands your service task categories.

Dispatchers handle the operational layer of inspection assignment. The Field Service-Dispatcher role is documented as the one that adds service tasks with inspections to work orders. A dispatcher does not build the inspection setup; they attach the pre-built inspection to a specific job during scheduling or dispatch. This distinction matters for small teams where one person might wear both hats. In practice, you need to verify which user account holds the Dispatcher role or the Administrator role. If your dispatch software allows custom role combinations, ensure the user can perform the task-addition action without accidentally triggering inspection setup creation. Check your system configuration to confirm the Field Service-Dispatcher role is assigned to the right staff.

Technicians access inspections through the Field Service-Resource role. This role allows users to view work orders they are assigned to, along with the work order service tasks and the related inspections. The resource does not create or assign these items; they see them on their assigned jobs. This viewing permission ensures the field worker has the checklist data needed to complete the job. You should test this visibility by assigning a sample work order to a resource account and confirming the inspection loads correctly. For how repeat visits are scheduled, see technician scheduling tools for repeat visits.

Identify whether your next software setup task needs a stock quantity control, an inspection permission or a checklist evidence location, then locate that documented setting in your existing tool. If you are preparing to record materials on a work order, check the inventory settings first. Adding serial numbers sets the transaction quantity to the number of serials, as described above. This specific behavior applies when managing serial items within Stock Settings. Do not assume this automatic calculation applies to every item type or business context. Instead, verify how your current system handles similar serial entries before relying on it for dispatch handoffs. For a dispatch checklist, see Field Service Work Order Checklist for Dispatch Handoffs.

If your task involves assigning field observations or verifying equipment conditions, focus on role-based permissions rather than material counts. The documentation distinguishes who can create inspections from who can view them. Match each setup responsibility to its documented role to avoid configuration errors. You do not need to guess which team member should hold these rights. Today, sort your setup tasks into administrative and technician-facing actions, then check each one against the role named above.

Related guides: Service invoice software: 4 tools for field job handoffs · Job costing setup for field service: 5 key settings · Low stock alert settings for field service: 3 platforms.

Which field service software documents stock controls and job forms?

Frappe, Odoo, Microsoft and Housecall Pro each document a stock control or job form feature. Frappe details specific quantity restrictions within its stock settings. Odoo describes reordering rule configurations for inventory replenishment. Microsoft outlines role-based permissions for creating inspection setups and for viewing inspections on work orders. Housecall Pro explains how checklist photos are stored separately from job attachments.

Does Frappe's negative-stock restriction apply to serial and batch items in version fifteen?

Yes, from version 15 users cannot make negative stock transactions for serial or batch items, even when Allow Negative Stock is enabled in the Stock Settings. Frappe specifies this limitation for those item types.

What minimum and maximum values does Odoo's documented reordering example use?

The documented example sets the Min field and Max field to 0.00 within a 0/0/1 reordering rule that uses the Buy route. Odoo presents these figures as one example configuration, not a universal recommendation for every service truck.

Who can create, assign and view Microsoft Field Service inspections?

The Field Service-Administrator role creates inspection setups and associates them with service task types, the Field Service-Dispatcher role adds service tasks with inspections to work orders, and the Field Service-Resource role views assigned work orders and their inspections. Microsoft defines these roles.

Where does Housecall Pro store photos uploaded to a checklist?

Photos uploaded to a checklist are stored and viewed on the checklist itself, not in the attachments section on jobs or estimates. Housecall Pro clarifies this storage location to prevent confusion between checklist evidence and general job files. Keep checklist photos separate from standard job attachments when organizing your digital records.