Skip to main content

Sell field services.

Project description

Beta License: AGPL-3 OCA/field-service Translate me on Weblate Try me on Runboat

The module integrates the Field Service application with the Sales one and allows you to sell products that generate field service orders.

Table of contents

Installation

To install Field Service and have the mapping features, you need to install GeoEngine.

Please refer to the installation instructions available at: https://github.com/OCA/geospatial/tree/13.0/base_geoengine

Configuration

Products must be configured properly in order to create field service orders upon sale order confirmation.

The field service tracking of a product defines how it generates a field service order if the product is sold via sale order.

To configure a product that generates a unique field service order on each sale order line:

  • Go to Sales > Catalog > Products

  • Create or select a product

  • Set the Field Service Tracking to ‘One FSM Order per Sale Order Line’

  • Select the FSM Order Template that will be used for creating FSM Orders when a Sale Order is confirmed with this product

To configure a product that generates a unique field service order for an individual sale order:

  • Go to Sales > Catalog > Products

  • Create or select a product

  • Set the Field Service Tracking to ‘One FSM Order per Sale Order’

  • Select the FSM Order Template that will be used for creating FSM Orders when a Sale Order is confirmed with this product

To setup a sales territory:

  • Go to Field Service > Master Data > Locations

  • Create or select a location

  • Go to the Sales tab and select the sales territory

Usage

  • Go to Sales

  • Create a new Quotation/Sale Order

  • Set the FSM Location to be used

  • On a Sale Order Line, select a product configured for field service orders

  • Confirm the Sale Order

  • Field Service orders linked to SO lines are created

  • When a Field Service order is completed, the quantity delivered for its
    linked sale order line will be updated to the quantity ordered, indicating this line is ready for invoicing.

Known issues / Roadmap

  • Provide a mapping between an address and the branch and use it to set the pricelist of a new partner

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Open Source Integrators

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

Current maintainers:

wolfhall max3903 brian10048

This module is part of the OCA/field-service project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

File details

Details for the file odoo_addon_fieldservice_sale-18.0.1.0.0.3-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_fieldservice_sale-18.0.1.0.0.3-py3-none-any.whl
Algorithm Hash digest
SHA256 5298857100cc6aa2666029afb016403a0c05f80f3ddb273d7fa2e3afca14edae
MD5 3438c15cd02d3d5c52bd275a0459b3ef
BLAKE2b-256 156de2d72f5e22e7eff349067d740893e533d5d5fec1b97db5ef78f13116a17f

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page