Arthur Ria
112 lines
5.5 KiB
Markdown
112 lines
5.5 KiB
Markdown
---
|
|
title: "VAS — Value Added Services"
|
|
type: module
|
|
sources:
|
|
- areas/vas/index.md
|
|
- areas/vas/Vas_admin/vas_activities.md
|
|
- areas/vas/Vas_admin/vas_stations.md
|
|
- areas/vas/Vas_config/Vas_admin/vas_templates.md
|
|
- areas/vas/Vas_config/vas_screen_printing.md
|
|
- areas/vas/Vas_config/vas_profile_stock.md
|
|
- areas/vas/Vas_config/vas_container_plastic.md
|
|
- areas/vas/Vas_config/vas_initial_configuration.md
|
|
- areas/vas/TransactionTypes.md
|
|
related:
|
|
- concepts/shipping.md
|
|
- concepts/order-outbound.md
|
|
- modules/multi-carrier.md
|
|
- concepts/stock.md
|
|
- concepts/container.md
|
|
last_compiled: "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 (`VASCode` field) 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
|
|
|
|
1. Shipping order released
|
|
2. Stock picked (standard picking process)
|
|
3. VAS order created (manually from web, or received from ERP via SOR, or auto-generated from profile)
|
|
4. Operator executes VAS activities at VAS station (RF or web confirmation)
|
|
5. 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
|
|
1. Configure VAS stations in EasyS (station type: VAS)
|
|
2. Configure routes from picking/staging areas to VAS stations
|
|
3. Create VAS templates with activities and instructions
|
|
4. (Optional) Create VAS profiles for automatic order generation
|
|
5. 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
|
|
1. After stock is picked, operator goes to VAS station
|
|
2. Select VAS order from RF menu or workstation
|
|
3. For each activity in the template, operator reads instructions and confirms completion
|
|
4. All activities confirmed → VAS order closed
|
|
5. 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
|
|
1. **Screen printing of clothing**: VAS template "Textile personalization" with Activity 1 "Screen printing" (3 instructions) + Activity 2 "Labeling"
|
|
2. **Client stock with custom profile**: VAS profile auto-generates orders for specific owner stock
|
|
3. **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 `VASCode` triggers 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
|