100%
Integrations › Email order import

The forwarding address for each store

Create the address the platform sends to, add it to the merchant portal, and understand which forwarding routes work.

Each store gets its own address on the Addresses tab. The address is what tells CloudPos which store an email belongs to, so a store with no address can never receive orders by email.

Create the address

  1. Open the Addresses tab.
  2. Give the address a label — usually the platform name, so a store on two platforms has one address for each and you can tell them apart later.
  3. Create it, then copy it with the copy button. Do not retype it: the address carries a signature and a single wrong character makes it unusable.
Image needed · mpemail-address-01
Capture: The Addresses tab with two stores listed, each showing its generated forwarding address and the copy button, one row with a label such as DoorDash and one such as GrubHub.

Add it to the platform

In the merchant portal for the platform, find the setting that controls where order notification emails are sent, and add the CloudPos address there. Keep your own address on the list as well — you want a copy you can read.

Image needed · mpemail-address-02
Capture: The merchant portal of one platform with the order-notification email field open and the CloudPos forwarding address pasted into it. Blur the merchant account name.
An address that resolves proves only that someone knew the address. It is not proof the email came from the platform — that is a separate check, covered under held mail.

Which routes work

  • The platform sends to it directly. Best. Nothing sits in the middle.
  • A rule in your mailbox auto-forwards to it. Works. The sender signature survives an automatic forward.
  • Someone presses Forward by hand. Does not work. A manual forward rewrites the message, the sender signature no longer matches, and the message is held rather than imported. This is deliberate — see the topic on held mail.

Changing the address

The signature is derived from a key held on the server. If that key is ever replaced, every address issued before the change stops resolving and has to be re-issued and re-entered in each merchant portal. Treat it as permanent.