KERV DIGITAL LIMITED

Microsoft Dynamics 365 Commerce

Use Dynamics/D365 commerce to provide a seamless online and in-store and shopping experience with integrated back office operations to grow sales and increase customer satisfaction We support discovery activities, business architecture, governance set-up, DevOps/SecOps tooling, service design, experience research/design, technical architecture, predictive science and all related services.

Features

• Seamlessly connected digital, in-store and back-office solutions.
• Built in web publishing tools, manage and optimise experiences.
• Context aware intelligent product search facilities.
• Rule based content creation/generation.
• Single view of connected stock, pricing, promotions and marketing.
• Intelligent AI powered product recommendations.
• Historical sales powered customer demand forecasting.
• On-Premise, Cloud and Edge deployment options.
• Comprehensive in-built security and compliance with online fraud protection.

Benefits

• Improve conversion rates, provide friction-less cross channel shopping experiences.
• Create a 360-degree customer view of behavioural data.
• Streamline content management across online and offline channels.
• Accelerate purchase decisions with product ratings and reviews.
• Use intelligent reporting to optimise merchandising and stock replenishment.

• Education pricing available

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at frameworks@kerv.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

584219360683630

Contact

Saad Khattak
01212815309
frameworks@kerv.com

About your service

• Service categories:

  Applications

  Customer relationship management

  • Digital commerce
• Multi cloud support: Yes

Service scope

• Software add-on or extension: No
• Cloud deployment model: Public cloud
• Service constraints: N/A
• System requirements:
  • Dynamics 365 Commerce licences required for all retail operations.
  • Dynamics 365 Finance licence required for back-office financial integration.
  • Azure subscription required for Commerce Scale Unit cloud deployment.
  • Windows iOS or Android devices required for Store Commerce application
  • Modern major web browser required for e-commerce and back-office.
  • Power Apps and Power Automate licences for custom extensions.
  • Azure DevOps and Visual Studio licences for customisation development.
  • Kerv Digital will propose appropriate licence arrangement to meet requirements.
  • Other third-party licences optional depending on solution procured.
  • Payment provider integration licence required for transaction processing.

User support

• Email or online ticketing support: Yes
• Support response times: P1: Critical – Response time: 2 hrs ; P2: Major – Response time: 4 hrs ; P3: Important – Response time: 8 hrs ; P4: Minor – Response time: varies on request
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: WCAG 2.2 AA
• Phone support: Yes
• Phone support availability: 24 hours, 7 days a week
• Web chat support: No
• Onsite support: Yes, at extra cost
• Support levels: Kerv offers predefined support packages incidents as follows: (9am – 5pm), core+ (8am – 6pm), extended (6am – 10pm) with 24/7 (10am – 6am) available. support packages for core business hours (9am – 5pm). Incidents are classified as P1 (Production System Down), P2 (Production System Impaired), P3 (System Impaired), P4 (General Guidance & Requests) with associated SLAs for response times. Response times are as follows: ; P1: 1 Hour Response ; P2: 2 Hour Response ; P3: 4 Hour Response ; P4: 2 Day Response ; ; Support for defect repair is available as a bolt on service. Support is provided directly via a team of dedicated DevOps Engineers. Technical support options come in various costs and benefits, depending on the needs of the customer.
• Support available to third parties: No

Onboarding and offboarding

• Getting started: Kerv Digital delivers a blended, role-based training approach tailored to each client's requirements, combining multiple delivery methods to ensure effective adoption. ; ; Training Delivery Methods ; We provide instructor-led training through both virtual and onsite sessions covering system fundamentals and role-specific processes. Our train-the-trainer programme equips nominated power users and superusers to support wider user communities independently. Hands-on learning includes practical build-with sessions and regular show-and-tell reviews during implementation, building familiarity before go-live. ; ; User Documentation and Resources ; Training materials are co-created with clients and include user guides, quick reference guides, FAQs, and detailed process documentation. Recorded training sessions provide on-demand access for flexible learning. Online knowledge content is hosted within the client's environment, typically SharePoint, alongside technical documentation for support and administrative teams. In-application contextual help guides users through processes directly within Dynamics 365. ; ; Ongoing Support ; Continuous knowledge transfer occurs throughout delivery via collaborative working and sprint reviews. Post-go-live support reinforces adoption and enables clients to sustain training for new starters and system changes. Refresher training scope and cadence are agreed per contract based on operational requirements. ; ; Training approaches are adapted for diverse user groups and learning styles, ensuring accessibility across the organisation.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • Other
• Other documentation formats:
  • Self-help resources, E-books, training videos and E-learning.
  • We personalise the user assistance by tailoring the in-product Help.
  • Learning Paths are also available to speed up onboarding.
• End-of-contract data extraction: To extract data, users would get in contact with Kerv upon completion of contract and we will work through this with them.
• End-of-contract process: No more than 180 days after expiration or termination of Customer’s use of an Online Service, Microsoft will disable the account and delete Customer Data from the account. Transfer of Customer Data. Unless Customer has opted out of the Standard Contractual Clauses, all transfers of Customer Data out of the European Union, European Economic Area, and Switzerland shall be governed by the Standard Contractual Clauses. Microsoft will abide by the requirements of European Economic Area and Swiss data protection law regarding the collection, use, transfer, retention, and other processing of personal data from the European Economic Area and Switzerland.
• Documentation accessibility standard: WCAG 2.2 AA

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
• Application to install: No
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: Service dependent.
• Service interface: Yes
• User support accessibility: WCAG 2.2 AA
• Description of service interface: Dynamics 365 Commerce provides multiple service interfaces for different interaction patterns. The Commerce Scale Unit exposes RESTful APIs enabling headless commerce scenarios, allowing external applications to access product catalogues, pricing, inventory, and order management functions. The e-commerce platform delivers responsive web storefronts with customisable rendering through the online SDK. Store Commerce application provides modern point-of-sale interfaces for Windows, iOS, and Android devices with offline capability. The back-office interface delivers browser-based administration for merchandising, promotions, and channel management. All interfaces implement OAuth 2.0 authentication and support OData v4 protocol for standardised data access and integration with external systems.
• Accessibility standards: WCAG 2.2 AA
• Accessibility testing: We have worked with users who have assistive technology needs as part of consultations and user research. ; ; Although we seek opportunities to do so at the right times, we have not had opportunity to engage users with assistive technology needs in formal accessibility test execution. However, our test team use assistive technology, such as screen readers, as part of the accessibility test execution which we carry out.
• API: Yes
• What users can and can't do using the API: Dynamics 365 Commerce provides comprehensive APIs through the Commerce Scale Unit, enabling headless commerce scenarios and seamless integration with external systems via RESTful endpoints secured with OAuth 2.0 authentication. ; ; Service Configuration via API ; Users can configure channels, product catalogues, pricing structures, and promotional rules programmatically through the Commerce runtime APIs. The Retail Server exposes Data Entities for bulk data management operations including product imports, customer synchronisation, and inventory updates. Channel configuration APIs enable programmatic setup of online stores, physical store hierarchies, and point-of-sale terminal registrations across the retail estate. ; ; Operational Changes via API ; The API supports complete transactional operations including cart management, checkout processing, order creation, and fulfilment workflows. Product information, pricing calculations, inventory availability, and customer data can be retrieved and modified in real-time. The e-commerce SDK provides client-side APIs for building custom storefront experiences with full access to commerce functionality. Webhooks enable event-driven integrations triggered by order status changes, inventory movements, and customer activities. ; ; Limitations ; Certain administrative functions, including environment provisioning and Commerce Scale Unit deployment, require access through Lifecycle Services rather than direct API calls. Payment processing requires certified payment connector integration. Real-time transaction APIs are subject to throttling limits to ensure platform stability during peak periods.
• API documentation: Yes
• API documentation formats: HTML
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: Dynamics 365 Commerce offers extensive customisation through multiple extensibility frameworks, enabling tailored retail experiences whilst preserving platform upgradeability and long-term supportability. ; ; Configuration Options ; Users can tailor the service through administrative interfaces without technical expertise. This includes configuring channel hierarchies, product attributes and categories, pricing and discount rules, loyalty programmes, and fulfilment options. Screen layouts for point-of-sale terminals can be customised using the visual designer. E-commerce storefronts support theme customisation, content management, and page layout modifications through the site builder tool without requiring developer involvement. ; ; Advanced Customisation ; For complex requirements, developers extend the platform using supported frameworks. The e-commerce SDK enables custom modules, data actions, and theme development using React and TypeScript. Commerce runtime extensions add custom business logic for pricing, promotions, and order processing. Point-of-sale extensibility allows custom operations, views, and hardware integrations. Back-office customisations use X++ extensions deployed through the standard Finance and Operations development lifecycle. Payment integrations require certified payment connectors meeting PCI compliance standards. ; ; Governance and Limitations ; All customisation must follow sealed extension patterns; direct modification of base application code is prohibited. Extension deployment requires validation through Lifecycle Services. Commerce Scale Unit customisation must maintain backward compatibility. Storefront customisation should follow accessibility guidelines.

Scaling

• Independence of resources: The service operates multiple scale groups in each data centre and automatically provisions new customers into a scale group. The architecture of scale groups is designed to meet the many needs of operating a service at scale, including security, scalability, performance, tenant isolation, serviceability and monitoring. Each customer has their own individual database, separate from other customers’ databases. Data processing is logically segregated through capabilities specifically developed to help build, manage and secure multi-tenant environments.

Analytics

• Service usage metrics: Yes
• Metrics types: This is service dependent and based on customer requirements.
• Reporting types: Real-time dashboards
• Resource tagging: Yes
• FOCUS resource tagging: Yes

Resellers

• Supplier type: Reseller providing extra features and support
• Organisation whose services are being resold: Microsoft

Staff security

• Staff security clearance: Conforms to BS7858:2019
• Government security clearance: Security Clearance (SC)

Asset protection

• Knowledge of data storage and processing locations: Yes
• Data storage and processing locations:
  • United Kingdom
  • European Economic Area (EEA)
  • Other locations
• User control over data storage and processing locations: Yes
• Datacentre security standards: Complies with a recognised standard (for example CSA CCM version 4.0)
• Penetration testing frequency: At least once a year
• Penetration testing approach: ‘IT Health Check’ performed by a CREST-approved service provider
• Protecting data at rest:
  • Physical access control, complying with CSA CCM v4.0
  • Physical access control, complying with SSAE-18 / ISAE 3402
  • Encryption of all physical media
  • Other
• Other data at rest protection approach: Microsoft ensures that data stored on its Azure Storage accounts is encrypted by default using AES-256 encryption. Additionally, customers can manage their encryption keys through Azure Key Vault to provide an additional layer of security.
• Data sanitisation process: Yes
• Equipment disposal approach: Complying with a recognised standard, for example CSA CCM v4.0, CAS (Sanitisation) or ISO/IEC 27001
• Data sanitisation type: Deleted data can’t be directly accessed / Cryptographic Erasure

Data importing and exporting

• Data export approach: To extract data, users would get in contact with Kerv upon completion of contract and we will work through this with them.
• Data export formats: CSV
• Data import formats: CSV

Data-in-transit protection

• Data protection between buyer and supplier networks:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Legacy SSL and TLS (under version 1.2)
  • Other
• Other protection between networks: Please see https://docs.microsoft.com/en-us/azure/security/azure-network-security .
• Data protection within supplier network:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
• Other protection within supplier network: Please see https://docs.microsoft.com/en-us/azure/best-practices-network-security

Availability and resilience

• Guaranteed availability: For SaaS and PaaS, we back-to-back SLAs to vendors and what they provide accordingly (MS, AWS etc) and we can offer a management wrapper to enable a single point of contact for our clients. ; ; For bespoke development/solutions we can provide a range of solutions and accompanying support offerings and SLAs up to the client's resilience needs and subject to their budget. ; ; We also provide a standard set of SLAs and availability figures in our support and CI contract.
• Approach to resilience: https://docs.microsoft.com/en-us/azure/architecture/resiliency/disaster-recovery-azure-applications
• Outage reporting: Via the service status portal, email, alerts or mobile application.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
• Access restrictions in management interfaces and support channels: Role based access control is used to restrict access, enforcing the principle of least privilege. For management interfaces, only authorised roles can configure systems, with granular permissions and audit trails ensuring compliance. For support channels, tiered roles restrict visibility and actions, preventing unauthorised access to sensitive data or functions.
• Access restriction testing frequency: At least once a year
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password

Audit information for users

• Access to user activity audit information: Users have access to real-time audit information
• How long user audit data is stored for: Between 1 month and 6 months
• Access to supplier activity audit information: Users contact the support team to get audit information
• How long supplier audit data is stored for: Between 1 month and 6 months
• How long system logs are stored for: Between 1 month and 6 months

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: Yes
• Security governance standards:
  • ISO/IEC 27001
  • Other
• Other security governance standards: ISO 9001:2015 ; Cyber Essentials & Cyber Essentials Plus accreditation.
• Information security policies and processes: Kerv ensures robust security, auditability and compliance across all operations with particular emphasis on AML, complaints handling, data protection, least-privilege access and controlled releases. Our approach is underpinned by certified frameworks, proactive governance and traceable artefacts. ; ; Kerv maintains an Information Security Management System certified to ISO9001, ISO 27001 and ISO27701 standards.; ; We can provide the following artefacts to support audit and compliance variation: ; - ISO 27001 / ISO 27701 / ISO 9001 certification reports ; - Internal audit reports and DPIAs ; - Role-based access control matrices and access logs ; - Security incident and breach management reports ; - Change control logs and release documentation ; - AI governance artefacts (e.g. Prompt Approval templates, Exception Review Procedures) ; - Supplier security policies and onboarding protocols.
• Software Security Code of Practice: Yes

Operational security

• Configuration and change management standard: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Configuration and change management approach: Our change control procedure considers: ; - The identification and documentation of planned change. ; - An assessment process of possible change impact. ; - Change testing in approved non-production environment. ; - Change management approval process. ; - Identification and recording significant changes. ; - Planning and testing changes. ; - Assessment of potential impacts, including security impacts, of such changes. ; - Formal approval procedure for proposed changes. ; - Communication of change details to relevant persons. ; - Fallback procedures, including procedures and responsibilities for aborting and recovering from unsuccessful changes and unforeseen events. ; - Validation and acceptance of each change by engineering teams.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: Kerv’s architectural approach removes the need for infrastructure vulnerability management through the exclusive use of platform-as-a-service and software-as-a-service products from Microsoft. A platform inventory will be created so any emerging risks or reported vulnerabilities for vendor services, e.g. Microsoft Power Platform, can be quickly identified and managed by Kerv and operational teams. ; ; Updating and patching systems - We develop and implement policies for regular updates and patch management. Our vulnerability management policy and process ensure all patches are prioritised based on the common vulnerability scoring system (CVSS) Version 3 or vendor priority e.g., Microsoft.
• Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Protective monitoring approach: See - https://docs.microsoft.com/en-us/azure/security/azure-threat-detection
• Incident management type: Complies with a recognised standard, for example, CSA CCM v4.0 or ISO/IEC 27035:2011 or SSAE-18 / ISAE 3402
• Incident management approach: Kerv has an Incident Management Procedure in place that defines how we record, define, mitigate and report incidents. Upon discovery of an incident, staff are required to follow this procedure, and customers and external parties are given contact details of how to report this. ; ; The Senior Management Team are responsible for this policy and its implementation. ; ; Incident reports are provided to customers and other stakeholders on a periodic basis to meet contractual requirements.
• Post-quantum cryptography secure: Yes

Secure development

• Approach to secure software development best practice: Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v4.0)

Public sector networks

• Connection to public sector networks: No

Pricing

• Discount for educational organisations: Yes
• Free trial available: No

Discount percentage by annual call-off contract value (excluding VAT)

• Less than £250,000: 2%
• Between £250,000 and £500,000: 4%
• Between £500,001 and £1,000,000: 5%
• Between £1,000,001 and £2,500,000: 6%
• Between £2,500,001 and £5,000,000: 7%
• Over £5,000,001: 7%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: NQA
• ISO/IEC 27001 accreditation date: Friday 4 October 2024
• What the ISO/IEC 27001 doesn’t cover: A 8.30 Outsources development
• ISO 28000:2022 certification: No
• ISO 9001 certification: Yes
• Who accredited the ISO 9001 certification: NQA
• ISO 9001 accreditation date: Friday 4 October 2024
• What the ISO 9001 doesn’t cover: N/A
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: Yes
• Please provide your Cyber Essentials Certificate Number: 2fbdbdf0-e870-4fbe-aa2d-7662ec986a6d
• Cyber essentials plus: Yes
• Please provide your Cyber Essentials Plus Certificate Number: 700337e5-63af-42f0-bb4c-577dcad1c30b
• Other security certifications: No

Social value

• Section B - Commitment for Future: Delivery:

  • Mission: Make Britain a clean energy superpower: To cut bills, create jobs and deliver security with cheaper, zero-carbon electricity by 2030, accelerating to net zero

    Policy Outcome 4: Sustainable procurement practices: Reducing carbon footprints, minimising waste, and promoting the use of clean energy and green technologies.

    • Delivery of additional environmental benefits through the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies

  • Mission: Break down barriers to opportunity: By reforming our childcare and education systems, to make sure there is no class ceiling on the ambitions of young people in Britain

    Policy Outcome 6: Employment and training: For those who face barriers to employment

    • Working conditions which promote an inclusive working environment and promote retention and progression

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at frameworks@kerv.com. Tell them what format you need. It will help if you say what assistive technology you use.