All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

ITSM for Retail · Available now

Retail ITSM built around store trading hours.

ITSM for Retail organizes store IT work around the affected service, asset and person. A service desk technician acknowledges a new incident, checks its linked service and asset, assigns a technician and records the acknowledgment time.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewOpen Store Incidents
Retail ITSM · Incidents

Open Store Incidents

Incidents in one list

New incident
Incidents in view
6
Low
2
Medium
2
High
1
Low2
Restore card payments before openingInventory lookup
24 Nov
Move pickup kiosk to backup networkReturns processing
16 Nov
Add
Medium2
Replace failing register diskBackroom receiving
23 Nov
Repair receipt printer at Union SquareInventory lookup
15 Nov
Add
High1
Update scanner firmware after closingPrice and promotion sync
13 Nov
Add
Critical1
Investigate delayed promotion syncReturns processing
26 Nov
Add
Restore card payments before openingIncidents · INC-18395
Low
StatusOpen
ServiceInventory lookup
AssetStore router, Market Street
Assigned toLuis Peralta
Opened at24 Nov
Approve changeINC-18395 · Restore card payments before opening

Change Approver reviews the risk, scheduled window and rollback plan before authorizing implementation.

Waiting for Change Approver
ApproveReturn
Example screen with sample data
Tables, ready to use
12
Saved views
13
Roles with set permissions
8
Reports and dashboards
9
Features

Store IT work in context

Every feature works on the same records. Pick one to see the screen your team works in.

Incidents

Acknowledge store issues with the affected service, asset and technician in view.

  • Intake
  • Acknowledgment
  • Follow-through
  • Incidents
  • Incident updates
  • Services
  • Assets
  • People
  • Register outages
Explore incidents
OverviewCritical Incidents
Retail ITSM · Incidents

Critical Incidents

Incidents

New
SummaryPriorityStatusServiceAssetAssigned to
Restore card payments before openingCriticalOpenReturns processingPickup kiosk, LakesideLuis Peralta
Replace failing register diskCriticalAcknowledgedReturns processingReceipt printer 1, RidgewayHiro Tanaka
Update scanner firmware after closingCriticalInvestigatingStore Wi-FiReceipt printer 1, RidgewayAmir Haddad
Investigate delayed promotion syncCriticalResolvedClick and collect pickupLabel printer 2, NorthgateOwen Mercer
Move pickup kiosk to backup networkCriticalClosedDistribution order feedLabel printer 2, NorthgateAmir Haddad
6 of 6 records
Restore card payments before openingIncidents · INC-22847
Critical
StatusOpen
ServiceReturns processing
AssetPickup kiosk, Lakeside
Assigned toLuis Peralta
Example screen with sample data
Process

From plan to change outcome

Approved change to outcome ships ready to use. One step needs a named approval before the work moves on: Approve change (Change Approver).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Draft change

    Record the service, risk, schedule and rollback plan.

    Restore card payments before openingINC-18395 · Change Implementer
    Draft changeBy Change Implementer
  2. Review change

    Check the planned work against the store operating window.

    Restore card payments before openingINC-18395 · Change Approver
    Review changeBy Change Approver
  3. Approve change

    The Change Approver decides whether work may proceed.

    Restore card payments before openingINC-18395 · Change Approver
    Approve changeBy Change Approver
    ApprovalChange Approver reviews the risk, scheduled window and rollback plan before authorizing implementation.
  4. Implement change

    The implementer checks the approved details and records the result.

    Restore card payments before openingINC-18395 · Change Implementer
    Implement changeBy Change Implementer
  5. Verify change

    Review whether the change was verified or rolled back.

    Restore card payments before openingINC-18395 · Change Approver
    Verify changeBy Change Approver
Inside a record

Provider events with an audit trail

Open any incident to see its register outages, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Status, Service, Asset and Assigned to.

  2. 2
    Register outages

    Each line is linked to this incident.

  3. 3
    Who works on it

    Admin, Service Desk Technician and Store IT Coordinator, each with their own permissions.

  4. 4
    Process stages

    Record incident and Capture store evidence, with the role that acts.

  5. 5
    Approvals

    Approve change, with who decides.

Open Store IncidentsRestore card payments before opening
Retail ITSM · Incidents

Restore card payments before opening

Inventory lookup · Low

Log activity
1
Record details
StatusOpen
ServiceInventory lookup
AssetStore router, Market Street
Assigned toLuis Peralta
2
Register outages

Restore card payments before opening

Store codeRegister numberStarted at
ALDER-01RO-2044808 Nov
HARBOR-03RO-7243310 Nov
RIDGE-02RO-4823005 Nov
Register outages
6
Total lost transaction estimate
2,180
3

Who works on it

  • AdminManage Users, People, Services, Assets
  • Service Desk TechnicianManage Incidents, incident updates
  • Store IT CoordinatorManage register outages, store trading windows
4

Process stages

  • Record incidentService Desk Technician
  • Capture store evidenceStore IT Coordinator
5

Approvals

  • Approve changeChange Approver
    Approved
Example screen with sample data
Approvals

Decisions before delivery

OverviewApprovals
Retail ITSM · Overview

Approvals

Signed in as Change Approver

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • CHN-95426Restore card payments before opening
    Restore prior register imageRequested by Admin
    Low1dActions
  • CHN-45385Replace failing register disk
    Reapply previous pricing feedRequested by Admin
    Medium1dActions
  • CHN-47208Update scanner firmware after closing
    Switch terminals to backup gatewayRequested by Admin
    High2dActions
  • CHN-59972Investigate delayed promotion sync
    Revert scanner firmware packageRequested by Admin
    Low4dActions

Who approves what

DecisionApprover
Approve changeThe Change Approver decides whether work may proceed.Change Approver
Approve service requestsService Request Approver
Approve ChangesChange Approver
3 approval rules · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens Retail ITSM to the work that is theirs. Pick a role to see what it starts with.

Admin

Maintains service desk access and the reference records used by store IT teams.

  • Manage Users, People, Services, Assets
  • View Incidents, service requests, Changes, Problems, integration receipts
Reports

See work by service and state

Use recorded times, states and service links to review store IT work.

Overview
Retail ITSM · Overview

Retail ITSM dashboard

This quarter

Changes in view
6
Low
2
Medium
2
High
2

Incidents by status

How far records got this quarter

StageReachedStep
Open48
Acknowledged1123%
Investigating218%
Resolved150%

Number of incidents by status

Sample counts per stage

100
-20Open
0Acknowledged
10Investigating
-30Resolved
-10Closed
Example screen with sample data
  1. 01Incident status by priority

    Group incidents by current status and priority to see the service desk workload.

  2. 02Acknowledgment timing

    Compare opened and acknowledged times for incidents with both timestamps.

  3. 03Resolution timing

    Compare opened and resolved times for incidents with both timestamps.

  4. 04Register downtime by store

    Compare start and restoration times for recorded register outages by store code.

  5. 05Estimated lost transactions by store

    Sum recorded lost transaction estimates by store code.

  6. 06Request completion by service

    Group service requests by linked service and status, with actual completion dates.

  7. 07Change outcomes by risk

    Group changes by risk and current status.

  8. 08Problem state by service

    Group root-cause records by service and status.

  9. 09Provider receipt outcomes

    Group integration receipts by provider and processing status.

Controls

Check the record before action

Each stage of approved change to outcome names the role that acts and the status it records, so a change is never anonymous.

OverviewApproved change to outcome
Retail ITSM · Process

Approved change to outcome

Each stage, the role that acts and the status it records

Process stages
12
Approval steps
1
Roles involved
6
Tables touched
7
Acknowledge incident
Service Desk Technician
StatusOpen → Acknowledged
RecordsServices, Assets
Resolve incident
Service Desk Technician
StatusInvestigating → Resolved
RecordsServices
Approve service requestApproval
Service Request Approver
StatusSubmitted → Approved
RecordsService requests
Approved change to outcome
  1. Start
    Acknowledge incidentOpen → Acknowledged
    Services
  2. Step
    Resolve incidentInvestigating → Resolved
    Services
  3. Approval
    Approve service requestSubmitted → Approved
    Service requests
  4. Step
    Fulfill service requestApproved → Completed
    Service requests
  5. Step
    Review changeDraft → Review
    Changes
Example screen with sample data
AI agent

Help for the service desk

Use Proto to work through store IT cases with the right records in view.

It can

  • Service Desk Technician: Show open store incidents with priority, affected service, asset and current assignee before triage.
  • Store IT Coordinator: Gather the selected incident, register outage interval and trading window for a handoff review.
  • Service Request Approver: Present submitted requests with the requester, service and due date for a human decision.
  • Change Implementer: Show the approved change's risk, scheduled times and rollback plan before work begins.

Stays with a person

  • An agent can prepare a case, but the assigned technician must confirm the asset and acknowledgment.
  • The request or change approver makes the authorization decision.
  • The implementer records what happened during execution, and a store operator supplies the local trading context.
  • Check the actual record before accepting an action or report.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Retail ITSM
  • Monitoring provider
  • Store equipment source
  • People directory
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 12 tables
12tables
  • Incidents7
  • Store Evidence3
  • Service Requests3
  • Changes2
  • Services and Assets7
  • Problems and Receipts6
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Prepare references

    Set up people, services and assets with clear owners, locations and lifecycle states.

  2. Rehearse incident response

    Use a store register issue to test intake, service and asset validation, assignment, acknowledgment and updates.

  3. Add store context

    Capture a register outage and trading window against the selected incident and check their intervals.

  4. Set decision ownership

    Agree who approves service requests and changes, then rehearse approval and rejection cases.

  5. Review outcomes

    Test approved request completion and change implementation, including a rolled-back result, then review the reports used in operations.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Retail ITSM.

All questions
How do I get started?

Click Get started, then use Proto to configure ITSM for Retail for your business. Pilot one store incident with its service, asset, technician and linked register outage before expanding to other work.

How does a store incident get assigned?

The technician checks the linked service and asset, validates their lifecycle states, records the assigned person and acknowledgment time on the incident.

Can I record a register outage separately from the incident?

The outage capture links to a selected incident. It records store code, register number, start and restoration times, and a lost transaction estimate.

Where do store operating hours go?

A trading window capture links to an incident and records the store code, opening and closing times and timezone.

Who approves a service request?

The Service Request Approver reviews a submitted request. The Service Request Fulfiller handles the approved work and records completion.

What does a change approver review?

The approver reviews risk, scheduled start and end, rollback plan and affected service before approving or rejecting the change.

How are recurring issues tracked?

A problem record holds a statement, root cause, affected service, owner and state. Incident updates keep the timeline for individual cases.

What do integration receipts show?

They record provider event identity, received time, payload hash and whether processing was received, applied, rejected or failed.

Can I review register downtime by store?

Use recorded outage start and restoration times with store codes. The lost transaction figure is an estimate recorded on each outage.

Set up Retail ITSM your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appITSM for Retail

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.