Customer satisfaction relies heavily on transparent delivery updates. Currently, tracking information can be inconsistent across different carriers, making it difficult for merchants to react quickly to shipping issues. To provide a high-end service, you need a unified way to monitor package statuses and trigger immediate actions when things don't go as planned.
Creating a central framework for delivery intelligence
Our objective is to implement a standardised shipment status logic for all packages within the PlentyONE system. By creating a unified set of status codes, we enable the system to "understand" the progress of a shipment regardless of the carrier, providing the foundation for powerful cross-carrier automation via Flow.
Enhancing your shipping transparency
- Unified Status Logic: Benefit from a standardised set of shipment statuses that work across various shipping service providers.
- Flow & FlowHub Integration: Move beyond legacy event procedures. Use our modern automation engine, Flow, to trigger actions based on shipment status changes.
- Manual Control (Phase 1): Gain the ability to manually set and update shipment statuses to keep your internal processes and customers informed.
- Push-API Readiness: We are building the infrastructure to support real-time tracking updates via Push APIs (e.g., DHL), ensuring your system stays updated without manual polling.
Future-proofing your logistics
While the first phase focuses on the API framework and manual status management, this project is the prerequisite for a fully automated tracking ecosystem. By moving away from older automation methods, we ensure that tracking updates can trigger sophisticated, multi-step workflows within Flow.
Impact on your support workflow
By standardising how tracking data is handled, you can reduce manual inquiries and proactively manage shipping exceptions. Instead of rigid legacy actions, you can now build flexible automation in Flow - for example, automatically creating a support ticket and notifying the customer if a package is marked as "return to sender."