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.3 KiB
5.3 KiB
title, type, sources, related, last_compiled
| title | type | sources | related | last_compiled | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Store Fulfillment | module |
|
|
2026-04-26 |
Store Fulfillment
Overview
The Store Fulfillment module integrates retail store stock management with Easy WMS, enabling a central warehouse to supply one or more physical stores. It handles the full cycle: store stock orders, automatic replenishment, POS integration, store returns to warehouse, and store counting.
The module is designed for warehouses that simultaneously fulfill B2B/B2C shipments and supply their own retail stores.
Key capabilities
- POS integration (Direct Selling Systems): sales/returns processed at POS automatically update WMS stock
- On-demand store orders: stores request specific stock from the warehouse
- Manual replenishment: warehouse sends stock to stores based on min/max review
- Automatic replenishment: daily job maintains configured min/max stock levels at each store
- Store returns: stock returned from stores back to warehouse
- Store inventory counts: count existing stock in stores
Architecture
Layout constraints
- Star structure only: one central warehouse supplies all remote stores (multi-hub not supported)
- No store-to-store: direct transfers between stores are not supported
- No desk stations: use local store stations instead of desk warehouse stations
- Multi-site: each store is a separate site (warehouse) in the system
POS integration flow
EasyWMS receives a TPV01 message from the ERP (or POS connector) each time a sale or return is processed at a POS terminal:
- Sale or customer return processed at POS terminal
- POS sends transaction to ERP
- ERP forwards a TPV01 message to EasyWMS
- WMS immediately decrements store stock (sale) or increments (return) in real time
- No manual WMS action required for POS-driven stock changes
The real-time nature of TPV01 means EasyWMS always reflects the current store stock - no end-of-day reconciliation needed for POS transactions.
Replenishment flows
| Mode | Trigger | Process |
|---|---|---|
| On-demand order | Store requests specific items | Creates outbound order from warehouse to store |
| Manual replenishment | Warehouse reviews min/max | Operator initiates stock transfer to store |
| Automatic replenishment | Daily job checks min/max levels | System generates transfers when stock below minimum |
ERP integration (inter-warehouse transfers)
Store fulfillment transfers between central warehouse and stores can be ERP-driven via two dedicated messages:
| Message | Direction | Description |
|---|---|---|
| TOR01 | ERP → WMS | Transfer order: ERP requests a stock transfer from central warehouse to a store (or vice versa). WMS creates the corresponding outbound + inbound orders. |
| TOF01 | WMS → ERP | Transfer order finalization: WMS notifies ERP that the transfer has been completed (goods shipped from warehouse and received at store). |
| TPV01 | ERP → WMS | POS sale/return: decrements (sale) or increments (return) store stock in real time. |
TOR01/TOF01 follow the standard transfer order lifecycle managed by the Store Fulfillment module. They can also be used for store-to-warehouse returns.
Real-time store stock view
Managers can view real-time stock per store from the WMS interface. The view shows:
- Current stock quantity per item per store
- Stock in transit (shipped from warehouse but not yet received at store)
- History of POS transactions (TPV01 events)
Configuration
Prerequisites
- Configure star layout: central warehouse + remote store warehouses
- Configure store stations (local, not desk type)
- Set min/max stock levels per item per store
- Integrate POS systems via Store Fulfillment connector
Key configuration options
| Option | Description |
|---|---|
| Min/max stock levels | Trigger thresholds for automatic and manual replenishment |
| POS connector | Integration settings for direct selling system |
| Store layout | Local stations, not desk-type stations |
Operations
Store orders (warehouse perspective):
- Receive store order (manual or automated)
- Pick stock at central warehouse
- Ship to store via standard outbound process
Store replenishment (automatic):
- Daily job reviews all stores' stock levels
- For items below minimum: generates transfer task to bring stock up to maximum
- Executed during off-hours; stores receive stock next operating day
Store returns:
- Store operator scans items for return via RFT
- Stock transferred back to central warehouse
- WMS creates receipt process for returned items
Store counts:
- Operator counts store stock via RFT
- Count process similar to standard location/item count
- Results update store stock records
Related
- order-outbound - Stock transfers from central warehouse to stores are outbound orders
- order-inbound - Store returns processed as inbound orders
- stock - Store stock maintained as separate WMS stock records per store warehouse
- replenishment - Replenishment logic controls min/max levels and transfer generation
- count - Store counting uses standard WMS count processes adapted for store environment