Troubleshooting: owner receipts and owner isolation

3PL add-on For: Warehouse staff, Compliance manager Checked on 18.0.0.2.0, 18.0.1.0.0

What to do when a receipt held for an owner, its supplier file, a custody receipt or a move of an owner's units is refused. The first part covers owner isolation: the refusals that keep one owner's units apart from another owner's and from your own stock, on every transfer. Entries are ordered from the most frequent.

Several refusals are also met on owner deliveries, returns and title transfers; their entry is here. The owner, counterparty and facility checks at Validate have their own page: Troubleshooting: facility checks.

Error: "DSCSA owner isolation (3PL): …"

What you see: an Invalid Operation dialog (or an Oh snap! dialog when you save a form) with the heading and one line per problem:

DSCSA owner isolation (3PL):
- LABEL: MESSAGE

LABEL is the product and transfer (for example [DEMO-DPZ-20] Demoprazole 20 mg Delayed-Release Capsules, 30 count (WH/IN/00040)) or the transfer alone. In Scan Serials, the same lines come after "Nothing was registered. Fix these scans and try again:", each starting with "Line N: Serial SERIAL …".

When: at Mark as Todo, Save, Scan Serials ‣ Register or Validate on any transfer that moves DSCSA units held for an owner, or that would take them.

Cause: each owner's DSCSA units stay the owner's until a title transfer: a transfer is for one owner (or for your own stock), takes only that owner's units, and never changes the owner of units it has touched. Background: these rules keep one owner's units from ever serving another owner's order. By default they apply to DSCSA products only; the company's Owner isolation for non-DSCSA products policy extends them.

Remedy: find the line in this table, then follow the entry it names.

Line (distinctive part)	Where you meet it	Entry
"… is held for OWNER, not for TARGET: it can't be used on this transfer."	a scan	Held for another owner
"… was announced by the supplier for OWNER's receipt RECEIPT: receive it there." / "… for our own receipt …"	a scan on a receipt	Announced for another receipt
"…: hold DSCSA stock for the owner company OWNER, not for its contact CONTACT."	Mark as Todo, Validate	A contact instead of the owner
"…: OWNER has no active owner profile, so DSCSA stock can't be held for it (Rx Tracking > 3PL)."	Mark as Todo, Validate	No active owner profile
"… is on our sale or purchase order: its DSCSA units can't be held for OWNER. …" / "…: units held for OWNER can't be on our sale or purchase order. …"	Save, Mark as Todo, Validate	On our order
"…: unreserve the transfer (or undo its scans) before changing the owner its units are held for."	Save after changing Held for Owner	Unreserve first
"… mixes DSCSA stock of several owners (…): one transfer per owner." / "…: the move is held for OWNER but the transfer for OWNER." / "…: a line (lot LOT) takes units held for OWNER, but the move is for OWNER." / "…: serial SERIAL is held for OWNER, not for OWNER."	Mark as Todo, Validate; mostly imports and API calls	One owner per transfer
"… is done: the owner its DSCSA units were held for can't be changed." / "…: this operation is done; the owner of its units (…) can't be changed to …" / "…: this operation is done and involves units held for an owner; its packages can't be changed." / "…: the owner of DSCSA stock can't be changed directly (… → …)."	editing a done transfer, a done line or a stock line; mostly imports and API calls	Owner of done units
"Package PACKAGE would hold units of several owners (…): unpack it first, one package per owner."	putting units in an Odoo package	Mixed owners in a package
"… (custody receipt): … instruction … is required …" and the other instruction lines	Validate on a custody receipt	Custody receipt without its instruction
"… was sold by SELLER: it can only come back into that seller's stock, not into …" / "…: returned serial SERIAL was sold by SELLER, not by OWNER."	a customer return	Troubleshooting: 3PL returns and adjustments
"…: only N more unit(s) of lot LOT held for OWNER are available in LOCATION, but N were scanned." / "…, lot LOT: N package(s) held for OWNER scanned but N of its unit(s) picked."	just-in-time deliveries	Troubleshooting: just in time and consignment

In the lines, "our own stock" (or "us") means your company's stock, not held for any owner.

Who can fix it: Rx Tracking User or Manager for scans and transfers; Rx Tracking Manager for owner profiles.

Error: "… is held for …, not for …: it can't be used on this transfer."

What you see: in Scan Serials:

Nothing was registered. Fix these scans and try again:
Line 1: Serial 200000000012 is held for our own stock, not for Northwind Generics LLC: it can't be used on this transfer.
Line 2: Serial 600000012001 is held for Summit Specialty Pharma Inc., not for Northwind Generics LLC: it can't be used on this transfer.

When: scanning units on a transfer, for example an owner delivery in Pick, scan and ship an owner order, or one of the owner's units on your own transfer.

Cause: the scanned unit belongs to another owner (here Summit Specialty Pharma Inc.) or to your own stock, and the transfer is for another owner (here Northwind Generics LLC).

Remedy: resolution. Set the unit aside and scan a unit of the transfer's owner. Check the unit's owner on its package form (Held for Owner; Inventory ‣ Rx Tracking ‣ Packages). Nothing was registered: correct or delete the line, then select Register again.

Who can fix it: Rx Tracking User or Manager.

Error: "… was announced by the supplier for …'s receipt …: receive it there."

What you see: in Scan Serials on a receipt:

Nothing was registered. Fix these scans and try again:
Line 1: Serial 600000020001 was announced by the supplier for Summit Specialty Pharma Inc.'s receipt WH/IN/00011: receive it there.

or "Serial SERIAL was announced by the supplier for our own receipt RECEIPT: receive it there."

When: scanning in Scan and validate an owner receipt, or on your own receipt.

Cause: a supplier's file attached to another open receipt (another owner's, or yours) announces this serial. The unit belongs to that shipment. The same owner's other receipt, or a backorder of the receipt, accepts it.

Remedy: resolution. Put the unit with the shipment it belongs to and scan it on the receipt named. If the goods really arrived together, check with the owner and the supplier which file is right before you receive anything.

Who can fix it: Rx Tracking User or Manager.

Error: "…: hold DSCSA stock for the owner company …, not for its contact …"

What you see:

DSCSA owner isolation (3PL):
- [DEMO-DPZ-20] Demoprazole 20 mg Delayed-Release Capsules, 30 count (WH/IN/00040): hold DSCSA stock for the owner company Northwind Generics LLC, not for its contact Northwind Generics LLC, Dana Reyes.

When: selecting Mark as Todo or Validate in Create a receipt held for an owner, or on any transfer held for an owner.

Cause: Held for Owner names a contact or an address of the owner (here Dana Reyes), not the owner company. Stock is held for the company only.

Remedy: resolution. In Held for Owner, choose the company, for example Northwind Generics LLC, then select Mark as Todo again.

Who can fix it: Rx Tracking User or Manager.

Error: "…: … has no active owner profile, so DSCSA stock can't be held for it (Rx Tracking > 3PL)."

What you see:

DSCSA owner isolation (3PL):
- [DEMO-DPZ-20] Demoprazole 20 mg Delayed-Release Capsules, 30 count (WH/IN/00041): Granite State Rx Supply LLC has no active owner profile, so DSCSA stock can't be held for it (Rx Tracking > 3PL).

When: selecting Mark as Todo or Validate on a transfer held for a partner.

Cause: Held for Owner names a partner that is not one of your owners (here a supplier), or an owner whose profile is archived (the relationship ended, for example Cedar Ridge Pharmaceuticals Inc. in the example database).

Remedy:

• Wrong partner: resolution. Choose the owner company in Held for Owner.
• A new or returning owner: resolution. An Rx Tracking Manager creates or re-activates its profile, see Create an owner profile and Change, end or re-open an owner relationship; then select Mark as Todo again.

Who can fix it: Rx Tracking User or Manager (the partner); Rx Tracking Manager (the profile).

Error: "… is on our sale or purchase order: its DSCSA units can't be held for …"

What you see: when you save:

DSCSA owner isolation (3PL):
- WH/IN/00021 is on our sale or purchase order: its DSCSA units can't be held for Northwind Generics LLC. An owner's goods ship on an owner order and arrive on an owner receipt.

or, for a line created by an import or an API call, "LABEL: units held for OWNER can't be on our sale or purchase order. An owner's goods ship on an owner order; our order takes them only after a title transfer."

When: setting Held for Owner on the receipt of one of your purchase orders (or the delivery of one of your sales orders).

Cause: goods on your own order are your stock. An owner's goods arrive on a receipt of their own, with no order of yours, and leave on an owner order.

Remedy: resolution. Select Discard changes. Receive the owner's goods on a receipt held for the owner (Create a receipt held for an owner). Your sale takes an owner's units only after a title transfer: see Owner stock and own stock.

Who can fix it: Rx Tracking User or Manager.

Error: "…: unreserve the transfer (or undo its scans) before changing the owner its units are held for."

What you see: when you save:

DSCSA owner isolation (3PL):
- WH/IN/00011: unreserve the transfer (or undo its scans) before changing the owner its units are held for.

or the same text starting with the product and transfer.

When: changing Held for Owner on a transfer that has scanned units or reserved lines.

Cause: units already scanned or reserved belong to the owner they were taken for; changing the owner would silently move them.

Remedy: resolution. Select Discard changes. If the owner really is wrong, remove the scans first (the ✖ Remove this scan icon on the DSCSA Packages tab, see Undo a scan) or select Unreserve on a delivery, then change Held for Owner, save, and scan again.

Who can fix it: Rx Tracking User or Manager.

Error: "… mixes DSCSA stock of several owners (…): one transfer per owner."

What you see: one of these lines under "DSCSA owner isolation (3PL):":

- TRANSFER mixes DSCSA stock of several owners (OWNERS): one transfer per owner.
- LABEL: the move is held for OWNER but the transfer for PICKING-OWNER.
- LABEL: a line (lot LOT) takes units held for LINE-OWNER, but the move is for OWNER.
- LABEL: serial SERIAL is held for PACKAGE-OWNER, not for OWNER.

When: confirming or validating a transfer whose lines were created or edited by an import or an API call. The form doesn't let you set a different owner per line, and its Pick From list doesn't offer another owner's stock.

Cause: a transfer carries the units of one owner (or your own stock) only. A line, a move or a serial of the transfer belongs to another owner.

Remedy: resolution. Split the goods into one transfer per owner: remove the other owner's lines (or correct the import file) and create a separate transfer for them.

Who can fix it: Rx Tracking User or Manager; whoever runs the import.

Error: "… is done: the owner its DSCSA units were held for can't be changed."

What you see: one of:

TRANSFER is done: the owner its DSCSA units were held for can't be changed.
LABEL: this operation is done; the owner of its units (OLD-OWNER) can't be changed to NEW-OWNER. Units change owner only through a title transfer.
LABEL: this operation is done and involves units held for an owner; its packages can't be changed.
PRODUCT: the owner of DSCSA stock can't be changed directly (OLD-OWNER → NEW-OWNER). Units change owner only through a title transfer.

When: changing the owner of a done transfer, of a done line or of stock, through an import or an API call. The forms show these fields read-only.

Cause: the owner of DSCSA units is part of their record. It changes only through a title transfer, which records the change and its documents.

Remedy: resolution. To buy an owner's units, see Buy an owner's units in place. If a receipt was held for the wrong owner and is already done, ask an Rx Tracking Manager: the units have to go back out and in again, or change owner by a title transfer.

Who can fix it: Rx Tracking Manager.

Error: "Package … would hold units of several owners (…): unpack it first, one package per owner."

What you see:

Package PACKAGE would hold units of several owners (OWNERS): unpack it first, one package per owner.

When: putting units into an Odoo package (Put in Pack, or a destination package on a line) that already holds another owner's units or your own.

Cause: an Odoo package holds the units of one owner only.

Remedy: resolution. Use a new package for these units, or unpack the existing one first.

Who can fix it: Rx Tracking User or Manager.

Error: "The buyer in the file has GLN …, but … has …"

What you see:

FILE-NAME was not imported:
- The buyer in the file has GLN 0614141000067, but Northwind Generics LLC has 0614141000050. If the file is right, add that GLN to Northwind Generics LLC (or one of its addresses); otherwise ask the supplier for a corrected file.

When: selecting Attach (or Import in Import EPCIS) in Attach the supplier's EPCIS file to an owner's open receipt, and for a late file.

Cause: on an owner receipt, the file's buyer must be the receipt's owner. The GLN in the file belongs to another owner (here Summit Specialty Pharma Inc.), to you, or to nobody recorded; or the owner's GLN in Odoo is wrong. A file is never re-assigned to another owner.

Remedy:

• The file is another owner's: resolution. Attach it to that owner's receipt (Find Receipt from the 3PL menu proposes it). Don't add another owner's GLN to this owner, even though the message suggests it: that owner's later files would then be accepted on this owner's receipts (PF-W14-03).
• The file is right and the owner has a second GLN: resolution. Record it on the owner company or one of its addresses. See Onboard a trading partner: DSCSA role, GLN and address.
• Otherwise: ask the owner to get a corrected file from the supplier.

Who can fix it: Rx Tracking User or Manager (the receipt); Rx Tracking Manager (the owner's GLN).

Error: "The file ships the goods to location GLN …, which is not one of our GLNs …"

What you see:

FILE-NAME was not imported:
- The file ships the goods to location GLN 0614141002122, which is not one of our GLNs (0614141000012, 0614141002016), and names no possessing party of ours: it doesn't describe a shipment to our warehouse. Ask the supplier for a corrected file (the destination location, or the possessing party, must be our warehouse).

When: attaching a file to an owner's open receipt. Not checked while your company has no GLN.

Cause: an owner's supplier must ship to your warehouse. The file's ship-to location is someone else's (for example the owner's own site), and the file doesn't name you as the possessing party.

Remedy:

• The GLN is really one of yours: resolution. Record it on your company or the warehouse, see Give a warehouse its own GLN.
• Otherwise: ask the owner to get a corrected file (ship-to your warehouse, or you as the possessing party).

A file that names another ship-to location but you as the possessing party is accepted; on a late file it gives the warning "The ship-to location of the file (GLN …) is not one of our GLNs; the file names us as the possessing party."

Who can fix it: Rx Tracking User or Manager; Administrator for your GLNs.

Error: "… is a custody receipt (…), but the file names another seller …"

What you see:

FILE-NAME was not imported:
- WH/IN/00047 is a custody receipt (the owner's own goods, no transaction), but the file names another seller (GLN 0399990000009): it is a sale to Northwind Generics LLC. Record the receipt as the owner's purchase.

When: attaching a supplier's file to a receipt whose Owner Receipt Kind is Custody (no transaction).

Cause: the file is a sale from a supplier to the owner, so the goods are the owner's purchase, not the owner's own goods.

Remedy: resolution. An Rx Tracking Manager sets Owner Receipt Kind to Owner's purchase (while the receipt is open), then attach the file again (Attach the supplier's EPCIS file to an owner's open receipt).

Who can fix it: Rx Tracking Manager.

Error: other refused supplier files on an owner receipt

What you see: one of these, alone or under "FILE-NAME was not imported:":

A late supplier file is attached to a done receipt held for an owner (WH/IN/00042 is not one). Import it on the open receipt instead.
A supplier file is already recorded for WH/IN/00010 (3pl_nwg_open-receipt_DEMO-DPZ-20_6ea.xml).
FILE-NAME can't be read as an EPCIS 1.2 file: The file is not well-formed XML and cannot be read: …
The file announces no serialized packages, so there is nothing to match with the receipt.
N package(s) have no lot number in the file: IDS.
None of the packages the file lists was received on WH/IN/00039: is it the right file?
GTIN GTIN-NUMBER is not on any product: set it on the product (Rx Tracking tab) and import again.

When: attaching a file to a done owner receipt (a late file, see Release a data-pending hold with the supplier's late EPCIS file), or any file that can't be read.

Cause and remedy:

• "… is not one": the done receipt is not an owner receipt of DSCSA products (for example it holds only non-DSCSA products, or it is your own receipt). Resolution: choose the right receipt.
• "already recorded": the receipt already has its supplier file. Resolution: nothing to do; open the file from the EPCIS Files smart button. A corrected file is handled by the owner's compliance contact with the supplier.
• "can't be read" or "no serialized packages": not an EPCIS 1.2 XML file with serialized units (for example a scans text file). Resolution: attach the supplier's .xml file.
• "no lot number": the file is incomplete. Workaround: ask the owner for a corrected file.
• "None of the packages … was received": the file belongs to another shipment. Resolution: attach it to its own receipt.
• "GTIN … is not on any product": see Error: "GTIN … is not on any product".

On an open receipt the file goes through the core import, whose messages are in Troubleshooting: receiving, for example Error: "… can't be read as an EPCIS 1.2 file".

Warnings (the file is imported, the import lists them): "… has no GLN in Odoo, so the buyer in the file (GLN …) could not be checked. Record the GLN so later files are checked." (record the owner's GLN); "Products that are not DSCSA products were left out: …."; "The seller has not affirmed the DSCSA Transaction Statement in this file: the received lots stay on hold until it is recorded." (see Record a missing Transaction Statement after validation). The full list is in Warnings on a supplier file's Warnings tab.

Who can fix it: Rx Tracking User or Manager.

Find Receipt proposes the wrong receipt, or none

What you see: after Find Receipt, Receipt shows another owner's receipt, a custody receipt or an unrelated receipt, and Attach is refused or attaches the file where it doesn't belong; or the dialog says "No open receipt held for an owner matches this file. Create the owner's receipt first."

When: in Attach the supplier's EPCIS file to an owner's open receipt, from Inventory ‣ Rx Tracking ‣ Attach Supplier Data (in the 3PL ‣ Operations section).

Cause: Find Receipt ranks open owner receipts only, and always pre-selects the best one, even with weak reasons (PF-A06-03). A late file (goods already received) is never matched to its done receipt, but it can be attached to another open receipt of the same owner (PF-W14-02). "No open receipt …" appears only when no owner has an open receipt at all (PF-A06-02).

Remedy: workaround.

1. Read the reasons under Matching Receipts (best first). Choose a receipt only when the reasons include "the file's buyer is …" and a product, serial or PO number that fits the goods.
2. For a late file, don't use Find Receipt: open the done receipt (or its Supplier Data Pending discrepancy) and select Attach Supplier Data there.
3. For a new shipment without a receipt, create the receipt first (Create a receipt held for an owner).
4. If a file was attached to the wrong open receipt, open the file (the receipt's EPCIS Files smart button) and select Cancel Import. The receipt shows its yellow banner again.

Who can fix it: Rx Tracking User or Manager.

Error: "…'s profile releases goods received before their data only with the supplier's data …"

What you see:

OWNER's profile releases goods received before their data only with the supplier's data (EPCIS file or transaction statement document), not with the owner's confirmation.

When: selecting Record in Record Owner Confirmation (Record the owner's confirmation or the supplier's statement before validating).

Cause: the owner profile's Goods Before Data policy is Supplier file only. The button is shown anyway (PF-A06-04).

Remedy: resolution. Attach the supplier's file or its statement document instead. Only an Rx Tracking Manager can change the policy, if the owner agrees: Set the owner's policies.

Who can fix it: Rx Tracking User or Manager (attach the data); Rx Tracking Manager (the policy).

Error: "The date of the owner's confirmation can't be in the future." and other input checks

What you see: one of:

The date of the owner's confirmation can't be in the future.
Give the date of the owner's confirmation.
Choose who at OWNER confirmed it (a contact of the owner).
Give the reference of the owner's confirmation (email subject, ticket or letter), so it can be found again.
Upload the evidence files in the window; files that belong to other records can't be used (FILES).

or a red "Invalid fields:" notice listing Confirmed By and Reference.

When: selecting Record in Record Owner Confirmation.

Cause: Confirmed By must be a contact of the owner, Confirmed On a date not after today, and Reference filled in; evidence files must be uploaded in the window itself.

Remedy: resolution. Correct the field and select Record again.

Who can fix it: Rx Tracking User or Manager.

Error: "The supplier's data is already recorded for …"

What you see: one of:

The supplier's data is already recorded for WH/IN/00011.
WH/IN/00010 has no supplier data pending.
WH/IN/00045 is a custody receipt (the owner's own goods): it needs no transaction information or statement.
WH/IN/NNNNN is not a receipt held for an owner.

When: Attach Supplier Data (statement document) or Record Owner Confirmation on a receipt.

Cause: the open receipt already has its file, confirmation or statement; the done receipt has nothing held for missing data; custody receipts need no data; or the receipt is not held for an owner.

Remedy: resolution. Nothing more is needed on this receipt. For a done receipt whose lots are held for missing data, see Receive an owner's goods before their data.

Who can fix it: Rx Tracking User or Manager.

Error: "… (custody receipt): …'s instruction (…) is required for …"

What you see: at Validate:

DSCSA owner isolation (3PL):
- WH/IN/00045 (custody receipt): Northwind Generics LLC's instruction (Other / Return to the owner (custody)) is required for WH/IN/00045: record the owner's order or approval first.

or, with an instruction of the wrong kind, "- WH/IN/00045 (custody receipt): Instruction NWG-HOLD-3113 (Quarantine, Northwind Generics LLC) is not a Other / Return to the owner (custody) instruction.", and the other instruction refusals (already used, another owner's).

When: validating a custody receipt in Receive the owner's own goods as a custody receipt.

Cause: a custody receipt needs the owner's unused instruction of kind Other or Return to the owner (custody), unless the owner profile's Owner Instructions is Optional or an attached file names the owner as both seller and buyer. The field lists every unused instruction of the owner, so a wrong kind can be chosen (PF-W14-04).

Remedy: resolution. Record the instruction if you don't have one (Record an owner's instruction), choose it in Owner Instruction, save, and select Validate again. The instruction messages are explained in Troubleshooting: owners, instructions and portal access.

Who can fix it: Rx Tracking Manager (the custody receipt); Rx Tracking User or Manager (the instruction).

Error: "Only a DSCSA manager can record a receipt as custody …"

What you see: an Oh snap! dialog when you save:

Only a DSCSA manager can record a receipt as custody (no transaction, no transaction statement), with the owner's instruction.

When: setting Owner Receipt Kind to Custody (no transaction) as an Rx Tracking User.

Cause: declaring that a shipment is not a sale is a manager's decision.

Remedy: resolution. Select Discard changes and ask an Rx Tracking Manager to record the receipt. A supplier file that names the owner as both seller and buyer makes the receipt custody without a manager.

Who can fix it: Rx Tracking Manager.

Error: "… is done: whether it was the owner's purchase or a custody receipt can't be changed any more."

What you see:

WH/IN/NNNNN is done: whether it was the owner's purchase or a custody receipt can't be changed any more.

When: changing Owner Receipt Kind of a done receipt through an import or an API call (the form shows it read-only).

Cause: the kind decides whether a transaction took place; once the receipt is done, it is part of the record.

Remedy: none in the software. Ask an Rx Tracking Manager; your procedure decides how a wrongly recorded receipt is documented.

Who can fix it: Rx Tracking Manager.

Error: "Only DSCSA users can record the supplier's data or the owner's confirmation."

What you see:

Only DSCSA users can record the supplier's data or the owner's confirmation.

When: recording the supplier's data or the owner's confirmation without an Rx Tracking right, for example through an import or an API call. Without the right, the banner and the Attach Supplier Data and Record Owner Confirmation buttons aren't shown.

Cause: these records need the Rx Tracking User right.

Remedy: resolution. Ask a user with the right, or an administrator to grant it. See Error: "Only DSCSA users …".

Who can fix it: Administrator (Administration: Settings).

The yellow banner or the Attach Supplier Data button isn't shown

What you see: a receipt held for an owner without the banner "No supplier data yet for this owner's receipt: …", or without Attach Supplier Data and Record Owner Confirmation.

When: in Create a receipt held for an owner.

Cause: one of:

• the receipt is still Draft: select Mark as Todo;
• you have no Rx Tracking right (an Inventory user sees neither the banner nor the DSCSA buttons);
• the receipt has only non-DSCSA products, or it is a custody receipt (no banner; custody needs no supplier data);
• the supplier's data or the owner's confirmation is already recorded (only the banner and Record Owner Confirmation go);
• Held for Owner is empty: it is your own receipt.

Remedy: resolution, as listed. For Held for Owner missing from the form, see Held for Owner doesn't show although 3PL is on.

Who can fix it: Rx Tracking User or Manager.

An internal transfer doesn't take the owner's units

What you see: a new transfer made with Inventory ‣ Operations ‣ Internal ‣ New has no Held for Owner field and reserves only your own units (for example lots BPDPZ2508K and BPDPZ2509B), never the owner's.

When: trying to put away or move an owner's units, inside a warehouse or to another of your warehouses.

Cause: a transfer made in the form is always for your own stock (PF-A06-06).

Remedy: workaround. Move owner units through the reception route or Odoo's Relocate: see Put away and move an owner's units inside the warehouse, or, to another warehouse, Move an owner's units to another of our warehouses. Cancel the internal transfer.

Who can fix it: Rx Tracking User or Manager (reception route); Inventory Administrator (Relocate).