High-frequency deliveries
Daily or JIT call-offs leave no room for a shipment announced by e-mail after the truck has left.
InboundSupplier Logistics
Turn purchase orders into structured shipments with ASN, packaging, labels, delivery documents and returnable packaging processes connected directly to your ERP.
Automotive logistics standards, in daily use.Messages, documents and labels exactly as they appear in the ESS Hub logistics process, connected to SAP and other ERP systems.
End-to-end logistics flow
The supplier prepares the delivery against the order or call-off. ESS Hub turns it into a structured shipment with packaging, labels and documents, and the ERP receives it before the truck does.
ASN / DESADV
The supplier announces the shipment as a structured advance shipping notice: what is on the truck, how it is packed and when it arrives. The plant knows before the goods do, and the ERP receives a DESADV, not a PDF.
Each ASN item points to the scheduling agreement or order it fulfils.
Part, description and quantity per line.
Pallets and boxes with their own identification numbers.
Plant, pickup date, gross weight and volume.
Carrier, pick-up window and transport order where available.
Packed, dispatched, acknowledged by the customer.

How an ASN is created
The supplier works through one guided sequence; the result is a structured message for the ERP and the documents for the truck.
Packaging
The ASN carries the packaging structure logistics needs: which handling units are on the truck, what is inside each of them, and the label that identifies every unit.
Pallets as master units, boxes as single units, each with its own identification number.
Pieces per box, boxes per pallet, following the packaging data sheet agreed for the part and plant.
Packaging specification per part and plant, versioned, with status.
Every handling unit gets its label from the same structure, ready to print.
Label generation
Labels are generated from the shipment and packaging data already in ESS Hub. No re-typing into a label tool, no mismatch between the label on the pallet and the ASN in the ERP.
One label per pallet (master) and per box (single), from the ASN structure.
All labels of a shipment in one print-ready PDF.
Print-ready PDF, or ZPL straight to the label printer.
The number on the label is the number in the message.

Label engine
Delivery documents
Delivery note and transport order are produced from the same ASN data, per shipment, as print-ready PDF. They are available to the supplier and to the plant.
Per ASN, generated from the shipment data.
For the carrier, from the same shipment.
Download or print directly from the shipment.
ASN number, plant, pickup date and transport order on every document.

Returnable packaging
Pallets, containers and lids circulate between suppliers and plants. ESS Hub keeps the balance per packaging type and plant visible to both sides and lets the supplier confirm or dispute the periodic statement.
EUR pallets, KLT containers, lids: current balance per plant and across all accounts.
Reconciled balances across all packaging accounts, published for the period.
The supplier confirms the statement or raises a dispute in the same place.
Every posting with date, direction (to or from the supplier), quantity and reference, per account.
The business problem: returnable packaging is money and capacity moving in a loop. Without shared visibility, balances drift, disputes pile up at year end and containers go missing between plants.
Visibility & exceptions
Both sides work from the same status. The enterprise sees inbound shipments and unconfirmed call-offs per supplier; the supplier sees overdue demands and documents awaiting confirmation.
ASNs in transit, per supplier and plant.
Who has not confirmed yet, visible to the buyer.
Late call-offs flagged in the supplier's demand list.
Packed, dispatched, acknowledged.
Read-and-confirm status per supplier.
Statements confirmed or disputed by the supplier.

ERP & EDI
Portal suppliers create the ASN in the browser. EDI suppliers send the DESADV automatically. Others integrate through API or files. Whatever the channel, the plant receives one structured shipment notice in the ERP.
Automotive & manufacturing
Automotive supply chains run on high-frequency deliveries against scheduling agreements. The processes on this page are not features; they are the daily routine between a plant and its suppliers.
Daily or JIT call-offs leave no room for a shipment announced by e-mail after the truck has left.
InboundLong-term agreements with firm releases: every shipment must point to the demand it fulfils.
DemandLearn about scheduling agreements & supplier call-offsGoods receipt is prepared from the DESADV; an unannounced pallet is an exception at the gate.
DESADVLearn moreAgreed packaging per part and plant: pieces per box, boxes per pallet, returnable container type.
PDSLearn about Packaging Data Sheets (PDS)Handling-unit labels that scan against the ASN, so receiving is a scan, not a search.
GTLLearn about automotive labelsPallets, KLTs and lids circulating between plant and supplier, with a balance that has to reconcile.
EmptiesReal product UI
Screens from the ESS Hub supplier workspace. Demo data, real application.



Request a demo
A live walkthrough of ESS Hub from call-off to ASN, labels, delivery note and returnables, connected to your ERP landscape.