Service Resources are records that represent the people or equipment that perform field service tasks[143].
Work Orders are records that track customer requests for service such as repairs or maintenance[144].
Resource Absences are records that mark resources as unavailable for work for specific time periods due to sickness, vacation, or other reasons[145]. If the Field Service Lightning User Territory feature is enabled, these three objects will be visible to users who are part of the User Territory by default[146]. Accounts are records that represent companies or individuals involved in business with an organization[147]. Work Types are records that define the standard tasks and duration for a specific type of work[148]. These two objects will not be visible to users who are part of the User Territory by default unless sharing rules are configured[149].
References: https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_work_orders.htm&type=5 https://help.salesforce.com/s
/articleView?id=sf.fs_resource_absences_overview.htm&type=5 https://help.salesforce.com/s/articleView?
id=sf.fs_user_territories_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.account.
htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_types_overview.
htm&type=5https://help.salesforce.com/s/articleView?id=sf.fs_user_territories_sharing_rules.htm&type=5

This object can be used to share service appointments with service resources in Salesforce Field Service by assigning service resources to service territories and assigning service appointments to the same service territories. References:https://help.salesforce.com/s/articleView?id=sf.fs_service_territories.htm&type=5

Service Reports aredocuments that summarize the details and outcomes of a service appointment such as work performed, products consumed, customer feedback, etc.[72]. Using the standard Service Report would allow Field Service Technicians to capture details and customer approval on completed work and send them to the customer electronically by generating and emailing service reports from the Field Service Mobile App or the web browser[73]. Creating a Process Builder to generate a report would not allow Field Service Technicians to capture details and customer approval on completed work. Process Builder is a tool that allows users to automate workflows based on specified criteria and actions[74]. Creating a custom report would not allow Field Service Technicians to capture details and customer approval on completed work. Custom reports are reports that allow users to view data based on specific criteria such as objects, fields, filters, or charts[75].
Using the standard Work Order email template would not allow Field Service Technicians to capture details and customer approval on completed work. Email templates are templates that allow users to send predefined emails with merge fields[76]. References: https://help.salesforce.com/s/articleView?id=sf.
fs_service_reports_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.
fs_service_reports_generate.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.process_overview.
htm&type=5 https://help.salesforce.com/s/articleView?id=sf.reports_builder_overview.
htm&type=5https://help.salesforce.com/s/articleView?id=sf.email_templates_overview.htm&type=5

Products consumed are records that track the products used during a service appointment[32]. A custom installation date field on products consumed would allow reporting on the volume of products installed within a specific timeframe by filtering on the installation date field values[33]. A work order related list on asset would show the work orders associated with an asset, but not the products installed. Field history tracking on asset would track field changes on an asset, but not the products installed. The standard installation date field on asset would show when an asset was installed, but not the products installed. References: https://help.
salesforce.com/s/articleView?id=sf.fs_products_consumed.htm&type=5https://help.salesforce.com/s
/articleView?id=sf.reports_filter_date_fields.htm&type=5

A Work Order can have only one Price Book associated with it, which is determined by the Price Book selected on the Work Type. To use products from different Price Books on the same Work Order, the price on Work Order Line Items for products on other Price Books can be overridden manually or by using automation tools such as Process Builder or Apex triggers. Creating one Work Order for each Price Book or using Work Types to assign Price Books to each Work Order Line Item would not allow using products from different Price Books on thesame Work Order. References: https://help.salesforce.com/s/articleView?id=sf.
fs_work_orders.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_types.
htm&type=5https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.htm&type=5