Read its business-account tags before opening the record.
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
Find the business account by its working code.
The business problem
An operational customer lookup can be buried in one-off marketplace contacts. Staff also use account codes that a standard name-only search does not explain.
What we changed
Contact-code lookup extends the account search, with later refinements to business-customer scope and code assignment.
What the team can do now
Teams can reach the intended customer record with account context that carries across screens.
Follow an actual record
A working account code leads to one customer.
The Contacts search uses an existing account code rather than a customer name.
Search field
Contact Code
Matching records
1
Account tags
ProA Portal · Wholesale
What the screen shows
The Contact Code filter returns one record with ProA Portal and Wholesale tags.
What the team does next
Confirm the matching account and continue from its customer record.
What the next team receives
Sales and service can refer to the same account identifier.
How the work moves
Follow the work from one decision to the next.
01
Use the account’s working identifiers
Support contact-code and postal-code lookup alongside customer names.
02
Apply context-specific exclusions
Keep marketplace-contact exclusions scoped to the workflows that request them.
03
Carry contact codes into orders
Map a selected contact code back to the corresponding customer or vendor.
04
Keep code assignments synchronized
Maintain the relationship between a contact-code record and its partner when mappings change.
Built, used, refined
How the workflow improved over time.
Ledger search by contact code
Expanded account-code lookup in the customer statement and partner-ledger workflow.
Reduce marketplace noise
Refined contact lookup for the business-customer context.
Maintain code assignments reliably
Corrected contact-code create/write behavior.
About these dates
Dates identify recorded implementation changes, not claimed rollout dates or measured results. Reviewed revisions: 841b1a6, 8c8c796, 35d28e2.
Build notes and background
Sales operationsPerformance engineering
The boundaries we made explicit.
Search scope is not deletion
Marketplace contacts remain in the system; the relevant lookup can exclude them.
Codes have uniqueness rules
The contact-code model enforces unique code and partner mappings.
Ledger context stays deliberate
The partner-ledger helper preserves the user’s report context while handling the search term.
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.
