The Customer module in LogixFlow allows organizations to manage and maintain customer master records centrally. It helps users create, view, and update customer information that is used across various modules such as Freight, Billing, and CRM. This ensures consistency and accuracy in customer-related operations throughout the LogixPlatform.
Overview
The Customer module under Masters in System Settings allows you to define and manage all customer details that the organization interacts with. These customer records are shared across business functions such as quotations, billing, shipments, and reports.
[PLACEHOLDER: Insert Screenshot Here — Customer List View]
Prerequisites
- Users must have Admin or Master Data Management access rights.
- Ensure that Operating Units, Business Categories, and Countries/States are pre-configured in the system.
- Access to System Settings → Masters → Customer in the left navigation menu.
Steps to Use
- Go to System Settings → Masters → Customer.
- Click the + Customer button to create a new record.
- Enter customer details such as Name, Customer Code, Contact Person, and Mobile.
- Select appropriate Country, State, City, and Operating Unit.
- Optionally, enter Address, Email, Postal Code, Tax ID, and Business Category.
- Click Save to store the record.
- Use the Edit (pencil icon) to modify existing customers when required.
[PLACEHOLDER: Insert Screenshot Here — Create Customer Form]
Field Reference
| Field | Required | Description | Examples / Notes |
|---|---|---|---|
| Name | Yes | Full name of the customer or organization. | e.g., ABC Corporation |
| Customer Alias | No | Short or alternate name used internally for quick reference. | Useful for reporting or searching. |
| Customer Code | Yes | Unique system code used to identify the customer. | Auto-generated or manually entered as per configuration. |
| Contact Person | Yes | Name of the primary contact person for the customer. | e.g., John Doe |
| Mobile | Yes | Primary contact number for the customer or contact person. | Ensure it follows country format. |
| No | Email address for communication or billing. | e.g., info@abccorp.com | |
| Country / State / City | No | Location details used for logistics and reporting. | Auto-populated dropdowns based on selection hierarchy. |
| Address | No | Complete mailing or billing address. | Include street, building, and landmark if applicable. |
| Postal Code | No | ZIP or postal code of the customer address. | Used for delivery and tax calculations. |
| Tax ID | No | Customer’s registered tax identification number. | Mandatory for invoicing in certain countries. |
| Business Category | No | Classification of the customer based on business type. | e.g., Retailer, Distributor, Exporter. |
| Operating Unit | Yes | The operational branch or unit to which this customer belongs. | Select from configured operating units. |
| Visible Across Organisation | No | When checked, makes the customer accessible to all operating units. | Useful for multi-branch customers. |
Usage Across Modules
- Customer records created here are available across Freight, Quotation, and Billing modules.
- Used for tagging customer information in transactions such as quotations, shipments, and invoices.
- Appears in reports and analytics dashboards for performance and account tracking.
[PLACEHOLDER: Insert Screenshot Here — Customer usage in Freight module]
Notes / Best Practices
- ✅ Maintain unique Customer Codes to prevent duplicate entries.
- ✅ Regularly review inactive customers and archive them if not in use.
- ⚠️ Ensure all required fields (Name, Code, Mobile, Contact Person, Operating Unit) are filled before saving.
- ⚠️ Avoid editing Customer Codes once linked to active transactions.
Troubleshooting
Unable to save customer record
Check that all required fields are completed and that the Customer Code is unique within the operating unit.
Dropdowns not populating (Country/State/City)
Ensure the respective master data is configured in Location Master under System Settings.
FAQs
- Can I delete a customer record?
- Only customers not linked to any transactions can be deleted. Otherwise, deactivate or archive them instead.
- Can multiple operating units use the same customer?
- Yes, if the Visible Across Organisation checkbox is enabled during creation.
- Is the Customer Code auto-generated?
- Depending on system configuration, it can be auto-generated or manually entered by the user.