Skip to main content

Sync location for Checkout operations

Project description

Beta License: AGPL-3 OCA/wms Translate me on Weblate Try me on Runbot

Regroup moves at the same location when they reach an operation type.

Example of use case:

  • We use several operation types for Picking Transfers (Pick Shelves, Pick Reserve)

  • We use several operation types for Packing (Pack, Pack Post)

  • The “Checkout Synchronization” flag is activated on the 2 Packing operation types

  • The Packing can occur in several areas (Packing/PACK1, Packing/PACK2, Packing/PACK3)

Based on these assumptions, we have these pickings, all for the same order:

  • SHELF001, pick 2 goods in the shelves

  • RESER001, pick 2 goods in the reserve

  • PACK001, pack 3 of the goods (2 from SHELF001, 1 from RESER001)

  • PPOST001, pack the remaining good of the reserve

The operator uses the button “Checkout Sync” on a pick transfer, for instance SHELF001, and select Packing/PACK2 as destination. We want all the lines that reach PACK001 to be updated with:

  • The move lines (except the one that goes to PPOST001) must now reach Packing/PACK2

  • The same moves’ destination must reach Packing/PACK2 as well: we constrain the user to move the goods there as we want to move all the goods at the same place for the packing.

  • As the moves’ destinations are updated to the same packing location, new move lines will have the correct destination as well

Checkout Synchronization Assistant Screen

Notes:

Works best when used with stock_available_to_promise_release:

  • When using the mentioned module, we assume that we release moves (which creates the whole chain of moves) only when we know that we have the quantities in stock (otherwise the module splits the delivery). Any exception (which is now rare when you release this ways) that would lead to a backorder is handled by canceling the remaining line.

  • When the module is not used, then the destination of the backorders may be changed at the same time

Compatible with stock_dynamic_routing.

Table of contents

Configuration

Activate syncing on the picking type form view (Inventory > Settings > Operations Types) by marking Checkout Synchronization.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Camptocamp

Contributors

Other credits

The migration of this module from 13.0 to 14.0 was financially supported by Camptocamp

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/wms project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

File details

Details for the file odoo14_addon_stock_checkout_sync-14.0.1.1.0-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo14_addon_stock_checkout_sync-14.0.1.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 41e529e50a85c7f6b076be53e1265e3cc8ff63fd2a326af1d01dc76ab6a03764
MD5 afd4baae50825cae50364c30e7ba45f7
BLAKE2b-256 5dc2b593ff6e392d295c3ad4caba226d6f0fe7ba9a4a3d4bfd0e5103c9e84056

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page