The work replaces an export, macro and upload cycle with configurable rules and a review workspace. It supports cost bands, dependent price tiers, individual exceptions and deliberate application.
Read each product’s cost, stock and sales activity alongside its price tiers.
Compare current and proposed prices, margins and differences.
Inspect why a product needs attention before selecting its review lines.
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
Review the price change before it reaches sales.
The business problem
New costs can affect several customer price tiers at once. A spreadsheet handoff makes it harder to see the current price, proposed price, stock, and sales context together.
What we changed
Current and proposed tiers now sit beside stock, sales activity and rule explanations. Reviewers select the changes to apply.
What the team can do now
The buyer can inspect the cost-to-price decision before selected changes reach the pricelist.
Read the actual screen
Ready does not mean selected.
The catalog shows one mirror needing attention and a tail lamp marked Ready. Both still have zero selected tiers in the captured review.
Mirror status
Needs Attention
Lamp status
Ready
Selected tiers
0 / 5
Apply action
Not performed
What the screen shows
The mirror’s rule messages say no active pricing rule was found. The lamp’s selection explanation says its current and proposed P1 margins are both inside the allowed review band.
What the team does next
Resolve missing rules where needed and choose which eligible tiers should change. A calculated proposal is not an instruction to apply every price.
What the next team receives
The pricing operator retains the reviewed selection and the reasoning behind the remaining work.
The scope of the system
Decisions this system handles.
The work replaces an export, macro and upload cycle with configurable rules and a review workspace. It supports cost bands, dependent price tiers, individual exceptions and deliberate application.
Several containers need repricing
Select eligible containers under receipt and landed-cost readiness rules, with kit parents excluded by default.
The next handoff The review has an explicit, eligible product scope.
Different products need different rules
Use product, category or fallback rules and cost bands to generate proposed tier prices.
The next handoff The reviewer can inspect the rule behind the proposal.
An earlier price tier changes
Edit the proposed tier and recalculate later tiers that depend on it.
The next handoff Dependent proposals stay connected to the reviewer’s change.
Only some proposals should go live
Compare current and proposed margins, resolve missing rules and apply the selected lines.
The next handoff Sales receives the selected changes while unresolved work remains reviewable.
These paths describe the implemented workflow. The captures show specific existing records; they do not demonstrate every branch being executed.
See the shipping-cost inputs needed for region-specific pricing.
How the work moves
Follow the work from one decision to the next.
01
Build the review
Choose eligible containers or a manual product selection. Configured rules generate the proposed tier prices.
02
Compare in context
Review prices and margins alongside stock and sales activity. Adjust proposals where the business needs an exception.
03
Apply selected lines
Select the changes that are ready. Apply those lines from the review instead of re-uploading an entire workbook.
Build notes and background
Workflow automationOperational reporting
Make the exceptions part of the workflow.
A missing rule needs attention
A product without an eligible pricing rule stays distinguishable from a usable proposal.
Scope matters
Container readiness, product eligibility and kit exclusions affect which products belong in a review.
Selection is deliberate
Review bands can leave a valid proposal unselected. Apply Selected operates on the reviewed selection.
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.
A custom Pro-A-Motors review workflow built on Odoo pricelists, stock and landed costs, with the Captivea container foundation and Pro-A-Motors extensions.
