From 16 June 2025, we’ve upgraded our Home Fibre plans. These changes are now live, but while some documents on this site may still reference the old plan names, rest assured, the new speeds apply. Find out more.
Name
Customer Requests Order Information
Description
This process provides you with the ability to retrieve a snapshot of an order belonging to you.
Related B2B Services
Preceded by
Succeeded by
Pre-conditions
You have created an order using BIC101: Customer Creates Order. The order can be in any state.
Post-Conditions
You receive our response containing the order details.
| STEP | DESCRIPTION | ROLE |
|---|---|---|
| 1,2 | Submit a query order request. | Customer |
| 3 |
Receive and validate the request. If the request is invalid refer to alternate flow. |
Chorus |
| 4 | Provide response containing order details and history. | Chorus |
| 5 | Receive the Query Order response and action as appropriate. | Customer |
| STEP | DESCRIPTION | ROLE |
|---|---|---|
| 3.1 | If the query order request information is invalid, return an error response. | Chorus |
| 3.2 | Return an error response explaining why the order information cannot be created. | Chorus |
Refer to the Exception Codes table for error details.
The Exception Codes table lists the exceptions that may be returned by this service.
For a full list of exception codes and their meanings see B2B Exception Codes.
| CODE | DESCRIPTION |
|---|---|
| 000 | Backendprocessingerrorencountered-IfproblempersistspleasecontactChorusadmin |
| 019 | Customer Order ID or Customer Reference ID not found |
| 026 | Request validation failed: {%s} |
| 033 | Multiple results found for Customer Reference entered |
The following table describes the use cases that support this business process.
Click on the scenario link to view the XML sample.
| SCENARIO | DESCRIPTION | REQUEST | RESPONSE |
|---|---|---|---|
| Customer Queries Order |
Query Order Request is executed to retrieve a snapshot of an order. Order details and history is returned. |
|
|
The following table describes the use case exceptions that support this business process.
Click on the scenario link to view the XML sample.
Use Case Exceptions
| SCENARIO | DESCRIPTION | REQUEST | RESPONSE |
|---|---|---|---|
| Customer Requests Order Information -Orderid does not exist |
Query Order Request is executed to retrieve a snapshot of an order. The order id is incorrect. |
|
|
This section provides a list of the User Story References that we have met in this business process, as defined by the Ultra-Fast Broadband BSS / OSS Business Interaction Framework.
The document is available from:
Refer to the TCF website for documentation.
Request Success Criteria
| ID | DESCRIPTION |
|---|---|
| US57 | As a Service Provider I want to view and monitor any of my service orders so that I can manage my Customer expectations throughout the service order lifecycle. |
| SC57.04 | Closed service orders will be held in and accessible by the system for 6 months. |
| SC57.05 | Closed service orders will be held in and accessible by the system for a minimum of 12 months. |
| SC57.06 | Service Provider can only view service orders placed by them. |
Response Success Criteria
| ID | DESCRIPTION |
|---|---|
| US35 | As a Service Provider I want to be able to add my own reference ID to a Service Request order so that I can easily match the order with orders in my own systems. |
| SC35.03 | ServiceProviderreferenceisprovidedonallnotificationsregardingtheservicerequest order. |
| US57 | As a Service Provider I want to view and monitor any of my service orders so that I can manage my Customer expectations throughout the service order lifecycle. |
| SC57.04 | Closed service orders will be held in and accessible by the system for 6 months. |
| SC57.05 | Closed service orders will be held in and accessible by the system for a minimum of 12 months. |
| SC57.06 | Service Provider can only view service orders placed by them. |