These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Retail ITSM
- Who it's for
- Checkout operations
Checkout operations
Checkout teams need to know what happened to a register and who is restoring it. The incident record carries the service, asset, priority, technician and response times. A register outage capture adds the store code, register number and interruption interval. The trading window gives local operating hours for the incident. These records let the service desk discuss the case in terms of actual equipment and time.
How Retail ITSM is set up for you
Register identity
Keep asset tag, serial number and location usable so the technician can confirm the reported device.
Outage timing
Record when the register stopped and when it returned, with the selected incident as the attribution point.
Estimate context
Use the recorded lost transaction estimate under an agreed method; keep it distinct from actual sales data.
Planned service work
Review a checkout change's risk, schedule and rollback plan before it reaches the implementer.
Checkout teams need to know what happened to a register and who is restoring it. The incident record carries the service, asset, priority, technician and response times. A register outage capture adds the store code, register number and interruption interval. The trading window gives local operating hours for the incident. These records let the service desk discuss the case in terms of actual equipment and time.
Choose one checkout service and several representative registers. Have a store report a device failure and let the desk select the matching asset. The technician acknowledges the incident after confirming the service and asset states, then adds a dated investigation update. The coordinator records the outage against that incident and supplies a trading window with the store's timezone. When the register returns, record the restoration time and resolve the incident.
Next, rehearse a planned update to the same service. The approver should see a real start and end time and a usable rollback plan before approving it. The implementer should check the approved details and record the outcome. A reader should be able to distinguish an unplanned register interruption from planned service work even when both affect checkout.
Features to start with
Roles on the team
- Admin
- Maintains service desk access and the reference records used by store IT teams.
- Service Desk Technician
- Acknowledges incidents, checks the affected service and asset, and records technician activity.
- Store IT Coordinator
- Captures register outage and trading window evidence against the selected incident.
- Change Approver
- Reviews the risk, schedule and rollback plan before approving a change.
- Change Implementer
- Executes an approved change and records its implementation outcome.
Set up Retail ITSM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.