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.
- Snowflake: stage POD event manifests for downstream warehouse loading.
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.
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
- Only fleet admins and managers with destination permissions can create or modify destinations.
- 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.