Connect movement and billing
Retain the container and service references behind each charge.
Depot and containers
Depot work spans the manifest, handling, storage, dispatch, and the invoice. ICD Management is an SAP Business One add-on for teams that need those steps in one operational flow.

Built around your business
Depot operations bring together manifests, container handling, storage periods, dispatch documents, and customer tariffs. ICD Management connects these operational and billing activities with SAP Business One, allowing the team to follow the charge back to the container movement that created it.
Retain the container and service references behind each charge.
Check storage and handling charges against the agreed pricing structure.
Follow the operational history through to release and invoicing.
Solution capabilities to scope
Build the scope around the records your team uses, the decisions it makes, and the exceptions it needs to manage.
01 / SOLUTION AREA
Connect manifest and MBL or HBL references with container records, arrival information, and the customer responsible for the activity.
02 / SOLUTION AREA
Scope general and specialized container handling, stuffing, destuffing, and loose-cargo activities around the services your depot performs.
03 / SOLUTION AREA
Apply customer-group pricing and verify storage periods and service charges using the agreed tariff and operational history.
04 / SOLUTION AREA
Keep dispatch documents, proforma or tax invoices, and empty-container operations connected with the SAP Business One process.
Recommended starting point
Discuss your operating requirements with LITPL to confirm product fit, configuration, integrations, and implementation scope.
Explore the solution approach ↗An example operational workflow
Follow a typical transaction through the business. We adapt the sequence, approvals, and handovers to your operation during discovery.
Capture manifest, MBL or HBL references, customer details, and the containers expected for handling.
Key record
Manifest and container register
Follow container receipt and the relevant general, reefer, dangerous-goods, or out-of-gauge handling requirements in the agreed scope.
Key record
Container arrival and handling record
Record the storage period and applicable stuffing, destuffing, loose-cargo, or empty-container operations.
Key record
Storage and service history
Apply customer-group pricing and check the storage calculation and service charges before finalizing billing.
Key record
Verified charge calculation
Prepare the required dispatch and invoice documents, then reconcile the container's operational history with billed services.
Key record
Dispatch documents and invoice
Reporting priorities
Agree report definitions, date ranges, ownership, and source transactions before implementation. Use these industry-specific views as a starting point for your reporting scope.
Implementation approach
Agree the scope and acceptance criteria first, then prepare the data and people who will run the process.
Walk through a real transaction with your operations and accounts teams. Agree the priorities, exceptions, and reports.
Confirm product fit, responsibilities, approvals, and data fields. Scope any add-ons, custom workflows, and integrations.
Clean and map master records, opening stock, balances, and active transactions. Reconcile the data before migration.
Run representative transactions and exceptions with your users. Verify calculations, reports, access, and operating procedures.
Agree the cutover plan and support arrangements. Review early transactions and resolve issues with the responsible team.
Before you decide
Choose container journeys with ordinary and exceptional handling, free periods, customer tariffs, and empty-container operations where applicable. Compare the proposed charge calculations and documents with approved examples in your SAP Business One environment.
The scope depends on your users, locations, opening data, approvals, reporting, and integrations. We review a representative workflow and agree what uses standard functionality, what needs configuration, and what needs additional development before preparing the proposal.