A purchasing workspace that connects product-level demand, supplier choices, commitments and arrivals to explainable order recommendations. Explore the real catalog panels, follow one SKU’s calculation and see how new purchasing, reserve calls and reserve replenishment work together.
See the real screens ↓Explore 14 real views of this workflow. Select a task, show every screen, or enlarge an image to read the original controls.
Actual Pro-A-Motors interface captures. Private identities and contact details are covered or outside the crop; screen data has not been replaced.
A buyer needs to know more than today’s stock: what is selling, what was returned, what is already committed, what will arrive and which supplier-held units have already been called. Reconstructing those answers across separate records makes the buying decision harder to check.
We extended the purchasing catalog with product-level demand and supply panels, then connected it to saved forecast calculations, reserve planning and the policy recorded on the order.
Buyers can inspect the evidence behind a quantity, distinguish new purchasing from reserve release and replenishment, and follow a recommendation back to its selected months, supply rows and settings.
For engine under-cover SKU TY7502IA, 30 of the 65 reserved units had already been called. That left 35 available against a one-month reserve target of 63.33.
The resulting reserve gap is 28.33 units. The saved calculation rounds that requirement up to a multiple of five, giving a 30-unit recommendation. The supplier minimum did not change this result.
Inspect which reserve quantities are still available, confirm the selected demand months and check the rounding rule before accepting the recommendation.
The saved forecast and order settings preserve the reasoning. The later catalog shows 25 on the existing order; the screenshots do not explain why that quantity differs from the 30-unit proposal.
A unit sitting with a supplier, a unit on a ship and a unit available in the warehouse solve different problems. The automation keeps those decisions separate.
Evaluate eligible vendor products against demand, existing supply and the selected tier and ETA rules. Apply supplier minimums and rounding, then use review settings to route the proposal into an order or review.
Why we built it
A large buying list needs consistent rules while preserving a route for exceptions and buyer judgment.
Use the uncalled reserve balance and release timing. Keep quantities already called, containerized or received distinguishable. This SKU has 35 units still available and 30 already scheduled across two call lines.
Why we built it
Calling existing stock is a different commitment from buying more. The buyer needs to avoid requesting the same reserved units again.
For reserve-strategy products, compare the reserve target with uncalled reserve plus reserve purchase orders. In the captured run, the 63.33 target minus 35 available leaves 28.33 to replenish, rounded to 30.
Why we built it
The supplier-held buffer can need replenishment even while warehouse stock and incoming shipments protect near-term demand.
The screens show an existing reserve replenishment run and saved reserve commitments. Normal purchase generation and review routing are supported by the implementation; no new orders or reserve calls were created for this case study.
This engine under-cover SKU was evaluated in a saved run on September 4, 2026. The run uses the best three months from a six-month pool and a one-month reserve target.
(68 + 64 + 58) ÷ 3 = 63.33 units / month
July, March and June are the best three months in the March–August pool. Stockout adjustments are visible for other candidate months; none displaces these three selected months.
63.33 × 1 month = 63.33 units
Reserve replenishment uses the base monthly order point and a one-month reserve target. The separate tier multiplier of three produces a 190-unit general order point; 190 is not the reserve target used here.
65 reserved − 30 already called = 35 available
The supply rows distinguish physical reserve from quantities already committed for release. The saved run has zero additional confirmed reserve PO supply to add to that available balance.
63.33 − 35 = 28.33 → 30 units
The system rounds the positive requirement up to the next multiple of five. The saved explanation records that the supplier minimum did not alter this result. This is the proposal, not a claim that 30 was ultimately ordered.
The catalog offers 11 detail choices. The buyer can change the panel across the catalog or inspect a product’s own panel while its stock, supplier rows and order quantity stay in view.
See the demand basis, stock considered, generation mode, recommendation and final rounded result next to the product.
Basic Forecast DebugCompare divisions, channel context, monthly net units and sold-versus-returned quantities. August’s 44 sold minus 4 returns gives 40 net units for this SKU.
Division Info · In depth division demandInspect the candidate months, selected months, in-stock coverage and adjustment logic. The saved run uses historical-only demand; current-month projection is another available calculation path.
MTD Calculation Details · Historical Calculation Details · History Basis MonthsCompare open orders and incoming stock with completed receipts. Two September 3 receipts show 25 and 20 units received for this SKU.
Supply Detail · Past ReceiptsInspect five waiting outbound units, then distinguish 35 uncalled reserve units from 30 already scheduled for release.
Allocated Details · Reserve DetailsFollow the saved projection at 2.11 units of demand per day. Day-14 receipts add 35 units after stock falls to 72.44. The captured scenario shows no stockout before its listed arrivals; it remains dependent on those assumptions.
Projection ThinkingA purchasing workspace that connects product-level demand, supplier choices, commitments and arrivals to explainable order recommendations. Explore the real catalog panels, follow one SKU’s calculation and see how new purchasing, reserve calls and reserve replenishment work together.
Choose the demand basis and lookback, account for current-month activity, and apply capped stockout adjustments where the available history supports them.
The next handoff The buyer can inspect why the demand estimate differs from raw sales.
Separate on-hand, on-order, reserved and incoming-container quantities; use stage targets and ETA planning where configured.
The next handoff The recommendation can account for supply already committed or on its way.
Apply vendor eligibility, minimum quantities, rounding and review thresholds; choose normal purchasing or reserve replenishment.
The next handoff Items can reach a purchase order or a review queue under the selected rules.
Compare saved forecast runs and inspect the calculation and source records behind changed recommendations.
The next handoff The buyer has a route back to the settings and data that changed the result.
These paths describe the implemented workflow. The captures show specific existing records; they do not demonstrate every branch being executed.
See the purchase-order view separating on-order, container and received quantities.
Inspect the sales forecast where stock commitments affect the promise to a customer.
Select the vendor, eligible products, demand basis and generation mode. Normal purchasing, reserve replenishment and reserve calls serve different needs.
Use monthly and division demand, returns, selected history months and in-stock coverage to understand the estimate.
Separate warehouse stock, open orders, incoming containers, uncalled reserve and scheduled calls. Use arrival dates when evaluating future cover.
Vendor eligibility, tier profiles, minimums, rounding and review variance shape which proposals become order lines and which need review.
Saved forecast lines and source details preserve the inputs; the order retains its generation settings for later inspection.
Changed Q/MTD calculation from invoice-based data to sales-order data.
Added stock-lock connections to the catalog, sales and purchase automation.
Expanded the purchasing view with past-receipt context.
Added sidebar improvements to the purchasing catalog.
Dates identify recorded implementation changes, not claimed rollout dates or measured results. Reviewed revisions: 1da6603, 6c92cfb, 26d314f, 31606db.
The catalog combines current product information with the debug record matched to the order’s saved run. Later stock and order quantities can differ from that snapshot.
Stockout uplift has a cap and minimum in-stock evidence. This run uses historical-only demand and the best three months; other settings change the calculation.
A reserve replenishment target is checked against available reserve and reserve purchase-order supply. A warehouse ETA check answers a different question.
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.
The Captivea product/purchasing customizations and standard Odoo provide the foundation. Pro-A-Motors product-detail and purchase-automation extensions add the decision context and forecasting workflow shown here.
Explains how allocations, incoming shipments and supplier-held reserve affect the stock available for future demand.
Connects catalog demand and supply evidence to new purchasing, reserve calls and explainable replenishment recommendations.