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

Sales stock availability

Give sales a usable stock figure that accounts for existing commitments, held stock and the parts needed to make a complete kit.

See the real screens ↓
Choose the warehouseCheck what can be promisedCheck the complete kitReview the whole order
The working interface

See it in use.

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

Explain availability at the order line / Actual Odoo screenEnlarge screenshot ↗
Actual availability popover on an existing quotation for kit GR4102B-LP. The screen shows seven available units and one complete kit needed. Customer identity and chatter are outside the crop; no quantities or order state were changed.
01 / Sales representative

Explain availability at the order line

  • Open availability from the quotation line.
  • Compare forecasted and available stock with the complete kits needed by this line.
  • Read the kit status before making the customer a stock promise.

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

Show what can be promised alongside what is on hand.

The business problem

Physical on-hand stock can include quantities already promised or intentionally held. Kits add another layer: a sales line needs to reflect the components that can actually support it.

What we changed

Sales indicators use shared availability calculations, including stock locks and the components that support a kit.

What the team can do now

Sales can review a stock promise with the warehouse’s restrictions still attached to the number.

Read the actual screen / Existing quotation

Seven available kits. One needed by this line.

The existing GR4102B-LP quotation line opens a native availability panel. It shows the complete-kit requirement beside available stock and explains that the least-available required component limits kit availability.

Product
GR4102B-LP
Available
7 units
Needed by this line
1 complete kit
Kit status
In stock

What the screen shows

The same panel shows forecasted stock, available stock and the line requirement. Those quantities remain visible in the capture.

What the team does next

Use the availability explanation to assess this line, then account for the rest of the order before confirming a promise.

What the next team receives

Sales and warehouse staff share an explanation of what the kit quantity represents. The capture observes a quotation; it does not demonstrate reservation or delivery.

How the work moves

Follow the work from one decision to the next.

01

Choose the warehouse

Read availability for the warehouse serving this order.

02

Check what can be promised

Account for stock already reserved or held.

03

Check the complete kit

See how the least-available required component limits the number of kits.

04

Review the whole order

Consider repeated product lines and quantities before promising stock.

Built, used, refined

How the workflow improved over time.

  1. Align order availability

    Brought sales availability into line with the shared stock calculation.

  2. Carry locks into kits

    Extended the stock-lock context into kit availability and sales indicators.

  3. Restore useful kit forecasts

    Refined the availability widget so kit lines expose the stock context staff need.

About these dates

Dates identify recorded implementation changes, not claimed rollout dates or measured results. Reviewed revisions: 58dfa3c, 51f57ac, b9555d1.

Build notes and background
Inventory logicSales operations

The boundaries we made explicit.

Availability is not just on hand

Reserved and actively locked quantities must not look freely available.

Own reservations need context

A confirmed order can include its own reserved units when showing what is available for that order.

No inventory was changed

This case describes calculation and presentation logic; it is not a stock adjustment.

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 →