Applies to: LogisticaHQ (P4 Warehouse), configured per tenant by an administrator Roles required: Administrator (configuration screen) Regulatory references: none
All tray behavior is controlled by tenant settings in the configuration screen. Every setting below lives under the Business_Kitting group. New capabilities are off by default — turning a feature on is always an explicit administrator decision.
System-Config > Configuration, then filter the list by Business_Kitting.
| Setting | Type | Default | Description |
|---|---|---|---|
| Business_Kitting_Enabled | Yes/No | No | Master switch for the whole tray module (tray screens, handheld flows, consumption documents). |
| Business_Kitting_KitNumberPrefix | Text | KIT- | Prefix for tray numbers. Numbers are always system-generated. |
| Business_Kitting_KitLpnPrefix | Text | KB- | Prefix for tray box LPNs. Kept on its own number sequence so tray boxes stay visually distinct from day-to-day LPNs. |
| Business_Kitting_ConsumptionNumberPrefix | Text | CONS- | Prefix for consumption documents. A number is only used when a surgery actually consumed something — a tray returned complete does not burn one. |
| Business_Kitting_InstrumentCategory | Text | INSTRUMENT | Product category that marks unflagged bill-of-materials lines as instruments (presence-checked, never billed). |
| Business_Kitting_AutoCreateReturnOnShip | Yes/No | Yes | Automatically create the Customer return (RMA) when a tray dispatch ships, pre-loaded with exactly what shipped. |
| Business_Kitting_ReceiveIntoKitLpn | Yes/No | Yes | Receive return counts directly back into the tray's own LPN. |
| Business_Kitting_AllowShortDispatch | Yes/No | No | Allow dispatching a tray that is short of its bill of materials. What ships is always the box's actual contents, so a short dispatch never inflates consumption. |
| Business_Kitting_AllowShortRefillComplete | Yes/No | No | Allow completing a refill while contents are still short of target. A short-completed tray lands in Draft, not Ready. |
| Business_Kitting_ShipOnDispatchScan | Yes/No | Yes | Ship the dispatch the moment the tray is scanned out on the handheld; the driver's signature can be collected afterwards. |
| Business_Kitting_LabelUseZpl | Yes/No | No | Print the tray dispatch label as native printer commands (ZPL) so it can carry a QR code. Requires a ZPL-capable printer. |
See Tray Expiry for the feature itself.
| Setting | Type | Default | Description |
|---|---|---|---|
| Business_Kitting_ExpiryWarningDays | Number | 30 | Days ahead to warn about expiring stock sitting inside trays. Drives the Trays > Expiry screen and the seeded "Tray expiring contents" scheduled report. Set to 0 to disable the warning. |
| Business_Kitting_ExpiryAlertEmails | Text | (empty) | Comma-separated recipients for the seeded expiry report. Applied when the report is created with Seed tray Reports. |
See Hospital Notifications for the feature itself.
| Setting | Type | Default | Description |
|---|---|---|---|
| Business_Kitting_NotifyHospitalOnDispatch | Yes/No | No | Email the hospital when a tray is dispatched to them: tray number, contents summary and the pick ticket reference. |
| Business_Kitting_NotifyHospitalOnConsumption | Yes/No | No | Email the hospital when a tray return is reconciled and a consumption document is produced. A tray returned complete sends nothing. |
| Business_Kitting_NotificationCcEmails | Text | (empty) | Comma-separated CC recipients added to every hospital tray notification — typically your own office. |
Hospital Notifications also require your tenant's outgoing Email (SMTP) to be configured under System-Config > Configuration > Email, and an Email address on the hospital's Customer record.
See Surgery Cases for the feature itself.
| Setting | Type | Default | Description |
|---|---|---|---|
| Business_Kitting_CaseNumberPrefix | Text | CASE- | Prefix for surgery case numbers. Numbers are system-generated. |
| Business_Kitting_CaseLeadDays | Number | 2 | Days before the surgery date a tray is committed to a case (pull, check, stage). Used for double-booking detection and the free-trays lookup. |
| Business_Kitting_CaseReturnDays | Number | 2 | Days after the surgery date the tray stays committed (return, count, refill). Used for double-booking detection and the free-trays lookup. |
| Business_Kitting_RequireCaseOnDispatch | Yes/No | No | Block tray dispatch unless the tray has an open surgery case. Leave off to keep dispatching without bookings. |
| Symptom | Likely cause | Resolution |
|---|---|---|
| Tray screens are missing from the menu | Business_Kitting_Enabled is off | Turn it on and refresh the browser. |
| No expiry rows appear although stock is short-dated | Business_Kitting_ExpiryWarningDays is 0, or the Products are not lot/expiry controlled | Set a warning window; confirm the Products carry expiry dates. |
| Hospitals receive no emails | Notification settings are off, SMTP is not configured, or the Customer record has no Email | Check all three; the tray flow itself never fails because an Email could not be sent. |
| Dispatch is blocked with "no open surgery case" | Business_Kitting_RequireCaseOnDispatch is on | Book a case first, or turn the requirement off. |
Was this page helpful?