Implementation and support
Implemented by the engineers who built it, supported by the same people.
An implementation follows the cut-over runbook step by step; a pilot store runs first; every posting flow is proven against your SAP company before the chain goes live. Support is named engineers, not a queue.
A TYPICAL PROJECT
Discoveryreceipts, tenders, returns, accounts
Install and connectserver, SAP, fields, sync
Configureprofiles, layouts, roles, hardware
Pilotone store, live postings
Roll outstore by store, by the runbook
Implementation
From the kick-off to the last store.
1
DiscoveryWe read your receipts, your tender types, your return rules, your chart of accounts and your SAP item setup, and write the configuration plan.
2
Install and connectThe server installer on your machine or VM, the SAP connection tested, the user-defined fields provisioned, the first master data sync.
3
ConfigureCompanies, stores, registers; roles and rights; configuration profiles; quick layouts with your pictures; currencies and accounts; receipts and labels.
4
Hardware sign-offPrinters, drawers, scanners, scales and terminals signed off on the register with the physical devices; adapters enabled per company.
5
PilotOne store sells live; every document type posts to your SAP company and is reversed; the findings become patch releases with changelog lines.
6
Roll out and hand overStore by store with the runbook; training for cashiers and managers; the manual in English and Arabic; the support agreement starts.
SUPPORT
Channelnamed engineers, e-mail and telephone
Hours[HOURS AND TIME ZONE]
Response[RESPONSE TARGETS BY SEVERITY]
Toolssupport bundles, remote actions, monitoring
Updatesevery build with release notes
TRAINING
Cashierson the lane, half a day
Managersportal, approvals, day close
Administratorsconfiguration, users, backups
Accountantsoperations, reconciliation