### nShift and Drop Zone configuration
When picking of a Dispatch Order is finished, new shipment 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.
UseDispatchServiceForShipments
If true, shipments are created via DispatchSerivce, using Consignor/nShift as a provider.
NshiftDropZoneConfiguration
Used for configuring the nShift integration per store. The values in this parameter is set by the UI in InStore App under settings:
This parameter should not be modified manually (But it can be if needed), but rather through the 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.
Configure nShift per store, and is a JSON object where each key corresponds to a store number. Example for store 222:
```json
{
"222": {
"TicketUsername": "leasv@eg.no",
"WorkstationId": "DA470611-82F0-4AE7-8A8D-C307C1456C99",
"LabelFormat": pdf
}
}
```
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.
More information about setting up nShift Drop Zone agent here.