Exceptions: quarantine, scrap and trace requests
Hold and release lots, scrap units, and answer trace requests within their deadline.
Requires: Rx Tracking (DSCSA). Works in Odoo Community and Enterprise.
Pages
Handle a recall of a lot we own
When a manufacturer recalls a lot, or you find that a lot of your own stock is suspect, these procedures, in this order, hold the lot, find who received it, bring the units back and keep the record. Your procedure decides whom you notify and how: the software notifies no one. For units a 3PL keeps for owners, see Recall an owner's lots.
- Hold the lot: Quarantine a lot so it can't be reserved or shipped. For several lots, quarantine each one.
- Find the customers who received it: Find, view, download and print DSCSA documents, searching Lot with the Outbound filter, grouped by Trading Partner. To see each unit and where it went, use Look up a unit in the package ledger: search the lot, remove the In Stock filter and group by Shipped To.
- When an authority or a trading partner asks for the lot's records, answer with a trace request: Log a trace request, Search the records by Lots, then Respond with the response zip.
- Take the units back: Receive a saleable customer return with its serials, or Take back units shipped at lot level to a small dispenser. The lot stays quarantined.
- Send the units to the manufacturer, which a quarantined lot allows: Send a non-saleable return to the supplier; or destroy them: Scrap DSCSA units, naming each unit's serial.
With Odoo Enterprise's Suspect Product add-on, the lot's investigation lists the customers for you: Find the trading partners to notify.
Known issue (PF-A03-02): units shipped at lot level (to a small dispenser, without scanning serials) stay In Stock in the package ledger and have no Shipped To, so step 2's ledger view misses them. The document search of step 2 finds their documents: use it to list the customers.
Known issue (PF-A04-07): a lot is quarantined one at a time; the lot lists have no action for several lots.