Configuration parameters
A few Click and Collect behaviours are configurable rather than fixed: when an order counts as urgent, how deep the picker's category tree goes, which container the picker is offered by default, and which barcode format a scanner produces.
These live in the Customer Configuration Center under the configuration kind cnc.configurations.v1, like the settings of every other Hii Retail service. Click and Collect has no configuration store of its own, and it is the Customer Configuration Center — not the Click and Collect API — where you set them.
Settings apply per business unit
Configuration resolves per business unit, not per tenant. Two stores under the same tenant can run different values.
You do not have to set every value on every store. The Customer Configuration Center resolves the hierarchy for you: set a value at the tenant level and every business unit inherits it, then override individual stores where they differ. Click and Collect receives the already-resolved value for each business unit and applies it as given — it does no inheritance of its own.
The practical consequence: there is one place to look when a store behaves unexpectedly — that store's resolved configuration. If it disagrees with what you set at tenant level, an override exists somewhere above it.
The parameters
| Id | Values | Effect |
|---|---|---|
urgentOrdersMaxValueForNotInProgress | non-negative integer, hours; 3 when unset | an order that has not been started is flagged urgent when its deadline falls within this many hours |
urgentOrdersMaxValueForInProgress | non-negative integer, hours; 3 when unset | the same, for an order already being picked |
highestVisibleItemCategoryLevel | positive integer | how many levels deep the picker's category tree goes. Categories at this level become the top level the picker sees |
defaultContainerType | PAPER_BAG, PLASTIC_BAG, CARDBOARD_BOX, GIFT_BOX | the container preselected when a picker records what the shopping went into |
barcodeNumberFormat | DataBar, DataMatrix, Plu, VariableWeightGtin | how a scanned barcode is interpreted when reporting picked lines |
The set is closed. These ids are the only ones Click and Collect recognises. You cannot define your own parameter — there is no mechanism for adding one without a change to the service. The kind holds a few further ids belonging to parts of the service these pages do not cover; treat the table above as the set that is meaningful to configure.
defaultContainerType saves a tap, it does not constrain the picker
Setting it preselects that container in the picker's packaging step. A store that only stocks paper bags sets PAPER_BAG once and its pickers never choose again — they just enter how many.
⚠ It is a default, not a restriction. A picker can always choose a different container; the setting only decides what is offered first, and a picker who deliberately switches keeps their choice on that device. So a store default never fights someone who has a reason to differ.
When an order counts as urgent
An order is flagged urgent when its pickup deadline falls within the threshold for its state, counted from now. Which threshold applies depends on whether picking has started: an order nobody has started uses urgentOrdersMaxValueForNotInProgress, and one already being picked uses urgentOrdersMaxValueForInProgress.
Two cases do not depend on the thresholds. An order past its deadline is always urgent, and an order due on a later day is not urgent yet, however small its distance in hours.
Unset, each threshold is 3 hours. A store that never sets them still gets a working urgency flag. Set them when your stores need a different warning.
The two are separate on purpose. An order nobody has started needs a longer warning than one already being picked, so the not-in-progress threshold is normally the larger of the two.
A change reaches the service asynchronously
Click and Collect keeps its own copy of the resolved configuration and serves reads from that. A change made in the Customer Configuration Center propagates to that copy; the two are not the same store and are not updated in the same instant.
In practice this means a configuration change is not an instant switch. If it has to coincide with something else — a store opening, a campaign — make it in advance rather than at the moment it must take effect.