[ADD] barcode_scanner: scanner-first Barcode app core - #1
Open
szalatyzuzanna wants to merge 1 commit into
Open
Conversation
szalatyzuzanna
marked this pull request as ready for review
September 9, 2026 10:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
barcode_scanner — base framework of the Barcode suite
This PR adds
barcode_scanner, the base module and first contribution toOCA/barcode-interface. It's the framework the rest of the Barcode suite builds on; feature modules (warehouse operations, GS1, device camera, inventory counts, purchase…) will follow in their own PRs on top of this base.What it does
barcode_scannerships no business logic of its own. It's a full-screen scanning application shell that other modules extend, the same way Odoo widgets self-register:(
barcode_screens,barcode_scan_handlers,barcode_menu_tiles);feedback, an ORM/API wrapper and shared hooks.
As the base framework it has no end-user screens of its own: the feature modules that plug into these registries provide the actual operations, and land in follow-up PRs.
Developed and maintained by @BinhexTeam.