Skip to main content

This module propagates extra step data from eCommerce checkout to FSM orders,

Project description

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

This module ensures that data introduced by customers during the extra step of the eCommerce checkout process is seamlessly propagated from the sale order to the corresponding Field Service Management (FSM) order. It transfers key details such as customer references, messages, and attachments, improving communication between sales and service teams while streamlining workflow efficiency.

Table of contents

Usage

1. Enable e-commerce’s extra step - Navigate to Website > Go To Website > Cart Icon > Customize > Enable ‘Extra Step Option’.

2. Configure Portal User: - Navigate to the Contacts module. - Create or edit a contact. - In the Action tab, execute the Convert to FSM Record option, select the Location record type. - Grant portal access to this contact. - Save the contact.

3. Configure FSM Location - Navigate to the Field Service module. - Under Master Data > Locations, edit the created location. - Assign a route to the location. Ensure the route has a person assigned to it and days of the week are specified. Adjust the route’s maximum capacity as desired. - Save the location.

4. Configure FSM Delivery Time Ranges - Navigate to the Field Service module. - Under Master Data > Delivery Time Ranges, create delivery time ranges. - When the Route field is specified, the delivery time range is used on the related route only. When the Route field is empty, the delivery time range is used on all routes. - Save the delivery time ranges.

5. Configure Field Service Products: - Navigate to the Field Service module. - Under Master Data > Products, create or edit a product. - In the Sales tab, enable the Create one FSM order per sale order option. - Save the product.

6. Create a Sale Order from the E-Commerce: - Log in to the e-commerce portal using the portal user created earlier. - Navigate to the shop and select a field service product. - Add the product to the cart and proceed to checkout. - At the Extra Info step, add the information. - Complete the checkout process. To confirm the sale order, if specified in the configuration, the signature and payment must be completed.

7. Validate the process: - Navigate to the Sales module. - Under Orders, you will see the new sale order created and confirmed. - This sale order will be linked to an FSM order, which will contain the extra step information from the sale order.

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

  • APSL-Nagarro

Contributors

APSL-Nagarro:

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 maintainer:

ppyczko

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

If you're not sure about the file name format, learn more about wheel file names.

File details

Details for the file odoo_addon_fieldservice_website_sale_extra_step-15.0.1.0.0.3-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_fieldservice_website_sale_extra_step-15.0.1.0.0.3-py3-none-any.whl
Algorithm Hash digest
SHA256 67712659fb313c01b0a1fbd890833f0c6a7f4fa2750876296c0a3555d16455dd
MD5 20e73fe1c7624b73d3182eccc7b077af
BLAKE2b-256 44da167dce626808d6cbcc93965666e957e9e9a63d5fbb08604d7dd0a748484a

See more details on using hashes here.

Supported by

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