Maciej Urbański

Work · POS reliability

Deliverect integration into production POS

Guided the Deliverect integration into the production POS stack and managed the technical and operational transition—protecting a revenue-critical delivery path across multi-site hospitality operations.

My role Technical project lead: requirements, vendor UAT, go-live, hypercare, and post-cutover IT/ops ownership boundaries.

Stack Deliverect · production POS · vendor UAT/go-live · multi-site rollout · IT/ops ownership model

Context
Delivery channel uptime directly impacts revenue in a café network. Integration with the core POS environment had to be stable across sites, with clear ownership between IT and operations whenever something broke. Stakeholders: ops, support, vendor, branch teams. Constraint: go-live without orphaning the integration after the project team moved on.
Intervention

Guided Deliverect into the production POS stack and managed both the technical cutover and the operational transition across teams.

Phase 1 — Requirements & ownership

Clarified what “working” meant for delivery→POS (orders, menus, failure modes). Named who owns what after go-live—IT vs ops—so incidents would not bounce forever.

Phase 2 — UAT with the vendor

Ran vendor UAT against the production POS path: happy path, edge cases, and rollback expectations. Kept a tight defect loop before cutting over sites.

Phase 3 — Go-live & hypercare

Executed go-live with hypercare coverage and a clear handoff into BAU support. Documented the owned integration path so future changes had a home.

Risks & how they were handled
  • Revenue impact on bad cutover → staged UAT, rollback plan, hypercare.
  • Orphaned ownership → explicit IT/ops RACI after go-live.
  • Site variance → treat multi-site differences as first-class test cases.
What I'd do differently
  • Capture a short “top 5 failure modes” card for support on day one of hypercare.
  • Add a lightweight health check for the delivery path earlier in BAU.
Outcome
Before: delivery-channel uptime sat in fragile handoffs between teams whenever something broke on the path into POS. After: Deliverect sits on the production POS revenue path with an owned technical cutover and clearer IT/ops ownership—incidents have a named handoff instead of an orphaned integration (qualitative; no invented uptime %).

System map

Delivery channel

apps

Deliverect

vendor

Core POS

production

POS path

UAT / go-live

owned handoff

Branches

multi-site

What it does

Puts delivery orders on the production POS path

Owns UAT through hypercare

Hands a clear ops model to IT

Revenue-critical delivery integration — requirements through go-live, then IT/ops ownership.

What shipped

  • Production integration path Delivery orders land on the live POS route via Deliverect.
  • UAT to go-live ownership Requirements, UAT, cutover, and hypercare with a clear IT/ops handoff.
  • Multi-site rollout Branch-aware ownership so the channel does not depend on tribal knowledge.

Stack Deliverect POS UAT go-live multi-site

← Workspace migration All work →