# Infor M3 Customer Order Status Codes: Worksheet to Map Your Order Lifecycle > Source: https://netray.co/tools/infor-m3-customer-order-status-tracking-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Document what each customer order status means in your M3 setup, stage by stage, and share it with the order desk. ## Category infor-cloudsuite ## Erp Infor M3 ## Audience - M3 functional consultant - Order desk lead - M3 support analyst ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Lifecycle stage **Key:** stage **Type:** text #### Level **Key:** level **Type:** select **Options:** - Header - Line - Both #### Status code (fill from your tenant) **Key:** code **Type:** text #### What it means here **Key:** meaning **Type:** text #### Where you see it **Key:** program **Type:** text #### Owner **Key:** owner **Type:** text #### Max days allowed **Key:** days **Type:** number **Unit:** days **Rows:** **Stage:** Entered, not yet released **Level:** Both **Meaning:** Order is saved but not accepted for processing **Program:** OIS100 **Owner:** Order desk **Days:** 1 **Stage:** Released / accepted **Level:** Both **Meaning:** Order passed credit and validation and is open for allocation **Program:** OIS100 **Owner:** Order desk **Days:** 1 **Stage:** Allocated **Level:** Line **Meaning:** Stock has been reserved against the line **Program:** OIS100 line **Owner:** Warehouse planner **Days:** 2 **Stage:** Picking list printed **Level:** Line **Meaning:** Pick has been requested in the warehouse **Program:** Pick list programs **Owner:** Warehouse **Days:** 1 **Stage:** Delivery confirmed **Level:** Line **Meaning:** Goods issued and delivery updated **Program:** Delivery programs **Owner:** Shipping **Days:** 1 **Stage:** Invoiced **Level:** Line **Meaning:** Invoice created and passed to accounts receivable **Program:** Invoicing programs **Owner:** Finance **Days:** 3 **Totals:** #### Total days in lifecycle **Key:** days **Agg:** sum **Format:** days **Summary:** #### Average days per stage **Key:** avg_stage **Expr:** sum_days / count **Format:** decimal **Notes:** The status code column is intentionally empty. Code values and names are configured and described in M3 documentation per version, so copy them from your own tenant and field help rather than from memory. Remember that an order header shows a lowest and a highest status across its lines. ## Content **Intro:** Order desks ask the same question every day: what does this status mean and who has to act. This worksheet lets you build the answer for your own M3 tenant, stage by stage, with owners and maximum time at each stage, then export it for the team. **Sections:** #### How to use the worksheet **Body:** Start with the six lifecycle rows, then look at the order in OIS100 and note the status code that appears at each point. Add rows for any special flows such as holds, backorders or customer blocks. Fill in who owns the next action and how long an order should sit at that stage. Export to Excel and share it with the order desk, the warehouse and finance so everyone uses the same words. #### How M3 order status works **Body:** In M3 the customer order has statuses at both header and line level. The line status moves as the line progresses through allocation, picking, delivery and invoicing. The header displays a lowest and a highest status derived from its lines, which is why a header can look stuck while some lines have moved on. The order type and the order flow settings decide which steps are used, so two sites on the same M3 can have different practical meaning for the same code. **Bullets:** - Check line status first when a header looks stuck - Compare lowest and highest status to spot partial shipments - Remember order type settings change the flow #### Common mistakes **Body:** Teams copy a status list from another customer and trust it. Others treat the header status as the truth for every line. A third issue is leaving the maximum days column empty, so the order desk has no clear trigger for escalation. Use the days column and the average per stage figure to find where orders wait longest and what to fix first. **Cta:** If you want a live view of orders stuck at each status, Netray can build a read-only question and answer layer over your M3 order data. **Faq:** #### Why is the status code column blank? **Answer:** Because status values depend on the version and configuration and we do not want to give you a wrong code. Open a real order in your tenant, read the status at each step and fill the column. That also creates documentation specific to your setup. #### What are lowest and highest status on an order? **Answer:** The order header shows the lowest and highest status among its lines. If they differ, lines are at different stages, for example some delivered while others still wait for stock. Work lines at the lowest status first. #### Can I add holds and blocks? **Answer:** Yes. Add rows for credit hold, customer block, allocation shortage and any custom step. Mark the level and the owner so each exception has a person who clears it. #### How do I report stuck orders? **Answer:** Use your M3 reporting tool or an API list of orders by status and age, then compare with the days column in this worksheet. Orders older than the limit at a stage are the escalation list. ## Search terms M3 customer order status codes, OIS100 order status, M3 order line status, M3 lowest highest status, M3 order lifecycle, Infor M3 status meaning, M3 order status list excel --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json