Overview
The OMS UI Reference Guide provides a comprehensive explanation of the XY Retail Order Management System user interface, focusing on how operations, customer support, merchandising, and store teams can efficiently execute their day-to-day workflows. It is intended to serve as a single source of truth for understanding screens, components, behaviours, and key actions available across the OMS UI.
This guide does not attempt to redefine business processes; instead, it translates agreed-upon OMS capabilities and workflows into clear, UI-centric explanations. Each section is organized around concrete user tasks (for example, searching and reviewing orders, managing fulfilment, handling exceptions, or processing returns) and shows how these tasks are supported in the product. Where relevant, the guide also calls out validations, edge cases, and dependencies on configuration so that teams can better understand why the UI behaves as it does in different scenarios.
By providing consistent, detailed documentation of the OMS interface, this reference enables both functional and technical stakeholders to align on how the system should be used, reduces ambiguity during implementation and training, and supports smoother communication between business teams, product, and engineering.
Scope and Audience​
The OMS UI Reference Guide covers:
- Core OMS UI modules (e.g., Order Search and Details, Fulfilment and Allocation views, Shipment and Delivery views, Returns/Refunds, and related dashboards).
- Page-level and component-level behaviour, including field definitions, actions, status transitions, and validation rules as expressed in the UI.
- Standard user journeys and operational scenarios that are executed directly through the OMS interface.
Primary audiences include:
- Operations and customer service teams using the OMS UI for daily order, fulfilment, and exception handling activities.
- Business and product owners who need to validate that the implemented UI supports agreed-upon processes and policies.
- Implementation, training, and support teams who require a stable reference to design SOPs, training material, and troubleshooting guides.
Outcomes​
By using and maintaining the OMS UI Reference Guide, we aim to achieve the following outcomes:
| Outcome | Description |
|---|---|
| Consistent usage of OMS UI features | All teams rely on a shared, authoritative description of screens and behaviours, reducing ad-hoc interpretations of how the OMS should be used. |
| Reduced onboarding and training time | New users can be trained faster with clear, scenario-based explanations of the UI, supported by examples and screenshots rather than informal, tribal knowledge. |
| Fewer operational errors and rework | Clear documentation of fields, validations, and status transitions helps prevent incorrect updates, duplicate efforts, and misrouted orders or fulfilments. |
| Improved support and troubleshooting | Support teams can refer to a standard reference when investigating issues, leading to quicker root-cause identification and more consistent resolutions. |
| Better alignment between business and product/engineering | A shared view of the UI and its intended behaviour supports more productive discussions around changes, enhancements, and defect triage. |
| Higher auditability and compliance | Documented flows, UI rules, and constraints make it easier to demonstrate adherence to business policies and regulatory or client-specific requirements. |