Delivery Tickets

The delivery ticket is basically a shipping manifest from the warehouse (back office) to the site where the work takes place (mobile). You can’t create Delivery tickets in FieldFX Mobile App, only field tickets and return tickets.

FieldFX Mobile App FieldFX Back Office

Environment

The FieldFX Mobile App is designed for field operations where connectivity may be limited. It allows users to:

  • Receive and confirm deliveries

  • Add ticket items and quantities

  • Attach photos or documents

  • Capture customer signatures

The Back Office environment is typically used by operations managers and office staff for planning and resource allocation. Common tasks include:

  • Creating delivery tickets before items are shipped.

  • Managing inventory and job resource assignments.

  • Reviewing and approving delivery ticket details.

Additional Features:

  • Supports offline mode and syncs with the back office when online.

  • Ideal for marking items as delivered and updating job resources in real time.

  • Provides full visibility into job inventory and delivery history.

When to use

For field personnel confirming deliveries and updating job resources on-site.

For pre-delivery setup, scheduling, and administrative oversight.

  • The Job Inventory module, introduced in FX25R1 and FX25R2, integrates delivery tickets with job resources.

  • Delivery tickets are essential for tracking inventory movement and updating job resource statuses.

Delivery Ticket Behavior and Job Resources

The FieldFX Mobile App respects the server-side rules introduced in FX25R1 for Delivery Tickets and Job Resources.

Some delivery tickets may not have automatically added items from pricing or required-item rules. This happens when the ticket was created from job resources (using Create Delivery Ticket or a similar action). In those cases, only items that were added by users appear on the ticket.

Automatic updates from Delivery Tickets

When users create or receive Delivery Tickets (from web or mobile), FieldFX automatically updates related Job Resource quantities and status.

Delivery Ticket Status Result

Created

For each Delivery Ticket Item, FieldFX updates the related Job Resource "Qty Shipped" with the Delivery Ticket Item quantity.

Received

A Delivery Ticket is considered received when its status is set to a status where Mark Delivery Ticket as Received is enabled.

For each Delivery Ticket Item, FieldFX:

  • Updates the related Job Resource Qty Delivered with the Delivery Ticket Item quantity.

  • Sets the Job Resource Status to On Site (if it is not already set).

These updates occur on the server and are reflected in the mobile app after sync; the mobile client does not need any additional workflow or configuration.

Restrictions on Delivery Ticket items

The same item and quantity rules enforced on the web are also enforced when users work with Delivery Tickets on mobile:

  • Labor and Service items cannot be added to Delivery Tickets. Delivery Tickets are for materials only

  • This also applies to parent–child bundles: labor and service job resources within a bundle are automatically excluded when generating a Delivery Ticket from Job Resources

    • Only items where Shipped Quantity ⇐ Quantity can be added to a Delivery Ticket.

  • This prevents the total shipped quantity from exceeding the quantity required on the Job.

If a user attempts to add an invalid item or exceed the allowed quantity, the mobile app will prevent the Delivery Ticket from being created or updated and will display a validation message from the server.

Using Delivery Tickets with Job Resources (Mobile)

This section explains how Delivery Tickets affect Job Resources when you are working in the FieldFX mobile app. The behavior is consistent with the web application.

How Delivery Tickets change Job Resource quantities

FieldFX automatically keeps Job Resource quantities in sync with your Delivery Tickets.

Delivery Ticket Status Result

Created

When you add items to a Delivery Ticket and save it:

  • The system updates Qty Shipped on each related Job Resource with the Delivery Ticket Item quantity.

You do not need to manually edit Qty Shipped on the Job Resource when you use Delivery Tickets.

Received

When you change a Delivery Ticket to a status where Mark Delivery Ticket as Received is enabled:

  • The system updates Qty Delivered on each related Job Resource with the Delivery Ticket Item quantity.

  • The Job Resource Status is set to On Site (if it is not already).

After the Delivery Ticket is received, you do not need to manually update Qty Delivered or set the Job Resource to On Site for those items.

Allowable and Not Allowable items for a Delivery Ticket (Mobile)

When adding items to a Delivery Ticket from the mobile app, the following rules apply:

Allowable Not Allowable

Material Job Resources where the Shipped Quantity is less than or equal to the Quantity on the Job.

  • This prevents you from shipping more than the required quantity.

  • Labor items.

  • Service items.

If you try to add an item or quantity that violates these rules, the app will block the change and show a validation message.

Example: Quantities through the Delivery Ticket lifecycle

  1. The Job Resource is created with Quantity = 10, Qty Shipped = 0, Qty Delivered = 0, Status = Planned.

  2. You create a Delivery Ticket on mobile and add that Job Resource with a quantity of 4.

    1. After saving and syncing, Qty Shipped = 4.

  3. You or a back office user move the Delivery Ticket to a status where Mark Delivery Ticket as Received = true.

    1. After the next sync, Qty Delivered = 4 in the mobile app.

    2. Job Resource Status = On Site.

This gives both office and mobile users a consistent, accurate view of what has been shipped and delivered to the Job site.

Some delivery tickets that are linked to job resources may not include any automatically added items from pricing rules or required-item logic.

This happens when the ticket was created from job resources using the Create Delivery Ticket button in FieldFX Back Office. In that case, only the items that users add directly appear on the ticket.

Create Delivery Tickets in FieldFX Back Office

Delivery tickets in Back Office are part of the Job Inventory and E-Ticketing workflow. They allow operations managers to plan and move inventory from the warehouse to the job site.

Key Features in Back Office

  • Integration with Job Inventory: Delivery tickets update job resource quantities and statuses.

  • Centralized Management: Operations managers can review, edit, and approve tickets before shipment.

  • Compliance and Billing: Attachments and approvals ensure accurate billing and compliance.

When a job uses parent–child bundles, the Create Delivery Ticket dialog displays only the parent bundle resource for selection. After you create the Delivery Ticket, both the parent and child bundle items appear as ticket items (labor and services job resources are excluded), and each ticket item is linked back to its originating job resource.
Process for Creating Delivery Tickets in Back Office

  1. Navigate to the Job Record

    In FieldFX Back Office, open the job for which you need to create a delivery ticket.

  2. Add a New Ticket

    Click Add Ticket or use the Create Delivery Ticket button available in the job interface.

    This option is typically found in the Tickets related list or the Job Inventory section.

When you create a delivery ticket from job resources using the Create Delivery Ticket button, FieldFX does not run the Rule Engine or Price Book Required Items for that ticket.

This means:

  • No additional ticket items are automatically added based on Rule Engine rules.

  • No Price Book Required Items are automatically added.

If you need extra charges, materials, or other items on these delivery tickets, add them manually.

  1. Add Ticket Item using the FX Item Picker.

    See FXL Item Picker Setup for more information.

    You can:

    • Add items from the Price Book or Quote

    • Enter quantities for each item

    • Use advanced features like Bulk Update, Barcode Scanning, and Stage Pricing for efficiency

  2. Attach Supporting Details

    1. Upload documents, photos, or FX Reports for compliance and tracking.

    2. Ensure all required fields (e.g., job resource references, quantities) are completed.

  3. Save and Dispatch

    1. Save the delivery ticket.

    2. The ticket is available to the field team if needed and syncs with the Mobile App for on-site confirmation.

Generate a Delivery Ticket from a parent–child bundle

When a Job Resource Bundle is configured as a parent–child bundle, the Delivery Ticket generation flow uses the parent as the selection entry, and then includes the child bundle items on the created Delivery Ticket.

Some delivery tickets may not have automatically added items from pricing or required-item rules. This happens when the ticket was created from job resources (using Create Delivery Ticket or a similar action). In those cases, only items that were added by users appear on the ticket.

Behavior

  • In the Create Delivery Ticket dialog, only the parent bundle resource is displayed for selection. Child items are not shown as separate selections in the dialog.

  • When you select the parent and create the ticket, FieldFX automatically generates ticket items for both the parent and all eligible child bundle items.

  • Labor and Service job resources in the bundle are excluded from the generated Delivery Ticket items.

  • Each created ticket item includes a job resource link back to its originating job resource — for both parent and child items.

This behavior applies when generating Delivery Tickets from Job Resources using a parent–child bundle selection.

The quantity of a parent job resource in a bundle is always 1 and cannot be changed.

Bundles must be added as a whole. You cannot split a parent–child bundle across multiple Delivery Tickets — all parent and child items are included on the same ticket.

Status behavior for parent–child bundles

Parent Item Type Status Behavior

Service or Labor

When the parent Job Resource is added to a Job, the parent and all child Job Resources in the bundle are set to On Site immediately, regardless of each child’s item type.

Material, Equipment, or other non-Service/Labor types

The parent Job Resource status is set to the default status (e.g., Planned). Child Job Resources that are Service or Labor are set to On Site. When a Delivery Ticket is created, all material-type items in the bundle change to In Transit.

Best Practices

To ensure accurate inventory tracking and smooth job resource management, follow these best practices when working with delivery tickets in FieldFX:

Validate Ticket Details Before Marking as Received

  • Confirm that all item quantities and descriptions match the actual shipment.

  • Ensure any required attachments (e.g., packing slips, photos) are included.

Use the Correct Platform for Your Role

  • FieldFX Mobile App: Ideal for field personnel confirming deliveries on-site and updating job resources in real time.

  • FieldFX Back Office: Best for pre-delivery setup, scheduling, and administrative oversight.

Keep Quantities Accurate

  • For serialized items, verify each serial number before marking as received.

  • For bulk items, remember that On Site Qty is cumulative (Qty Delivered) — multiple delivery tickets can fulfill the requested quantity.

Update Status Promptly

  • Mark delivery tickets as Received immediately after items arrive on-site to keep job resource statuses current.

  • This ensures accurate reporting and prevents delays in job progress.

Handle Partial Deliveries Correctly

  • For bulk items, mark them as On-Site even if only partially delivered.

  • Document any remaining quantities to avoid confusion later.

Attach Supporting Documentation

  • Include photos, signed receipts, or other proof of delivery for compliance and audit purposes.

Sync Regularly

  • If using the Mobile App offline, sync as soon as connectivity is available to update the back office system

For more information, see:

FieldFX Documentation PTC ServiceMax Help Center Salesforce Documentation

  • n/a

  • n/a