Preparing for peak trading

Preparation well in advance makes the difference between a smooth peak and a stressful one.

4 weeks before

• Confirm all streams are active and processing normally

• Resolve any existing failures in the event log — entering peak with a backlog makes it harder to spot new issues

• Check destination system API rate limits (ERP, 3PL) and confirm they can handle elevated throughput; raise with HC if uncertain

• Complete any planned integration changes before this point — avoid configuration changes in the final weeks before peak

1 week before

• Verify alert settings in Settings > Notifications: confirm the right people are receiving alerts and thresholds reflect peak expectations

• Confirm team access to the Control Panel — anyone who may need to monitor or act during peak should be able to log in

• Run an end-to-end test order through the full flow and verify it arrives correctly at the destination

• Review the bulk resend process with your team so everyone knows the procedure if failures need to be reprocessed

On the day

• Check the Control Panel dashboard before trading opens

• Monitor the event list during peak hours — failed events, retrying events, and volume patterns

• Keep HC's contact details to hand

If something goes wrong

Contact HC immediately using the urgent contact method. When you reach out, provide:

• The stream name

• The volume of failures or affected events

• The error messages shown in the Control Panel

Do not bulk-resend failed events until HC has confirmed the root cause. Reprocessing events before the underlying issue is fixed can result in duplicate records or compounded errors.

After peak

• Review the event log for the peak window

• Reprocess any failures that were held back during the event

• Check inventory and financial postings for the period to confirm accuracy