Skip to main content

[Organizing Production - GCW] Rush SLA - How it Works

Juliana Maciel Maruri da Cunha avatar
Written by Juliana Maciel Maruri da Cunha
Updated over a week ago

What Is a Rush SLA?

Rush SLA (Service Level Agreement) allows you to prioritize and accelerate order production beyond the standard processing times.
This feature ensures that urgent orders are produced faster than normal by applying a special configuration designed for speed.

Rush SLAs provide faster production times compared to normal SLAs and ensure rush orders meet tighter delivery deadlines

How Are Rush Orders Identified?

Rush orders are flagged when placing the order using a special tag:

  • Tag: RUSH

  • The RUSH tag is attached to the order at order intake stage as order metadata.

Example:

"metadata": [ { "key": "rush", "value": true } ]

  • The system uses this tag to automatically select the rush SLA path instead of the normal production flow.

How to Configure Rush SLA

Step-by-Step Setup:

  1. Access SLA Configuration

Navigate to the SLA settings for the relevant product model(s).

  1. Identify the Correct SLA Row

Find the row corresponding to the standard production setup for the product.

  1. Enable Rush Orders

Turn on the "Rush Orders" toggle for the selected SLA configuration row.

  1. Set Rush SLA Days

  • In the "Rush SLA Days" field, specify the required rush production timeline.

  • This value defines how many days production will take for rush-tagged orders.

  1. Save Changes

Ensure the updated rush SLA settings are saved correctly.

What Happens When a Rush Order Is Placed?

  • The order is placed with the RUSH tag attached.

  • When order reached production, sysytem automatically:

    • Detects the RUSH tag.

    • Applies the Rush SLA timeline configured.

    • No any specific faster production workflows are triggered.


📝 Not what you needed?

Help us improve this article, send us an email to [email protected] — please include the article title.


Did this answer your question?