Upcoming change to email sender address for nShift system-generated notifications – nShift TMS Help Center

Overview

nShift will switch all system‑generated emails back to the unified sender address this coming Wednesday at 08:00 CET. This affects notifications, booking emails, and scheduled reports sent from TMS and other connected nShift solutions.

Updated Effective Date

Switch date and time: Wednesday, 18 March at 08:00 CET
(Previously postponed due to a rollback.)

Important Update – Switch to Unified Sender Address

The temporary rollback introduced after 14 January 2026 is now resolved. nShift will proceed with the change to the unified email sender address on the date above.

After the switch, all automated system emails will be sent from:

noreply@notification.nshift.com

Previous sender domains such as @unifaun.com, @apport.net, @spedpoint.com, and @memnon.se will no longer be used.

What is Changing

All system‑generated emails from TMS and other connected nShift solutions will use one verified sender address:
noreply@notification.nshift.com

This applies to:

Notifications
Booking emails
Scheduled reports
Emails from partner‑branded portals powered by nShift

Why This Change Is Being Made

The transition to a unified sender address improves:

Reliability through AWS Simple Email Service (SES)
Security, by ensuring all emails are sent from a verified nshift.com domain
Consistency across all system notifications
Monitoring and maintenance, using the centralized Notification Hub

What You Need to Do

Most customers do not need to take action.
However, we recommend:

Adding noreply@notification.nshift.com to your allowlist
Reviewing any filtering or forwarding rules based on old sender domains

If a customer uses a custom sender domain via AWS SES, that configuration remains unchanged.

What Will Stay the Same

Email content
Email timing
Notification behaviour

Only the sender address changes.

When This Will Happen

The switch will take place on Wednesday at 08:00 CET.
After this time, all system emails will be sent from:
noreply@notification.nshift.com

Need Help?

If you experience issues with email delivery after the change, contact nShift Support.

Frequently Asked Questions (FAQs)

Q1. Will this change affect the content of the emails I receive?

No. The content, format, and timing of your emails (such as booking confirmations, shipment notifications, or scheduled reports) will stay exactly the same. Only the sender address will change.

Q2. Why might some emails go to spam after the change?

In some cases, your email provider might treat a new sender address as unknown. Adding noreply@notification.nshift.com to your allowlist or trusted senders will prevent this.

Q3. Does this affect emails sent from our own domain or custom sender?

No. If your organization uses its own verified email domain for outbound notifications, that setup will remain unchanged.

Q4. Will I still be able to reply to these emails?

No — messages from noreply@notification.nshift.com are system-generated and not monitored. Please contact nShift Support or your regular nShift contact for any questions.

Q5. I use a white-labeled booking portal (e.g., Frigoscandia). Am I affected?

Yes. Partner-branded portals powered by nShift are included in this update. By default, emails from these portals will also be sent from noreply@notification.nshift.com after 14 January 2026.

However, if the nShift customer managing the white-label solution has configured a custom sender domain in AWS SES, those emails will use that customized sender address instead. This configuration is managed by the customer and is outside nShift’s direct control.

TMS Help Center