odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/studio/views.md

@@ -0,0 +1,363 @@
+---
+title: "Views"
+source_url: "https://docs.odoo.sbggai.top/applications/studio/views.html"
+---
+
+=====
+# Views
+
+Views are the interface that allows displaying the data contained in a :doc:`model
+<models_modules_apps>`. One model can have several views, which are simply different ways to show
+the same data. In Studio, views are organized into four categories: :ref:`general
+<studio/views/general>`, :ref:`multiple records <studio/views/multiple-records>`, :ref:`timeline
+<studio/views/timeline>`, and :ref:`reporting <studio/views/reporting>`.
+
+> **tip**:
+>    - To change the default view of a model, :ref:`access Studio <studio/access>`, go to
+     :guilabel:`Views`, click the :icon:`fa-ellipsis-v` (:guilabel:`ellipsis`) icon next to the
+     desired view, and click :guilabel:`Set as Default`.
+   - You can modify views using the built-in XML editor: Activate the :ref:`Developer mode
+     <developer-mode>`, go to the view you want to edit, select the :guilabel:`View` tab, and
+     click :guilabel:`</> XML`.
+
+     > **important**:
+>         If you are editing a view using the XML editor, avoid making changes directly to standard
+        and inherited views, as these would be reset and lost during updates or module upgrades.
+        Always make sure you select the right Studio inherited views: When you modify a
+        view in Studio by dragging and dropping a new field, for example, a specific Studio
+        inherited view and its corresponding XPath, which defines the modified part of the view, are
+        automatically generated.
+
+.. _studio/views/general:
+
+# General views
+
+> **note**:
+>    The settings described below are found under the view's :guilabel:`View` tab unless specified
+   otherwise.
+
+.. _studio/views/general/form:
+
+## Form
+
+The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and editing records, such as
+contacts, sales orders, products, etc.
+
+- To structure a form, drag and drop the :guilabel:`Tabs and Columns` element found under the
+  :guilabel:`+ Add` tab.
+- To prevent users from creating, editing, or deleting records, untick :guilabel:`Can Create`,
+  :guilabel:`Can Edit`, or :guilabel:`Can Delete`.
+- To add a button, click :guilabel:`Add a button` at the top of the form, enter a :guilabel:`Label`,
+  and select the button's action:
+
+  - :guilabel:`Run a Server Action`: select the :ref:`server action <reference/actions/server>` to
+    be executed from the dropdown list;
+  - :guilabel:`Call a method`: specify an existing Python method already defined in Odoo.
+
+- To change a button's label or style, click the button and edit its :guilabel:`Label` or
+  :guilabel:`Class` (either `btn-primary` or `btn-secondary`) in the :guilabel:`Properties` tab.
+- To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) icon in the top-right
+  corner of the form. Enter a :guilabel:`Label`, choose an :guilabel:`Icon`, and select a
+  :ref:`related field <studio/fields/relational-fields-related-field>`.
+
+.. example::
+
+   .. image:: views/form-sales-order.png
+      :alt: Sales order model's Form view
+
+.. _studio/views/general/activity:
+
+## Activity
+
+The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and have an overview of
+activities (emails, calls, etc.) linked to records.
+
+> **note**:
+>    This view can only be modified within Studio by editing the XML code.
+
+.. example::
+
+   .. image:: views/activity-lead-opportunity.png
+      :alt: Lead/Opportunity model's Activity view
+
+.. _studio/views/general/search:
+
+## Search
+
+The :guilabel:`Search` :icon:`oi-search` view is added on top of other views to filter, group, and
+search records.
+
+- To add custom :guilabel:`Filters` and structure them using :guilabel:`Separators`, go to the
+  :guilabel:`+ Add` tab and drag and drop them under :guilabel:`Filters`.
+- To add an existing field under the search dropdown menu, go to the :guilabel:`+ Add` tab and
+  drag and drop it under :guilabel:`Autocompletion Fields`.
+
+.. example::
+
+   .. image:: views/search-project-kanban.png
+      :alt: Project model's Search view on the Kanban view
+
+.. _studio/views/multiple-records:
+
+# Multiple records views
+
+> **note**:
+>    The settings described below are found under the view's :guilabel:`View` tab unless specified
+   otherwise.
+
+.. _studio/views/multiple-records/kanban:
+
+## Kanban
+
+The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support business flows by moving
+records across stages or as an alternative way to display records inside *cards*.
+
+> **note**:
+>    If the :guilabel:`Kanban` view exists, it is used by default to display data on mobile devices
+   instead of the :ref:`List view <studio/views/multiple-records/list>`.
+
+- To prevent users from creating new records, untick :guilabel:`Can Create`.
+- To create records directly within the view, in a minimalistic form, enable :guilabel:`Quick
+  Create`.
+- To set a default grouping for records, select a field under :guilabel:`Default Group By`.
+
+.. example::
+
+   .. image:: views/kanban-project.png
+      :alt: Project model's Kanban view
+
+.. _studio/views/multiple-records/list:
+
+## List
+
+The :guilabel:`List` :icon:`oi-view-list` view is used to overview many records at once, look for
+records, and edit simple records.
+
+- To prevent users from creating, editing, or deleting records, untick :guilabel:`Can Create`,
+  :guilabel:`Can Edit`, or :guilabel:`Can Delete`.
+- To create and edit records directly within the view, select either :guilabel:`Add record at the
+  bottom`, :guilabel:`Add record on top` or :guilabel:`Open form view` under
+  :guilabel:`When Creating Record`.
+
+  > **note**:
+>      This prevents users from opening records in :ref:`Form view <studio/views/general/form>` from the
+     :guilabel:`List` view.
+
+- To edit several records at once, tick :guilabel:`Enable Mass Editing`.
+- To change the way records are sorted by default, select a field under :guilabel:`Sort By`.
+- To set a default grouping for records, select a field under :guilabel:`Default Group By`.
+- To add a button, click :guilabel:`Add a button` at the top of the list, enter a :guilabel:`Label`,
+  and select the button's action:
+
+  - :guilabel:`Run a Server Action`: select the :ref:`server action <reference/actions/server>` to
+    be executed from the dropdown list;
+  - :guilabel:`Call a method`: specify an existing Python method already defined in Odoo.
+
+> **tip**:
+>    To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder records manually, add an
+   :ref:`Integer field <studio/fields/simple-fields-integer>` with the :guilabel:`Handle` widget.
+
+   .. image:: views/list-drag-handle.png
+      :alt: Drag handle icon enabling to sort records manually in List view
+
+.. example::
+
+   .. image:: views/list-sales-order.png
+      :alt: Sales order model's List view
+
+.. _studio/views/multiple-records/map:
+
+## Map
+
+The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on a map. For example, it
+is used in the Field Service app to plan an itinerary between different tasks.
+
+> **note**:
+>    A :ref:`Many2One field <studio/fields/relational-fields-many2one>` linked to the *Contact* model
+   is required to activate the view, as the contact address is used to position records on the map.
+
+- To select which kind of contact should be used on the map, select it under :guilabel:`Contact
+  Field`.
+- To hide the name or the address of the record, tick :guilabel:`Hide Name` or :guilabel:`Hide
+  Address`.
+- To add information from other fields, select them under :guilabel:`Additional Fields`.
+- To have a route suggested between the different records, tick :guilabel:`Enable Routing` and
+  select which field should be used to sort records for the routing.
+
+.. example::
+
+   .. image:: views/map-task.png
+      :alt: Task model's Map view
+
+.. _studio/views/timeline:
+
+# Timeline views
+
+> **note**:
+>    - When you first activate one of the timeline views, you need to select which :ref:`Date
+     <studio/fields/simple-fields-date>` or :ref:`Date & Time
+     <studio/fields/simple-fields-date-time>` fields on your model should be used to define when the
+     records start and stop in order to display them on the view. You can modify the
+     :guilabel:`Start Date Field` and :guilabel:`Stop Date Field` after activating the view.
+   - The settings described below are found under the view's :guilabel:`View` tab unless specified
+     otherwise.
+
+.. _studio/views/timeline/calendar:
+
+## Calendar
+
+The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and manage records inside a
+calendar.
+
+- To create records directly within the view instead of opening the :ref:`Form view
+  <studio/views/general/form>`, enable :guilabel:`Quick Create`.
+
+  > **note**:
+>      This only works on specific models that can be *quick-created* using only a *name*. However,
+     most models do not support quick creation and open the :guilabel:`Form` view to fill in the
+     required fields.
+
+- To color records on the calendar, select a field under :guilabel:`Color`. All the records sharing
+  the same value for that field are displayed using the same color.
+
+  > **note**:
+>      As the number of colors is limited, the same color can end up being assigned to different
+     values.
+
+- To display events lasting the whole day at the top of the calendar, select a :ref:`Checkbox field
+  <studio/fields/simple-fields-checkbox>` that specifies if the event lasts the whole day.
+
+- To choose the default time scale used to display events, select :guilabel:`Day`, :guilabel:`Week`,
+  :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Display Mode`.
+
+> **note**:
+>    You can also use a :guilabel:`Delay Field` to display the duration of the event in hours by
+   selecting a :ref:`Decimal <studio/fields/simple-fields-decimal>` or :ref:`Integer
+   <studio/fields/simple-fields-integer>` field on the model which specifies the duration of the
+   event. However, if you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be
+   taken into account.
+
+.. example::
+
+   .. image:: views/calendar-event.png
+      :alt: Calendar Event model's Calendar view
+
+.. _studio/views/timeline/cohort:
+
+## Cohort
+
+The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the life cycle of records over
+a time period. For example, it is used in the Subscriptions app to view the subscriptions' retention
+rate.
+
+- To display a measure (i.e., the aggregated value of a given field) by default on the view, select
+  a :guilabel:`Measure Field`.
+- To choose which time interval is used by default to group results, select :guilabel:`Day`,
+  :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Interval`.
+- To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` :dfn:`the percentage
+  of records staying over a period of time, it starts at 100% and decreases with time` or
+  :guilabel:`Churn` :dfn:`the percentage of records moving out over a period of time - it starts at
+  0% and increases with time`.
+- To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, select either
+  :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` (from -15 to 0). For most purposes,
+  the :guilabel:`Forward` timeline is used.
+
+.. example::
+
+   .. image:: views/cohort-subscription.png
+      :alt: Subscription model's Cohort view
+
+.. _studio/views/timeline/gantt:
+
+## Gantt
+
+The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine the overall progress of
+records. Records are represented by a bar under a time scale.
+
+- To prevent users from creating or editing records, untick :guilabel:`Can Create` or :guilabel:`Can
+  Edit`.
+- To fill cells in gray whenever a record should not be created there (e.g., on weekends for
+  employees), tick :guilabel:`Display Unavailability`.
+
+  > **note**:
+>      The underlying model must support this feature, and support for it cannot be added using
+     Studio. It is supported for the Project, Time Off, Planning, and Manufacturing apps.
+
+- To show a total row at the bottom, tick :guilabel:`Display Total row`.
+- To collapse multiple records in a single row, tick :guilabel:`Collapse First Level`.
+- To choose which way records are grouped by default on rows (e.g., per employee or project), select
+  a field under :guilabel:`Default Group by`.
+- To define a default time scale to view records, select :guilabel:`Day`, :guilabel:`Week`,
+  :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Scale`.
+- To color records on the view, select a field under :guilabel:`Color`. All the records sharing the
+  same value for that field are displayed using the same color.
+
+  > **note**:
+>      As the number of colors is limited, the same color can be assigned to different values.
+
+- To specify with which degree of precision each time scale should be divided by, select
+  :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or :guilabel:`Hour` under :guilabel:`Day
+  Precision`, :guilabel:`Half Day` or :guilabel:`Day` under :guilabel:`Week Precision`, and
+  :guilabel:`Month Precision`.
+
+.. example::
+
+   .. image:: views/gantt-planning.png
+      :alt: Planning Shift model's Gantt view
+
+.. _studio/views/reporting:
+
+# Reporting views
+
+> **note**:
+>    The settings described below are found under the view's :guilabel:`View` tab unless specified
+   otherwise.
+
+.. _studio/views/reporting/pivot:
+
+## Pivot
+
+The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and analyze the data contained
+in records in an interactive manner. It is especially useful to aggregate numeric data, create
+categories, and drill down the data by expanding and collapsing different levels of data.
+
+- To access all records whose data is aggregated under a cell, tick :guilabel:`Access records from
+  cell`.
+- To divide the data into different categories, select field(s) under :guilabel:`Column grouping`,
+  :guilabel:`Row grouping - First level`, or :guilabel:`Row grouping - Second level`.
+- To add different types of data to be measured using the view, select a field under
+  :guilabel:`Measures`.
+- To display a count of records that made up the aggregated data in a cell, tick :guilabel:`Display
+  count`.
+
+.. example::
+
+   .. image:: views/pivot-purchase-report.png
+      :alt: Purchase Report model's Pivot view
+
+.. _studio/views/reporting/graph:
+
+## Graph
+
+The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data from records in a bar,
+line, or pie chart.
+
+- To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` under
+  :guilabel:`Type`.
+- To choose a default data dimension (category), select a field under :guilabel:`First dimension`
+  and, if needed, another under :guilabel:`Second dimension`.
+- To select a default type of data to be measured using the view, select a field under
+  :guilabel:`Measure`.
+- *For Bar and Line charts only*: To sort the different data categories by their value, select
+  :guilabel:`Ascending` (from lowest to highest value) or :guilabel:`Descending` (from highest to
+  lowest) under :guilabel:`Sorting`.
+- *For Bar and Pie charts only*: To access all records whose data is aggregated under a data
+  category on the chart, tick :guilabel:`Access records from graph`.
+- *For Bar charts only*: When using two data dimensions (categories), display the two columns on top
+  of each other by default by ticking :guilabel:`Stacked graph`.
+
+.. example::
+
+   .. image:: views/graph-sales-report.png
+       :alt: Sales Analysis Report model's Bar chart on Graph view
+       :scale: 75%

package/payload/skills/odoo18-docs/references/docs/applications/studio.md

@@ -0,0 +1,43 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/studio.html"
+---
+
+:show-content:
+:hide-page-toc:
+# 
+# Studio
+
+.. toctree::
+   :titlesonly:
+
+   studio/fields
+   studio/views
+   studio/models_modules_apps
+   studio/automated_actions
+   studio/pdf_reports
+   studio/approval_rules
+
+**Studio** is a toolbox used to customize Odoo without coding knowledge. For example, in any app,
+add or modify:
+
+- :doc:`Fields <studio/fields>`
+- :doc:`Views <studio/views>`
+- :doc:`Models <studio/models_modules_apps>`
+- :doc:`Automation rules <studio/automated_actions>`
+- :doc:`Webhooks <studio/automated_actions/webhooks>`
+- :doc:`PDF reports <studio/pdf_reports>`
+- :doc:`Approval rules <studio/approval_rules>`
+- Security rules
+
+Learn how to :doc:`build an app from scratch <studio/models_modules_apps>`.
+
+.. _studio/access:
+
+To access Studio, navigate to the app and model you want to modify, then click the :icon:`oi-studio`
+(:guilabel:`Toggle Studio`) icon, or vice versa.
+
+To close **Studio**, click :guilabel:`Close` in the upper-right corner.
+
+.. seealso::
+   [Odoo Tutorials: Studio ](https://www.odoo.com/slides/studio-31)

package/payload/skills/odoo18-docs/references/docs/applications/websites/blog.md

@@ -0,0 +1,128 @@
+---
+title: "Blog"
+source_url: "https://docs.odoo.sbggai.top/applications/websites/blog.html"
+---
+
+====
+# Blog
+
+**Odoo Blog** allows you to create and manage blog posts on your website to engage your audience and
+build a community.
+
+> **tip**:
+>    If the Blog module is not yet installed, click :guilabel:`+New` on the website builder, select
+   :guilabel:`Blog Post`, and click :guilabel:`Install`.
+
+# Creating a blog
+
+To create or edit a blog, go to :menuselection:`Website --> Configuration --> Blogs: Blogs`. Click
+:guilabel:`New`, and enter the :guilabel:`Blog Name` and the :guilabel:`Blog Subtitle`.
+
+The :guilabel:`Blog` menu item is added to your website's menu the first time you create a blog and
+gathers all your blogs.
+
+# Adding a blog post
+
+Go to your website, click :guilabel:`+New` in the top-right corner, and select
+:guilabel:`Blog Post`. In the pop-up, **select the blog** where the post should appear, write the
+post's :guilabel:`Title`, and :guilabel:`Save`. You can then write the post's content and customize
+the page using the website builder.
+
+> **tip**:
+>    - Illustrate your articles with copyright-free images from :doc:`Unsplash
+     </applications/general/integrations/unsplash>`.
+   - Type `/` in the text editor to format and add elements to your text.
+
+> **important**:
+>    Don't forget to toggle the :guilabel:`Unpublished` switch in the top-right corner to publish
+   your post.
+
+# Using tags
+
+Tags let visitors filter all posts sharing the same tag. By default, they are displayed at the
+bottom of posts, but can also be displayed on the blog's main page. To do so, click
+:menuselection:`Edit --> Customize` and enable the :guilabel:`Sidebar`. By default, the sidebar's
+:guilabel:`Tags List` is enabled.
+
+To create a tag, go to :menuselection:`Website --> Configuration --> Blogs: Tags` and click
+:guilabel:`New`. Fill in the:
+
+- :guilabel:`Name`
+- :guilabel:`Category`: tag categories let you group tags displayed on the sidebar by theme.
+- :guilabel:`Used in`: to apply the tag to existing blog posts, click :guilabel:`Add a line`,
+  select the posts, and click :guilabel:`Select`.
+
+You can add and create tags directly from posts by clicking :menuselection:`Edit --> Customize` and
+select the post's cover. Under :guilabel:`Tags`, click :guilabel:`Choose a record...`, and select
+or create a tag.
+
+.. image:: blog/create-tag.png
+   :alt: Adding a tag to a blog post
+
+> **note**:
+>    To manage tag categories, go to :menuselection:`Website --> Configuration --> Blogs: Tag
+   Categories`.
+
+# Customizing blog homepages
+
+Customize the content of blog homepages by opening a blog homepage and clicking :menuselection:`Edit
+--> Customize`.
+
+> **note**:
+>    Settings apply to **all** blogs homepages.
+
+:guilabel:`Top Banner`: :guilabel:`Name/Latest Post` displays the title of the latest post on the
+top banner, while :guilabel:`Drop Zone for Building Blocks` removes the top banner and lets you use
+any building block instead.
+
+:guilabel:`Layout`: organizes posts as a :guilabel:`Grid` or :guilabel:`List`.
+
+- :guilabel:`Cards`: adds a *card* effect.
+- :guilabel:`Increase Readability`: improves the text's readability.
+
+:guilabel:`Sidebar`: displays a sidebar containing an :guilabel:`About us` section.
+
+- :guilabel:`Archives`: allows visitors to select a month and filter all posts created during that
+  month.
+- :guilabel:`Follow Us`: displays links to your social media networks. They can be configured using
+  the Social Media building block somewhere on your website.
+- :guilabel:`Tags List`: displays all tags related to a blog. Visitors can select a tag to filter
+  all related posts.
+
+:guilabel:`Posts List`: :guilabel:`Cover` displays the posts' images, and :guilabel:`No Cover` hides
+them.
+
+- :guilabel:`Author`: displays the posts' authors.
+- :guilabel:`Comments/Views Stats`: displays the posts' number of comments and views.
+- :guilabel:`Teaser & Tags`: displays the posts' first sentences and tags.
+
+# Customizing blog posts
+
+Customize posts by opening a blog post and clicking :menuselection:`Edit --> Customize`.
+
+> **note**:
+>    Settings apply to **all** posts.
+
+:guilabel:`Layout`: :guilabel:`Title Inside Cover` displays the title inside the cover image, and
+:guilabel:`Title above Cover` displays it above.
+
+- :guilabel:`Increase Readability`: increases the text's readability.
+
+:guilabel:`Sidebar`: displays the :guilabel:`Sidebar` and additional options:
+
+- :guilabel:`Archive`: allows visitors to select a month and filter all posts created during that
+  month.
+- :guilabel:`Author`: displays the post's author and creation date.
+- :guilabel:`Blog List`: displays links to all your blogs.
+- :guilabel:`Share Links`: displays share buttons to several social networks.
+- :guilabel:`Tags`: displays the post's tags.
+
+:guilabel:`Breadcrumb`: displays the path to the post.
+
+:guilabel:`Bottom`: :guilabel:`Next Article` displays the next post at the bottom, and
+:guilabel:`Comments` enable visitors to comment on the post.
+
+:guilabel:`Select To Tweet`: visitors are offered to tweet the text they select.
+
+> **tip**:
+>    Use :ref:`Plausible <analytics/plausible>` to keep track of the traffic on your blog.

package/payload/skills/odoo18-docs/references/docs/applications/websites/ecommerce/cart.md

@@ -0,0 +1,110 @@
+---
+title: "Add to cart"
+source_url: "https://docs.odoo.sbggai.top/applications/websites/ecommerce/cart.html"
+---
+
+===========
+# Add to cart
+
+The :guilabel:`Add to Cart` button can be customized in multiple ways. You can:
+
+- Choose on which page customers go after clicking the 'Add to Cart' button;
+- Hide the 'Add to Cart' button to prevent sales;
+- Add a 'Buy Now' button to skip the cart step and lead customers straight to checkout;
+- Create additional 'Add to Cart / Buy Now' buttons;
+- Add an 'Order Again' button to the customer portal.
+
+.. seealso::
+   :doc:`checkout`
+
+.. _ecommerce/cart/action_customization:
+
+# 'Add to Cart' action customization
+
+When customers click on the :guilabel:`Add to Cart` button, the product is added to their cart, and
+customers remain **by default** on the product's page. However, customers can either immediately be
+**redirected** to their cart, or given the choice on what to do through a **dialog box**.
+
+To change the default behavior, go to :menuselection:`Website --> Configuration --> Settings`. Under
+the :guilabel:`Shop - Checkout Process` section, look for :guilabel:`Add to Cart` and select one of
+the options.
+
+> **note**:
+>    If a product has :doc:`optional products <products/cross_upselling>`, the **dialog
+   box** will always appear.
+
+.. seealso::
+   :doc:`products/catalog`
+
+.. _cart/prevent-sale:
+
+# Replace 'Add to Cart' button by 'Contact Us' button
+
+You can replace the 'Add to Cart' button with a 'Contact Us' button which redirects users to the URL
+of your choice.
+
+> **note**:
+>    Hiding the :guilabel:`Add to Cart` button is often used by B2B eCommerces that need to restrict
+   purchases only to :ref:`customers with an account <ecommerce/checkout/policy>`, but still want to
+   display an online product catalog for those without.
+
+To do so, go to :menuselection:`Website --> Configuration --> Settings --> Shop - Products` and tick
+:guilabel:`Prevent Sale of Zero Priced Product`. This creates a new :guilabel:`Button url` field
+where you can enter the **redirect URL** to be used. Then, set the price of the product to `0.00`
+either from the **product's template**, or from a
+:doc:`pricelist </applications/sales/sales/products_prices/prices/pricing>`.
+
+.. image:: cart/cart-contactus.png
+   :align: center
+   :alt: Contact us button on product page
+
+> **note**:
+>    The 'Contact Us' button and '*Not Available For Sale*' text can both be modified using the
+   **website builder** on the product's page (:menuselection:`Edit --> Customize`) by clicking on
+   them.
+
+# Customizable 'Add to Cart' button
+
+You can also create a customizable 'Add to Cart' button and link it to a specific product. The
+**customized button** can be added on any page of the website as an **inner content** building
+block, and is an *additional* button to the regular :guilabel:`Add to Cart` button.
+
+To add it, go on the :guilabel:`Shop` page of your choice, click :menuselection:`Edit --> Blocks`
+and place the building block. Once placed, you have the following options:
+
+- :guilabel:`Product`: select the product to link the button with. Selecting a product renders the
+  :guilabel:`Action` field available;
+- :guilabel:`Action`: choose if the button should :guilabel:`Add to Cart` or :guilabel:`Buy Now`
+  (instant checkout).
+
+.. image:: cart/cart-add.png
+   :align: center
+   :alt: Customizable 'Add to Cart' button
+
+.. _ecommerce/cart/buy-now:
+
+# 'Buy Now' button
+
+You can enable the :guilabel:`Buy Now` button to take customers directly to the :ref:`review order
+<ecommerce/checkout/review_order>` step instead of adding the product to the
+cart. This button is an *additional* option and does not replace the :guilabel:`Add to Cart` button.
+To do so, go to :menuselection:`Website --> Configuration --> Settings`, scroll to the
+:guilabel:`Shop—Checkout Process` section, enable :guilabel:`Buy Now`, and :guilabel:`Save`.
+
+> **tip**:
+>    Alternatively, you can enable the :guilabel:`Buy Now` button directly from a product page by
+   clicking :guilabel:`Edit` and navigating to the :guilabel:`Customize` tab.
+
+.. image:: cart/cart-buy-now.png
+   :alt: Buy Now button
+
+# Re-order from portal
+
+Customers have the possibility to **re-order** items from **previous sales orders** on the customer
+portal. To do so, go to :menuselection:`Website --> Configuration --> Settings --> Shop - Checkout
+Process` and enable :guilabel:`Re-order From Portal`. Customers can find the :guilabel:`Order Again`
+button on their **sales order** from the **customer portal**.
+
+.. image:: cart/cart-reorder.png
+   :align: center
+   :alt: Re-order button