Troubleshooting Vendor Order Notification Emails
Summary
Learn how order notification emails are triggered for vendors and how to resolve common issues with missing or inconsistent delivery.
When a Fulfillment Request (FR) is created in Flxpoint, an email notification is sent to the vendor to alert them of the new order in their portal. The timing of this email depends on how the FR is processed:
Automated Processing: If the source is configured to auto-process, Flxpoint generates the FR and immediately triggers the notification workflow.
Manual Processing: If auto-process is disabled, the notification is only sent after a user manually moves the FR to the "Processed" status within the Flxpoint UI.
Notification cache race conditions
When multiple orders (POs) for the same vendor are processed in a single batch, a race condition can occur in the notification cache. If the system is still looking up the vendor's email preferences for the first order, subsequent orders in that same batch may incorrectly read a null value and assume the vendor has opted out of notifications. This results in the vendor receiving only one email for the entire batch rather than individual alerts for each order.
Failures in automated workflows
If you have automated steps configured to run immediately after an order is created, such as automatedBuyShippingLabel or autoGeneratePackingSlip, a failure in these specific steps can block the notification. Because the notification is the final step in the sequence, an error in label or packing slip generation will prevent the email from ever being sent, even though the order correctly appears in the Vendor Portal.
Template errors
Following platform updates, custom email templates may occasionally fail due to a TemplateInputException. This is often caused by an outdated fragment call within the HTML of the email template. If you suspect a template error, the fragment call must be rewritten to align with current system requirements.
Verify portal settings. Navigate to the Vendor Portal settings for the specific source and ensure the correct email addresses are listed and the notification toggle is enabled.
Test with manual processing. To isolate whether the issue is related to automation rules, temporarily disable "Auto Process" for the source. Manually move a test FR to the Processed status and verify if the email is delivered.
Check for routing errors. Review your fulfillment logs for generic routing errors. If an error occurred during the shipping label or packing slip generation phase, it likely blocked the notification trigger.