Symptom

You receive stock against a purchase order (PO) that was created or linked as part of a purchase-to-order allocation for a specific sales order line. After the receiving report is saved, you expect a fulfillment order (FO) to appear on the linked sales order automatically — but no FO is created.

Why it happens

In Luminous's purchase-to-order workflow, when a sales-order line is pegged to a PO (whether a newly created purchase-to-order PO or an existing inbound PO), the fulfillment order is intentionally not created at the time of allocation. Instead, the system holds the line and waits for the PO to be received. When receiving stock triggers a receipt, Luminous automatically detects all sales-order lines pegged to that PO, calculates how much new stock just landed, and generates the fulfillment order for the released quantity.

This automatic step can be silently skipped under several conditions:

1. The purchase-to-order feature is not enabled for your account. This workflow is controlled by a feature flag that is off by default. If it has not been enabled for your tenant, the receipt handler exits immediately and no fulfillment orders are generated from pegs.

2. The sales order is set to "Ship Complete." If the sales order requires all lines to ship together (Ship Complete mode), Luminous deliberately holds every pegged line — including newly received stock — until every line on the order is coverable at once. A fulfillment order will not be created for any individual line until the entire order can ship. If only some lines have received stock, the system keeps waiting.

3. The peg type is "Preorder," not a PO-backed peg. When a line is allocated as a preorder (no specific PO is linked — the system is told to auto-fulfill as soon as stock becomes available at the designated warehouse), the receipt of stock does not directly trigger FO generation. Instead, Luminous's available-stock sweep — which runs on a schedule — detects that stock has landed and generates the fulfillment order. If this sweep has not yet run, or if the available stock is still below the required threshold, the FO will not appear immediately after receiving.

4. The received quantity did not increase the pegged line's released amount. For each peg, Luminous calculates a "delta" — the difference between the newly received quantity and what was previously released. If the received quantity on the PO line has not increased (e.g., the receiving report corrected or redistributed existing quantities rather than adding new ones), the delta is zero and no FO is generated for that peg.

5. An error occurred during fulfillment order generation. The receipt-to-fulfillment-order step is wrapped in error handling that prevents receipt failures from interrupting the core receiving workflow. If something goes wrong during FO creation (for example, the pinned fulfillment channel is no longer valid, or a data inconsistency is encountered), the error is logged internally but the FO is silently skipped. This is not visible in the UI.

How to resolve

  1. Confirm the allocation exists on the sales order. Open the sales order and check the allocation panel or allocation planner. Verify that the line shows an active allocation linked to the PO you just received. If no allocation appears, the peg was never created and the line needs to be allocated again.
  2. Check whether Ship Complete is enabled. On the sales order, look for a "Ship Complete" or "Require all lines to ship together" indicator. If Ship Complete is on and some lines are still unmet, the system will wait for full coverage before generating any fulfillment orders. You can either allocate and receive the remaining lines, or — if appropriate — remove the Ship Complete requirement from the order so lines can ship as they become available.
  3. For preorder allocations, wait for the next available-stock sweep. If the allocation was created as a preorder (no PO was linked at allocation time), the fulfillment order is generated by a scheduled sweep, not immediately on receipt. Allow a short period for the sweep to run. If the FO still does not appear after sufficient time, contact support.
  4. Verify the receiving report was fully saved. Navigate to the PO and confirm the receiving report shows the expected quantities as received. A partially saved or cancelled receiving report will not trigger fulfillment order generation.
  5. Check that the pinned fulfillment channel is still active. The fulfillment order is forced onto the channel you selected when you created the allocation. If that channel has since been disabled or its warehouse group reassigned, FO creation may fail silently. Review your channel configuration under Settings and ensure the channel used in the allocation is active and has a valid warehouse group.

When to contact support

Contact Luminous support if:

  • The allocation exists, Ship Complete is not enabled, the peg is PO-backed (not preorder), the receiving report is fully saved, and still no fulfillment order was generated.
  • You suspect an error occurred during FO generation (support can check server logs for the specific receipt event).
  • The purchase-to-order feature flag has not been enabled for your account and you need it activated.
  • A fulfillment order was partially created or appears in an unexpected state after receiving.