Fluent Commerce Logo
Docs
Sign In

Enable Fluent Store on your Existing Account

How-to Guide

Author:

Fluent Commerce

Changed on:

19 Sept 2024

Key Points

  • Verify Compatibility: Ensure your existing account meets all prerequisites for enabling Fluent Store.
  • Follow Step-by-Step Guide: Adhere to the provided instructions to enable Fluent Store on your account seamlessly.
  • Utilize Support Resources: Refer to the official documentation and support channels for any issues or queries.

Steps

Step arrow right icon📺 Watch this quick demonstration on how you can enable Fluent Store.

Enabling Fluent Store

Watch this quick demonstration on how you can enable Fluent Store.

Step arrow right iconAssumptions

  • An existing FluentCommerce Account with atleast one Retailer will be setup
  • Global Inventory will be enabled on the account
  • Atleast one valid Location and Location user will be set up
  • The location user will have one of the following roles assigned on the RETAILER and AGENT context, with the following permissions 
    `ROLE NAME: STORE/ STORE_ASSISTANT`

Step-by-step guide

Step arrow right iconUpdate location user with the correct permissions

Update the role assigned to your location user with the following permissions:

  • LOCATION_VIEW
  • PRICE_VIEW
  • RETAILER_VIEW
  • SETTING_VIEW
  • CARRIER_VIEW

To update the Role, you can run the following mutation in an API client that supports GRAPHQL queries and mutations, like the POSTMAN or a GRAPHQL client (GRAPHiQL).

1mutation{updateRole(input:
2{name:"STORE"
3permissions:
4 [
5   {name:"LOCATION_VIEW"},
6   {name:"RETAILER_VIEW"},
7   {name:"PRICE_VIEW"},
8   {name:"SETTING_VIEW"}
9   {name:"CARRIER_VIEW"}
10 ]})
11 {id
12 name
13 permissions{name}}}

Language: json

Name: Code Sample

Description:

[Warning: empty required content area]

Step arrow right iconUpdate Location Workflow with the user actions

Fluent Store adapts the user actions in the workflow. In this step we will configure the user actions in the Location workflow. These user actions are required by a store user to complete the pick and pack process required to fulfil online orders.

In the previous store UI, these user actions were coded into the UI and was not read from the workflow. Whereas, in the new store web app Fluent Store, these user actions will be read from the Location workflow.

In the reference solution, Fluent Commerce provides the following user actions to complete the pick and pack process:

1.CREATE WAVE

  • Ruleset Name: WaveCreate
  • Subtype: 
    `"subtype": "STORE",`
  • User Action Value:
1    "userActions": [
2        {
3            "context": [
4                {
5                    "label": "Create Wave", 
6                    "type": "PRIMARY",
7                    "modules": [
8                        "servicepoint"                             
9                    ],
10                    "confirm": false
11                }
12            ],
13            "attributes": [
14                {
15                    "name": "maxCount", 
16                    "label": "fc.sf.ui.waves.index.create.numberOfFulfilments.label", 
17                    "type": "INTEGER",
18                    "defaultValue": 1,
19                    "mandatory": true
20                },
21                {
22                    "name": "userName",
23                    "label": "Wave Owner",
24                    "type": "STRING",
25                    "source": "loggedInUsername",
26                    "defaultValue": "",
27                    "mandatory": false
28                }
29            ]
30        }
31    ]

Language: json

Name: WaveCreate

Description:

[Warning: empty required content area]

2. CONFIRM PICK

  • Ruleset Name: PickConfirm
  • Subtype: 
    `"subtype": "STORE",`
  • User Action Value: 
1    "userActions": [
2        {
3            "context": [
4                {
5                    "label": "CONFIRM PICK",
6                    "type": "PRIMARY",
7                    "modules": [
8                        "servicepoint"                               
9                    ],
10                    "confirm": true
11                }
12            ],
13            "attributes": [
14                {
15                    "name": "pickedItems",
16                    "label": "PICK",
17                    "type": "PICKED_ITEMS",
18                    "mandatory": true
19                }
20            ]
21        }
22    ]

Language: json

Name: PickConfirm

Description:

[Warning: empty required content area]

`
`
3. CONFIRM PACK

  • Ruleset Name: WaveDispatch
  • Subtype: 
    `"subtype": "STORE",`
  • User Action Value: 
1    "userActions": [
2        {
3            "context": [
4                {
5                    "label": "CONFIRM PACK",
6                    "type": "PRIMARY",
7                    "modules": [
8                        "servicepoint"                          
9                    ],
10                    "confirm": true
11                }
12            ],
13            "attributes": []
14        }
15    ]

Language: json

Name: WaveDispatch

Description:

[Warning: empty required content area]

`
`
4. COMPLETE WAVE

  • Ruleset Name: WaveComplete
  • Subtype: 
    `"subtype": "STORE",`
  • User Action Value: 
1    "userActions": [
2        {
3            "context": [
4                {
5                    "label": "Wave Complete",
6                    "type": "PRIMARY",
7                    "modules": [
8                        "servicepoint"
9                    ],
10                    "confirm": false
11                }
12            ],
13            "attributes": []
14        }
15    ]

Language: json

Name: WaveComplete

Description:

[Warning: empty required content area]

`
`


Step arrow right iconAdd the “subtype” to the following rulesets in the Home Delivery order workflow

Ruleset Name

Ruleset Description

Subtype Value

ARTICLE_COLLECTED

Ruleset responsible for marking the articles as Courier Collected

"subtype": "DEFAULT"

Step arrow right iconAdd the “subtype” to the following rulesets in the Click & Collect order workflow

Ruleset Name

Ruleset Description

Subtype Value

ARTICLE_COLLECTED

Ruleset responsible for marking the articles as Customer Collected

"subtype": "DEFAULT"

ARTICLE_ARRIVED

Ruleset responsible for marking the articles as Arrived in store (for the use case of inter store transfers only)

"subtype": "DEFAULT"

ArticleCancellation

Ruleset responsible for cancelling the Uncollected articles

"subtype": "DEFAULT"




Step arrow right iconLog in to Fluent Store

Log in to the URL, 

`<ACCOUNT_ID>.apps.fluentcommerce.com/store`
 with the location user credentials

You are now ready to use the Fluent Store App.

Fluent Commerce

Fluent Commerce

Copyright © 2024 Fluent Retail Pty Ltd (trading as Fluent Commerce). All rights reserved. No materials on this docs.fluentcommerce.com site may be used in any way and/or for any purpose without prior written authorisation from Fluent Commerce. Current customers and partners shall use these materials strictly in accordance with the terms and conditions of their written agreements with Fluent Commerce or its affiliates.

Fluent Logo