SERP feature guide
Customers and Contacts
Customer and contact records supply the commercial identity, communication details and branch context used in sales transactions.
What does customers and contacts do in SERP?
Customer and contact records supply the commercial identity, communication details and branch context used in sales transactions. SERP connects this work with sales, so users can review its operational context through the related records.
Business problem it addresses
Repeatedly typing addresses and payment terms creates inconsistent documents and makes it harder to identify the responsible contact.
Key functions
- Maintain customer identity, currency, credit limit and payment terms.
- Keep billing and shipping addresses distinct.
- Review branch contacts, inventory location and company branch before order processing.
How the workflow works
- Maintain the customer.
- Check branch and contacts.
- Review commercial defaults.
- Use the customer on a document.
- Inspect subsequent activity.
Example business scenario
A distributor invoices a head office but ships to a branch warehouse. The customer setup needs both addresses and the correct shipping contact so the order reflects the actual arrangement.
Controls and availability
A saved customer is not a sale. Existing accounting activity can restrict changes to currency and accounts. CRM contact access and accounting customer access are separate permission concerns.
How to assess the result
Use a representative sales document to inspect the selected customer, branch, shipping contact and location defaults. Confirm that billing and shipping details match the intended transaction. Review customer history before changing defaults that may affect future work.
Connected SERP capabilities
Read the Sales module guide for the wider process and SERP reporting for the distinction between a transaction document and an analytical report.
A few useful answers
Frequently asked questions
What is customers and contacts?
Customer and contact records supply the commercial identity, communication details and branch context used in sales transactions.
Which functions can I review in SERP?
Maintain customer identity, currency, credit limit and payment terms; Keep billing and shipping addresses distinct; Review branch contacts, inventory location and company branch before order processing.
What is a practical example?
A distributor invoices a head office but ships to a branch warehouse. The customer setup needs both addresses and the correct shipping contact so the order reflects the actual arrangement.
What should we confirm before using this workflow?
A saved customer is not a sale. Existing accounting activity can restrict changes to currency and accounts. CRM contact access and accounting customer access are separate permission concerns.
Where does this fit in the wider ERP process?
It is part of Sales. Review the source requirement, the resulting transaction and the handoff to the next team.
Explore this workflow with your team.
Bring a representative requirement and the roles involved. Follow the records and review the result in a focused SERP demonstration.
Request a Demo → Discuss your requirements