Guide for Master data

In an enterprise s'etup, Master data source is always a 3rd party solution where production data is managed. Typically it is your ERP being the master data source. 
At the minimum the following data must be available at your master data source and pushed to Front Systems whenever there are new data available.

BASIC MASTER DATA

REQUIRED

We define the basic master data as:

  • Product name Eg. Air Max

  • Product number (style no) Eg. M123456

  • Color code (Variant) Eg. 00001
    Typically productNumber + Color code is the unique VariantID in your master data source. M12345600001

  • Brand Eg. Nike

  • Group Eg. Sneakers

  • Season Eg. BASIC, 2104, Etc

  • Color Eg. Black diamond

  • EAN/GTIN Eg. 70451234567891

  • External SKU Eg. 123456789. This is the SKU identifier used in the master data system.

  • Size Eg. XL

PRODUCTS

Use the Products CRUD API to maintain products in Front Systems. A product in Front Systems is defining the master data on the number-variant level. It can have many sizes, but the sizes included in the variant must share prices. Products are instantly updated in Front Systems whenever you do updates in your master data source. This is especially interesting when it comes to prices. However, it can take up to 15 minutes before the changes are visible in the POS and in the portal.

IMPORTANT
When creating products, you must include all available sizes from the master data source.
eg. if a T-shirt can be available in XS, S, M, L, XL then you should include all those sizes and their GTINs in the payload.
To Create a Product
POST /api/Products

Example body request to create a product

{
"name": "Letto Lady Jkt",
"number": "139539393",
"variant": "0045",
"groupName": "Jacket",
"color": "Jacket Shell",
"season": "Winter 2020",
"brand": "Bergans",
"price": 2500,
"description": "Letto er en meget lett 3-lags skalljakke i Dermizax®-membran, lav vekt og minimalt pakkvolum.",
"productSizes": [
{
"externalSKU": "053569470207",
"gtin": "7031582003441",
"label": "S"
},
{
"externalSKU": "053569470209",
"gtin": "7031582003458",
"label": "M"
},
{
"externalSKU": "053569470211",
"gtin": "7031582003465",
"label": "L"
}
],
"images": [
"https://exampleurlfrompim.com/a4b4ec82-d655-4e46-ba11-87a250807d1a.jpg",
"https://exampleurlfrompim.com/49c26de8-8686-47d3-a90a-2de7238ec1ec.jpg",
"https://exampleurlfrompim.com/23c394bb-f381-4467-aade-bb4bbc7ab704.jpg",
"https://exampleurlfrompim.com/899fa291-3934-4a8d-b10a-978044aa948e.jpg",
"https://exampleurlfrompim.com/7f39f934-6fe8-4db0-abd9-8541d7aa3306.jpg"
],
"cost": 500
}

PRICES

REQUIRED FROM START

Prices can be divided into different price lists based on the retailer need. If the retailer have stores in several countries/currencies, use of price lists is mandatory.
Eg. one price list per currency. Each currency can be represented by one or more price lists. Eg one price list of Flagship stores operating in Euro, and another price list for outlet stores in Euro. 

As soon as you have created the price-lists relevant for you, inform your contact person at Front Systems so she/he can assign the price lists to the relevant Stores.

To Create or Update a PriceList
POST /api/PriceListV2

Cost prices is maintained per Stock (usually 1-1 relationship with Store) in Front Systems. The simplest way to update the cost prices is using the cost price endpoint with update on the currency level.

As soon as you have created the price-lists relevant for you, inform your contact person at Front Systems so she/he can assign the price lists to the relevant Stores.

To Create or Update cost prices
POST /api/Pricelist/cost

ENRICHED MASTER DATA

To enable the store associates to use front systems as a sales tool, they need to able to see the same images and product descriptions you already have available on your web shop. This integration is not necessary to begin with. You can easily set this up later during or after the pos rollout. On the other side, having images in the pos from day one, leaves a pretty nice first impression. Out of the box, Front Systems support the  PIM , InRiver. If that’s your PIM, jackpot! Just send the Api-token to your Front Systems contact person and we will have the integration up and running in no time. In case you have another PIM or you would like to control the integration your self, then go ahead and read.

Loop through your products and update them using
PUT /api/Products

Include only images and description in the body if you only are updating those.
In case you dont have the Front Systems ProductId, then look it up by using the GetProductByGTIN endpoint.

Example update payload

{
"description":" "Our model is 186cm long and is wearing a Medium",
"images":" [
"https://yourpimsourceurlexample/1",
"https://yourpimsourceurlexample/2",
"https://yourpimsourceurlexample/3"
]
}

TIP: The first url in the images array will be set as the main image in Front Systems.