ShiperooConnect — Change Management Flow

Phase 1 — Intake & Logging

01

Change Request Logged

Client or Internal Ops team submits new feature or change request

02

Stakeholder Review

Key stakeholders assess scope, priority & feasibility

03

Requirements Completed

Dev team authors functional & technical requirements for the relevant system area

04

Ops Team Review

Operations team confirms requirements are accurate and complete before dev begins

Phase 2 — Development

Target Systems: OMS / WES · Carrier Integration · ShiperooConnect Integration Hub · Client-Facing APIs

05

Local Dev Environment

Developer builds & tests change locally against target system area

06

Push to Dev Branch

Code pushed to dev branch for peer review & SIT

07

Peer Review & SIT

Code review by peers + System Integration Testing executed

Phase 3 — Testing

GATE

SIT Test Cases Passed?

✓ Yes → Proceed to UAT ✗ No → Return to Dev

Phase 3b — User Acceptance Testing

08

Push to UAT Branch

Merge into uat branch once SIT passes

09

User Acceptance Testing

Business / Ops users validate change meets requirements in UAT environment

10

Release Prepared

Change release notes, backout plan & deployment runbook prepared

Phase 4 — Change Advisory Board

CAB GATE

Change Advisory Board Approval

Change presented to CAB for formal sign-off · Release notes, test evidence & rollback plan reviewed
Not Approved → Return to dev/requirements Approved → Schedule change window

Phase 5 — Deployment

11

Change Window Scheduled

Tues – Thurs evenings only (unless emergency change approved)

12

Privileged Access Deploy

Authorised key team member only merges to prod branch

13

Pre-Deploy Backups

Prod code backup (always) · Dependent datastore backup (if required)

PRODUCTION DEPLOYMENT

Branch Merge → PROD Instances / Containers

Outage window initiated · PROD branch merge executed · All dependencies deployed in correct order
Services & containers restarted · Health checks confirmed

Phase 6 — Post-Deployment Verification

14

Tech Team Checks

Infrastructure, logs, API health & integration endpoints validated by tech team

15

Ops Team Checks

Ops team verifies business flows: OMS, WES, Carrier integrations & Connect Hub APIs

Phase 7 — Outcome

GATE

All Checks Passed?

✓ Yes → Change Complete ✗ No → Investigate / Rollback

Change Successfully Deployed

Change closed · Stakeholders notified
Documentation updated · Monitoring continues

ALT

Tech Team Investigates Issue

Root cause analysis & fix attempted within change window

Rollback Plan Initiated

No resolution found within window
CTO approval required to initiate rollback
Restore from pre-deploy code & datastore backups
Systems restarted & re-verified post rollback