Terminology:
- Owner: it is the owner of the tasks and is responsible for creating them
- Carrier: it receives tasks from an owner and is responsible for executing them
Key Features:
1. Multi-Carrier Management:
- The Owner can work with multiple carriers by creating and linking the flows in both the Sender and Platform portals.
- Tasks are announced in the Sender Portal and must be assigned to a specific Platform during the announcement.
2. Task Assignment and Management:
- Rules in the Sender flow direct tasks to the correct Platform. Any tasks that are not matching any Platform's rules won't be created.
- Once created, tasks cannot be switched between platforms. Changing platforms requires deleting and recreating the task.
- The Sender can't configure task properties such as item types, assets, zones, or dimensions.
3. Visibility and Access:
- The Sender Portal can access tasks created in all the platforms.
- The Owner has visibility over the rounds created by the Platforms if all the tasks in the round were created by the Owner.
4. Round and Fleet Operations:
- The Sender Portal cannot create or optimize rounds; this is handled by the carrier platforms.
- The Owner doesn't have a fleet and can't execute rounds in this architecture.
- Carriers can have tasks from different Owners within the same round.
5. Hub Management:
- Hubs are created and managed within the Carrier platforms.
6. Configuration and Customization:
- Branding and tracking pages are set up in the Sender Portal.
- Notifications must be configured on each connected Carrier platform.
- Webhooks for the Owner are configured in the Sender Portal, while Carrier webhooks are set up in each Platform Portal.
- Senders can't create and use scheduling flows and can't create time slots.
| Sender Portal | |
| Announcement | it is done in the Sender portal and the tasks must be assigned to a Platform during the announcement otherwise the task is not created. |
| Re allocation of tasks | It is not possible to change the carrier |
| Hubs | The hubs are created in the Carrier |
| Notifications | They need to be configured in each Carrier |
| Branding | It needs to be configured in the Sender Portal |
| Webhooks | Webhooks for the Owner are configured in the Sender Portal.Webhooks for Carriers are configured in each Platform Portal |
| Optimization | Owner can't optimize, only the Carrier can create rounds |
| Fleet and rounds | Owner doesn't have a fleet and can't perform rounds |
| New features | The new features are not supported in the Sender Portal. they are only available for Carriers. For instance, system monitor and insights. |
| Carrier rounds | Carrier can mix tasks of different Owners in the same round |
| Task configuration | Sender can't configure properties of the task such as item types, assets, zones, dimensions and more |
| Time slots | Senders can't create and use scheduling flows and can't create time slots. |
Important Considerations:
- Dimensions and metadata fields in the connected platform must match the task shared in the announcement.
- Structured data (e.g., labels, failure reasons) is not shared between the Sender Portal and Carrier platforms.
This architecture is well-suited for organizations needing to coordinate with multiple carriers while maintaining centralized task management.
Urbantz analyzes each customer's unique requirements to recommend the most suitable architecture type for their specific business needs.