Line items with pick or ship activity are intentionally protected from sync deletion
Luminous protects order lines that have already been picked or shipped from being hard-deleted by an inbound channel sync. If a line item was removed on the channel side (for example, a ShipStation order edit, a Shopify order update, or an Amazon cancellation) after your warehouse recorded a pick or ship quantity against it, Luminous will not delete that line. This is intentional.
Why the protection exists
Deleting a picked line item used to cascade into the linked fulfillment order item record, which would:
- Blank out the live Fulfillment Order and Picklist views mid-operation
- Leave no Luminous record of the units your warehouse already handled
- Create silent inventory discrepancies between Luminous and your physical stock
What happens instead
- The line item stays in the sales order with its existing pick/ship quantities intact.
- The sync logs a warning noting which items were skipped.
- The existing cancellation/refund workflow is used to close out the surviving line in place — the same path triggered for split-order cancellations.
When a removed line is deleted
Lines with zero picked quantity and zero shipped quantity are still removed normally when the channel reports them as absent. The protection only applies to lines with recorded warehouse activity.
What you should do
If you see a line that was removed on the channel but is still open in Luminous:
- Verify the quantities — confirm that a pick or ship quantity was recorded (visible on the Sales Order line item detail).
- Cancel the line in Luminous — use the standard refund or cancellation flow to close the line and return the reserved inventory.
- Check the fulfillment order — if the fulfillment order was already pushed to your warehouse, follow your normal short-ship or cancel procedure with the warehouse.
This does not affect normal operations
For the vast majority of orders — where channel edits happen before picking starts — line items are still removed from Luminous automatically during sync, exactly as before.