Oracle Xstore Point of Service
Xstore is the till. When it is down, the store stops trading, and the tolerance for defects is lower than anywhere else in the estate. It is also the most heavily customised application most retailers own.
What actually goes wrong
Customisations that block the upgrade path
Xstore is extensible by design, but extensions written against internal classes rather than published extension points break on every version upgrade. Raw SQL and DtxQueryHandler queries in overlays are the classic example — deprecated at Release 18 and non-functional in Xstore Office Cloud Service, where DTXQL is the supported route. The cost is never the original build; it is paying for it again at every release.
Upgrades that stall on payment certification
The Xstore version upgrade is often the easy half. EFT integration, payment terminal firmware, and re-certification with the acquirer run on someone else's timeline. Projects that plan these in sequence rather than in parallel lose months.
Offline mode that has never actually been tested
Xstore keeps trading when the network drops — in theory. Whether it does at your store, with your peripherals and your tender types, is only known if someone has pulled the cable and tried. Very often nobody has, and the first real test is an outage. Worth knowing when you plan: unlike Merchandising, Xstore never gets Extended Support. Every Xstore row in Oracle Lifetime Support is marked not available, which changes the upgrade conversation entirely.