# IFS Shop Order Status Reference

> Source: https://netray.co/tools/ifs-shop-order-status-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A searchable table of the IFS shop order lifecycle: the main statuses, the events that move an order between them and what to check at each step.

## Category

mes-shop-floor

## Erp

IFS Cloud

## Audience

- Production planner
- IFS consultant
- Shop floor supervisor
- Trainer

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Step

**Key:** step

**Type:** number

#### Status or event

**Key:** name

**Type:** text

#### Type

**Key:** type

**Type:** text

#### What it means

**Key:** meaning

**Type:** text

#### What to check

**Key:** check

**Type:** text

**Rows:**

#### Planned

**Step:** 1

**Type:** Status

**Meaning:** The order exists with a quantity and dates but is not yet released to the floor.

**Check:** Quantity, dates, structure and routing revision

#### Release

**Step:** 2

**Type:** Event

**Meaning:** Moves the order from planned to released so work can be organised.

**Check:** Material availability and capacity before release

#### Released

**Step:** 3

**Type:** Status

**Meaning:** The order is open for planning and material handling.

**Check:** Operations, work centers and priorities

#### Material reservation

**Step:** 4

**Type:** Event

**Meaning:** Component quantities are reserved against stock for the order.

**Check:** Shortages and substitute parts

#### Reserved

**Step:** 5

**Type:** Status

**Meaning:** Material has been reserved for the order.

**Check:** Reservation completeness by component

#### Material issue

**Step:** 6

**Type:** Event

**Meaning:** Components are issued from stock to the order.

**Check:** Lot or serial numbers and issued quantity

#### Start

**Step:** 7

**Type:** Event

**Meaning:** Production begins, usually triggered by first reporting or manual start.

**Check:** Start date and first operation

#### Started

**Step:** 8

**Type:** Status

**Meaning:** Production is in progress on the order.

**Check:** Open operations and reported quantity

#### Operation reporting

**Step:** 9

**Type:** Event

**Meaning:** Labor, machine time and quantities are reported against operations.

**Check:** Run time, setup time and scrap

#### Scrap reporting

**Step:** 10

**Type:** Event

**Meaning:** Rejected quantity is reported with a reason.

**Check:** Reason code and cost impact

#### Receipt of finished goods

**Step:** 11

**Type:** Event

**Meaning:** Completed quantity is received into inventory.

**Check:** Receiving location and quantity

#### Backflush

**Step:** 12

**Type:** Event

**Meaning:** Components consumed automatically based on reported output.

**Check:** Backflush settings per component

#### Cost review

**Step:** 13

**Type:** Check

**Meaning:** Compare reported cost to planned cost before closing.

**Check:** Variances by material, labor and overhead

#### Close

**Step:** 14

**Type:** Event

**Meaning:** Finalises the order so no more reporting is allowed.

**Check:** All operations reported and no open reservations

#### Closed

**Step:** 15

**Type:** Status

**Meaning:** The order is finished and costs are final.

**Check:** Variance posting and archive rules

#### Cancel

**Step:** 16

**Type:** Event

**Meaning:** Stops an order that should not be produced.

**Check:** Reservations, issued material and any reported time

#### Cancelled

**Step:** 17

**Type:** Status

**Meaning:** The order was cancelled before completion.

**Check:** Reason, and stock or demand impact

**Notes:** This is a general lifecycle guide. Status names, available events, and the exact behavior of release, reservation and close depend on your IFS release and site configuration. Confirm against your own system and process documentation.

## Content

**Intro:** Shop orders are the backbone of IFS manufacturing, and most production issues show up as an order that is in the wrong status. This reference lays out the lifecycle in order, so planners and consultants can check where an order is and what should happen next.

**Sections:**

#### How to use the reference

**Body:** Use the search box to find a status or event by name, or read down the steps in sequence. Each row says what the status means and what to check before moving on. Planners can use it to explain why an order is stuck, and trainers can use it as a one page lifecycle sheet. Export to Excel to adapt the wording to your own process.

**Bullets:**

- Search by status or event name
- Read the steps in order for training
- Use the check column as a review prompt
- Export and adapt to your process

#### Statuses versus events

**Body:** A status is the state an order is in. An event is the action that changes the state or records progress. Confusing the two leads to wrong conclusions, for example assuming material was issued because the order is released. Releasing allows work to be organised, reserving sets aside stock, and issuing physically moves material to the order. Check each one separately.

#### Where orders get stuck

**Body:** Typical blockers are shortages at reservation, missing routing or structure data on planned orders, operations that were never reported, and open reservations that block close. When an order will not close, look for unreported operations and unissued or unreturned material first. When it will not release, check structure, routing and any site specific release conditions.

#### Common mistakes

**Body:** Planners often close orders before costs are reviewed, which pushes variances into the wrong period. Others cancel orders with reported time or issued material, leaving stock and cost cleanup behind. Treat close and cancel as final steps with a checklist, and agree who is allowed to perform them in production.

**Cta:** If you want production questions such as which shop orders are blocked and why answered in plain language from live IFS data, Netray can discuss a read-only approach.

**Faq:**

#### Are these the exact IFS status names?

**Answer:** The core statuses such as Planned, Released, Reserved, Started, Closed and Cancelled are widely used in IFS, but the exact set and behavior depend on release and configuration. Verify against your own system.

#### Why can I not close my shop order?

**Answer:** Common reasons are unreported operations, open material reservations, or unfinished receipts. Review the operations and material tabs of the order and resolve each item before trying to close.

#### Does release issue material?

**Answer:** Not by itself. Release makes the order available for work. Reservation sets stock aside and issue moves it. Depending on your setup, some of these can be automated, so check your configuration.

#### Can I export this table?

**Answer:** Yes. The export bar downloads the reference as Excel, CSV or PDF so you can add site specific rules and ownership.

## Search terms

IFS shop order status, IFS shop order lifecycle, IFS shop order released reserved started, IFS shop order close, IFS manufacturing shop order, IFS shop order material reservation, IFS shop order reporting, IFS shop order training

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json