Webstores

Configure connectivity to webstore

Ability to configure connectivity to a webstore

Ability to support connectivity to multiple webstore platform

Ability to maintain / amend connectivity configuration

Exists for shopify - others TBC

High

Customer store set up processing

This exists as chargeable service but there is no infrastructure to capture fees

• Ability to record store set up / product mapping work

• Ability to generate invoices for above

New

TBC/High

Define Webstore Entity

Ability to support multiple webstores per company

Ability to treat webstore as unique entity (contacts, prices, credit limits, invoicing, definition)

Ability for webstore to optionally inherit parent company definition parameters if so defined

Enhancement

High

Define Business/Service Parameters

Ability to define terms of business for webstore

 - delivery schedules

 - SLA terms

 - pricing matrices (processing, garments, shipping, packaging etc)

 - business services (processes, packaging etc)

 - shipping agents; service methods

Enhancement

High

Inventory Synchronisation, Alignment and reconciliation

• Ability to consume inventory data from webstore

•  SKU data , (ids, description, imagery, customs codes, weights, etc.....to be fully defined)

• Ability to rapidly / easily map / align webstore SKU data to internal item data objects

• (common id - or push TOT reference to web platform ?? )

• Ability to create internal item objects from webstore inventory

• Ability to reconcile item inventories between internal system and webstores

• Ability to update internal item attributes

• Ability to push updates to webstore products - qtys

Enhancement

High

SKU Profile

• I suspect this will come out of the POGO group integrations - the concept of having a profile at the level of the SKU or similar

• this would contain the data set for

• Processes to use for an order against that product  - e.g. print front, print back, sew in label etc;

• Garments to use

• Design(s) to print

• Any other parameters - (maybe delivery, specific tooling ?)

Assuming we go down this path, I would think the following would be needed

• Ability to define a profile

• Ability to assign a profile to one or more products

• Ability to easily duplicate a profile and assign to another SKU

• Ability to amend a profile

New

TBC

Barcode Identification

Ability to generate (and read) unique barcode identifiers for items

For OTS products - represents the Item

For POD product  - it is attached to the input blank garment and represents not just item attributes (including design) but the associated webstore order that generated the POD requirement

(Thus POD barcode is both item and order identifier)

Exists

Essential

Returns Functionality

New Functionality to accommodate order returns

two main aspects

• Inventory Management - return to stock ; exchange etc

• Fee capture and invoicing

New

TBC / High

Booking In / Storage Processing

New Functionality to capture services rendered for Storing

i.e.

• Barcodes generated

• Machine Bagging

• S/Seal Bagging

• Booking In time.

Note: currently webstores process a PO to book in OTS stock and generate the barcodes as part of this and don't charge per barcode. Additionally, if client wants their stuff bagged - only way to currently do would be raise manual job for the processes - so 2 sets of objects and invoiceable data

New

TBC / High

Support other Webstore services planned / listed on price sheets

There are a series of services on the Webstore price cards that do not currently have system functionality / capability

Below is an overview of these

• Transfer on Demand

• Embroidery on Demand

• Other Processes (there are multiples)

• Stickers on Demand

• Direct to Film

• Delivery Packing

• Returns

• Storage

• Store Set up / Mapping

Work will be needed to understand the data requirements / model for these services and thus how they can be incorporated / unified with TOT existing services  data models

New

TBC / High

Webstore Product Consumption / Internal Product Creation

• Ability to consume product data from external source (both webstores and for example via a file)

•  SKU data , (ids, description, imagery, customs codes, pricing, weights,identifiers, barcodes any custom metafields) etc

• Ability to rapidly / easily map / align external SKU data to internal item data objects

• Ability to define / apply a mapping template that can be assigned to a webstore to assist in mapping external <--> internal items

• Ability to amend / Duplicate / Delete template

• Ability to assign single template to multiple stores

• Provide for the ability to update internal data values from external items using template

• Provide for the ability to create internal item objects from external items using template

• Provide for reporting / Control around consumption of external item data / objects to allow users to see statuses, where errors occurred etc

Bottom line webstores / POD is expected to be balloon in size (order of magnitude above current), so future state must have capabilities to make data exchange easy, rapid and controlled.

Enhancement

High

Webstore Product Art Consumption

• Ability to consume high resolution artwork

• Ability to link artwork to design / group / sku profile

• Ability to interface with art required records so new artwork can be processed

I think this is worthy of some discussion - rules of the road. What level of art room processing is required for POD  - aside from ripping ? - are there visuals required / approval needed

Can the ripping process be automated ?

Exists / Enhancement

Essential

Webstore Product Alignment and Reconciliation

• Ability to automatically reconcile item inventories between internal system and webstores

• Ability to on demand reconcile inventories - by store; by company

• Ability to push updates to webstore products - Qtys etc

Exists

Essential

Ability to consume orders from external webstore (or other external source)

Provide capability to do this at the single webstore level

Provide capability to do this at multiple webstore level

Provide capability to do this at all webstores level

Provide capability to run above on schedule

Provide capability to do this on demand at above level(s)

Note: This needs to be performant and scalable.
Current volume ~150 orders per day
Assume this can grow to 1,500 per day very quickly

Exists & Enhancement

Essential

Confirm / Control consumed orders

Provide confirmation to source system as required

Provide control / status overview to show successfully received orders

Provide ability to correct / replay orders where required

Exists

Essential

Creation of internal order records

Create equivalent internal order records ready for processing

[Internal order records need to contain sufficient data to support manufacture, delivery and invoicing processes]

Respect webstore single order id per customer order dimension

Order creation should account for the quantity ordered and deduct this from corresponding SKU balance

Note: As per earlier, service parameters - the order needs to be created with all invoiceable elements - with details per the charging matrices / price cards
There is a gap in this currently as pricing cards have a series of services / chargeable items that are not supported by system functionality

Exists

Essential

Ordering of input garments required for POD order

Currently order creation process allocates blank input garments where they are available

Where item is not available the requirement is added automatically to order bucket functionality together with associated order reference

This form of pro active inventory ordering will be needed in a future state

Organise Workload

Staff currently manually tag orders as POD or OTS (or combination) as this guides the initial picking processes

Given that we know the contents of the order and by extension whether the items need to be manufactured or not, this manual tagging should be automated

Exists & Enhancement

Essential

Ability to organise orders into sets for picking

Currently staff generate a list of job orders with their associated job order barcodes, and scan these along with a trolley barcode to create a workload for picking that is processed via a mobile device

A future state should automate this process - i.e. ability to simply create a picking workload based on a series of orders, associate that to an individual and have it available on a mobile device

Exists & Enhancement

Essential

Process Picking Requirements - Retrieving items

Provide user with optimum route to retrieve  items from storage locations

Provide user with ability to scan items in location to process retrieval  action
Validate that scanned barcode is for the ordered product - if not - prevent the user retrieving it

provide user with ability to accommodate situation where physical qty < pick requirement
> update the picking workload with additional location(s) if possible; else account for qty retrieved and loop to next item

At the end of this process, staff have a trolley with a series of OTS items in it

i.e.

per order identifier - SKU ordered qty; retrieved qty , trolley location identifier

the following metrics should also be recorded

start time, end time; and total duration

Exists & Enhancement

Essential

Process Picking Requirements - Generate Delivery Notes

Provide ability to generate a list of orders that are contained in the picking trolley

This creates a foundset of job records where the requirement is in the picking trolley

Staff then interrogate this list of records to ensure that all shipping information is present (courier, service code, packaging requirements, weight etc)

Provide functionality for orders to make API call to external couriers to obtain shipping references / prepaid labels

Note: Currently TOT does not record what the API response is in terms of cost of the requested service. This should be done so that reconciliation of courier charges can be done and also allow analysis of what customer is charged vs TOT cost

Provide capability to generate delivery notes for this foundset of orders
(these are then "married" to picking pods in next capability)

Note: the delivery note contains a shipping section that can be peeled off and attached to packaging in final process

Exists & Enhancement

Essential

Process Picking Requirements -Placing Delivery Notes

Users place each printed delivery note in a unique "picking POD"

Provide users with ability to scan delivery note and picking pod location to record

Delivery Note (i.e. order identifier) with Picking pod location

Record this data

Exists

Essential

Process Picking Requirements - Marrying retrieved items to picking pod locations

Staff physically select a picking trolley and scan its location barcode to bring its order contents to focus

(Is this necessary given next processes)

Provide capability to scan barcode of item in trolley

Provide system function to audibly tell user which picking pod into which the item should be placed

Provide functionality to confirm this by scanning the picking pod location

Update SKU picking requirement (picked Qty and status, location update)

Provide control capability to prevent user scanning a SKU into the incorrect picking POD
(i.e. when user confirms the pick by scanning the picking pod location, it should validate that the SKU is required on the corresponding delivery note)

Exists

Essential

Process Picking Requirements - Packaging and Despatching Goods

For each fully picked pod / order - staff interrogate the corresponding order reference to determine what packaging is needed (parcel, letter etc)

** Can we not automate this - and somehow pro-actively expose the packaging requirements  is needed per picked pod  **

Provide ability to scan the delivery note and mark the corresponding order as sent

Provide capability to confirm the sent status to source webstore

Provide capability to communicate shipping references / identifiers to source webstore

Provide capability to communicate status and shipping references to additional parties

Update internal record as sent

Record date / timestamp

Exists & Enhancement

Essential

OTS Picking  - MIS

in a future state recording the processing times will be crucial to identify, predict and mitigate processing pinch points

Therefore MIS for timings should be captured and persisted into an environment to facilitate analysis

Enhancement

High

Identification of Blank garment to order

Provide capability of generating unique barcode  per each blank garment that will be required to manufacture a POD order

barcode contains key information

The order identifier - e.g. customer, shipping details etc

The POD manufacturing requirements - SKU (colour, garment type etc) - POD image

Note: a customer order can be for multiple SKUs / Qtys of a SKU - but a single web order  cannot be for multiple customers

Exists

Essential

Printing of POD image

This is currently done as part of the DTG workload

Provide capability to recall process information from barcode

Provide capability of recalling required design from barcode

Provide capability to book in printed SKU into a location (typically a POD trolley - Pink 3
Note: webstore team informs me that all POD jobs when raised locate the stock into Pink 3)

The physical trolley containing multiple POD printed orders is then provided to webstore staff

Unless it has other processes required in which care > Other processes team

Exists

Essential

Process POD Picking Requirements - Processing the Pick

Provide capability to scan a trolley location and return its contents and associated order identifiers

Provide capability to scan barcode of item in trolley to trigger the following updates if fully picked

 - API call to external couriers to obtain shipping references / prepaid labels

 -  print delivery note

 - update sku qty as picked ; dr available and location balance

 - mark the associated order as sent > send notification to webstore and any interested parties

Provide functionality to accommodate part-pick

 - if the barcode scanned is for an order with other items which are partly picked - notify user of the part pick location and assuming all now fully picked proceed

 -if the barcode scanned is for an order where the other items have not yet been picked - notify the user that of this and provide capability for them to record a part picked location to store the item in

Exists

Essential

Charge capturing

Automate the capture of charges according to the services provided on the order

partial - needs reengineering

Essential

Invoicing

TBD - as part of invoicing requirements - but existing invoicing information is poor and manually processed outside production application

This is likey inadequate for larger scale operations.

Additionally, what is the SLA for webstore owner payment receipts - B2C webstores are paid at order inception, so should be invoiced promptly  ??

Enhancement

Essential

Exchanges

Ability to support returns and exchanges workflow - TBD

Include position adjustments

fees

Enhancement

Essential

Storage

Ability to support storage services :-

 - barcoding

 - custom bagging

 - storage costs

 - invoicing this

 -

Enhancement

Essential

Consultancy

Product Mapping

Store set up / assistance

How to track / invoice this?

Enhancement

Essential

Portal

Webstore orders are not properly exposed through the portal

Serious consideration needs to be given to minimise client enquiries

Information to expose

Store Level  - orders by date etc

Order level info - see whether produced, picked, packed, despatched etc

Dimensions - at the level of the webstore presumably

This really should be the conduit for reporting / invoice statements etc.

TBC

TBC

Design Receipt

Can we not look to get customers to drop the design imagery into an online record

TBC

TBC