What the Barcode app leaves to standard Odoo
Odoo Enterprise: Barcode app For: Administrator, Warehouse staff Checked on 18.0.0.2.0, 18.0.1.0.0
Rx Tracking (DSCSA) - Barcode changes one thing in Odoo Enterprise's Barcode app: a scan that has a serial number and belongs to a DSCSA product is recorded in the package ledger. Everything else in the app works as in standard Odoo. This page lists what that means, so you can plan which work happens in the app and which in the Inventory forms. Abbreviations: EPCIS: Electronic Product Code Information Services; GTIN: Global Trade Item Number; SSCC: Serial Shipping Container Code; T3: Transaction Report (see the glossary).
What the Barcode app leaves to standard Odoo
Products that aren't DSCSA products
Scans of any product that isn't a DSCSA product work exactly as without the add-on: the lot and serial number come from the code (GS1 codes
10 and 21; when a code has both, the serial wins for a serial-tracked product), and nothing is written to the package ledger. For example,
scanning 010061414107001510THMLOT1#21THM90001 on a receipt that doesn't list the Digital Oral Thermometer (serial-tracked, not a DSCSA
product) adds a line of the thermometer with the serial number THM90001 (Odoo may first ask "Add extra product?": select Ok), and no
package is created.
A product becomes subject to the DSCSA checks only when DSCSA Product is selected on its DSCSA tab (see Set up a DSCSA product).
Paths that don't record DSCSA serials
The following work as in standard Odoo and record quantities by lot, without serials. For DSCSA receipts, deliveries and returns the serial count then refuses Validate ("… scan one DSCSA serial for each unit being validated."), so use them only where no serials are needed, or use the path named.
| In the Barcode app | What happens | Use instead, for DSCSA units |
|---|---|---|
| Batch transfers (Batch Transfers app) | the serial of a DSCSA scan is dropped; only the lot quantity counts (PF-A10-04) | open each receipt or delivery on its own (BC-03, BC-04); batches for internal pick steps only |
| A sealed case's label (SSCC, GS1 code 00) | "To use packages, enable 'Packages' in the settings", or with Packages on, an Odoo package; no unit is recorded (PF-A10-03) | Scan Serials in the Inventory form (IN-04), or scan every unit label |
Scanning an Odoo package (stock.quant.package) on a delivery | its content moves by lot, without serials; Odoo packages are not linked to the package ledger | scan each unit |
| A lot-only code (GTIN and lot, no serial), the + buttons, a typed quantity | quantities without serials | fine for internal moves (BC-05) and lot-level deliveries to exempt small dispensers |
| Inventory count | counts quantities; the serials are named in the DSCSA Serials dialog | BC-08 |
| Scrap (gear icon) | refused for DSCSA products (PF-A10-01) | the Inventory app (BC-09) |
| A transfer created in the app (New) | DSCSA serial scans are refused ("… is not on this transfer.", then "… only 0.0 ordered."); lot scans work (PF-W25-03) | create receipts and deliveries from their orders |
| Manufacturing orders | DSCSA products can't be consumed (see Which outbound paths are refused or skipped) | — |
The batch transfer, Odoo package and manufacturing rows are described from the module's design: Batch Transfers, Odoo's Packages setting and Manufacturing are off in the example database, so they were not performed.
What the app doesn't show
The app shows its own transfer screen. None of the Rx Tracking tabs, buttons, banners or smart buttons of the Inventory forms appear in it, not even in the transfer's details (the title at the top of a transfer). Do these in the Inventory form of the same transfer:
| Task | Where |
|---|---|
| Import the supplier's EPCIS file | Import the supplier's EPCIS file on the receipt |
| See the missing Transaction Statement banner and record the statement (PF-A10-05) | Record the supplier's Transaction Statement |
| See the "GLN missing" warning of a delivery | Handle a document posted without an EPCIS file |
| See or remove the scanned units (DSCSA Packages tab) (PF-A10-02) | Undo or correct a serial scanned by mistake |
| Open the posted DSCSA document, its T3 and EPCIS file | Find, view, download and print DSCSA documents |
The success of a scan shows only as the line flashing, the line being selected and a sound; no text is displayed. A refusal shows as a red notification at the top right for a few seconds, and nothing of that scan is recorded.
Line quantities
The app counts what its own lines hold. The add-on rebuilds a line when a DSCSA unit is scanned, so the app's count can differ from the
order (PF-W25-01): a receipt line shows 2 instead of 2/12; a transfer you reopen shows the scanned count as the demand; the pack and
ship steps after a pick show 0/N although the serials travel with the goods. The Inventory form's Operations and DSCSA Packages
tabs show the order and the units.
Settings of the app that DSCSA scans ignore
- Source Location = Mandatory Scan on an operation type: a DSCSA serial scan is accepted without the location; the server places the unit by its lot.
- Allow full picking validation: allowed by the app, then refused by the serial count for DSCSA lines.