GSPANN and an anonymised specialty retailer: Manhattan Active Omni test automation case analysed
Verdict: what is checkable
The evidence grade (this site's label for how a case is sourced: primary with client or press confirmation, secondary when vendor-hosted only.) is secondary: the only source is the vendor's own page; of 1 metric, 0 are verifiable yes, 0 partial and 1 no. [ev-0977]
Client profile as published
- Client
A multi-brand specialty retailer.
(the vendor's description; the vendor does not name the client)- Segment
- Specialty retail
- Region
- not stated in the source
- Channels
- stores and ecommerce
- Size indicators
global multi-channel retailer
;multi-brand specialty retailer
The client description and size indicators are quoted from the source; segment, region and channels are this site's classification. [ev-0977]
Systems in scope
- OMS (order management system: software that routes, splits and tracks customer orders across stores, warehouses and carriers.) (Manhattan Active Omni): named in the summary and the Challenge section
- Payments: named in the Our Solution section (New payment gateway testing)
- Loyalty: named in the Our Solution section (loyalty program and gift cards)
- Integrations (Retail Management Systems (RMS); S4 (SAP validation for Finance)): named in the Our Solution section
Where the source names each system is quoted or summarised from the case page. [ev-0977]
Problem as stated
The retailer chose Manhattan Active Omni to replace an order management system it found complex and inadequate. Neither the retailer nor its main technology partner had any quality engineering setup. GSPANN was asked to build automated end-to-end testing for orders placed online, in store and through partners, including carts that mix home delivery and in-store pickup. It was also asked to add new test management tools. [ev-0977]
no quality engineering infrastructure in place(quoted from the source)
Approach
- Testing types
- automation and functional (main scope: automation)
- Team shape
- not stated
- Duration
- not stated
- Engagement model
- not stated
- Tooling named in the source
- GCP, Firebase Analytics, Firebase Crashlytics, Swift, PostgreSQL, Objective-C, Java, Oracle, Hibernate
Metrics claimed
| Metric | Value | Unit | Claimed by | Verifiable | Evidence |
|---|---|---|---|---|---|
| time for GSPANN engineers to get up to speed on MAO testing | less than one month | month | vendor | no | ev-1570 |
What the case does not say
- Baseline before the engagement.
- Measurement method.
- Team size on both sides.
- Cost.
- Whether the client is still a client.
- Date of the work.
Reading notes for a buyer
This case speaks to the scenario “OMS or WMS (warehouse management system: software that runs receiving, storage, picking and shipping inside a distribution center.) replacement” and feeds dimension D2 (Retail system coverage) of the methodology. A question to put to GSPANN:
Which test automation framework did you build for the Manhattan Active Omni order flows, given the case lists no test tool? [ev-0977]
Source and verification
- Source
- Quality Engineering Streamlines Order Management System Migration
- Published
- not dated by the vendor
- Verified
- 2026-10-30
- Evidence grade
- secondary
- Corroborating sources
- none found
| Id | Claim | Source | Class | Grade | Published | Verified |
|---|---|---|---|---|---|---|
| ev-0977 | Quality Engineering Streamlines Order Management System Migration | Quality Engineering Streamlines Order Management System Migration | vendor-case-study | secondary | 2026-10-30 | |
| ev-1570 | Despite the lack of information from the technology partner, our engineers, starting entirely from scratch, could get up-to-speed on MAO testing in less than one month. | Simplify OMS Transition with Omnichannel Quality Engineering | vendor-case-study | secondary | 2026-10-30 |
Vendor profile: GSPANN. System facet: OMS and WMS testing vendors.
Positions on this page are computed from the methodology published at /methodology/ and from the evidence records linked on this page. Case study figures are the vendor's or the client's claims as published at the linked source; the "verifiable" column states what this site could check. The site does not recommend vendors, does not accept paid placement and does not publish rates. Last computed: 2026-11-03.
Published by the editor of retailqavendors.com. Last reviewed .