Fenix provides multiple ways to consume the order and the fulfillment data from retailers. For retailers on platforms like Shopify, BigCommerce, etc., Fenix uses platform-specific webhooks to retrieve that information.
For retailers not on such platforms, Fenix provides a feed upload service where the retailer can upload the necessary data, order, fulfillment, etc., to an agreed-upon cloud location, and Fenix can consume that data every 30min of the upload.
Folder structure and description
Fenix provides two ways to upload the order and fulfillment feed.
SFTP
AWS S3
Below is a standard folder structure of either of the above two locations.
CSV Sample Templates
Inbound Order Attributes
Attribute | Required | Allowed Fields |
|---|---|---|
ORDER_NUMBER | YES | |
PLACED_DATE_TIME | YES | |
ITEM_QUANTITY | YES | |
TOTAL_WEIGHT_IN_LBS | NO | |
CART_COST_IN_USD | YES | |
SHIPPING_SOURCE | NO |
|
SHIPPING_METHOD | YES | |
SHIPCOST_IN_USD | YES | |
ORDER_STATUS | NO |
|
FULFILLMENT_STATUS | NO | |
BUYER_ADDRESS_1 | YES | |
BUYER_CITY | YES | |
BUYER_STATE | YES | |
BUYER_ZIPCODE | YES | |
BUYER_COUNTRY | YES | |
SKUS | YES | |
QUANTITIES | YES | |
SHIPPABLE_FLAGS | YES | |
IMAGE_URLS | YES | |
ROUTING_URLS | NO | |
EXPECTED_SHIPMENT_DATE_TIME | YES | |
PROMISED_DELIVERY_DATE_TIME | YES |
Inbound Fulfillment Attributes
Attribute | Required | Allowed Fields |
|---|---|---|
SHIPMENT_ID | YES | |
ORDER_NUMBER | YES | |
SHIPMENT_DATE_TIME | YES | |
TRACKING_NUMBER | YES | |
CARRIER_NAME | YES | |
CARRIER_SERVICE | YES | |
ITEM_QUANTITY | YES | |
SKUS | YES | |
QUANTITIES | YES | |
TOTAL_DIM_WEIGHT_IN_LBS | NO | |
SHIPCOST_IN_USD | YES | |
SHIPMENT_STATUS | NO |
|
SHIPPER_ADDRESS_1 | YES | |
SHIPPER_CITY | YES | |
SHIPPER_STATE | YES | |
SHIPPER_ZIPCODE | YES | |
SHIPPER_COUNTRY | YES |