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)
5.4 KiB
title, type, sources, related, last_compiled
| title | type | sources | related | last_compiled | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| VAS - Value Added Services | module |
|
|
2026-04-10 |
VAS - Value Added Services
Overview
The Value Added Services (VAS) module enables the execution of extra value-adding operations on items or containers during the warehouse process - operations that enhance the value, functionality, or utility of goods before shipment. Examples include screen printing, labeling, palletizing, quality verification, and custom packaging.
VAS integrates natively with the shipping and packing flows, allowing VAS work orders to be created manually, received from ERP, or generated automatically from VAS profiles.
Note: VAS during the reception process (inbound VAS) is documented but not yet supported as of current version.
Key capabilities
- VAS templates: define a sequence of activities and instructions for each service type
- VAS profiles: automatically generate VAS orders based on stock and order characteristics
- Integration points: VAS in shipping process (most common), VAS at packing station (Multi-Carrier Shipping integration)
- ERP integration: VAS orders can arrive via SOR message (
VASCodefield) or via direct communication - Per-activity instructions: step-by-step instructions displayed to operators
- Station-based execution: VAS operations performed at dedicated VAS stations
- RF and web interface: confirmation of VAS activities from both RF terminals and web UI
Architecture
VAS building blocks
VAS station: a dedicated station configured in EasyS where VAS operations are performed. Multiple stations can be defined.
VAS template: a named sequence of activities, each with ordered instructions. Templates are reusable across multiple orders.
VAS activity: a specific operation step (e.g., "Screen printing", "Ironing", "Labeling"). Each activity has a code, description, and one or more instructions.
VAS instructions: step-by-step operator guidance within an activity (e.g., "Spread the garment well on the table for ironing").
VAS order: the actual work order generated for a shipment or reception, referencing a template and the stock to be processed.
VAS in shipping process
- Shipping order released
- Stock picked (standard picking process)
- VAS order created (manually from web, or received from ERP via SOR, or auto-generated from profile)
- Operator executes VAS activities at VAS station (RF or web confirmation)
- Standard shipping flow continues (consolidation, truck load, carrier)
VAS profiles
VAS profiles automatically create VAS orders based on:
- Whether the order is for shipping or inbound (profile type)
- Stock characteristics (item, owner, account)
This eliminates manual VAS order creation for recurring service requirements.
Configuration
Initial setup
- Configure VAS stations in EasyS (station type: VAS)
- Configure routes from picking/staging areas to VAS stations
- Create VAS templates with activities and instructions
- (Optional) Create VAS profiles for automatic order generation
- Assign VAS templates to shipping orders (manually, via ERP SOR message, or via profile)
VAS station configuration
VAS stations are defined in EasyS/EasyAssistant. They require routes from the areas where picked stock arrives. Multiple VAS stations allow parallel processing of VAS orders.
Operations
Shipping VAS execution
- After stock is picked, operator goes to VAS station
- Select VAS order from RF menu or workstation
- For each activity in the template, operator reads instructions and confirms completion
- All activities confirmed → VAS order closed
- Stock continues to consolidation/shipping
Packing station VAS (Multi-Carrier integration)
VAS activities can be executed directly at the Multi-Carrier packing station. This allows VAS (e.g., labeling, wrapping) to occur during the packaging process without a separate VAS station visit.
ERP integration (SOR message)
The SOR (Shipping Order Request) message supports a VASCode field that specifies which VAS template to apply to the order. This enables automated VAS order creation for orders arriving from ERP.
Use case examples from documentation
- Screen printing of clothing: VAS template "Textile personalization" with Activity 1 "Screen printing" (3 instructions) + Activity 2 "Labeling"
- Client stock with custom profile: VAS profile auto-generates orders for specific owner stock
- Full container palletizing (container plastic): VAS applied at container level for plastic wrapping
Related
- shipping - VAS orders are created within the shipping process after picking and before consolidation
- order-outbound - SOR message
VASCodetriggers VAS order creation at order reception - multi-carrier - VAS can be executed at Multi-Carrier packing stations
- stock - VAS operations may alter stock characteristics (quality status, packaging)
- container - Container-level VAS (e.g., full container palletizing) affects container attributes