Central DMS Management
DMS provides the core management and operational context for supported activities, including distributor information, orders, inventory, delivery, collection, returns, reconciliation, and reporting.
Codithic DMS
DMS + SFA
Integration
Connect central management
with field execution.
Codithic DMS and Codithic SFA are related components of one connected solution. DMS provides distributor management and backend operations. SFA is the mobile-first field sales application that works with DMS — not a standalone system — connecting field execution with the operational context maintained in DMS.
Key capabilities
Connected Management and Field Execution
Connect central DMS processes with field activities performed through Codithic SFA.
Van Sales
Supported Van Sales workflows let users work with assigned customers, create or capture orders, check stock context, record collection activity, and connect operational records with DMS.
Presales
Presales users capture customer visits and order activity through SFA. Relevant order information connects to DMS operational processes where supported.
Delivery & Collector
Supported delivery and collection workflows can connect field execution with DMS operational records.
Each activity belongs to the role and workflow supported for that implementation.
How it works
DMS → SFA → DMS
Central management and field execution work together across the operational workflow.
DMS → SFA → DMS
1. DMS
Plan and manage supported operational work.
- Customers and distributors
- Orders
- Inventory context
- Delivery planning
- Collection
- Reconciliation
2. SFA
Execute assigned field activities.
- Van Sales
- Presales
- Delivery
- Collector
3. DMS
Record and review the resulting operational activity.
- Orders
- Delivery status
- Collection
- Returns
- Reconciliation
This diagram shows a conceptual relationship between management and field execution. Field activities follow the workflow supported for that role.
Van Sales
Execute Sales Where the Work Happens
Codithic SFA supports mobile-first Van Sales activity connected to the DMS operational layer.
Assigned Customer → Visit Customer → Create Order → Check Current Stock → Deliver if Stock Available → Collect Payment → Reconciliation → Unload
A Van Sales user can create a Presales Order when required.
Delivery depends on stock availability and the supported operational workflow.
Not every order is necessarily delivered immediately.
Presales
Capture Orders in the Field
Presales supports field order capture. The resulting order activity connects into the DMS operational process for planning and delivery.
Assigned Customer → Visit Customer → Take Order → Presales Order → DMS Order Management → Planning / Delivery
Order capture and delivery execution are distinct responsibilities. A Presales order follows the planning and delivery path supported for that operation.
Delivery
Execute Assigned Deliveries
Delivery planning is based on existing or predefined orders.
Existing / Predefined Order → Delivery Planning → Delivery Assignment → Load Request → Delivery → Confirmation → Status → Return Collection → Reconciliation → Unload
Delivery confirmation can be configured as:
Delivery-based confirmation
Confirm delivery based on the configured delivery process for your operation.
Code verification
Use code verification for delivery confirmation. The code may be sent via email or SMS, based on the supported configuration.
Where code verification is configured, it may use email or SMS. Messaging uses customer-provided SMTP or SMS APIs, or a Codithic-arranged messaging setup when agreed. A deployment uses the confirmation approach supported for that operation.
Collection
Field Collection Connects to DMS Settlement
Field teams collect payment, and the collection information is recorded in DMS. Cashier settlement happens in DMS. Operational reconciliation follows the collection process.
Field Collection → DMS → Cashier Settlement → Reconciliation
Collection is an operational process. DMS is not a payment gateway or banking system.
Keep Returns and Reconciliation Connected
Returns and replacements can be connected to inventory context and operational reconciliation where supported.
Van Sales
Returns and replacements are distinct Van Sales activities. Where supported, they connect with operational reconciliation and unload.
Van Sales → Return / Replacement → Reconciliation → Unload
- Van Sales
- Return / Replacement
- Reconciliation
- Unload
Delivery
Delivery return collection is a separate closeout activity. Where supported, it connects with operational reconciliation and unload.
Delivery → Return Collection → Reconciliation → Unload
- Delivery
- Return Collection
- Reconciliation
- Unload
Clear responsibilities
One Operational Model. Two Execution Layers.
DMS
Core management platform
- Master Data
- Planning
- Order Management
- Inventory Management
- Distributor Management
- Delivery
- Collection
- Returns / Replacements
- Reconciliation
- Reports
- Administration / Configuration
SFA
Mobile-first field execution
- Van Sales
- Presales
- Delivery
- Collector
DMS provides the core operational management layer. SFA supports mobile-first field execution within that operational model and depends on the backend context managed in DMS.
Business value
Connected Field Execution. Stronger Operational Visibility.
Connected Operations
Connect supported field activities with the DMS operational context.
Clearer Execution
Give field teams a structured way to carry out supported operational activities.
Better Visibility
Help teams review field activity alongside related operational information where supported.
Consistent Reconciliation
Support operational closeout by connecting relevant delivery, collection, return, and reconciliation records where applicable.
Ready to connect field execution?
Explore DMS + SFA
See how Codithic DMS and SFA can work together across distribution operations.