The Smart Fulfillment Automation Settings within Luminous give administrators granular control over how Fulfillment Orders (FOs) are automatically generated and managed. These settings optimize inventory usage, streamline fulfillment workflows, and allow customization based on your business needs.
Current Settings
Default Fulfillment Priority List
Specifies the default priority list used for products without an explicitly assigned priority list.
Example Use:
Ensuring all products have consistent fallback behavior when specific lists aren't assigned.
Auto-generation Trigger
Determines when Fulfillment Orders are automatically created.
Immediate: FO generated at the moment the order is posted.
Scheduled/Delayed: FO created after a set delay or at a specific daily time.
Manual: FO creation initiated manually by users.
Example Use:
Immediate trigger for rapid fulfillment scenarios.
Scheduled for batch processing during off-peak hours.
Delay FO Generation
Specifies a time delay after order posting for FO generation. Only applicable if the Auto-generation Trigger is set to Scheduled.
Example Use:
Allowing a buffer time for customer order modifications.
Always Create Fulfillment Orders Even When No Stock Is Available
If enabled, the system creates Fulfillment Orders even when warehouse stock isn't sufficient, assigning FOs to the highest priority warehouse group regardless of availability.
Example Use:
Ensuring an FO is always generated, useful for tracking backorders or inventory replenishment needs.
Upcoming Features (Not Yet Available)
Order Consolidation (In Development)
When enabled, Luminous consolidates all line items into a single FO if one warehouse group can fulfill the entire order, ignoring individual product priority lists.
Example Scenario:
Products A and B have separate warehouse priorities, but one warehouse can fulfill both. With consolidation enabled, a single FO is created.
Line Item Splitting (In Development)
Allows a single product line to be split across multiple warehouses based on availability, optimizing partial fulfillment.
Example Scenario:
100 units ordered; Warehouse 1 has 40, Warehouse 2 has 60. With splitting enabled, two FOs are created to fulfill the total quantity.
Partial Fulfillment Threshold (In Development)
Defines a minimum percentage of ordered quantity a warehouse must have available to be considered for partial fulfillment.
Example Scenario:
A 50% threshold requires at least 50 units of a 100-unit order to be available in a warehouse group to fulfill partially from that warehouse.
Lot-Based Fulfillment (In Development)
Automated or manual selection of specific inventory lots for fulfillment, with splitting capability across multiple lots.
Example Scenario:
Automatically selecting the oldest inventory lot to manage product expiry, or manually splitting a large order across several lots.
Backorder Handling (In Development)
Configures how to handle products that can't be fully fulfilled:
Split and mark remaining as backorder.
Keep consolidated and mark remainder as backorder.
Do not split at all.
Example Scenario:
Automatically splitting orders to fulfill available stock while clearly marking unfulfilled quantities as backordered.
Notification and Alerts (In Development)
Automatic notifications to designated users when automated fulfillment encounters inventory shortages.
Example Scenario:
Alert fulfillment managers immediately when automated processes detect inventory shortages, facilitating proactive response.
Best Practices
Regularly review and update settings as your business evolves.
Clearly communicate any changes in automation settings to fulfillment and inventory teams.
Monitor system logs to identify patterns and adjust automation settings accordingly for improved efficiency and accuracy.