ServiceTitan pricebook items can be brought into Acumatica as new items or mapped manually to existing items. The Biz-Tech Services ServiceTitan Acumatica Connector documents both paths. Its Inventory area can load Materials, Equipment, and Services for review; its item-generation option uses the selected stock item class, non-stock item class, and unit of measure. The current product page also describes a Pricebook view that shows the ServiceTitan item code, name, unit of measure, price, and item type.
Those facts establish a review workflow, but not an automatic code-matching formula. Neither the supplied workflow document nor the product page names an alias table, a duplicate-code rule, or the exact field used to pair a ServiceTitan code with an Acumatica Inventory ID.
Start With the ServiceTitan Store Inventory Settings
The ServiceTitan Store governs item handling alongside invoice imports, warehouse mapping, and inventory transactions. Configure and test the store connection before loading item data. The Biz-Tech Services Acumatica ServiceTitan Connector provides Test Credentials for the connection settings; a successful test confirms access to the ServiceTitan store, not the correctness of an item map.
In the Inventory area, selecting Import Item makes Generate Item from ServiceTitan available. The manual also says ServiceTitan items can be mapped manually to Acumatica items instead of being created. Use Load Materials, Equipment, Services to display the source items on the Inventory tab, then review what each row should become before importing transactions against it.
The product page adds a dedicated Pricebook view with item code, name, unit of measure, price, and item type. It does not publish a screen ID or describe which of these values acts as the match key. Treat the code as an identifier to inspect and reconcile, not as a confirmed automatic Inventory ID mapping rule.
Pricebook Item Mapping at a Glance
The Biz-Tech Services ServiceTitan Acumatica Integration supports this practical sequence:
Test the ServiceTitan Store connection and confirm that the intended store is selected.
Load Materials, Equipment, and Services and compare the loaded rows with the Pricebook view’s code, name, unit of measure, price, and type.
For each source item, choose an existing Acumatica item for manual mapping or approve creation of a new one.
For generated items, review Stock Item Class, Non-Stock Item Class, and Unit of Measure before using Generate Item from ServiceTitan.
Test a small invoice or inventory transaction and inspect the Acumatica item and related warehouse before widening the import scope.
The first four controls are documented. The last step is a validation recommendation: the source describes invoice and inventory imports but provides no formal item-map test procedure.
Choose an Existing Inventory Item or Generate a New One
Manual mapping is the documented path when the Acumatica item already exists. Review its Inventory ID and business meaning against the loaded ServiceTitan row. A matching name alone is a weak basis for approval; the available Pricebook code, type, unit of measure, and price give reviewers more context, though the sources do not say which values the connector itself compares.
For a new Acumatica item, the manual says Materials and Equipment generate stock items, while Service generates non-stock items. Generate Item from ServiceTitan uses the Stock Item Class, Non-Stock Item Class, and Unit of Measure values in the store configuration. Approve those defaults before creation. An incorrect class or unit can make a newly created item unsuitable for the transactions that follow.
Keep a record of the owner who approved each creation or manual link. The sources do not describe a built-in approval queue. This is a project control for avoiding duplicate item masters, not a product feature claimed by the documentation.
Cross-References, Aliases, and Unmapped Records
The Biz-Tech Services Acumatica ServiceTitan Integration documentation confirms manual mapping but does not show an item cross-reference table or an alias field. The current product page says the Pricebook view preserves cross-system identifiers, yet it does not explain how multiple codes, renamed items, or duplicate codes are resolved.
List ambiguous rows before enabling broad item creation or transaction imports. For each one, record the ServiceTitan code and name, the intended Acumatica Inventory ID, the unit and type, and the person who decided the link. If a code has no safe match, leave the disposition open until a controlled test establishes what the connector does. No item-specific error text or unmapped-item queue is provided in the source.
Warehouse and truck IDs are a separate map on the ServiceTitan Store. Load Warehouses retrieves those values so they can be paired with Acumatica warehouses. A correct item link does not substitute for that location mapping when receipts, transfers, adjustments, or returns are imported.
Validate the Link With a Small Import
A loaded row is only the beginning of validation. Choose a small set that includes a Material, Equipment item, and Service line, plus one item that was mapped manually. Inspect the generated or linked Acumatica records, including item type, class, and unit of measure. Then process a representative transaction and confirm it uses the intended item.
For invoice imports, the Import SO Invoices screen retrieves ServiceTitan invoices by updated date and selected status, and creates them in Acumatica’s Invoices and Memos screen. For inventory movements, the manual lists receipts, transfers, adjustments, and returns, each with its own release-after-import choice. If a transaction looks wrong, first separate item choice from warehouse and release settings; these controls live in different parts of the store setup.
The supplied guide does not provide a field-by-field pricebook-to-invoice-line map or an item-specific validation message. Save a test result that shows the source code, chosen Inventory ID, resulting document line, and any observed exception. That gives the team evidence for a mapping decision without implying an undocumented rule.
Where to Check Your Work
The Biz-Tech Services ServiceTitan Acumatica Integrator exposes the documented controls in these locations:
ServiceTitan Store and Connection Settings: confirm store selection and Test Credentials result.
Inventory area: review Import Item, Generate Item from ServiceTitan, Stock Item Class, Non-Stock Item Class, and Unit of Measure.
Inventory tab: inspect the rows retrieved by Load Materials, Equipment, Services and the manually chosen item relationships.
Pricebook view: compare the published item code, name, unit of measure, price, and item type with the approved item decision.
Warehouses mapping: check ServiceTitan Warehouse and Truck IDs against Acumatica warehouses before testing inventory movements.
Import SO Invoices and Invoices and Memos: review a sample imported invoice and its item lines.
Inventory Transactions tab: check receipt, transfer, adjustment, and return settings, including release-after-import choices.
ServiceTitan Pricebook Mapping: Frequently Asked Questions
Does the connector require new Acumatica items for every ServiceTitan item?
No. The workflow document says users can manually map ServiceTitan items to existing Acumatica items instead of generating new records.
Which ServiceTitan types generate stock items?
Materials and Equipment generate stock items; Service generates non-stock items. The selected item classes and unit of measure are inputs to generation.
Is the ServiceTitan item code automatically the Acumatica Inventory ID?
The product page says the Pricebook view shows ServiceTitan item code, but neither source specifies that the code becomes Inventory ID or defines the match formula. Verify the relationship in the installed connector.
Can one ServiceTitan item use multiple aliases?
The supplied sources do not document an alias field or multiple-code precedence. Record the requirement and test it before relying on it.
Where is an unmapped-item error shown?
No item-specific error message or exception queue is named. Review the loaded inventory rows and resulting test document; capture any actual message from your configuration.
Why might a mapped item still fail in an inventory transaction?
Check the separate ServiceTitan Warehouse or Truck ID mapping and the transaction settings. The documentation requires the related purchase order before a purchase receipt or bill can be imported.
Approve the Map Before Scaling Imports
The documented choice is straightforward: link each loaded ServiceTitan item to an existing Acumatica item or generate a new stock or non-stock record using reviewed class and unit settings. The Pricebook view helps reviewers compare catalog identifiers and attributes. Duplicate-code, alias, and unmatched-item behavior still need an agreed test result because the sources leave them unspecified.
For help reviewing ServiceTitan item mappings and testing sample imports, contact the Biz-Tech Services Acumatica ServiceTitan Integrator team at https://biz-techservices.com.
Sources: Biz-Tech Services, Service Titan – Acumatica Integration workflow document, Inventory and Import SO Invoices sections; and ServiceTitan Integration product page, https://biz-techservices.com/servicetitan-integration (accessed October 26, 2026).
