[MERGE] Forward-port of branch 12.0 to 13.0
This commit is contained in:
@@ -17,7 +17,7 @@ Start generating leads
|
||||
==========================
|
||||
You will now have a new button **Generate Leads** available in your pipeline.
|
||||
You are also able to create lead mining requests from the
|
||||
:menuselection:`Configuration --> Lead Mining Requests` and trough
|
||||
:menuselection:`Configuration --> Lead Mining Requests` and through
|
||||
:menuselection:`Leads --> Leads` where you have the **Generate Leads** button.
|
||||
|
||||
.. image:: media/LM2.png
|
||||
|
||||
@@ -3,7 +3,7 @@ Assign leads based on scoring
|
||||
=============================
|
||||
|
||||
With *Leads Scoring* you can automatically rank your leads based on
|
||||
selected criterias.
|
||||
selected criteria.
|
||||
|
||||
For example you could score customers from your country higher or the
|
||||
ones that visited specific pages on your website.
|
||||
@@ -24,7 +24,7 @@ You now have a new tab in your *CRM* app called *Leads Management*
|
||||
where you can manage your scoring rules.
|
||||
|
||||
Here's an example for a Canadian lead, you can modify for whatever
|
||||
criteria you wish to score your leads on. You can add as many criterias
|
||||
criteria you wish to score your leads on. You can add as many criteria
|
||||
as you wish.
|
||||
|
||||
.. image:: media/lead_scoring02.png
|
||||
|
||||
@@ -24,7 +24,7 @@ Configure the Lane/5000 for Ingenico BENELUX
|
||||
Click on the F button of the terminal, then go in the
|
||||
:menuselection:`PoS Menu --> Settings` and enter the settings password.
|
||||
|
||||
Now, click on connexion change and TCP/IP. Type the IP of your *IoT
|
||||
Now, click on connection change and TCP/IP. Type the IP of your *IoT
|
||||
Box* (you can find it on the form view of your IoT Box). Then, enter
|
||||
9000 as port. The terminal will restart. Once it is done, go on your
|
||||
*IoT Box* form in Odoo and verify that the terminal has been found.
|
||||
@@ -66,12 +66,12 @@ still retry to send the payment request.
|
||||
|
||||
If there is any issue with the payment terminal, you can still force the
|
||||
payment using the *Force Done*. This will allow you to validate the
|
||||
order in Odoo even if the connexion between the terminal and Odoo has
|
||||
order in Odoo even if the connection between the terminal and Odoo has
|
||||
issues.
|
||||
|
||||
.. note::
|
||||
This option will only be available if you received an error message
|
||||
telling you the connexion failed.
|
||||
telling you the connection failed.
|
||||
|
||||
Once your payment is processed, on the payment record, you’ll find the
|
||||
type of card that has been used and the transaction ID.
|
||||
|
||||
@@ -50,5 +50,5 @@ Successful*. You can always reverse the last transaction by clicking on
|
||||
|
||||
If there is any issue with the payment terminal, you can still force the
|
||||
payment using the *Force Done*. This will allow you to validate the
|
||||
order in Odoo even if the connexion between the terminal and Odoo
|
||||
order in Odoo even if the connection between the terminal and Odoo
|
||||
encounters issues.
|
||||
|
||||
@@ -24,7 +24,7 @@ Listing with variations
|
||||
=======================
|
||||
|
||||
When the **use eBay** on a product with variations is checked and with **Fixed
|
||||
Price** as **Listing Type**, the eBay form is sligthly different. In the
|
||||
Price** as **Listing Type**, the eBay form is slightly different. In the
|
||||
variants array, you can choose which variant will be listed on eBay as well as
|
||||
set the price and the quantity for each variant.
|
||||
|
||||
@@ -47,4 +47,4 @@ Products identifiers such as EAN, UPC, Brand or MPN are required in most of the
|
||||
The module manages the EAN and UPC identifiers with the **Barcode** field of the product variant.
|
||||
If the **Barcode** field is empty or is value is not valid, the EAN and UPC values will be set as 'Does not apply' as recommended by eBay.
|
||||
The Brand and MPN values are working as item specifics and should be define in the **Variants** tab on the product form.
|
||||
If theses values are not set, 'Does not apply' will be used for the eBay listing.
|
||||
If these values are not set, 'Does not apply' will be used for the eBay listing.
|
||||
|
||||
@@ -42,7 +42,7 @@ Using the updated synchronisation method
|
||||
If you have a lot of products, the eBay API can sometimes refuse some synchronization
|
||||
calls due to a time-based limit on the number of requests that eBay enforces.
|
||||
|
||||
To fix this issue, a new implementation mechanism has been developped; however this
|
||||
To fix this issue, a new implementation mechanism has been developed; however this
|
||||
updated mechanism is disabled by default to avoid having the 2 systems running in
|
||||
parallel in existing installations.
|
||||
|
||||
|
||||
@@ -66,12 +66,12 @@ Prices per minimum quantity
|
||||
Discounts, margins, roundings
|
||||
=============================
|
||||
|
||||
*Advanced pricing based on formula* allows to set price change rules.
|
||||
Changes can be relative to the product list/catalog price, the product cost price,
|
||||
or to another pricelist. Changes are calculated via discounts or surcharges and can be
|
||||
forced to fit within floor (minumum margin) and ceilings (maximum margins).
|
||||
Prices can be rounded to the nearest cent/dollar or multiple of either
|
||||
(nearest 5 cents, nearest 10 dollars).
|
||||
*Advanced pricing based on formula* allows to set price change rules.
|
||||
Changes can be relative to the product list/catalog price, the product cost price,
|
||||
or to another pricelist. Changes are calculated via discounts or surcharges and can be
|
||||
forced to fit within floor (minimum margin) and ceilings (maximum margins).
|
||||
Prices can be rounded to the nearest cent/dollar or multiple of either
|
||||
(nearest 5 cents, nearest 10 dollars).
|
||||
|
||||
Once installed go to
|
||||
:menuselection:`Sales --> Configuration --> Pricelists`
|
||||
|
||||
Reference in New Issue
Block a user