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)
4.6 KiB
4.6 KiB
title, type, sources, related, last_compiled
| title | type | sources | related | last_compiled | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| eCommerce | module |
|
|
2026-04-10 |
eCommerce
Overview
The eCommerce module adds Just-In-Time (JIT) warehouse management capabilities to Easy WMS, designed for warehouses that receive stock and immediately classify it for pending shipping orders rather than storing it. The key innovation is the ability to classify received items at reception time, routing them directly to packing areas when a corresponding outbound order already exists.
Key capabilities
- JIT reception: at goods receipt, items are immediately classified against active grouped shipping orders
- Three-way classification of received items:
- Single-unit orders: item goes directly to packing area (Multi-Carrier Shipping module)
- Multi-unit orders (more than one unit): item routes to sorting/ungrouping area for subsequent packing
- No matching order: item is putaway to storage
- Grouped order management: orders grouped by waves or groups (same operative for both)
- Integration with Multi-Carrier Shipping for final packaging and labeling
- Item identification via EAN aliases for unambiguous identification across logistic attribute variants
Architecture
The eCommerce module sits between Reception and Shipping in the WMS flow:
Supplier → Reception → eCommerce Classification
↓ ↓ ↓
Single-unit → Packing Multi-unit → Ungrouping → Packing No order → Storage
Important: The system does not handle different logistic variables, conversions (without EAN), or user status variations without customization. Using EAN aliases is strongly recommended so each item presentation is uniquely identifiable.
Configuration
Prerequisites
- Multi-Carrier Shipping module installed
- Items configured with EAN aliases for unambiguous identification
- Grouped shipping orders (waves or groups) released before reception begins
Parameters
| Parameter | Default | Description |
|---|---|---|
ECOMMERCE_RECEPTION_ALLOW_AUTOSELECTION |
False | Auto-select the best receipt for each received item (no manual selection required) |
ECOMMERCE_RECEPTION_ALLOW_MULTIQUANTITY |
False | Allow receiving more than one unit per scan |
ECOMMERCE_RETURN_ALLOW_AUTOSELECTION |
False | Auto-select the best return receipt for each item |
ECOMMERCE_RECEPTION_MAX_SECONDS_TO_CONFIRM |
30 | Maximum seconds after item entry before operator must confirm cart/container/conveyor (useful for concurrent multi-operator reception) |
Operations
Reception process
- Release grouped shipping orders (waves or groups) before receiving goods
- Operator receives items at dock/reception station
- System classifies each item:
- Single-unit order pending: route to packing area → Multi-Carrier Shipping packaging
- Multi-unit order pending: route to sorting/ungrouping zone → later packing
- No pending order: standard putaway to storage location
- If
ECOMMERCE_RECEPTION_ALLOW_MULTIQUANTITY= True, operator can receive multiple units per scan - If
ECOMMERCE_RECEPTION_ALLOW_AUTOSELECTION= True, system automatically selects receipt without manual choice
Post-classification flow
- Items arriving at packing area are processed by Multi-Carrier Shipping module (see multi-carrier)
- Items arriving at ungrouping zone are sorted and later sent to packing
- Items sent to storage follow standard putaway rules
Errors & troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| Items not classified to orders | Orders not released before reception | Release grouped orders first |
| Ambiguous item identification | Items lack EAN aliases with logistic attribute variants | Configure EAN aliases per presentation |
| Multiple operators receiving same item | No confirmation timeout configured | Set ECOMMERCE_RECEPTION_MAX_SECONDS_TO_CONFIRM to appropriate value |
Related
- multi-carrier - Downstream packaging module for items classified as single-unit or post-ungrouping
- marketplaces - Marketplace connectors generate the eCommerce orders that reception classifies against
- reception - Base reception process; eCommerce adds JIT classification layer
- picking - Multi-unit items go through ungrouping/sorting before packing
- order-outbound - Shipping orders must be grouped and released before eCommerce reception