Every dispatch recorded: purpose, vehicle, responsible, and what went on it
Log outbound movements as logistics records — a code, date, delivery purpose, vehicle number, responsible user, and the product lines with quantity, price, and total. Deliveries transfers and gate passes complete the picture.
Built for
- Dispatch & warehouse teams — Record what left, on which vehicle, for what purpose, and who signed it off.
- Operations managers — Review dispatches by date and purpose without chasing paper delivery notes.
- Sales & customer service — Confirm that a customer order was dispatched and when.
- Finance — Reconcile dispatched value against invoices and stock transfers.
What Logistics does inside ERPS X
Logistics is where your company records goods leaving the building. Each logistics record has a Logistic Code, a Date, a Delivery Purpose — Customer Order, To Warehouse, or Other with a free-text description — the Vehicle Number, and the user Responsible for the dispatch.
Below the header are the product lines: product, quantity, unit of measure, price, and sub-total, rolled up into a Grand Total. That gives operations a value for what was loaded, not just a count, and gives finance a document to reconcile against the sales order or transfer that triggered it.
Logistics works alongside two neighbours in the Inventory department. Deliveries transfers move stock out against a source document and scheduled date; Gate Pass records the security and vehicle detail at the gate. Together they cover the physical, the stock, and the paperwork side of a shipment.
Dispatch & warehouse teams
Record what left, on which vehicle, for what purpose, and who signed it off.
Operations managers
Review dispatches by date and purpose without chasing paper delivery notes.
Sales & customer service
Confirm that a customer order was dispatched and when.
Finance
Reconcile dispatched value against invoices and stock transfers.
Everything Logistics gives your team
Each feature below is part of the application as it ships in your ERPS X workspace — no add-ons, no separate licences.
Logistic code & date
Each dispatch gets its own code and date, so it can be quoted on gate passes, delivery notes, and customer correspondence.
Delivery purpose
Choose Customer Order, To Warehouse, or Other — with a description field for anything that does not fit.
Vehicle number
Record the vehicle so security, drivers, and customers can be matched to the load.
Responsible user
Name the person accountable for the dispatch on the record itself.
Valued product lines
Product, quantity, UOM, price, and sub-total per line with a grand total for the load.
Works with Deliveries & Gate Pass
Stock movement is posted through Deliveries transfers; gate-side control is handled by Gate Pass.
A closer look at Logistics
The screens, records, and controls you will actually work with day to day.
Dispatch header
- Logistic Code
- Date
- Delivery Purpose: Customer Order / To Warehouse / Other
- Other Delivery Purpose description
- Vehicle Number and Responsible user
Load lines
- Product from the product master
- Quantity and UOM
- Price per line
- Sub-Total per line
- Grand Total for the dispatch
Around the dispatch
- Deliveries transfer with source document and scheduled date
- Gate Pass with vehicle, driver, and security officer
- Sales Orders as the origin of customer dispatches
- Product Moves report for stock history
- Access controlled by department and application (Logistics)
The Logistics workflow
From first setup to daily use — the path your team follows inside the application.
Confirm the source
A sales order, warehouse transfer, or other need triggers a dispatch.
Create the logistics record
Enter code, date, delivery purpose, vehicle number, and the responsible user.
Add the load
List each product with quantity, UOM, and price; the grand total is calculated.
Post the stock movement
Record the Deliveries transfer against the source document so on-hand stock falls.
Clear the gate
Raise the Gate Pass with driver and security details, then release the vehicle.
Where teams use Logistics every day
Customer order dispatch
Record the vehicle and load for a confirmed sales order and keep the value with it.
Stock transfer to another site
Use the To Warehouse purpose for goods moving between your own locations.
Manufacturer shipping finished goods
Dispatch production output with the manufacturing order or sales order as source.
Wholesaler with daily runs
One logistics record per vehicle per day, each with its own code and responsible user.
Investigating a shortage claim
Match what the customer says arrived against the logistics lines and the gate pass.
Month-end reconciliation
Compare dispatched grand totals with invoices raised in the period.
What changes when Logistics runs on ERPS X
Outcomes you can expect once the application is live for your company.
Every dispatch on record
No load leaves without a code, date, purpose, vehicle, and owner.
Value, not just count
Product lines carry price and total, so dispatch documents mean something to finance.
Clear accountability
The responsible user is named on the record.
Connected to stock and gate
Deliveries transfers and Gate Pass complete the physical and stock trail.
Per-company records
Each ERPS X company keeps its own logistics history in its own database.
Controlled access
Only users granted the Logistics application for their department can create records.
Works with the rest of your ERPS X workspace
Logistics shares one database with every other application in your company workspace. No connectors, no exports — the same record everywhere.
Popular with
Logistics — common questions
What does a logistics record contain?
Does a logistics record reduce stock by itself?
How does Logistics differ from Gate Pass?
Can I record transfers between my own sites?
Who can create logistics records?
Know what left, when, and on which vehicle
Start a 14-day trial, activate ERPS for your company, and record your first dispatch from the Inventory menu.