arthur
9ce6ae37be
- Em dashes: 1712 remplaces par tirets simples (86 fichiers + _index.md, en-tete section Limagrain conserve) - Checklists: 24 '- [ ]' -> '- ☐' (3 pages operations, plus de todos Obsidian) - Ancres: 33 reparees (slugs GitHub + ancres HTML <a id> reconnues), 1 reciblee (manuel de reten) - related: tenseflow -> tense-flow, pie -> mechanical-elements, group.md retire (doublon shipping) - Registre: compteur global 122 -> 131 pages - Rapport racine _lint_report.md mis a jour (scan v2 + re-scan final: 0 anomalie) - Aucun fichier limagrain/ modifie (cloisonnement)
101 lines
4.5 KiB
Markdown
101 lines
4.5 KiB
Markdown
---
|
|
title: "Carrier"
|
|
type: concept
|
|
sources:
|
|
- areas/multi_carrier_shipping/multicarrier_admin/views/view_extended_carriers.md
|
|
- areas/multi_carrier_shipping/multicarrier_admin/views/view_deliveries.md
|
|
- areas/multi_carrier_shipping/multicarrier_admin/packing_supported_services.md
|
|
- areas/multi_carrier_shipping/multicarrier_admin/packing_printing.md
|
|
related:
|
|
- concepts/shipping.md
|
|
- concepts/order-outbound.md
|
|
- concepts/labels.md
|
|
- modules/multi-carrier.md
|
|
- concepts/erp-interface.md
|
|
- modules/yard-management.md
|
|
last_compiled: "2026-04-10"
|
|
---
|
|
|
|
# Carrier
|
|
|
|
## Overview
|
|
|
|
A **carrier** in EasyWMS is the transport company that delivers outbound shipments to accounts. At the basic level, the carrier is a master data entity with a code and preferred assignment on shipping orders. When the **Multi-Carrier Shipping module** is active, carriers become **extended carriers** with a full set of integration attributes (label formats, tracking code generation, packaging workflows, staging docks, etc.).
|
|
|
|
---
|
|
|
|
## Base Carrier Attributes
|
|
|
|
| Property | Description |
|
|
|----------|-------------|
|
|
| Code | Unique identifier |
|
|
| Name | Descriptive name |
|
|
| Account (preferred) | Optional preferred carrier for an account (informational) |
|
|
|
|
---
|
|
|
|
## Extended Carrier Attributes (Multi-Carrier module)
|
|
|
|
| Property | Description |
|
|
|----------|-------------|
|
|
| Client code | Account code assigned by the carrier to the organization (provided by carrier) |
|
|
| Stage | Mandatory stage station for loading this carrier's packages |
|
|
| Carrier type | Carrier implementation type (standard known carrier or custom/personalized) |
|
|
| Print label | Whether carrier label (tracking barcode) is printed during packaging |
|
|
| Label report | Report implementing the carrier's label format (auto-filled for standard carriers) |
|
|
| Print delivery note | Whether delivery note is printed per package |
|
|
| Cargo manifest report | Report for cargo manifests (auto-filled for standard carriers) |
|
|
| Weight capture | Whether package weight must be captured during packaging |
|
|
| Ship containers | Whether containers can be shipped directly (vs. individual packages only) |
|
|
| Packaging mode | Preferred packaging mode: ONE_PACKAGE / CHOOSE_NUM_PACKAGES / CAPTURE_STOCK |
|
|
| Files directory | Server directory for tracking code calculation files (custom carriers only) |
|
|
| Additional data | Carrier-specific configuration (provided by carrier) |
|
|
| Sequence code | Sequence for tracking code generation (when required by carrier) |
|
|
| Work process (tracking code) | Workflow for tracking code calculation (custom carriers only) |
|
|
| Waiting time to cancel delivery | Minimum minutes before a delivery can be canceled (carrier-specific) |
|
|
|
|
---
|
|
|
|
## Carrier Selection
|
|
|
|
Carriers are assigned to shipping orders:
|
|
- **Manual assignment**: via SOR ERP message (carrier field on order).
|
|
- **Automatic selection**: Multi-Carrier auto-selection rules match order attributes (destination, weight, dimensions) to eligible carriers.
|
|
- **Account preferred carrier**: informational default, not enforced automatically.
|
|
|
|
---
|
|
|
|
## Delivery Entity
|
|
|
|
When the Multi-Carrier module is active, a **Delivery** combines carrier + consignee (account address) for a specific shipment. Deliveries hold the tracking number, delivery note, package list, and carrier label. One shipping order can produce multiple deliveries (e.g., when `DlvShareDeliveries` is set on the SOR). See [Multi-Carrier](../modules/multi-carrier.md).
|
|
|
|
---
|
|
|
|
## ERP Integration
|
|
|
|
| Message | Direction | Description |
|
|
|---------|-----------|-------------|
|
|
| CAR | ERP→WMS | Create/update carrier master data |
|
|
| RUT | ERP→WMS | Create/update route definitions (used with carriers for truck loading) |
|
|
|
|
---
|
|
|
|
## Interface
|
|
|
|
| Path | Equipment | Description |
|
|
|------|-----------|-------------|
|
|
| `Masters > Carriers` | PC | View and manage base carriers |
|
|
| `Multi-Carrier > Extended carriers` | PC | Extended carrier attributes (Multi-Carrier module) |
|
|
| `Multi-Carrier > Deliveries` | PC | View deliveries per carrier |
|
|
|
|
---
|
|
|
|
## Related
|
|
|
|
- [[shipping]] - shipping orders reference carriers; routes and loads assign containers to carriers
|
|
- [[order-outbound]] - SOR message can include carrier assignment; carrier determines delivery structure
|
|
- [[labels]] - carrier labels (tracking barcodes) printed during Multi-Carrier packaging
|
|
- [[multi-carrier]] - full carrier integration: packaging stations, tracking, delivery lifecycle
|
|
- [[yard-management]] - carrier appointments at yard checkpoints and docks
|
|
- [[erp-interface]] - CAR message syncs carrier master; RUT message sends route data
|