--- title: Importing Options slug: importing-options createdAt: 2026-04-23T16:00:03.346Z --- Connecting planeus to your existing IT system is straightforward. You can manage the main import and interface settings in one place: **Administration → Settings → Import / API** # Key settings at a glance ::Image[]{src="https://api.archbee.com/api/optimize/M1QBpK9lJudQQL_d-GMK2/gWrMG3NuWGp2x-MI2D6pL_image.png" size="80" isUploading="false" width="682" height="334" darkWidth="682" darkHeight="334" position="flex-start" showCaption="false"} Here are some of the most useful options: - **Reschedule by changing delivery dates** planeus can automatically react when delivery dates change in the source system. - **Update order items during import** If an order item already exists, planeus can update it with the latest imported values. - **Automatic scheduling options** You can decide whether planeus should schedule order items automatically and how strictly it should follow planning rules. - **Comment handling** You can choose whether imported comments should replace existing comments. - **Email notifications for import errors** planeus can notify your team when an automatic import fails, so issues do not go unnoticed. # Flexible import parameters planeus includes a range of import parameters that let you fine-tune how the system works with your data. These settings apply across all supported import types, including: - manual import - automatic import - weclapp - Unleashed Some advanced settings would require support from planeus teams. Contact the planeus customer service team for details. | Option | What it means for your integration | Possible values | Default Values | | ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -------------- | | **Plan anyway (PlanAnyway)** | Force planeus schedule an order by ignoring all constraints.

This is useful for urgent orders or activities that still need to go ahead, even when the required resources are not fully available. This will create planning conflicts that need to be resolved in planeus. | Yes / No | No | | **Update order items (UpdateOrderPositions)** | Updates existing order items when imported data changes, for example item, quantity, or dates. | Yes / No | Yes | | **Update not planned order items (UpdateNotPlannedOrderPositions)** | Updates order items that are not yet scheduled when new data is imported. | Yes / No | No | | **Do not plan order items automatically (DoNotPlanOrderPositions)** | Order items will not be automatically scheduled in planeus when imported.

This means they will require manual scheduling through Planning Objects before they appear on the Gantt charts. | Yes / No | No | | **Automatically set missing order items to “Completed"** | The Status of Order Items will be changed **Completed** if they are no longer included in the imported data.

This also means they will no longer shown on the Gantt charts.
Use this carefully, because it can affect many records at once. | Yes / No | No | | **Do not update comment (DoNotUpdateOrderPositionComment)** | Keeps existing comments in place and prevents imported data from overwriting them. | Yes / No | No | | **Update planned order items (UpdatePlannedOrderPositions)** | Updates data in **Scheduled Order Items** when new data is imported. | Yes / No | No | | **Date formats (DateFormats)** | Defines which date formats planeus accepts during import. Multiple formats are possible. | Example:
**dd.MM.yyyy hh\:mm\:ss, MM/dd/yyyy 00:00:00** | - | | **CultureInfo** | Defines the regional format used to read and convert dates correctly. | Example:
**en-EN, de-DE** | - |