Introduction to Odoo Warehouse Management
29. Special Cases
1. Odoo Warehouse Management Josse Colpaert, Technical Coordinator
3. Use Case Bert's store needs to adapt for growth
7. Configuration Warehouses and routes
21. Operating Making sure our operators can do their work
35. Customer References Used by 2.000.000 users worldwide
8. Configuration Conclusion Operating Operating Configuration Use Case
14. Example interWH route Conclusion Special Cases Operating Configuration Use Case
15. Example interWH route Conclusion Special Cases Operating Configuration Use Case
17. Example interWH + crossdock Conclusion Special Cases Operating Configuration Use Case
32. Logistic Unit vs. Packaging ● Logistic unit : pallet, box of certain dimensions ● Packaging : how one product can be arranged
11. Pull rules Conclusion Special Cases Operating Configuration Use Case Customers Take
30. Special Cases ● Negative stock ● Returns ● Multi-company and owner (see next slide) ● Packaging
9. Configuration Conclusion Operating Operating Configuration Use Case Show configuration of warehouse : 2 step in, 3 step out + shops
10. Configuration Conclusion Operating Operating Configuration Use Case Show configuration of warehouse : 2 step in, 3 step out + shops
16. Example interWH + crossdock Conclusion Special Cases Operating Configuration Use Case Warehouse : Product : Result :
22. From 3 to custom picking types Conclusion Special Cases Operating Configuration Use Case ● Allows to follow up operations by picking type <<screenshot dashboard>>
2. 1 Topics Use Case 2 Configuration 3 Operating 4 Special Cases 5 Conclusion
6. Use Case Scenario : Products Conclusion Special Cases Operating Configuration Use Case Vegetable Bricks: CROSSDOCK Regular Bricks : 2-step in / pick-pack-ship out Coffee : produced Coffee Beans : needed to produce the coffee
12. Push rules Conclusion Special Cases Operating Configuration Use Case ● Manual Purchase Order : ● Apply push rule in WH/Input
31. Inter company rules ● Intercompany vs Intracompany interwarehouse location ● Real-time valuation : when changing company ● Locations / warehouses are related to a company, but « owner » makes it possible to store something of someone else
34. " " From the announcement of this talk The Odoo Warehouse Management System fulfills the simplest needs in an intuitive way, fulfills complex needs by default and is the platform of choice for development of the most complex needs. Conclusion
5. Use Case Scenario Conclusion Special Cases Operating Configuration Use Case Supplier Bert's Central Depot Jim's Shop Frank's Shop
36. Odoo email@example.com +32 (0) 2 290 34 90 www.odoo.com R&D and services office Chaussée de Namur 40 B-1367 Grand Rosière Sales office Avenue Van Nieuwenhuyse 5 B-1160 Brussels Thank You
27. Manufacturing ● Finished Products ↔ Components traceability – Produce wizard based on stock reserved instead of moves ● Simplified : no picking before ● MTO if from component in MTO route, otherwise MTS
4. Use Case Scenario Conclusion Special Cases Operating Configuration Use Case Bert has a little shop with vegetable green Lego bricks and other Lego bricks. His shop is growing, but growth is limited by his shop being far from the city. He decides to work together with his friends Jim and Frank who will open shops in the city. Bert’s shop would function as a central depot.
24. Back orders and splitting of moves ● Splitting moves : – We keep track of the move it was split from (e.g. to check if stock needs to come from original moves) – Procurements and moves have a destination move and original moves ● In case of split propagation (forward) the destination of the move will alter, but not the procurement's ● Needs to work without procurements with push rules also
28. Benefits ● All logic towards extra moves, backorders, splitting, reservation of stock,... is already handled by the system ● Easy custom development : – Grouping of moves in pickings allows easy development of batch picking, dock & yard management, ... – Creating own putaway and removal strategies ● FIFO, LIFO, FEFO
13. Pull and push into routes Conclusion Special Cases Operating Configuration Use Case ● Pull and push are bundled into routes that can be applied on : – Procurement (Sale order) – Product and product categories – Warehouse
26. Pack Operations ● Take some product / Take entire pack ● Preparing pack operations for the picking: – Are created based on quants reserved : ● Location from / quantities / lots / packs from – Will be put somewhere according to putaway strategy – Take entire packs as much as possible ● Bar code interface : – Warehouse operator can decide otherwise
20. In our use case Conclusion Special Cases Operating Configuration Use Case ● Vegetable products get crossdock route ● Reordering rules (procurement groups) ● Need to define putaway strategy : – Regular products => Stock / Regular Products – Components => Stock / Components – Finished products => Stock / Finished Products
18. Routes Conclusion Special Cases Operating Configuration Use Case ● Benefits : – Integrated supply chain management and warehousing – Simpler configuration than push/pull only – Consistent also for dropshipping – Easy configuration of base config in warehouse form – Very practical for creating Proof of Concepts
25. Reservation of stock ● Reservation of stock has custom domain – Has to come from original moves – Has to come from returned move ● Picking : – Ready to Transfer : ● When all quants (stock) are reserved – Partially Available ● When the move type of the picking is direct and at least some stock is available ● Removal Strategy : FIFO/LIFO/FEFO
23. Back orders and splitting of moves ● Moves : – Determine 'parent location flow' based on pull/push rules – Cancelling splitting them will mostly be propagated ● Cancelling moves : forward direction ● Cancelling procurements : backwards direction – Should not contain anything anymore with lots/packing ● Pickings – Are a 'related' to the moves in them : moves get created and a picking is assigned afterwards – Moves can easily be transferred to another picking, for example when creating backorders
19. Features Comparison Warehouse config Simple to understand Can tackle a lot of basic cases already Not for more complicated situations Routes config You can do complex routes without any developments Ideal for Proof of Concepts Not that easy to understand You can start with the warehouse configuration and continue on the configuration the system created
- 5444 Total Views
- 905 Website Views
- 4539 Embeded Views
- Social Shares
- 1 Likes
- 0 Dislikes
- 0 Comments
- 0 Facebook
- 0 Twitter
- 0 Google+
- 5 www.odoo.com
- 10 accounts.odoo.com
- 7 onlinesync.odoo.com
- 1 www.google.com.sa
Keynote: Odoo 9 New Features41594 Views .
Odoo Mobile Development Framework & App build with it14811 Views .
Odoo 9 New Design- The rationales behind it11580 Views .
How A/B testing can help you optimize your website10889 Views .
Open Source Licenses10805 Views .
Import and export data - Tips & Tricks9778 Views .
Shipper integration - UPS, DHL, FedEx7951 Views .
UX best practices to create your module6366 Views .
Keynote: Odoo Strategy 20156291 Views .
Contributing to the Odoo Community Association (OCA)5966 Views .
How to use Odoo in a Restaurant5811 Views .
Odoo 9: New Business Model5594 Views .
Performance Tips & Tricks5397 Views .
VOIP: One-click Button to Automate Calls5314 Views .
Odoo cms Performance Comparison and Optimisation5244 Views .
State of the Odoo JS framework4627 Views .
How to use Odoo in a service company4455 Views .
First steps in Odoo dev4436 Views .
Advanced Features of the API4087 Views .