Overview
Order Status 2.0 in eXtendPS-SE is used to to return PromoStandards Order Status 2.0-compliant responses.
If your Order Status 1.0 configuration doesn't include custom workflows, scripts, or special order status configurations, you can usually activate Order Status 2.0 without additional configuration. Order Status 1.0 and 2.0 follow similar rules, so customers using either version will see consistent results.
If your account includes custom workflows, scripts, or special order status mappings used by Order Status 1.0, review those customizations to determine what changes are needed to maintain support for Order Status 1.0 and add support for Order Status 2.0. This is especially important if you plan to run both services simultaneously. Treat this work as a customization project rather than a standard upgrade.
Prerequisites
Before you upgrade, review your current Order Status 1.0 configuration for any custom scripts, workflows, or order status mappings used to determine order status values.
Configuration
Standard Order Status 2.0 triggers
The table below outlines the standard triggers used to determine the PromoStandards Order Status returned for each order or line.
| PromoStandards Order Status | Action |
|---|---|
received | Returned when the order status is Pending Approval, regardless of line-level information. |
confirmed | Returned when the order status is Pending Fulfillment, regardless of line-level information. |
preproduction | Requires custom logic to support this status. |
inProduction | Requires custom logic to support this status. |
inStorage | If NetSuite's Pick, Pack and Ship feature is enabled, this status is returned when the line item fulfilled quantity is 0 and the picked or packed quantity is non-zero. If custom logic has been implemented, the custom logic takes precedence over this default behavior. |
partiallyShipped | Returned when the line item fulfilled quantity is less than the total quantity. |
shipped | Returned when the line item fulfilled quantity is equal to the total quantity. |
complete | Returned when the line item billed quantity is equal to the total quantity. |
canceled | Returned when the line is closed. |
Upgrade scenarios
Use the guidance below to determine the correct upgrade path.
- If no customizations are present, activate Order Status 2.0 directly. The standard triggers above will apply.
- If customizations are present, review the existing custom workflows or scripts to determine what changes are needed to continue supporting Order Status 1.0 while adding support for Order Status 2.0, if you plan to run both services simultaneously.
- Treat customized Order Status 2.0 logic as a customization request rather than a self-service upgrade.
Additional considerations
For information about Unit of Measure mapping, see Unit of Measure (UOM) Mapping in Order Status 2.0.
Frequently Asked Questions (FAQs)
Q: Can I activate Order Status 2.0 without additional configuration?
A: Yes, if your Order Status 1.0 setup doesn't include custom workflows, scripts, or special order status configurations.
Q: What should I do if my current Order Status 1.0 setup uses custom workflows or scripts?
A: Review the existing customizations to determine what changes are needed to maintain support for Order Status 1.0 and add support for Order Status 2.0. If you plan to run both services simultaneously, treat this as a customization project.
Q: Will Order Status 1.0 and 2.0 return similar results?
A: Yes. Order Status 1.0 and 2.0 follow similar rules, so customers using either version to retrieve order status updates will see consistent results.