Shippit Connector
Author:
Fluent Commerce
Changed on:
28 Nov 2024
Overview
To accelerate carrier integration between the Shippit and Fluent Order Management platforms, Shippit and Fluent Commerce provide a connector that enables seamless pick, pack and dispatch processes inside the Fluent Store App.
Key points
- The client must have a direct account with Shippit about their shipping agreement. The Shippit Connector helps to speed up the integration timeline between Fluent and Shippit.
- Before obtaining the Shippit Connector, a Fluent commercial agreement must be in place prior to using the connector; please get in touch with your Fluent Customer Success Manager.
- The Shippit Connector will be integrated with the Fluent Store App, where the pick, pack, and dispatch processes will be integrated with the Shippit integration.
- The Shippit Connector can support the following features:
- Creating labels and shipping manifests at the wave level that streamline the Store User process;
- The Store User can select one or more articles for a manifest within the same location;
Prerequisites
Here are the prerequisites for the client to obtain the Shippit Connector:
- A commercial account with Shippit
- A commercial agreement with Fluent to use the Shippit Connector
- Fluent Sandbox account access
Overview
The Shippit Connector includes the following integration sequence, which is part of the typical process between Fluent OMS and Shippit:
- Create a carrier order
- Retrieve the carrier label
- Book the carrier order
- Retrieve the manifest summary
Configuration
Within Fluent's OMS, the Shippit Connector plugin includes rules, reference workflows, and documentation. The client/partner can follow the documentation to enable the Shippit integration.
The Shippit account setup can be found here: https://support.shippit.com/en/articles/8942277-fluent-commerce-integration
The Fluent workflows and UI manifest can be extended to support special or custom business requirements.
The reference Shippit Connector workflow
The Shippit Connector would allow the Store User to process a group of fulfilments at the wave level. The advantage of this logic is that it would allow the Store User to generate shipping labels and the carrier manifest in one user action, whereas some carriers would penalise the client for not submitting the carrier manifest. This process streamlines the dispatch process at the store level.
Alternative workflow - select one or more articles for a manifest
An alternative workflow can allow the Store User to select one or more articles to be included in a manifest. This manifest process occurs outside of the wave. The advantage of this approach is that the Store can generate manifest once a day and reduce the amount of paper printed. This feature can be easily added by updating workflows, settings and UI manifest.
Example UI manifest and user action in Fluent Store:
Initial bulk manifest request UI screen:
