Find the backorder by its original container name.
See the outstanding fog-lamp line and its ten-unit demand.
Continue the remaining receiving work separately from the completed batch.
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 shortage visible after a partial receipt.
The business problem
A shipment can arrive short even when most of the receipt is complete. The team needs to see what arrived, which products remain outstanding and which container those products belong to.
What we changed
Receiving review shows expected and scanned quantities, while the completed receipt and remaining backorder retain their container link.
What the team can do now
Inbound teams can retain the connection between what was purchased, what arrived and where it should move next.
A real container / Three connected views
700 scanned. Ten still need follow-up.
Container 1838A2 has a saved scanning session, a completed receipt batch and an in-progress backorder. The three screens let a receiving team follow the same shipment.
Expected
710
Scanned
700
Remaining
10
Follow-up
Container backorder
What the screen shows
The session shows the ten-unit difference. The backorder lists ten fog lamps with Picked still unchecked.
What the team does next
Use the backorder to locate the unfinished receiving work. The saved session also retains review flags; its Validated label alone does not tell the whole story.
What the next team receives
The completed products and the remaining receipt stay connected to container 1838A2.
How the work moves
Follow the work from one decision to the next.
01
Keep the shipment together
Start with the container and its receiving work.
02
Compare the scan totals
Read the expected, scanned and remaining quantities.
03
Review the receipt
Inspect the products and quantities on the completed batch.
04
Follow up on the remainder
Find unfinished goods in the backorder attached to that container.
Built, used, refined
How the workflow improved over time.
Group container backorders
Refined unfinished batch work and its downstream internal-transfer routing.
Connect collaborative receiving
Adapted container behavior to the collaborative scanning workflow.
Protect kit identity
Strengthened receiving checks around kit and component disaggregation.
Refine edge cases
Corrected kit and clip handling in the container batch path.
About these dates
Dates identify recorded implementation changes, not claimed rollout dates or measured results. Reviewed revisions: 61bfa2e, d91335f, d3f98a5, 64d1dec.
Build notes and background
Inventory logicWarehouse UXWorkflow automation
The boundaries we made explicit.
One internal transfer has a container scope
The model constrains container linkage so unrelated container work cannot silently share the same route.
Kit receipt and kit consumption differ
Buying a set is not automatically the same operation as receiving each BoM component separately.
Backorders retain their origin
Backorder batches do not create an unrelated second internal route for the same container.
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.
