POD destinations automatically forward uploaded internal order POD data and files to external systems such as your TMS, archive, data warehouse, or cloud storage.
Available destination types
- Webhook: receive a signed HTTP POST with POD metadata and file URLs when a proof is uploaded.
- Cloud Storage (S3): copy POD files and metadata to your Amazon S3 bucket.
- Cloud Storage (GCS): copy POD files and metadata to Google Cloud Storage.
- Cloud Storage (Azure Blob): copy POD files and metadata to Azure Blob Storage.
- DocuWare: file POD documents into a configured cabinet and store dialog. See Connect DocuWare for proof of delivery.
- Snowflake: stage POD event manifests for downstream warehouse loading.
- SFTP server: file the proof of delivery as a PDF plus an index file on your own server. Your archive picks both up from there. See Connect an SFTP server.
Setting up a destination
- Navigate to Fleet → Internal Orders in the dashboard, then open the destinations settings.
- Click Add Destination, choose the type (Webhook or Storage), and enter your connection details.
- Enable the
order.pod.uploaded.v1event subscription to start receiving data. - Use the Test button to verify connectivity before going live.
Connect an SFTP server
An SFTP destination fits when your archive cannot be reached from the internet, for example a DocuWare inside your own network. After the last drop-off of an order, Maxmove files two files in your directory: the proof of delivery as a PDF and an index file with the search terms. Your archive's import job picks both up.
You need the server, port, user, directory and a password from your IT. Instead of a password, your IT can also store a key that Maxmove creates.
- In the dashboard, open Administration → Orders → POD destinations and click Add destination. Choose SFTP, enter the details and click Connect.
- Maxmove shows the key your server presents. Compare it once with your IT and confirm it. Nothing is transferred until then. Maxmove then puts a test file in your directory, and the destination is active.
- Set how the files are named and which columns the index file has. The preview shows the next file name and an example value for each column.
Good to know:
- The index file comes as CSV or JSON. You name the columns freely, to match the fields of your archive.
- When an order has tour and shipment numbers from your own TMS, they are on the PDF, in the index file and, if you want, in the file name.
- Maxmove only sends to the confirmed server. If the server later presents a different key, Maxmove pauses the delivery until you confirm the new key.
- Maxmove never deletes or overwrites a filed PDF. A corrected proof arrives as a new file ending in
_r2.
Managing destinations
- Pause or disable a destination without deleting its configuration.
- Replay past events to backfill a new destination or recover from outages.
- Adjust retry attempts (1–20) for transient failure handling.
Access control
- Owners, admins, fleet managers and dispatchers can create or modify destinations. Drivers cannot.
- The default Maxmove system destination is read-only and managed automatically.
Destinations ensure internal order proof reaches the systems that need it — automatically and reliably.