Industries · Logistics
You move things, and every movement accumulates costs from carriers, fuel, handling and demurrage. Attaching those to the right job, before the customer is invoiced, is most of the battle.
The operation
A logistics business moves things, and every movement accumulates costs from carriers, fuel, handling and demurrage. If those costs arrive after the customer is invoiced, job profitability is a guess and the overage is never recovered.
AlpineERP attaches costs to the shipment that caused them. Carrier invoices, fuel, handling and accessorials post against the job as they are incurred, so margin is real before billing. A shipment is a record holding parcels, tracking, milestones and documents that anyone can open, vehicles run as assets with depreciation and maintenance, and accessorial charges are raised through a workflow rather than an act of memory.
What matters here
Carrier invoices, fuel, handling and accessorials posted to the shipment they belong to, so job margin is real before billing.
Parcels, tracking, milestones and documents on one object that anyone can open, instead of a thread only one person can follow.
Vehicles as assets with depreciation, maintenance schedules and downtime recorded against the operations they interrupted.
Accessorial charges raised as they are incurred, so recovery is a workflow rather than an act of memory.
What usually goes wrong
Try building it
Describe the rule you would add and Alpine builds the fields, workflow and permissions for it.
Questions
Yes, over the API and webhooks. Booking, status milestones and carrier invoices can be wired in with retries, so shipment status stops living with the person who booked it.
Costs post against the shipment as they occur, so accumulated cost versus what you will bill is visible live, and Alpine can flag a job before it slips below margin.
Vehicles run as assets with depreciation, maintenance schedules and downtime recorded against the operations they interrupted.
