> 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/retail-operations/workflow/job-workflows.md).

# Job Workflows

Find job workflows by business process and open the configuration and run-history guides.

Use these guides to understand what a job does and how it fits into a business process.

| Process                                                                    | Guide                                                                                                       |
| -------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Maintain the pre-order catalog, tags, promise dates, and release schedules | [Pre-Orders](https://docs.hotwax.co/documents/retail-operations/workflow/job-workflows/pre-orders.md)       |
| Import orders and maintain order-related information                       | [Orders](https://docs.hotwax.co/documents/retail-operations/workflow/job-workflows/orders.md)               |
| Process fulfillment and order notifications                                | [Fulfillment](https://docs.hotwax.co/documents/retail-operations/workflow/job-workflows/fulfillment.md)     |
| Import inventory and synchronize Shopify availability                      | [Inventory](https://docs.hotwax.co/documents/retail-operations/workflow/job-workflows/inventory.md)         |
| Synchronize products and maintain product information                      | [Products](https://docs.hotwax.co/documents/retail-operations/workflow/job-workflows/products.md)           |
| Process bulk files and other supporting jobs                               | [Miscellaneous](https://docs.hotwax.co/documents/retail-operations/workflow/job-workflows/miscellaneous.md) |

## Find and inspect a job

1. Open the Job Manager app and confirm the active instance and Product Store.
2. Use [Catalog](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/job-manager/jobs/catalog.md) to find the job.
3. Open [Job details](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/job-manager/jobs/job-details.md) and review its service, parameters, schedule, and state.
4. Inspect [Run history](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/job-manager/jobs/run-history.md) to confirm the latest outcome.

The [Job Parameters](https://docs.hotwax.co/documents/retail-operations/workflow/job-workflows/parameters.md) reference explains common inputs. Use the selected job's parameter definitions and configured values when editing it; a parameter or default used by one job does not apply to every job.

If a job does not run or finishes with an error, follow [Job runs and schedules](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/job-manager/troubleshooting/job-runs-and-schedules.md). For jobs that process files, also inspect [File imports](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/job-manager/troubleshooting/file-imports.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hotwax.co/documents/retail-operations/workflow/job-workflows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
