Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Fenix Branded Tracking page consists of the following sections:

  • Section 1: Delivery Status

  • Section 2: Important Updates

  • Section 3: Track Event History

  • Section 4: Order Line Items in the Package

  • Section 5: Digital Assets (2-Vertical images)

  • Section 6: Promotional Videos & Digital Assets (1-Horizontal image)

  • Section 7: Product Recommendations

  • Section 8: Multi-Shipment View

  • Section 9: Feedback Rating & Comments

  • Section 10: Delivery status updates subscription

  • Section 11: Headers & Footers

...

Section 1: Delivery Status

...

  1. The Delivery Status section depends on TrackingStatus API Response.

  2. This section consists of:

    1. Progress Bar Menu

      1. Progress Bar menu names come from the selected_shipment_activities list. Progress Bar menu names can be configured as per your needs. The bar moves by considering a concise info list.

    2. Delivery Date (delivery_date field from edd_info object)

    3. Delivery Status (latest event from concise info list)

    4. Order Number and Placed on date ( from order_info)

    5. Tracking Number (taking from tracking_number field)

 Section 2: Important Updates

...

  1. Important updates: Considering the important_updates field from TrackingStatus API Response.

  2. It's easily configurable from the backend.

Section 3: Track Event History

...

  1. Tracking page API response provides the track events.

  2. We are considering events from the shipment_activities list.

Section 4: Order Line Items in the Package

...

  1. Fenix will enable the boolean flag display_line_items from the backend configuration if you want to display the order line items on the tracking page

  2. We are considering line items from line_items list from the TrackingStatus API Response.

Section 5: Digital Assets (2-Vertical images)

...

  1. Fenix UI team will integrate the Digital Assets (2-Vertical images) that you provide. It's a static configuration.

Section 6: Promotional Video & Digital Assets (1-Horizontal image)

...

  1. Fenix UI team will integrate the Promotional video (Youtube) & Digital Asset (1-Horizontal image) that you provide. It's a static configuration.

Section 7: Product Recommendations

...

  1. RecommendedProducts API  response provides the recommended product information.

  2. Fenix team uses Shopify Algorithm to display recommended products. 

  3. Fenix team will enable the boolean flag display_recommended_products from the backend configuration if you want to showcase the recommended products on the tracking page.

Note: If you have your own Algorithm or Recommendation engine to retrieve recommended products, you can utilize it to show recommended products.

Section 8: Multi-Shipment View

...

  1. Fenix provides flexibility to track different shipments of the same order through the multi-shipments view.

  2. MultiShipment View API  Response API provides multi-shipments information.

  3. See Full Order link is enabled only if the order contains multiple shipments.

Section 9: Feedback Rating & Comments

...

  1. We are capturing Feedback Ratings and Comments provided by shoppers through Feedback API.

  2. We will store this information in the Fenix data warehouse.

Section 10: Delivery Status updates subscription

...

  1. To get the subscriptions from the shoppers either via email id or phone number to get automatic notifications on different shipment status from fenix.

  2. Currently, Fenix supports two channels for sending delivery status notifications to subscribers:

    1. Email 

    2. SMS

Section 11: Headers & Footers

...

  1. Fenix UI team will integrate the Headers & Footers that you provide.

...

Track Status API Components

identifier-name

Unique Name For Retailer

notification_id

We identify the notification from where the tracking page got triggered using notification_id.

important_updates

Message which retailer wants to display in the tracking page.

edd_info

Contains information regarding 

  • Delivery date

  • Delivery message

  • Split delivery date

  • Header name 

Note : Header name refers to whether the delivery date is the promised delivery date which is shown in checkout page or expected delivery date which is provided by the carrier after pickup or delivery date on package delivered to customer.

Code Block
{
    "delivery_date": "Friday, September 09 2022", 
    "promised_date": "Monday, September 12 2022", 
    "delivery_message": "Yay, it\"s early...", 
    "expected_shipment_date": "Wednesday, September 07 2022", 
    "split_delivery_date": {
        "day": "Friday", 
        "month": "September", 
        "date": "09", 
        "year": "2022"
    }, 
    "header_name": "Expected Delivery Date"
}

display_order_info

Refers to whether to display order details(refer to order_info field)  on the page or not.

  • true : display

  • false : not to display

order_info

Contains Order related information such as 

Code Block
{
    "number": "AAA", 
    "placed_dtm": "2022-09-07T10:55:11-05:00", 
    "formatted_dttm": "Wednesday, September 07 2022"
}

concise_infos

Moves the progress bar to the latest status (event). Events that Fenix can track are:

  • Order Confirmed

  • Shipment Confirmed

  • Ready To Ship

  • Shipment Cancelled

  • Left Warehouse

  • Shipment Exception

  • Intransit

  • Out for delivery

  • Delivery Exception

  • Return To Sender

  • Returned To Sender

  • Delivered

Depending on the last tracked event, Fenix shows only 4 events in the progress bar.

For more details refer here.

shipment_activities

To display Shipment Track Event History.

recent_shipment_info

Latest Track Event info which we will show in Latest update in Delivery Status section.

selected_shipment_activities

To build the complete progress bar section with stoppers.

line_items

Contains all the product details which are part of order or shipments. We will display line items information in Section 4.

display_lineitems

Refers to whether to display order line items on the tracking page or not. 

  • true : display

  • false : not to display

item_count

Refer to whether to display a multi shipment section or not.

Code Block
{
    "total_ordered": 3, 
    "total_filled": 2, 
    "current_packaged": 2
}
  • total_filled: Items shipped by retailer.

  • current_packaged:  Items which exist in the current package.

Note : Based on total ordered and current packaged count “See full Order” will be displayed if order has multiple shipments.

display_recommended_products

Refers to whether to call Recommended products API or not.

  • true : call API

  • false : not call API

Note: If ‘false’ then product recommendations section will be hidden.

...

  • Using RecommendedProducts API, Section 7 will be populated.

  • Fenix completely relies on Shopify Recommended Product API to get and display recommended products.

...

  • Using Delivery Status Subscription API, Section 10 will be populated.

Email Subscription 

Resource Name

subscribeForEmail

Resource URL

api/v1/btp/{identifier-name}/trackevent-notification/email-subscription

Method

POST

Params (query/path)

PathVariable:

Identifier-name

Headers

Request Payload

Code Block
languagejson
{
    "channel_type": "EMAIL", 
    "channel_hub_id": "30685b53-95c8-4f20-ad9c-b2f0526c7b4b", 
    "tracking_number": "123", 
    "track_events": [
        "OUT_FOR_DELIVERY", 
        "DELIVERED", 
        "PICKED_UP_BY_CARRIER", 
        "GENERIC"
    ], 
    "email_id": "abc@gmail.com"
}

Response Payload

Code Block
languagejson
{
    "subscription_id": "72cef79c-43c1-45b1-920e-0969cbff737b"
}

Response Status

200 - Success

400 – Failure

401 - Un-Authentication 

SMS Subscription 

Resource Name

subscribeForSMS

Resource URL

api/v1/btp/{identifier-name}/trackevent-notification/sms-subscription

Method

POST

Params (query/path)

PathVariable:

Identifier-name

Headers

Request Payload

Code Block
languagejson
{
    "channel_type": "SMS", 
    "channel_hub_id": "30685b53-95c8-4f20-ad9c-b2f0526c7b4b", 
    "tracking_number": "123", 
    "track_events": [
        "OUT_FOR_DELIVERY", 
        "DELIVERED", 
        "PICKED_UP_BY_CARRIER", 
        "GENERIC"
    ], 
    "phone_number": "98684002210"
}

Response Payload

Code Block
languagejson
{
    "subscription_id": "72cef79c-43c1-45b1-920e-0969cbff737b"
}

Response Status

200 - Success

400 – Failure

401 - Un-Authentication 

...