Skip to Content
Pro-A-Motors / Sales & Customer

Storefront stock status

Help online customers understand whether a part is available before they place an order.

See the real screens ↓
Read website availabilityDistinguish backorder from unavailablePreserve useful merchandisingUpdate and audit
The working interface

See it in use.

Explore 2 real views of this workflow. Select a task, show every screen, or enlarge an image to read the original controls.

Make availability visible while browsing / Actual Odoo screenEnlarge screenshot ↗
Actual storefront search results with native Out of stock ribbons and product cards. The signed-in header is outside the crop. Product images, stock messages, references and prices are unchanged.
01 / Customer browsing the catalog

Make availability visible while browsing

  • Read the availability ribbon alongside the product picture.
  • Compare product identifiers and prices in the same card.
  • Open a product to inspect its ordering status.
Keep the product page consistent / Actual Odoo screenEnlarge screenshot ↗
Actual product page for SKU 1000242, with the Out of stock ribbon, unavailable-order message and back-in-stock notification entry point visible. No cart or notification action was used.
02 / Customer reviewing a product

Keep the product page consistent

  • See the stock message beside the product information.
  • Distinguish the notification option from an available Add to Cart action.
  • Review the product identifiers and vehicle fitment without losing the stock context.

Actual Pro-A-Motors interface captures. Private identities and contact details are covered or outside the crop; screen data has not been replaced.

What improved

Keep the availability message tied to the buying decision.

The business problem

A manually stored Sold Out label can remain after stock returns. A product allowed to sell on backorder also needs a different message from a product that cannot be ordered.

What we changed

Stock labels and ordering controls follow availability and backorder policy, including when stock returns.

What the team can do now

The storefront can communicate stock state using the same availability context as the purchase controls.

Read the actual screen / Existing storefront product

The catalog and product page agree.

SKU 1000242 displays an Out of stock ribbon in the search results. Opening it shows the same ribbon and an Out of Stock message beside the back-in-stock notification option.

Product
1000242
Search results
Out of stock
Product page
Out of Stock
Next option
Back-in-stock notification

What the screen shows

Both real captures show the same availability state for the same product.

What the team does next

A customer can inspect the product and choose whether to request a future notification. No cart or notification action was performed for this capture.

What the next team receives

The customer-facing message stays attached to the product. Source review explains how availability and the continue-selling policy select the state.

How the work moves

Follow the work from one decision to the next.

01

Read website availability

Evaluate the product using the website’s available-quantity source.

02

Distinguish backorder from unavailable

Use Continue Selling policy to choose Backorder or Out of Stock when availability is zero.

03

Preserve useful merchandising

Keep Sale or New ribbons while products are available, while clearing stale stock-state ribbons.

04

Update and audit

Update ribbon information with variant combinations and audit manually stored stock-state ribbons.

Built, used, refined

How the workflow improved over time.

  1. Dynamic availability ribbons

    Added website-aware stock ribbons, variant refresh, migration cleanup and a scheduled audit. This is distinct from the fitment-search story: it controls the availability message after a product has been found.

About these dates

Dates identify recorded implementation changes, not claimed rollout dates or measured results. Reviewed revisions: 9a496b6.

Build notes and background
Ecommerce UXInventory logic

The boundaries we made explicit.

Warehouse context matters

A storefront quantity belongs to the website’s stock context, not an arbitrary global on-hand total.

Marketing and availability are different

Promotional ribbons can survive availability changes when they remain appropriate.

An audit is a diagnostic

The scheduled audit warns about manually stored stock-state ribbons; it is not a stock correction.

Existing records are shown as captured. Private identities are covered or outside the crop. No business records were changed for this collection. Implementation history supports behavior beyond the visible screen; a still image is not an end-to-end test or a measured productivity result.

Built on Captivea CAP modules and Odoo. This case describes the subsequent Pro-A-Motors extensions and refinements recorded in the reviewed repository; it does not attribute the original CAP implementation to Toro.

Which handoff is slowing your team down?

Talk through your workflow →