### nShift and Drop Zone configuration
When picking of a Dispatch Order is finished, new shpiment is created using configured provider. There are two system parameters in _CustomerOrder_ area for shipment configuration. This configuration is used by _CustomerOrderService_, so modifying the parameters affects other ways of creating shipments as well.
| Name | Type | Default value | Description | Remarks |
| ------------------------------------ | ------------------------------------- | ------------- | ----------- | ------- |
NshiftDropZoneConfiguration | JSON string | \{\} | Used to configure the nShift integration per store. This parameter should not be modified manually, but rather through the [Settings](#settings) page in InStore App. | The value is a JSON object where each key corresponds to a store number where the nshift configuration should apply. See example below.
UseDispatchServiceForShipments | boolean | false | If true, shipments are created via DispatchSerivce, using Consignor/nShift as a provider. | Supported values: _true_, _false_. Case insensitive.
_NshiftDropZoneConfiguration_ is used to configure nShift per store, and is a JSON object where each key corresponds to a store number. Example for store 222:
```json
{
"222": {
"TicketUsername": "dummy-user-222",
"WorkstationId": "DUMMY-ID-1234-ABCD",
"LabelFormat": null
}
}
```
Where:
* TicketUsername - username from nShift. Configured in [Settings](#settings) page.
* WorkstationId - workstation (installation) id from Drop Zone client. Configured in [Settings](#settings) page.
* LabelFormat - configured when finishing order. Last used value is saved as default.