When fulfilling replenishment requests generated from surgical cases, Beacon automatically links replacement inventory back to the specific trays and kits that held the consumed items. Instead of requiring administrators to manually look up and reassign each replacement device to a container one by one, the system saves the original host container at the moment the request is created and pre-populates it directly in the fulfillment workflow.
How Host Container Auto-Population Works
Captured at Request Creation: When a replenishment request is generated from an event, Beacon records the host container for each consumed device before the case closes and detaches the original inventory links.
Pre-Populated at Fulfillment: When an administrator opens the request to fulfill it and build the transfer, the fulfillment assignment control automatically displays the saved host container for each item.
Multi-Container Line Splitting: If devices for a single catalog line were pulled from multiple trays during surgery (e.g., two screws from Tray A and one screw from Tray B), Beacon automatically creates separate assignment rows for each container with its corresponding quantity.
Availability Verification: Before displaying a pre-filled container, Beacon confirms that the host container still exists and remains active. If a container has been deleted or is unavailable, the assignment field remains blank for manual selection.
Full Admin Control: Auto-assignment does not lock the line. Fulfillers can change, override, or clear any pre-filled container assignment before generating the transfer.
Automatic Consignment & Location Inheritance
Once the replenishment transfer is accepted by the recipient, items assigned to a host container automatically inherit the container's operational attributes:
Consignment Status: The replacement device automatically matches the host container’s consignment classification (Consigned, Loaned, or Possession) without requiring a separate consignment update.
Tracking & Controls: The device inherits the host container’s geographic custom location, active hold statuses, due-back dates, and any location restrictions.
Loose Inventory Handling: Consumed items that were originally used as loose stock (not stored in a container) will not have a host container saved and will display a blank assignment field during fulfillment.
Key Requirements & Permissions
Role Permissions: Container assignment controls are available exclusively to Administrator and Operations users during request fulfillment.
New Requests Only: Automatic host container population applies to replenishment requests created after this feature release. Historical requests generated prior to the update will not have saved source container metadata and will display blank assignment controls.