Fenix and Everlane Integration

 

 Objective

Shipwire wants Fenix to be the default Order Routing platform for Everlane. Currently, Shipwire is using Geodis as their only 3PL. Slowly, they want to transition from Geodis to Shipwire. During the transition and after, Fenix will route the orders to the respective warehouse.

As part of this integration, we also aim to integrate with Shipwire APIs for a long term partnership.

 Success metrics

Below set of main objectives are targeted for the integration.

Goal

Metric

Goal

Metric

Inventory: Geodis to Fenix

Syncs the inventory position at the Geodis location to Fenix.

Inventory: Shipwire to Fenix (via Shipwire API)

Syncs the inventory position at the Shipwire location to Fenix.

New order: Everlane OMS to Fenix

Everlane pushes the new order information to Fenix

Order Routing: Fenix to Everlane OMS

Fenix routes the orders received to either to Geodis or Shipwire and updates the same to Everlane OMS

Order Info: Fenix to Shipwire

The orders routed to Shipwire are sent to Shipwire via their API

Fulfillment info: Shipwire to Fenix

Once the order is fulfilled at Shipwire, it will send the fulfillment information to Fenix

 Assumptions

  • Fenix will update routing details to Everlane and it is Everlane responsibility to route the orders to Geodis. Fenix will not integrate with Geodis APIs

 Milestones

N/A

 Requirements

Requirement

User Story

Importance

Jira Issue

Notes

Requirement

User Story

Importance

Jira Issue

Notes

Inventory: Geodis to Fenix

Create SFTP Feed for Everlane. The Geodis can be added over there.

 

 

 

 Inventory: Shipwire to Fenix (via Shipwire API)

Short term

Create SFTP Feed for Shipwire (basically we will use the same SFTP location as the Everlane)

LongTerm

For Shipwire, the inventory/product webhooks from Shipwire will be implemented by Fenix. Below are some webhooks that needs to be implemented.

product.created product.updated product.retired stock.transition stock.transition.good

 

 

 

New order: Everlane OMS to Fenix

Once the order is created in their OMS, Everlane will send the order to Fenix via the Order Created API provided by Fenix. Fenix needs to make sure if the complete order data is being stored in its system.

 

 

 

Order Routing: Fenix to Everlane OMS

Once Fenix receives the order, the order routing is done and the same information is updated to Everlane via their order Update API.

 

 

 

Order Info: Fenix to Shipwire

Along the update to Everlane, Fenix also pushes the order to Shipwire using their Create order API.

 

 

 

Fulfillment info: Shipwire to Fenix

When the order is fulfilled at Shipwire, it sends the fulfillment information for the order via its tracking.created webhook. Fenix must implement the webhook api to receive the fulfillment details.

 

 

 

 User interaction and design

Below is the finalized flow.

Integration touchpoints are 1A, 1D, 2 and 3

 Open Questions

Question

Answer

Date Answered

Question

Answer

Date Answered

For Everlane integration, do we do SFTP integration or webhook integration.

Pros with SFTP: Can onboard everlane quickly.

Pros with webhook: Long term plan with shipwire is webhook integration.

 

 Out of Scope