The shipment becomes a shared reference for receiving, backorders, supplier costs and price review. Each stage answers a different question before the next team relies on its result.
Use the posted allocation as context for the next price review.
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
Trace import charges into the products received.
The business problem
The physical shipment and its financial consequences were spread across different documents. This view was created to give the inbound process one traceable operating reference.
What we changed
Received products connect to a posted cost record, charge-specific allocation methods and each product’s additional landed cost.
What the team can do now
Operations and finance share a clearer path from supplier shipment through receipt, exceptions, cost formation, and product-price review.
Follow an actual record
One receipt, five costs, a traceable allocation.
The posted cost includes $5,950 in freight and $1,406.18 in customs duties, plus clearance, ISF and transit.
Charge total
$8,233.18
Freight split
By Volume
Duties split
By Current Cost
What the screen shows
Freight is split by volume; customs duties are split by current cost. The allocation tab shows the resulting charge for each product.
What the team does next
Inspect the allocation method and trace an item before relying on its landed cost.
What the next team receives
Purchasing and finance retain the same reference from the received product to its share of import costs.
The scope of the system
Decisions this system handles.
The shipment becomes a shared reference for receiving, backorders, supplier costs and price review. Each stage answers a different question before the next team relies on its result.
A shipment arrives short
Review scanned versus expected quantities and preserve the remainder on a linked backorder.
The next handoff Receiving can close the arrived quantity without losing the shortage.
Charges use different allocation bases
Separate freight, transit, clearance and duties, and inspect the split method for each.
The next handoff Finance can explain how the charge reaches the product.
One SKU’s cost needs investigation
Trace its quantity and additional landed-cost lines back to the posted record.
The next handoff The buyer gets a cost with an inspectable origin.
The next step is customer pricing
Respect container cost-readiness rules before creating a price review.
The next handoff Pricing receives eligible products with the current cost context.
These paths describe the implemented workflow. The captures show specific existing records; they do not demonstrate every branch being executed.
Continue from cost preparation into tier-price proposals and selection.
How the work moves
Follow the work from one decision to the next.
01
Create the inbound container
Supplier shipments and their relevant purchase lines gain one operational reference.
02
Receive what actually arrived
Grouped transfers, partial quantities, backorders, and kits are handled without losing container context.
03
Prepare the complete cost
Bills, duties, fees, currencies, and landed-cost rules are assembled against the received goods.
04
Review the downstream price
The team can see which containers have completed cost preparation and which products still need review.
Built, used, refined
How the workflow improved over time.
Protect container-line consistency
Refined purchase-container line handling so the inbound source relationships remain usable for later work.
About these dates
Dates identify recorded implementation changes, not claimed rollout dates or measured results. Reviewed revisions: d480960.
Build notes and background
Financial workflowsInventory logic
Make the exceptions part of the workflow.
Receipt and cost are different milestones
Physical arrival does not by itself establish that duties and landed costs are complete.
Duty and shipping are separate inputs
The form keeps charge categories and the customs-duty table in distinct review tabs.
Posting and downstream review differ
The cost record is already posted. Its allocation can be inspected without implying that a later price review has been applied.
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.
Odoo purchasing, inventory and accounting, the Captivea container foundation, and existing import-fee/landed-cost modules provide the base. Pro-A-Motors extensions connect collaborative receiving, container readiness and downstream price review. The case shows that combined operating workflow.
