> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/system-admins/administration/data-manager.md).

# Data Manager

Data Manager configuration defines how files enter and leave the HotWax Commerce Order Management System. Use these administration pages to maintain import services, execution modes, templates, and queue behavior.

Use Job Manager for daily operations:

* [Upload a file manually](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/retail-operations/workflow/job-management/mdm/manual-uploads.md)
* [Monitor file processing](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/retail-operations/workflow/job-management/mdm/file-history.md)
* [Review file details](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/retail-operations/workflow/job-management/mdm/file-details.md)

## Open Data Manager configurations

1. Open the Order Management System.
2. Open the main menu.
3. Select `Settings`.
4. Select `Data Manager Configurations`.

The exact administration menu depends on the connected Order Management System version and your permissions.

## Understand a configuration

A Data Manager configuration represents one import or export contract. Separate configurations can use different:

* Import or export services
* File formats
* Execution modes
* Templates
* Priorities
* Notification behavior

For example, order imports, fulfillment updates, and inventory resets can each use a different service and data contract.

Most configurations use a generic HotWax Commerce service after middleware transforms the source data. A native integration can use a service designed for that system’s original payload.

## Choose an execution mode

| Execution mode | Behavior                                                                                      |
| -------------- | --------------------------------------------------------------------------------------------- |
| `Queued`       | Waits in the shared queue and processes in queue order                                        |
| `Async`        | Processes in the background when resources are available without waiting for the shared queue |
| `Sync`         | Processes immediately in the submitting request                                               |

Use `Sync` only when the service owner has confirmed that the file size and operation are safe. Large synchronous imports can consume resources needed by other work.

## Understand the queue poller

Queued imports enter File History in a pending state. The configured bulk-file processing job finds pending files and starts processing them.

When one poller run is already processing the queue, a later scheduled run can stop without starting another processor. Check the run result and active file before treating this behavior as an error.

Use [Troubleshoot file imports](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/retail-operations/workflow/job-management/troubleshooting/file-imports.md) to check the queue and processing job from Job Manager.

## Configure with care

Before you change a configuration:

1. Record its current service, execution mode, and template.
2. Confirm every source that uses the configuration.
3. Test the change with approved non-production data.
4. Monitor the resulting file in Job Manager.
5. Restore the previous configuration when the test does not produce the expected contract.

See [Configuration options](/documents/system-admins/administration/data-manager/configuration-options.md) and [Frequently used configurations](/documents/system-admins/administration/data-manager/freq-used-configurations.md) for the available backend fields and examples.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hotwax.co/documents/system-admins/administration/data-manager.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.