Inventory Support Records

Retrieval metadata

feature_group: "Inventory"
record_count: 6
approx_page_tokens: 5177
recommended_chunking: one Knowledge Record section per vector chunk

Feature group overview

This page contains chatbot training records for Inventory sub-features. Retrieve one ### Knowledge Record: chunk at a time when possible.

This section contains chatbot training records for Inventory sub-features.

Knowledge Record: Inventory / Services, services are visible in a table view (Name, Barcode, Description, C...

record_id: LFS-inventory-services-services-are-visible-in-a-table-view-name-barcode-description-c

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync
permissions_visibility

Sample user utterances

How do I set up Services, services are visible in a table view (Name, Barcode, Description, C in Lexul?
When should we use Services, services are visible in a table view (Name, Barcode, Description, C?
Why is Services, services are visible in a table view (Name, Barcode, Description, C not working or not showing?
Can Lexul handle Services, services are visible in a table view (Name, Barcode, Description, C for our workflow?

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
item_name
warehouse
unit_of_measure
barcode
quantity

Services are the billable/non-billable labor or service catalog items users add to work orders and invoices. Use it when users need consistent service selection, pricing, quoting, or invoice line items. Before giving exact setup steps, confirm: Is this item a service, non-inventory item, or labor type? Does it come from QuickBooks. Then explain the recommended configuration, test with a sample record, and note this guardrail: For QBO/QBD-connected workspaces, services/items are commonly synced from QuickBooks; verify source of truth.

Configure when

users need consistent service selection, pricing, quoting, or invoice line items.

Ask before answering

Is this item a service, non-inventory item, or labor type? Does it come from QuickBooks?

Dependencies

QuickBooks version confirmed
integration settings checked
source-of-truth rules defined
items/services
warehouses
units of measure
inventory permissions

Role workflow

Warehouse/office maintains items and stock; technicians consume/scan items; accounting reviews valuation/sync impacts.

Permissions and visibility

Use warehouse and inventory permissions; restrict counts, transfers, POs, and valuation-sensitive actions to appropriate users.

Known limits and guardrails

For QBO/QBD-connected workspaces, services/items are commonly synced from QuickBooks; verify source of truth.

Escalation rule

Escalate if data is missing after sync, accounting source-of-truth is unclear, or the user asks for accounting treatment. Escalate inventory valuation, historical correction, negative quantity, and warehouse-permission problems.

Source URLs

Default response pattern

For questions about Services, services are visible in a table view (Name, Barcode, Description, C..., first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Inventory / Parts, parts are visible in a table view (Name, Barcode, Description, Part Nu...

record_id: LFS-inventory-parts-parts-are-visible-in-a-table-view-name-barcode-description-part-nu

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync
permissions_visibility

Sample user utterances

How do I set up Parts, parts are visible in a table view (Name, Barcode, Description, Part Nu in Lexul?
When should we use Parts, parts are visible in a table view (Name, Barcode, Description, Part Nu?
Why is Parts, parts are visible in a table view (Name, Barcode, Description, Part Nu not working or not showing?
Can Lexul handle Parts, parts are visible in a table view (Name, Barcode, Description, Part Nu for our workflow?

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
item_name
warehouse
unit_of_measure
barcode
quantity

Approved answer basis

Parts are catalog items/materials technicians or office staff add to work orders and invoices. Use it when jobs consume materials, need itemized billing, barcode lookup, inventory tracking, or job costing. Before giving exact setup steps, confirm: Is this part inventory-tracked, non-inventory, serialized, or unit-of-measure based. Then explain the recommended configuration, test with a sample record, and note this guardrail: If inventory tracking is enabled, confirm warehouse, quantity, costing method, and QuickBooks behavior before answering.

Configure when

jobs consume materials, need itemized billing, barcode lookup, inventory tracking, or job costing.

Ask before answering

Is this part inventory-tracked, non-inventory, serialized, or unit-of-measure based?

Dependencies

QuickBooks version confirmed
integration settings checked
source-of-truth rules defined
items/services
warehouses
units of measure
inventory permissions

Role workflow

Warehouse/office maintains items and stock; technicians consume/scan items; accounting reviews valuation/sync impacts.

Permissions and visibility

Use warehouse and inventory permissions; restrict counts, transfers, POs, and valuation-sensitive actions to appropriate users.

Known limits and guardrails

If inventory tracking is enabled, confirm warehouse, quantity, costing method, and QuickBooks behavior before answering.

Escalation rule

Source URLs

Default response pattern

For questions about Parts, parts are visible in a table view (Name, Barcode, Description, Part Nu..., first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Inventory / Warehouses

record_id: LFS-inventory-warehouses

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync

Sample user utterances

How do I set up Warehouses in Lexul?
When should we use Warehouses?
Why is Warehouses not working or not showing?
Can Lexul handle Warehouses for our workflow?

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
item_name
warehouse
unit_of_measure
barcode
quantity

Approved answer basis

Warehouses represent stock locations such as main warehouse, service vans, job sites, or storage areas. Use it when the business needs location-specific inventory visibility, truck stock, transfers, or permission-based counts. Before giving exact setup steps, confirm: Which physical locations need separate quantities? Should technicians have warehouse permissions. Then explain the recommended configuration, test with a sample record, and note this guardrail: QBO does not natively split inventory quantity by warehouse; Lexul is used to manage field-focused quantities.

Configure when

the business needs location-specific inventory visibility, truck stock, transfers, or permission-based counts.

Ask before answering

Which physical locations need separate quantities? Should technicians have warehouse permissions?

Dependencies

QuickBooks version confirmed
integration settings checked
source-of-truth rules defined
items/services
warehouses
units of measure
inventory permissions

Role workflow

Warehouse/office maintains items and stock; technicians consume/scan items; accounting reviews valuation/sync impacts.

Permissions and visibility

Use warehouse and inventory permissions; restrict counts, transfers, POs, and valuation-sensitive actions to appropriate users.

Known limits and guardrails

QBO does not natively split inventory quantity by warehouse; Lexul is used to manage field-focused quantities.

Escalation rule

Source URLs

Default response pattern

For questions about Warehouses, first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Inventory / Purchase Orders, purchase orders are visible in a table view (PO, Created Dat...

record_id: LFS-inventory-purchase-orders-purchase-orders-are-visible-in-a-table-view-po-created-dat

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync
permissions_visibility

Sample user utterances

How do I set up Purchase Orders, purchase orders are visible in a table view (PO, Created Dat in Lexul?
When should we use Purchase Orders, purchase orders are visible in a table view (PO, Created Dat?
Why is Purchase Orders, purchase orders are visible in a table view (PO, Created Dat not working or not showing?
Can Lexul handle Purchase Orders, purchase orders are visible in a table view (PO, Created Dat for our workflow?

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
item_name
warehouse
unit_of_measure
barcode
quantity

Approved answer basis

Purchase orders support receiving inventory and supplier purchasing workflows. Use it when items are ordered from vendors and received into one or more warehouses. Before giving exact setup steps, confirm: Is receiving by quantity, serial number, expiry/lot, or serial+expiry? Which warehouse receives the stock. Then explain the recommended configuration, test with a sample record, and note this guardrail: Confirm whether QBO is source of purchasing records and how inventory value will be accounted for.

Configure when

items are ordered from vendors and received into one or more warehouses.

Ask before answering

Is receiving by quantity, serial number, expiry/lot, or serial+expiry? Which warehouse receives the stock?

Dependencies

QuickBooks version confirmed
integration settings checked
source-of-truth rules defined
items/services
warehouses
units of measure
inventory permissions

Role workflow

Warehouse/office maintains items and stock; technicians consume/scan items; accounting reviews valuation/sync impacts.

Permissions and visibility

Use warehouse and inventory permissions; restrict counts, transfers, POs, and valuation-sensitive actions to appropriate users.

Known limits and guardrails

Confirm whether QBO is source of purchasing records and how inventory value will be accounted for.

Escalation rule

Source URLs

Default response pattern

For questions about Purchase Orders, purchase orders are visible in a table view (PO, Created Dat..., first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Inventory / Transfer Orders, transfer orders are visible in a table view (Number, Status,...

record_id: LFS-inventory-transfer-orders-transfer-orders-are-visible-in-a-table-view-number-status

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync
permissions_visibility

Sample user utterances

How do I set up Transfer Orders, transfer orders are visible in a table view (Number, Status, in Lexul?
When should we use Transfer Orders, transfer orders are visible in a table view (Number, Status,?
Why is Transfer Orders, transfer orders are visible in a table view (Number, Status, not working or not showing?
Can Lexul handle Transfer Orders, transfer orders are visible in a table view (Number, Status, for our workflow?

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
item_name
warehouse
unit_of_measure
barcode
quantity

Approved answer basis

Transfer orders move inventory between warehouses, vans, job sites, or other stock locations. Use it when parts need to be moved from main warehouse to truck, between techs, or back to stock. Before giving exact setup steps, confirm: What source warehouse, destination warehouse, item, quantity, and approval workflow are required. Then explain the recommended configuration, test with a sample record, and note this guardrail: Transfers should preserve operational quantities; confirm accounting treatment if inventory valuation is synchronized.

Configure when

parts need to be moved from main warehouse to truck, between techs, or back to stock.

Ask before answering

What source warehouse, destination warehouse, item, quantity, and approval workflow are required?

Dependencies

QuickBooks version confirmed
integration settings checked
source-of-truth rules defined
items/services
warehouses
units of measure
inventory permissions

Role workflow

Warehouse/office maintains items and stock; technicians consume/scan items; accounting reviews valuation/sync impacts.

Permissions and visibility

Use warehouse and inventory permissions; restrict counts, transfers, POs, and valuation-sensitive actions to appropriate users.

Known limits and guardrails

Transfers should preserve operational quantities; confirm accounting treatment if inventory valuation is synchronized.

Escalation rule

Source URLs

Default response pattern

For questions about Transfer Orders, transfer orders are visible in a table view (Number, Status,..., first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Inventory / Reports, reports are visible in a table view (Inventory Report Schema, Create...

record_id: LFS-inventory-reports-reports-are-visible-in-a-table-view-inventory-report-schema-create

primary_intents:

how_to_setup
when_to_use
workflow_design
troubleshooting
quickbooks_sync
permissions_visibility
export_report

Sample user utterances

How do I set up Reports, reports are visible in a table view (Inventory Report Schema, Create in Lexul?
When should we use Reports, reports are visible in a table view (Inventory Report Schema, Create?
Why is Reports, reports are visible in a table view (Inventory Report Schema, Create not working or not showing?
Can Lexul handle Reports, reports are visible in a table view (Inventory Report Schema, Create for our workflow?

Entities to extract

user_role
workspace
feature_area
quickbooks_version
sync_status
source_of_truth
item_name
warehouse
unit_of_measure
barcode
quantity

Approved answer basis

Inventory reports provide operational visibility into stock quantities, valuation, counts, and actions. Use it when managers need to audit inventory, run counts, reconcile warehouses, or understand usage. Before giving exact setup steps, confirm: Which report schema is needed: quantity, value, warehouse, item, serial/lot, or count variance. Then explain the recommended configuration, test with a sample record, and note this guardrail: If a specific report is not documented publicly, document internal fields and escalate report customization requests.

Configure when

managers need to audit inventory, run counts, reconcile warehouses, or understand usage.

Ask before answering

Which report schema is needed: quantity, value, warehouse, item, serial/lot, or count variance?

Dependencies

QuickBooks version confirmed
integration settings checked
source-of-truth rules defined
items/services
warehouses
units of measure
inventory permissions

Role workflow

Warehouse/office maintains items and stock; technicians consume/scan items; accounting reviews valuation/sync impacts.

Permissions and visibility

Use warehouse and inventory permissions; restrict counts, transfers, POs, and valuation-sensitive actions to appropriate users.

Known limits and guardrails

If a specific report is not documented publicly, document internal fields and escalate report customization requests.

Escalation rule

Escalate inventory valuation, historical correction, negative quantity, and warehouse-permission problems.

Source URLs

Default response pattern

For questions about Reports, reports are visible in a table view (Inventory Report Schema, Create..., first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Inventory Support Records

On this page