Skip to main content

Website Warranty Info

Purpose​

Website Warranty Info adds warranty and shipping messages to the native eCommerce product page, alongside a Terms and Conditions link. Each message uses the product's own text when present and otherwise falls back to a saved default.

It is an information display extension. It does not register warranties, calculate warranty expiry, handle claims, track shipments or provide a returns workflow.

Before you start​

Install eis_product_warranty for Odoo 18.0 with Product and eCommerce (product, website_sale). No Enterprise-only dependency is declared. Your hosting must allow server addons, and your website theme must retain the native product-page location that the module extends.

This guide is based on the 18.0 model and template source. No website or installation test was performed during this review.

Access and roles​

The module creates no active new role or access grant in its installation manifest. Normal product-editing rights control the product text, and the normal settings administration rights control the defaults. Website visitors see the resulting text on accessible product pages.

The default values are stored as database configuration parameters. They are not separate settings per website or company in the reviewed implementation. Coordinate changes if several websites share the database.

Setup and menu​

In settings, locate the product catalogue area and the added Product Warranty String and Product Shipping String settings. Enter the business's approved wording and save. The source supplies example defaults of a 30-day money-back message and a 2–3-business-day shipping message; review those examples before they appear to customers.

On the product template form, the extension places Website Warranty Text and Website Shipping Text after the website ribbon field. Enter an override only when the product should differ from the default.

There is no separate warranty menu. The template links to /terms; ensure that your website has an appropriate Terms and Conditions page at that address.

Workflow​

  1. Save the approved default warranty and shipping messages in settings.
  2. Open a product intended for the website. Check both text fields rather than assuming they are empty: new products have a default warranty message in the model.
  3. Enter product-specific wording where required. To use the global fallback for a message, leave that product field empty.
  4. Save the product and open its website product page. Inspect the warranty message, shipping message and Terms and Conditions link in the terms/share area.
  5. Repeat with a second product that has blank override fields to check the fallback behavior. Inspect the actual public page before publishing changes to customers.

Practice scenario​

In an authorized test website, set a fictional default shipping message to “Dispatch within five business days.” Give “Harbor Custom Desk” its own message, “Made to order; dispatch within twenty business days.” Leave a second test product's shipping field blank. The intended result is the custom message on the desk and the saved default on the second product. This is a source-derived exercise, not a recorded test.

Troubleshooting and limitations​

The default is not showing: a non-empty product message takes precedence, including the model's initial warranty value. Clear that field only if the product should inherit the default.

The message area is missing: verify the native eCommerce template and the theme's product-page structure. A custom theme may need a compatible inherited view.

Use plain text. Although field help mentions HTML, these fields are ordinary text and the template uses escaped output; this guide does not promise rich-HTML rendering. The Terms link is fixed rather than selected from a configurable page field.

The module does not validate whether warranty or delivery promises are accurate for the business. Review the actual page content and your terms before customer use.

The supplied catalogue qualification covers 18.0. Older 16.0–17.0 source exists, but those pairs are not qualified for the public demo in the supplied inventory and their workflows are not established by this guide.