FPS eFulfilment

The Marketplace Module

and marketplace listing
platforms

eFulfilment Team

Version Date Who Comments

1.0 29.03.2016 eFulfilment Team Initial Document
1.1 29.03.2016 eFulfilment Team Updates to section - Volo integration

1.2 31.09.2016 eFulfilment Team Update to section 2.4 SKU Format & Mapping

Revision history
This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

CONTENTS

1. OVERVIEW
1.1. Introduction
1.2. Functions
1.2.1. Inventory Updates
1.2.2. Order Processing
1.2.3. Shipping Updates
1.3. Overview Diagram
2.1. Inventory Updates
2.2. Order Processing
2.3. Shipping Updates
3. Supported Platforms
3.1. Currently Supported
3.2. Supported Functionality
4. Platform Set Up Guide
4.1. Volo Commerce
4.1.1. Request API User - Required
4.1.2. Create Product Folder & Allocate SKUs - Required
4.1.3. Carrier Rules - Optional
4.1.4. Stock Location - Optional
4.2. Seller Dynamics
4.2.1. Request API User - Required
4.2.2. Prefix SKUs in Product Range - Required
5. Monitoring Activity
5.1. Volo Commerce
5.1.1. Inventory Updates
5.1.2. Order Processing
5.1.2.1. Successful Orders
5.1.2.2. Failed Orders
5.1.2.3. Exported Orders Not In Marketplace Module
5.1.3. Shipping Updates

The Marketplace Module and marketplace listing platforms v 1.3

This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

5.2. Seller Dynamics

5.2.1. Inventory Updates
5.2.2. Shipping Updates
6. Platforms specific API message
6.1. Volo
6.1.1. Volo Order Processing message
6.1.2. Volo Order/Shipping Update message
6.1.3. Volo Inventory API message
6.2. Seller Dynamics
6.2.1. Seller Dynamics Processing message
6.2.2. Seller Dynamics Order/Shipping Update message
6.2.3. Seller Dynamics Inventory API message
7. Marketplace Module Import / Export Schedule
8. Checklist / Step By Step
APPENDICES

The Marketplace Module and marketplace listing platforms v 1.3

This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

1. OVERVIEW

1.1. Introduction

The Marketplace Module allows FPS customers to integrate their online marketplaces such as eBay or
Amazon via multichannel eCommerce listing platforms such as Volo and Seller Dynamics.

1.2.Functions
1.2.1. Inventory Updates

FPS customers will receive 6 to 12 inventory updates per day directly into their multi-channel eCommerce
platform. This will include live stock information and will cover the full product range that the customer sells
via their marketplace accounts.

1.2.2. Order Processing

Orders received from marketplaces assigned for FPS Fulfilment are collected by FPS and processed into the
National Distribution Centre NDC) in Sheffield. If the customer wishes the goods to be shipped directly to
the end user, the orders are booked onto a carrier service. Otherwise, the goods are delivered to the customer
via the normal FPS delivery service.

1.2.3. Shipping Updates

Orders which are marked for shipping directly to the end user and are successfully processed by the
Marketplace Module will be updated with carrier tracking and order status information (where applicable).

1.3. Overview Diagram

Inventory and Shipping Updates are provided by the Marketplace Module and Orders are downloaded
from the eCommerce platforms.

The Marketplace Module and marketplace listing platforms v 1.3

This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

2. MARKEPLACE MODULE FUNCTIONALITY

2.1.Inventory Updates

Each customer on the Marketplace Module has their own product range assigned to them. This product
range is a list of SKUs agreed with and maintained by FPS. A customer can choose to either use the FPS Part
Number as the SKU for a product, or can use their own SKU format provided that it follows a strict naming
convention. Please see section 2.4 for details about this. Important: If a customer is using their own SKU
format, the customer must provide the FPS Part Number cross reference for every SKU in the range in order
for the inventory updates to allocate the stock correctly.

It is important that customers notify FPS of any intention to increase or reduce the product range as the
Marketplace Module will need to be updated accordingly.

The Marketplace Module will only check orders for the current business day (midnight - midnight). If you
need orders collecting that are dated for previous days, please contact FPS eFulfilment to arrange this.

At the defined schedule (see section 7) the customers product range, including stock levels is exported to the
customers platform. Depending on your platform, this will appear in slightly different ways. For supported
platforms, please see section 3.

2.2. Order Processing

Orders from marketplaces such as eBay and Amazon are automatically imported into the customers
platform as usual. The Marketplace Module checks for new orders and imports them based on the rules* that
have been setup.

The orders that have been imported are each processed by FPS and the customers platform is immediately
updated* with the result of processing the order. This will be either success, or failure. Where an order has
failed, a reason will be provided in the message update and the customer will then have an opportunity to
contact FPS and resolve the issue. If an order is successful, tracking information for shipping will not be
provided immediately. Instead it is provided in a daily summary (see section 7).

* For supported functionality and your individual platform setup please see sections 3.3 and 4 respectively.

2.3. Shipping Updates

Orders placed throughout the day are updated with tracking information for shipping once per day at the
agreed schedule (see section 7). This tracking information will include the carrier name and tracking code.

2.4 SKU Format & Mapping

The Marketplace Module and marketplace listing platforms v 1.3

This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

The simplest way to setup a multi channel ecommerce platform in order to integrate with the marketplace
module is to use the FPS Part Number as the SKU. This allows for straight through processing and less
maintenance work. However, if a customer must use their own SKU format, then this is possible provided
that it follows a set pattern and the SKU contains the FPS Part Number as part of its structure.

In order to do this, the marketplace module will derive the FPS Part Number by breaking the SKU down
using certain characters as the delimiter. This can be a prefix character, a suffix character, or both. The
delimiter characters must not already be part of FPS Part Numbers. For example the underscore _ is
acceptable but the dot character . is not. Please see Supported Platforms section for details and
platform exclusions.

The following examples explain this.

Prefix Example:

A customer wishes to use their own SKU for the FPS Part Number GDB199
The customer prefixes their part number with their required SKU modification, for example
BRAKEPAD#GDB199.
In this case the character # is used as the prefix delimiter.
Suffix Example:

A customer wishes to use their own SKU for the FPS Part Number GDB199
The customer suffixes their part number with their required SKU modification, for example
GDB199_BRAKEPAD.
In this case the character _ is used as the suffix delimiter.
Prefix and a Suffix Example:

A customer wishes to use their own SKU for the FPS Part Number GDB199
The customer prefixes their part number with their required SKU modification, for example
BRAKE#GDB199. In addition, the customer suffixes their part number with their required SKU
modification, for example BRAKE#GDB199_PAD.
In this case, the character # is the prefix delimiter and the character _ is the suffix delimiter.
Multiple Position

A customer wishes to use multiple delimiters in a prefix or a suffix

The customer prefixes their part number with their required SKU modification, for example
BRAKE#PAD#GDB199.
In this case, the character # is the delimiter, but importantly, with a count of 2.
The above also can apply to suffixes.
The prefix and suffix rules that are provided to FPS apply to the entire SKU range that will be
used on the marketplace module, so all SKUs must have the same format.

The Marketplace Module and marketplace listing platforms v 1.3

This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

3. SUPPORTED PLATFORMS

3.1. Currently Supported

Volo Commerce (formerly eSellerPro) - https://www.volocommerce.com/

Seller Dynamics - http://www.sellerdynamics.com/

3.2. Supported Functionality

Volo Commerce Seller Dynamics

Inventory Update

Order Processing

Product Differentiation 1 2

Mark As Shipped

Add Shipment Tracking 3

1 Ability for the platform to easily mark those orders that should be automatically processed by FPS, and
those that should not.

2 Seller Dynamics supports this functionality but it would require the customer to change their SKU
references.

3 This feature is pending development and will be released in the future.

4. PLATFORM SET UP GUIDE

4.1.Volo Commerce
4.1.1. Request API User - Required

The Marketplace Module and marketplace listing platforms v 1.3

 This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

Request an API Username and Password from Volo Support or your Volo Account Manager. Explain that it
will be used to connect to the FPS eFulfilment Programme. Provide this API Username and Password to FPS.

4.1.2. Create Product Folder & Allocate SKUs - Required

This is an essential part of the setup process as it ensures that orders for products in your Product Range are
processed by FPS. FPS orders are identified by Product Folder name (note: sub folder name or Supplier
field cannot be used as they do not feature in the Volos API).

Create a new Product Folder (e.g. FPS Fulfilment) for items in your agreed FPS Product Range. To
1.
do this, in the left hand menu go to Maintenance Product Folders Add.

Ensure Volo SKU is the same as FPS SKU/part number, unless the customer is using their own SKU
2.
format, in which case the customer should supply their SKU rules as identified in section 2.4

SKUs that are in your agreed FPS Product Range should be added to this Product Folder. Initially it is
recommended that you do this for a single SKU or small range of SKUs for testing purposes.
3.
Note: Orders for products outside of the Product Folder will not be processed but the products may
have their stock levels updated on a regular basis if they are part of the agreed FPS Product Range.

4. Provide this exact Product Folder name to FPS.

4.1.3. Carrier Rules - Optional

FPS offer two shipping options, MetaPack (via FPS) and Royal Mail.

If using MetaPack (via FPS), then you need to select this courier option in Volo. You may need to use Postage
Template in Volo to set this up, please consult with Volo. Orders will be booked onto the Carrier service as
agreed with FPS eFulfiment as part of the on-boarding process. Note: Volo offers integration with MetaPack
via Seller Rules, but it is important to note that this is not used in the FPS eFulfilment process.

If using Royal Mail, in Volo you must set up Seller Rules. To do this, go to Courier Seller Rules. Volo
will be able to assist you in this. As part of the Marketplace Module, FPS will receive some data from Volo to
indicate the correct carrier service the goods should be booked onto. Therefore it is important that you share
your Seller Rules with FPS eFulfiment, in particular providing the information that is contained in the Source
Shipping Method field, this will be a code such as RMC-48SP.

The Marketplace Module and marketplace listing platforms v 1.3

 This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

4.1.4. Stock Location - Optional

If you wish for your FPS Product Range to be allocated to a particular Stock Location, e.g. FPS Fulfilment or
Virtual Stock, then you must create a new Stock Location and allocate SKUs to it.

1.
To do this, go to Maintenance Locations Add.
2.
Add the new stock location.
3.
SKUs that are in your agreed FPS Product Range should be associated with this Stock Location.
4.
Provide this exact Stock Location name to FPS.

4.2. Seller Dynamics

4.2.1. Request API User - Required

Request an API Account from Seller Dynamics Support or from your Seller Dynamics Account Manager. This
will have two attributes: a Retailer ID and an Encrypted Login. Explain that it will be used to connect to
the FPS eFulfilment Programme. Provide the Retailer ID and Encrypted Login to FPS.

4.2.2. Prefix SKUs in Product Range - Required

In order for FPS to identify those orders that should be processed by FPS eFulfilment, the SKUs in the
Product Range should be prefixed with a unique identifier. The customer can choose what this unique
identifier is.

For example, if the unique identifier was FPS-, then a SKU of ABC123 would become FPS-ABC123. This
change must be carried out for each SKU in the range and will not affect the marketplace listings.

The Marketplace Module and marketplace listing platforms v 1.3

This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

5. MONITORING ACTIVITY

5.1. Volo Commerce

5.1.1. Inventory Updates

If there is a stock change for a given SKU in Volo it will be visible in the Movements screen, which can be
found under Inventory Details Movements.

The screenshot below shows a line External Stock. The description is API V2 Update Adjustment: 30. This
means that the inventory was set to 30 by the Marketplace Module.

5.1.2. Order Processing

5.1.2.1. Successful Orders

Successful orders will be updated in the Memo window, located in the bottom right of the
Payment/Shipping tab of the Sales Orders Screen. Successful orders will remain on the Waiting for Delivery
status until the Shipping information is added, at which stage the order is marked as Shipped.

5.1.2.2. Failed Orders

If an order fails it will be put at the status On Hold on the Sales Orders screen (see lines in turquoise with
the red stop hand)

10

The Marketplace Module and marketplace listing platforms v 1.3

This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

The reason for the On Hold status can be seen by hovering over the red hand icon or on the Order History
/ Notes tab of the Sales Orders Screen.

FPS eFulfilment will assist in determining the reason for a failed order. Common problems include incorrect
delivery address information. Once identified, FPS eFulfilment can coordinate the successful reprocessing of
the order and the status in Volo will be updated accordingly.

5.1.2.3. Exported Orders Not In Marketplace Module

Occasionally, orders will be exported from Volo, but not successfully entered into the Marketplace Module.
In this rare instance, FPS are unable to retrieve this order for a second time and FPS eFulfilment may request
that you duplicate the order(s) to be reprocessed successfully, cancelling the original in your Volo system.

5.1.3. Shipping Updates

At 19.00hrs each evening orders that have been successfully placed during the trading day are marked as
Dispatched and the tracking information is available on via Sales Orders Consignment.

5.2. Seller Dynamics

5.2.1. Inventory Updates

Inventory updates are visible via Bulk Edit Own Stock Import Summary Activity. Please see the
screenshot below. The stock import displays a date and time and an indicator as to whether it was completed
successfully or not. There is also a count of SKUs updated under the Uploaded column. This should match
your Product Range count.

11

The Marketplace Module and marketplace listing platforms v 1.3

This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

5.2.2. Shipping Updates

Orders being processed during the day will be in a Pending state.

Later in the day, if successful, these orders will be marked as Dispatched and visible in the History tab.

6. PLATFORMS SPECIFIC API MESSAGE

6.1.Volo
6.1.1. Volo Order Processing message
TBC

12

The Marketplace Module and marketplace listing platforms v 1.3

This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

6.1.2. Volo Order/Shipping Update message

TBC

6.1.3. Volo Inventory API message

TBC

6.2. Seller Dynamics

6.2.1. Seller Dynamics Processing message
TBC

6.2.2. Seller Dynamics Order/Shipping Update message

TBC

6.2.3. Seller Dynamics Inventory API message

TBC

7. MARKETPLACE MODULE IMPORT / EXPORT SCHEDULE

Direction Process Schedule

Upstream Update Inventory 08:05, 10:05, 12:05, 14:05, 16:05,

18:05, 20:05, 22:05, 00:05

Downstream Retrieve New Orders From Platform Every 30 minutes

Downstream Process New Orders Into NDC Every 30 minutes (10 minutes
past order collection/retrieval)

Upstream Update Shipping Information Once per day at 1900 (where

applicable)

13

The Marketplace Module and marketplace listing platforms v 1.3

This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

8. CHECKLIST / STEP BY STEP

# Task

1 Ensure that you have an FPS eFulfillment Account set-up

2 Setup API User with your Multi Channel eCommerce Platform. Provide credentials to FPS
eFulfilment

3 Agree SKU Range with FPS

4 Setup your Multi Channel eCommerce Platform as per the information in section 4 and
provide any information requested by FPS eFulfilment. Do this for a single SKU, or small set
of SKUs.

5 Place a test transaction and notify FPS eFulfilment when this has taken place

6 Once the test transaction has been successful, repeat step 4 for your full SKU range

14

The Marketplace Module and marketplace listing platforms v 1.3

This document is CONFIDENTIAL and subject to standard T&Cs and Non-Disclosure Agreement (NDA) terms. The document is sole
property of FPS and cannot be used by any third party without prior written approval by FPS and a signed copy of the NDA.

APPENDICES

15

The Marketplace Module and marketplace listing platforms v 1.3