When does a split mismatch happen?
If a single inbound shipment includes the same SKU across two or more purchase orders (a consolidated container split between POs), the receiving process may attribute units to the wrong PO line. For example, a shipment might record 570 units for PO A and 7,046 for PO B, but a receiving report could have been posted with those numbers reversed — leaving 7,046 units received against PO A and only 570 against PO B.
Luminous detects this condition automatically and surfaces a fix directly on the shipment view.
Prerequisites
- You are viewing an existing PO Shipment (not editing or creating one).
- The shipment spans two or more purchase orders that share the same SKU.
- The over-received PO lines have not been fully billed against a vendor bill. If they have, you must unbill those lines first (see below).
Step-by-step
- Open the Purchase Orders module and navigate to the shipment in question (via the PO's Shipments tab or the PO Shipments list).
- Open the shipment detail page (view mode).
- If a mismatch is detected, a banner appears above the line items explaining that one or more SKUs have a received quantity that does not match the shipment split quantity.
- Affected line items are highlighted in the items table so you can see exactly which PO lines are over- or under-received.
- Review the banner to confirm the mismatched SKUs and their deltas.
- Click Reallocate to shipment split.
- Confirm the prompt — it shows which SKUs will be corrected and reminds you that the total received quantity stays the same; only the attribution between POs changes.
- Luminous moves the units: quantities are reversed out of the over-received PO lines (newest unbilled receiving-report entries first) and credited to the under-received ones.
- The page refreshes and the banner clears when all mismatches are resolved.
What the reallocation does (and does not) change
| What changes | What stays the same |
|---|---|
| Which PO line each unit is attributed to on the receiving report | Total units received across the whole shipment |
| On-hand counts per PO for cost-layer and AP purposes | Physical inventory quantity |
| Cost attribution per PO line | Shipment-level extra costs |
The reallocation never creates or deletes stock — it only moves receiving-report lines between the sibling PO lines within the same shipment.
If the button is greyed out or blocked
The action is blocked when the over-received PO line's receiving-report quantity has already been fully or partially billed on a vendor bill.
Error shown: Not enough unbilled receiving-report quantity to reverse. Unbill the billed lines first.
Resolution:
- Go to the relevant vendor bill and remove the payment or unbill the affected receiving-report line.
- Return to the shipment and run Reallocate to shipment split.
- Re-apply the billing after the reallocation is confirmed.
Tip: partial reallocation
If you only want to fix one SKU on a shipment that has multiple mismatched SKUs, contact your Luminous administrator — the underlying API supports per-SKU reallocation, though the UI button currently fixes all mismatches at once.
After reallocation
- Receiving reports, inventory on-hand, and cost layers now reflect the correct PO line attribution.
- No additional receiving or adjustment steps are needed.
- If this shipment feeds a TrackStar inbound or a purchase-to-order allocation, verify those records reflect the corrected quantities.